RFC 9403 on A YANG Data Model for RIB Extensions
rfc-editor@rfc-editor.org Tue, 21 November 2023 03:40 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D20AEC14CE40; Mon, 20 Nov 2023 19:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.26
X-Spam-Level:
X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gx_2EuiCPfLi; Mon, 20 Nov 2023 19:39:59 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0164C14CE3F; Mon, 20 Nov 2023 19:39:59 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 8EF6619D452A; Mon, 20 Nov 2023 19:39:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9403 on A YANG Data Model for RIB Extensions
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtgwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231121033959.8EF6619D452A@rfcpa.amsl.com>
Date: Mon, 20 Nov 2023 19:39:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/4FJ9_Sx30QvuiW2ROR21Zq1X1aQ>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Nov 2023 03:40:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9403
Title: A YANG Data Model for RIB Extensions
Author: A. Lindem,
Y. Qu
Status: Standards Track
Stream: IETF
Date: November 2023
Mailbox: acee.ietf@gmail.com,
yingzhen.qu@futurewei.com
Pages: 22
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtgwg-yang-rib-extend-24.txt
URL: https://www.rfc-editor.org/info/rfc9403
DOI: 10.17487/RFC9403
A Routing Information Base (RIB) is a list of routes and their
corresponding administrative data and operational state.
RFC 8349 defines the basic building blocks for the RIB data model,
and this model augments it to support multiple next hops (aka paths)
for each route as well as additional attributes.
This document is a product of the Routing Area Working Group Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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