YANG Data Model for Segment Routing
draft-ietf-spring-sr-yang-15
Document Type Active Internet-Draft (spring WG)
Last updated 2020-01-09
Replaces draft-litkowski-spring-sr-yang
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Reviews
YANGDOCTORS Early Review (of -09): On the Right Track
Additional URLs
- Yang catalog entry for ietf-segment-routing-common@2020-01-09.yang
- Yang catalog entry for ietf-segment-routing-mpls@2020-01-09.yang
- Yang catalog entry for ietf-segment-routing@2020-01-09.yang
- Yang impact analysis for draft-ietf-spring-sr-yang
- Mailing list discussion
Stream WG state WG Document
Document shepherd Rob Shakir
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Rob Shakir <robjs@google.com>
Email authors Email WG IPR References Referenced by Nits 
SPRING Working Group                                        S. Litkowski
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                                   Y. Qu
Expires: July 12, 2020                                         Futurewei
                                                               A. Lindem
                                                           Cisco Systems
                                                               P. Sarkar
                                                              Individual
                                                             J. Tantsura
                                                                  Apstra
                                                         January 9, 2020

                  YANG Data Model for Segment Routing
                      draft-ietf-spring-sr-yang-15

Abstract

   This document defines a YANG data model ([RFC6020], [RFC7950]) for
   segment routing ([RFC8402]) configuration and operation.  This YANG
   model is intended to be used on network elements to configure or
   operate segment routing MPLS data plane [RFC8660].  This document
   defines also generic containers that SHOULD be reused by IGP protocol
   modules to support segment routing.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 12, 2020.

Copyright Notice

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

Litkowski, et al.         Expires July 12, 2020                 [Page 1]
Internet-Draft                 sr-yang-cfg                  January 2020

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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 provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology and Notation  . . . . . . . . . . . . . . . . . .   3
     2.1.  Tree diagram  . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   3
   3.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   3
   4.  Configuration . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IGP Control plane configuration . . . . . . . . . . . . . . .   6
     5.1.  IGP interface configuration . . . . . . . . . . . . . . .   7
       5.1.1.  Adjacency SID properties  . . . . . . . . . . . . . .   7
         5.1.1.1.  Bundling  . . . . . . . . . . . . . . . . . . . .   7
         5.1.1.2.  Protection  . . . . . . . . . . . . . . . . . . .   8
   6.  States  . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Notifications . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  26
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  27
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  27
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  27
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  27
     12.2.  Informative References . . . . . . . . . . . . . . . . .  29
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  29

1.  Introduction

   This document defines a YANG data model for segment routing
   configuration and operation.  This document does not define the IGP
   extensions to support segment routing but defines generic groupings
   that SHOULD be reused by IGP extension modules.  The reason of this
   design choice is to not require implementations to support all IGP
   extensions.  For example, an implementation may support IS-IS
   extension but not OSPF.

   The YANG modules in this document conform to the Network Management
   Datastore Architecture (NMDA) [RFC8342].
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools