This document describes a framework for traceability in the Interface
to the Routing System (I2RS) and information model for that
framework. It specifies the motivation, requirements, 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
Working Group Summary
Working consensus for requirements was honed over 6 months (May -Nov 2015).
WG LC done on individual draft 5/26/2015 to 6/9/2015
WG LC done with All of requirement drafts 10/6/2015 to 10/20/2015
This draft is comes out of the work with Open Daylight Project
and other implementations of early I2RS protocols.
A significant number of vendors have indicated their plan to
expand existing protocols to create an IRS amalgamate protocol.
A list includes the following: Cisco, Juniper, Huawei, Ericsson,
Google, Packetdesign (Client software) and others.
Reviews of the requirement package did not change the traceability draft.
The NETCONF reviewed the traceability document and found no additional
requirements for the NETCONF or RESTCONF suite.
The security directorate QA review found that traceability did not by itself
provide security's level of assurance or tracing. Traceability was targeted for logging
information that adds to data assurance or tracing.
Document shepherd: Susan Hares
WG Chairs: Susan Hares and Jeff Haas
AD: Alia Atlas