[spring] RFC 9020 on YANG Data Model for Segment Routing
rfc-editor@rfc-editor.org Thu, 27 May 2021 02:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 778873A02C1; Wed, 26 May 2021 19:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 hJAMZNQtcqU7; Wed, 26 May 2021 19:21:41 -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 1F7B33A02BB; Wed, 26 May 2021 19:21:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CC5DF4079F; Wed, 26 May 2021 19:21:28 -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, spring@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210527022128.4CC5DF4079F@rfc-editor.org>
Date: Wed, 26 May 2021 19:21:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/HDdlMDF5zr5GZJAAh2LMkIByTsQ>
Subject: [spring] RFC 9020 on YANG Data Model for Segment Routing
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2021 02:21:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9020
Title: YANG Data Model for Segment
Routing
Author: S. Litkowski,
Y. Qu,
A. Lindem,
P. Sarkar,
J. Tantsura
Status: Standards Track
Stream: IETF
Date: May 2021
Mailbox: slitkows.ietf@gmail.com,
yingzhen.qu@futurewei.com,
acee@cisco.com,
pushpasis.ietf@gmail.com,
jefftant.ietf@gmail.com
Pages: 39
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-spring-sr-yang-30.txt
URL: https://www.rfc-editor.org/info/rfc9020
DOI: 10.17487/RFC9020
This document defines three YANG data models. The first is for
Segment Routing (SR) configuration and operation, which is to be
augmented by different Segment Routing data planes. The next is a
YANG data model that defines a collection of generic types and
groupings for SR. The third module defines the configuration and
operational states for the Segment Routing MPLS data plane.
This document is a product of the Source Packet Routing in Networking 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