[i2rs] RFC 7922 on Interface to the Routing System (I2RS) Traceability: Framework and Information Model

rfc-editor@rfc-editor.org Thu, 30 June 2016 17:45 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 19CCE12DB05; Thu, 30 Jun 2016 10:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3MfYU9EpIu9W; Thu, 30 Jun 2016 10:45:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3B2612D110; Thu, 30 Jun 2016 10:44:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DECA4B80B9C; Thu, 30 Jun 2016 10:44:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160630174458.DECA4B80B9C@rfc-editor.org>
Date: Thu, 30 Jun 2016 10:44:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/PuswYC5UYYauDo-tXlzZIz-7l5s>
Cc: i2rs@ietf.org, rfc-editor@rfc-editor.org
Subject: [i2rs] RFC 7922 on Interface to the Routing System (I2RS) Traceability: Framework and Information Model
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 17:45:14 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7922

        Title:      Interface to the Routing System (I2RS)
                    Traceability: Framework and Information Model 
        Author:     J. Clarke, G. Salgueiro, C. Pignataro
        Status:     Informational
        Stream:     IETF
        Date:       June 2016
        Mailbox:    jclarke@cisco.com, 
        Pages:      17
        Characters: 36070
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-i2rs-traceability-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7922

        DOI:        http://dx.doi.org/10.17487/RFC7922

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

This document is a product of the Interface to the Routing System Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC