RFC 7922: Interface to the Routing System (I2RS) Traceability: Framework and Information Model
In plain English — editorial summary, not part of the RFC
This document describes a framework for traceability in the Interface to the Routing System (I2RS) and the information model for that framework. It specifies the motivation, requirements, and use cases, and defines an information model for recording interactions between elements implementing the I2RS protocol. This framework provides a consistent tracing interface for components implementing the I2RS architecture to record what was done, by which component, and when. It aims to improve the management of I2RS implementations, and can be used for troubleshooting, auditing, forensics, and accounting purposes.
Document record
- Document ID
- RFC7922
- Published
- June 2016
- Authors
- J. Clarke; G. Salgueiro; C. Pignataro
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7923Requirements for Subscription to YANG DatastoresCurrent
June 2016
- RFC 7921An Architecture for the Interface to the Routing SystemCurrent
June 2016
- RFC 7920Problem Statement for the Interface to the Routing SystemCurrent
June 2016
- RFC 7926Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered NetworksCurrent
July 2016
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
- RFC 7909Securing Routing Policy Specification Language (RPSL) Objects with Resource Public Key Infrastructure (RPKI) SignaturesCurrent
June 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?