IS-IS is an interior gateway protocol, designed for use within an administrative domain or network.
| FactSnippet No. 1,567,907 | 
IS-IS is an interior gateway protocol, designed for use within an administrative domain or network.
| FactSnippet No. 1,567,907 | 
IS-IS is a link-state routing protocol, operating by reliably flooding link state information throughout a network of routers.
| FactSnippet No. 1,567,908 | 
IS-IS protocol was developed by a team of people working at Digital Equipment Corporation as part of DECnet Phase V It was standardized by the ISO in 1992 as ISO 10589 for communication between network devices that are termed Intermediate Systems by the ISO.
| FactSnippet No. 1,567,909 | 
The purpose of IS-IS was to make possible the routing of datagrams using the ISO-developed OSI protocol stack called CLNS.
| FactSnippet No. 1,567,910 | 
IS-IS was developed at roughly the same time that the Internet Engineering Task Force IETF was developing a similar protocol called OSPF.
| FactSnippet No. 1,567,911 | 
IS-IS is an OSI Layer 3 protocol initially defined for routing CLNS.
| FactSnippet No. 1,567,913 | 
However, IS-IS is easier to expand: its use of TLV data allows engineers to implement support for new techniques without redesigning the protocol.
| FactSnippet No. 1,567,914 | 
For example, in order to support IPv6, the IS-IS protocol was extended to support a few additional TLVs, whereas OSPF required a new protocol draft.
| FactSnippet No. 1,567,915 | 
IS-IS is therefore augmented with a small number of TLVs and sub-TLVs, and supports two Ethernet encapsulating data paths, 802.
| FactSnippet No. 1,567,916 |