RFC 8196: IS-IS Autoconfiguration
In plain English — editorial summary, not part of the RFC
This document specifies IS-IS autoconfiguration mechanisms. The key components are IS-IS System ID self-generation, duplication detection, and duplication resolution. These mechanisms provide limited IS-IS functions and are therefore suitable for networks where plug-and-play configuration is expected.
Document record
- Document ID
- RFC8196
- Published
- July 2017
- Authors
- B. Liu; L. Ginsberg; B. Decraene; I. Farrer; M. Abrahamsson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8202IS-IS Multi-InstanceCurrent
June 2017
- RFC 8203BGP Administrative Shutdown CommunicationObsoleted
July 2017
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 8206BGPsec Considerations for Autonomous System (AS) MigrationCurrent
September 2017
- RFC 8185Dual-Homing Coordination for MPLS Transport Profile (MPLS-TP) Pseudowires ProtectionCurrent
June 2017
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8184Dual-Homing Protection for MPLS and the MPLS Transport Profile (MPLS-TP) PseudowiresCurrent
June 2017
- RFC 8208BGPsec Algorithms, Key Formats, and Signature FormatsObsoleted
September 2017
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?