RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments
In plain English — editorial summary, not part of the RFC
This memo specifies an integrated routing protocol, based on the OSI Intra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering Task Force. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1195
- Published
- December 1990
- Authors
- R. Callon
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 85
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3359Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate SystemCurrent
August 2002
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 5120M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)Current
February 2008
- RFC 5310IS-IS Generic Cryptographic AuthenticationUpdated
February 2009
- RFC 6326Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISObsoleted
July 2011
- RFC 6571Loop-Free Alternate (LFA) Applicability in Service Provider (SP) NetworksCurrent
June 2012
- RFC 7180Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesObsoleted
May 2014
- RFC 7780Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and UpdatesUpdated
February 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?