IS-IS

This article is about a computer network protocol. For topics with similar names, see Isis (disambiguation).

Internet history timeline

Early research and development: 1960–1962: J. C. R. Licklider networking ideas 1960–1964: RAND networking concepts developed 1962–1964: ARPA networking ideas 1965 (1965): NPL network concepts conceived 1966 (1966): Merit Network founded 1967 (1967): ARPANET planning begins 1967 (1967): Symposium on Operating Systems Principles 1969 (1969): NPL followed by the ARPANET carry their first packets 1970 (1970): Network Information Center (NIC) 1971 (1971): Tymnet switched-circuit network 1972 (1972): Merit Network's packet-switched network operational 1972 (1972): Internet Assigned Numbers Authority (IANA) established 1973 (1973): CYCLADES network demonstrated 1973 (1973): PARC Universal Packet development begins 1974 (1974): Transmission Control Program specification published 1975 (1975): Telenet commercial packet-switched network 1976 (1976): X.25 protocol approved and deployed on public data networks 1978 (1978): Minitel introduced 1979 (1979): Internet Activities Board (IAB) 1980 (1980): USENET news using UUCP 1980 (1980): Ethernet standard introduced 1981 (1981): BITNET established Merging the networks and creating the Internet: 1981 (1981): Computer Science Network (CSNET) 1982 (1982): TCP/IP protocol suite formalized 1982 (1982): Simple Mail Transfer Protocol (SMTP) 1983 (1983): Domain Name System (DNS) 1983 (1983): MILNET split off from ARPANET 1984 (1984): OSI Reference Model released 1985 (1985): First .COM domain name registered 1986 (1986): NSFNET with 56 kbit/s links 1986 (1986): Internet Engineering Task Force (IETF) 1987 (1987): UUNET founded 1988 (1988): NSFNET upgraded to 1.5 Mbit/s (T1) 1988 (1988): Morris worm 1988 (1988): Complete Internet protocol suite 1989 (1989): Border Gateway Protocol (BGP) 1989 (1989): PSINet founded, allows commercial traffic 1989 (1989): Federal Internet Exchanges (FIX East|FIXes) 1990 (1990): GOSIP (without TCP/IP) 1990 (1990): ARPANET decommissioned 1990 (1990): Advanced Network and Services (ANS) 1990 (1990): UUNET/Alternet allows commercial traffic 1990 (1990): Archie search engine 1991 (1991): Wide area information server (WAIS) 1991 (1991): Gopher 1991 (1991): Commercial Internet eXchange (CIX) 1991 (1991): ANS CO+RE allows commercial traffic 1991 (1991): World Wide Web (WWW) 1992 (1992): NSFNET upgraded to 45 Mbit/s (T3) 1992 (1992): Internet Society (ISOC) established 1993 (1993): Classless Inter-Domain Routing (CIDR) 1993 (1993): InterNIC established 1993 (1993): AOL added USENET access 1993 (1993): Mosaic web browser released 1994 (1994): Full text web search engines 1994 (1994): North American Network Operators' Group (NANOG) established Commercialization, privatization, broader access leads to the modern Internet: 1995 (1995): New Internet architecture with commercial ISPs connected at NAPs 1995 (1995): NSFNET decommissioned 1995 (1995): GOSIP updated to allow TCP/IP 1995 (1995): very high-speed Backbone Network Service (vBNS) 1995 (1995): IPv6 proposed 1996 (1996): AOL changes pricing model from hourly to monthly 1998 (1998): Internet Corporation for Assigned Names and Numbers (ICANN) 1999 (1999): IEEE 802.11b wireless networking 1999 (1999): Internet2/Abilene Network 1999 (1999): vBNS+ allows broader access 2000 (2000): Dot-com bubble bursts 2001 (2001): New top-level domain names activated 2001 (2001): Code Red I, Code Red II, and Nimda worms 2003 (2003): UN World Summit on the Information Society (WSIS) phase I 2003 (2003): National LambdaRail founded 2004 (2004): UN Working Group on Internet Governance (WGIG) 2005 (2005): UN WSIS phase II 2006 (2006): First meeting of the Internet Governance Forum 2010 (2010): First internationalized country code top-level domains registered 2012 (2012): ICANN begins accepting applications for new generic top-level domain names 2013 (2013): Montevideo Statement on the Future of Internet Cooperation 2014 (2014): NetMundial international Internet governance proposal 2016 (2016): ICANN contract with U.S. Dept. of Commerce ends, IANA oversight passes to the global Internet community on October 1st Examples of Internet services: 1989 (1989): AOL dial-up service provider, email, instant messaging, and web browser 1990 (1990): IMDb Internet movie database 1994 (1994): Yahoo! web directory 1995 (1995): Amazon online retailer 1995 (1995): eBay online auction and shopping 1995 (1995): Craigslist classified advertisements 1995 (1995): AltaVista search engine 1996 (1996): Outlook (formerly Hotmail) free web-based e-mail 1996 (1996): RankDex search engine 1997 (1997): Google Search 1997 (1997): Babel Fish automatic translation 1998 (1998): Yahoo Groups (formerly Yahoo! Clubs) 1998 (1998): PayPal Internet payment system 1998 (1998): Rotten Tomatoes review aggregator 1999 (1999): 2ch Anonymous textboard 1999 (1999): i-mode mobile internet service 1999 (1999): Napster peer-to-peer file sharing 2000 (2000): Baidu search engine 2001 (2001): 2chan Anonymous imageboard 2001 (2001): BitTorrent peer-to-peer file sharing 2001 (2001): Wikipedia, the free encyclopedia 2003 (2003): LinkedIn business networking 2003 (2003): Myspace social networking site 2003 (2003): Skype Internet voice calls 2003 (2003): iTunes Store 2003 (2003): 4chan Anonymous imageboard 2003 (2003): The Pirate Bay, torrent file host 2004 (2004): Facebook social networking site 2004 (2004): Podcast media file series 2004 (2004): Flickr image hosting 2005 (2005): YouTube video sharing 2005 (2005): Reddit link voting 2005 (2005): Google Earth virtual globe 2006 (2006): Twitter microblogging 2007 (2007): WikiLeaks anonymous news and information leaks 2007 (2007): Google Street View 2007 (2007): Kindle, e-reader and virtual bookshop 2008 (2008): Amazon Elastic Compute Cloud (EC2) 2008 (2008): Dropbox cloud-based file hosting 2008 (2008): Encyclopedia of Life, a collaborative encyclopedia intended to document all living species 2008 (2008): Spotify, a DRM-based music streaming service 2009 (2009): Bing search engine 2009 (2009): Google Docs, Web-based word processor, spreadsheet, presentation, form, and data storage service 2009 (2009): Kickstarter, a threshold pledge system 2009 (2009): Bitcoin, a digital currency 2010 (2010): Instagram, photo sharing and social networking 2011 (2011): Google+, social networking 2011 (2011): Snapchat, photo sharing 2012 (2012): Coursera, massive open online courses 2016 (2016): TikTok, video sharing and social networking

Intermediate System to Intermediate System (IS-IS, also written ISIS) is a routing protocol designed to move information efficiently within a computer network, a group of physically connected computers or similar devices. It accomplishes this by determining the best route for data through a packet switching network.

The IS-IS protocol is defined in ISO/IEC 10589:2002 as an international standard within the Open Systems Interconnection (OSI) reference design.

In 2005, IS-IS was called "the de facto standard for large service provider network backbones".

Description

IS-IS is an interior gateway protocol, designed for use within an administrative domain or network. This is in contrast to exterior gateway protocols, primarily Border Gateway Protocol (BGP), which is used for routing between autonomous systems.

IS-IS is a link-state routing protocol, operating by flooding link state information throughout a network of routers. Each IS-IS router independently builds a database of the network's topology, aggregating the flooded network information. Like the OSPF protocol, IS-IS uses Dijkstra's algorithm for computing the best path through the network. Packets (datagrams) are then forwarded, based on the computed ideal path, through the network to the destination.

History

The IS-IS protocol was developed by a team of people working at Digital Equipment Corporation as part of DECnet Phase V.

The Internet Engineering Task Force (IETF) published IS-IS in 1990, but that RFC was later retracted and marked as historic because it republished a draft rather than a final version of the International Organization for Standardization (ISO) standard, causing confusion.

The protocol was standardized by ISO in 1992 as ISO 10589, for communication between network devices that are termed Intermediate Systems (as opposed to end systems or hosts) by the ISO. The purpose of IS-IS was to make the routing of datagrams possible using the ISO-developed OSI protocol stack called Connectionless-mode Network Service (CLNS). IS-IS was developed at roughly the same time that the Internet Engineering Task Force IETF was developing a similar protocol called OSPF. IS-IS was later extended to support routing of datagrams in the Internet Protocol (IP), the network-layer protocol of the global Internet. This version of the IS-IS routing protocol was then called Integrated IS-IS.

IS-IS terminology

The ISO for IS-IS standard uses specific jargon to refer to components of the network, some of which differ, or is less common, in typical industry language.

• Intermediate System - Router
• Designated Intermediate System - An IS selected to represent a group of ISs on a shared circuit.
• End System (ES) - any host or device that does not participate in routing.
• Circuit - Layer 2 broadcast domain. This can be a single point-to-point connection, or a LAN.
• Adjacency - A neighboring IS that an IS exchanges routing information with.

Packet types

IS-IS adjacency can be either broadcast or point-to-point.

IS-IS Hello PDU (IIH)

An IS-IS hello packet needs to be exchanged periodically between 2 routers to establish adjacency. Based on the negotiation, one of them will be selected as the DIS (Designated IS). This hello packet will be sent separately for Level-1 or Level-2. There are 3 IS-IS hello packets depending on the circuit type -

• LAN L1 (PDU type 15)
• LAN L2 (PDU type 16)
• P2P (PDU type 17). On point-to-point links, there are no separate hello packets per level like there are on broadcast links. Unlike OSPF, IS-IS hello interval timers do not need to match.

Link State PDU (LSP)

This contains the actual routing information. The LSP contains a number of fields called type–length–values (TLVs), which contain the routing data.: The LSP header is called LSP ID and consists of a System ID, Pseudonode ID and Fragment ID. :: In this example LSP with ID 1921.6820.0002.02-01,

• 1921.6820.0002 is the System ID (that generated this LSP),
• 02 is the Pseudonode ID,
• 01 is the Fragment ID.

If the Pseudonode ID is equal to zero, then it represents a real intermediate system. Any non-zero value means that the LSP is generated by a DIS (Pseudonode).

If the LSP is too big to fit inside an ethernet frame, then it gets fragmented. To indicate fragmentation, a Fragment ID is used. If the Fragment ID is equal to zero, then no fragmentation has occurred.

Complete Sequence Number PDU (CSNP)

This packet will be sent only by the DIS. By default, every 10 seconds, a CSNP packet will be transmitted by the DIS. The CSNP contains the list of LSP IDs along with sequence number and checksum.

Partial Sequence Number PDU (PSNP)

If the router which receives a CSNP packet finds a discrepancy in its own database, it will send an PSNP request asking the DIS to send a specific LSP back to it.

IS-IS addressing and NET

Unlike other routing protocols, IS-IS does not principally operate at Layer 3, and does not use IP addresses to identify each interface on an Intermediate System.

Instead, IS-IS uses an ISO Network Address. Each unique connection point in the autonomous system, such as a port on a router, is assigned a ISO Network Address called a Network Service Access Point (NSAP).

Individual ISs are assigned an ISO Network Address called a Network Entity Title (NET). The NET is similar to the NSAP, but does not have its Selector field set.

While this is not an IP address, and serves a different purpose, it is recommended practice to set the System ID field equal to a unique IPv4 address assigned to one of the router's loopback interfaces.

On a single intermediate system there can be up to 3 NET addresses. This may be useful during migration of an IS from one area to another.

The NET consists of an Area, System ID and NSEL field.Area itself consists of an AFI (Address Family Identifier) and an Area ID.

Area can have a variable length of 1 - 13 bytes. The System ID is 6 bytes long and the NSEL is 1 byte.

As an example, the fields of the ISO Network Address "49.0100.1921.6821.1138.00" are as follows:

• 49 is the AFI. 49 specifically represents the "private address space", similar to RFC1918 for IPv4.,
• 0100 is the Area ID,
• 49.0100 is the Area,
• 1921.6821.1138 is the System ID,
• 00 is the NSEL, which must be zero. Routers will not form adjacencies with routers with a non-zero NSEL in their NET, as that field is only used by the NSAP.

Hostname resolution

When administrating large networks, using IP addresses directly is often difficult and inconvenient.

Network engineers generally prefer to use domain names like "if-bundle-22-2.qcore1.pye-paris.as6453.net" to identify routers, as they contain more relevant and human-readable information.

Other routing protocols which principally identify routers using IP addresses can easily solve this problem using local DNS resolution.

Because IS-IS is not an IP-based protocol, it has hostname resolution built into the standard. Link-state PDUs can carry a Type Length Value 137 (TLV 137) field, which contains a hostname associated with a NET.

Areas and levels

Similar to OSPF, IS-IS employs the concept of areas to divide the network, reducing the overall burden on routers in the network, by only requiring them to have complete link-state information for their area.

In IS-IS, ISs operate at either Level 1, Level 2 or Level 1/Level 2.

• Level 1 routers are internal to an area, and only maintain a Link State Database (LSDB) for that area.
• Level 2 routers form the backbone of an IS-IS network, and route traffic between areas. They maintain a separate Layer 2 LSDB for inter-area routing. Layer 2 routers must be contiguous, meaning the network of Layer 2 routers must be fully internally routable without crossing into different areas.
• Level 1/Level 2 routers are on the boundaries between L1 and L2 routers, and participate in both intra-area and inter-area routing, maintaining separate L1 and L2 LSDBs.

When an L1 router needs to send traffic to a destination not within its area, it directs it to an L1/L2 router.

L1/L2 routers advertise their status as boundary routers by setting the Attached Bit (ATT), in its L1 LSP. Routers that receive this LSP will add a default route to the origin of the LSP.

External routes can be redistributed to L1 areas, including their L1/L2 routers. However, by default, external routes will not be redistributed to L2 routers. To change this policy, L1/L2 routers must be configured to originate these external routes to the L2 network.

Attribute bits in LSPs

IS-IS LSPs contain information about the LSP itself in the attribute block of the LSP header, which is 8 bits long.

• P bit - Partition repair bit, 8^th bit, indicates if a partitioned L1 area can be repaired (joined together) over L2 area. Modern deployments of IS-IS generally do not support partition repair, and will not set the P bit.
• ATT bit - Attached bit, 7^th - 4^th bits, indicates if the originating router is attached to another area.
  • If these bits are set by the L1/L2 router in its L1 LSP, other routers in the L1 area will automatically generate a default route to the originator.
  • There are 4 ATT bits which represent the Error, Expense, Delay and Default metrics respectively.
  • Typically, only the 4^th (default) ATT bit is used, as typical IS-IS networks only use the Default (Cost) metric.
• OL bit - Overload bit, 3^rd bit, indicates if the router is overloaded.
  • If this bit is set, then this router will not be forwarded traffic. However, it will be still reachable.
  • The overload bit can be set automatically by a router under heavy load or intentionally by an administrator.
  • Setting the overload bit is an easy way to gracefully offload the router prior to maintenance which requires the router to reboot. After the router reboots and is available, then the overload bit can be cleared manually.
  • The overload bit may also be set while a router waits for other dependent protocols (such as BGP) to establish neighborship, before allowing traffic to be routed to itself. This may be desirable because IS-IS converges much faster than some dependent protocols, and a router that becomes available before another dependent routing protocol converges, the router could become a traffic black hole.
  • An example of this behavior is a provider edge router running an MPLS VPN with IS-IS and BGP. After the router boots, it establishes IS-IS adjacency before it finishes establishing BGP neighborship with other routers. When BGP is finished establishing neighborship, the overload bit is cleared and this router joins the MPLS VPN.
• IS type bits - 2^nd and 1^st bits, indicate the IS type of the originator. It can either be L1 only, L2 only, or L1/L2.
  • 01 - L1
  • 10 - L2
  • 11 - L1/L2

Wide metrics

When IS-IS was initially introduced, TLVs for IS reachability (TLV 2) and IP reachability (TLVs 128 and 130) could have an interface metric of no more than 63 (6 bits) and total accumulated path metric of no more than 1023 (10 bits).

Over time, networks outgrew the constraints imposed by these metrics as speeds and hop-counts increased with better hardware.

To allow for these larger networks 2 new TLVs — TLV 22 for Extended IS reachability and TLV 135 for Extended IP reachability — were introduced.

These additions to the protocol allowed link metrics up to 16.7 million (24 bits) and total accumulated path metric up to 4 billion (32 bits).

Metrics without TLV 22 and 135 are called narrow metrics, and metrics that include them are called wide metrics.

Wide metrics or narrow metrics can be set on a per-level basis.

Adjacency formation

Compared to OSPF, IS-IS rules of adjacency formation are much simpler and depend primarily on the router level.

• A L1 router cannot form any adjacency with L2 router.
• A L1 router can form a L1 adjacency with other L1 router in the same area.
• A L1 router can form a L1 adjacency with L1/L2 router in the same area
• A L2 router can form a L2 adjacency with other L2 routers regardless of their areas.
• A L2 router can form a L2 adjacency with an L1/L2 router regardless of their areas.
• L1/L2 router can form both an L2 and L1 adjacency with other L1/L2 routers if their areas match.

Broadcast segments and designated intermediate system

Similar to OSFP, all routers in a broadcast domain need to form adjacencies and exchange LSPs, resulting in there being $n^{2}$ LSPs for each router in the domain.

In order to overcome this issue, on each LAN segment a designated intermediate system (DIS) is elected. The router with the highest priority and System ID is elected as the DIS, but if another router is connected with a higher priority (or higher System ID if the priorities are equal), will be elected as the new DIS.

Instead of each router forming an adjacency with every other router in the broadcast domain, each router forms an adjacency with just the DIS, and the DIS becomes responsible for relaying LSPs to the subordinate routers, in a hub-and-spoke topology.

An elected DIS router is a pseudonode, which uses the resources (including System ID) of one real router.

The Pseudonode ID in LSPs originated by a DIS, always have a non-zero Pseudonode ID field.

The DIS will send periodic CSNPs on the LAN segment and reply to PSNPs from other routers.

If the DIS stops communicating, a new DIS will be elected in the segment.

Authentication

IS-IS supports both simple password and MD5 authentication types. In IS-IS, per-level or per-interface authentication is possible.

In addition, to protect from a replay attack, IS-IS uses an increasing sequence number in the IIH.

IPv6 support and multi-topology

Unlike OSPF, which operates at Layer 3, IS-IS encapsulates its PDUs into Layer 2 frames, and does not depend on Layer 3 protocols, such as IPv4 or IPv6.

In order to support IPv6 routing information TLV 232 for IPv6 interface address and TLV 236 for IPv6 reachability were added.

In order to display supported Layer 3 protocols, also called NLPID (Network Layer Protocol ID), TLV 129 is used. Here, IPv4 has code of 0xCC, while IPv6 has a code of 0x8E.

There might be an issue, if the IPv4 and IPv6 topologies do not overlap. This could happen due to misconfiguration or lack of support for IPv6 by routers in the network. For this situations, multi-topology support is added to IS-IS.

TLV 229 was added to indicate support for multi-topologies, such as IPv4 unicast and IPv6 unicast.

If multi-topology is enabled, IS-IS will calculate separate SPF tree for IPv4 and IPv6. This means twice the resource usage, but from the other side, this prevents traffic black holes.

When multi-topology is enabled, then IS-IS will use TLV 222 for Multi-topology IS reachability, TLV 235 for Multi-topology IP reachability and TLV 236 for Multi-topology IPv6 reachability.

IS-IS path selection

Depending on the configuration, the router can have either L1, L2 or both L1/L2 Link-State Databases. IS-IS uses Dijkstra's algorithm to generate the routing tables from these databases.

But there can be situations, when IS-IS router has exactly the same prefix in different level databases, or external and internal. In order to choose best path in this situations, there is a specific order in which the route goes from the most preferred to the least preferred:

• L1 intra-area with internal metric,
• L1 external with internal metric,
• L2 intra-area with internal metric,
• L2 external with internal metric,
• Inter-area (from L1 to L2) with internal metric,
• Inter-area external (from L1 to L2) with internal metric,
• Inter-area (from L2 to L1) with internal metric,
• Inter-area external (from L2 to L1) with internal metric,
• L1 external with external metric,
• L2 external with external metric,
• Inter-area external (from L1 to L2) with external metric,
• Inter-area external (from L2 to L1) with external metric.

BFD support

IS-IS has Hello packets (IIH) which carry information about the router and are used to form adjacencies. Another function of hello packets is to detect a fault between adjacent routers.

Hello packet transmission intervals can be lowered in order to detect faults faster, but this will necessarily create more load on the routers.

Instead of this, BFD can be used. BFD is a low-overhead fault detection protocol that places little demand on the CPU, and can provide sub-second fault detection.

Other uses

IS-IS is the base for the control plane in Shortest Path Bridging (SPB). SPB enables equal-cost multipath routing among Ethernet switches in a mesh topology: Ethernet frames are forwarded along multiple load-balanced, service-specific paths, which are all equally the shortest. To support this, SPB extends IS-IS with new TLVs.

Related protocols

• Fabric Shortest Path First (FSPF)
• Transparent Interconnection of Lots of Links (TRILL)

External links

• IS-IS standard (ISO/IEC 10589:2002, Second Edition) – free-of-charge PDF version
• OSPF and IS-IS: A Comparative Anatomy by Dave Katz, Juniper
• Collection of RFCs pertaining to IS-IS Archived 2013-06-02 at the Wayback Machine
• IS-IS and OSPF difference discussion (Vishwas Manral, Manav Bhatia and Yasuhiro Ohara)
• Google Quagga IS-IS implementation
• Sample isisd.conf file: used with Quagga
• IS-IS route preference for Extended IP and IPv6 Reachability