RFC 8242: Interface to the Routing System (I2RS) Ephemeral State Requirements
In plain English — editorial summary, not part of the RFC
"An Architecture for the Interface to the Routing System" (RFC 7921) abstractly describes a number of requirements for ephemeral state (in terms of capabilities and behaviors) that any protocol suite attempting to meet the needs of the Interface to the Routing System (I2RS) protocol has to provide. This document describes, in detail, requirements for ephemeral state for those implementing the I2RS protocol.
Document record
- Document ID
- RFC8242
- Published
- September 2017
- Authors
- J. Haas; S. Hares
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8243Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)Current
September 2017
- RFC 8241Interface to the Routing System (I2RS) Security-Related RequirementsCurrent
September 2017
- RFC 8245Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444Current
October 2017
- RFC 8237MPLS Label Switched Path (LSP) Pseudowire (PW) Status Refresh Reduction for Static PWsCurrent
October 2017
- RFC 8249Transparent Interconnection of Lots of Links (TRILL): MTU NegotiationCurrent
September 2017
- RFC 8234Updates to MPLS Transport Profile (MPLS-TP) Linear Protection in Automatic Protection Switching (APS) ModeCurrent
August 2017
- RFC 8233Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)Updated
September 2017
- RFC 8232Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCECurrent
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?