Browse Prior Art Database

Interface to the Routing System (I2RS) Traceability: Framework and Information Model (RFC7922)

IP.com Disclosure Number: IPCOM000246798D
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jul-01
Document File: 34 page(s) / 36K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Clarke: AUTHOR [+3]

Abstract

The architecture for the Interface to the Routing System [RFC7921] specifies that I2RS clients wishing to retrieve or change the routing state on a routing element MUST authenticate to an I2RS agent. The I2RS client will have a unique identity it provides for authentication, and should provide another opaque identity for applications communicating through it. The programming of routing state will produce a return code containing the results of the specified operation and associated reason(s) for the result. All of this is critical information to be used for understanding the history of I2RS interactions.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Internet Engineering Task Force (IETF)                         J. Clarke Request for Comments: 7922                                  G. Salgueiro Category: Informational                                     C. Pignataro ISSN: 2070-1721                                                    Cisco                                                                June 2016

                  Interface to the Routing System (I2RS)              Traceability: Framework and Information Model

Abstract

   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7922.

Clarke, et al.                Informational                     [Page 1]
 RFC 7922                    I2RS Traceability                  June 2016

 Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are prov...