[i2rs] RFC 8430 on RIB Information Model

rfc-editor@rfc-editor.org Wed, 26 September 2018 16:51 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6B2130EF3; Wed, 26 Sep 2018 09:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkjnhxlKoHwZ; Wed, 26 Sep 2018 09:51:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98D5312958B; Wed, 26 Sep 2018 09:51:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EFB6DB8119C; Wed, 26 Sep 2018 09:51:50 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, i2rs@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180926165150.EFB6DB8119C@rfc-editor.org>
Date: Wed, 26 Sep 2018 09:51:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/F3LqXRi1EH7WRYTLZ6rcMOeBPoI>
Subject: [i2rs] RFC 8430 on RIB Information Model
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 16:51:55 -0000

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

        
        RFC 8430

        Title:      RIB Information Model 
        Author:     N. Bahadur, Ed.,
                    S. Kini, Ed.,
                    J. Medved
        Status:     Informational
        Stream:     IETF
        Date:       September 2018
        Mailbox:    nitin_bahadur@yahoo.com, 
                    sriganeshkini@gmail.com, 
                    jmedved@cisco.com
        Pages:      28
        Characters: 60982
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-i2rs-rib-info-model-17.txt

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

        DOI:        10.17487/RFC8430

Routing and routing functions in enterprise and carrier networks are
typically performed by network devices (routers and switches) using a
Routing Information Base (RIB).  Protocols and configurations push
data into the RIB, and the RIB manager installs state into the
hardware for packet forwarding.  This document specifies an
information model for the RIB to enable defining a standardized data
model.  The IETF's I2RS WG used this document to design the I2RS RIB
data model.  This document is being published to record the higher-
level information model decisions for RIBs so that other developers
of RIBs may benefit from the design concepts.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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