YANG Data Model for Segment Routing
draft-ietf-spring-sr-yang-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (spring WG)
|
|
Last updated |
|
2015-07-20
|
|
Replaces |
|
draft-litkowski-spring-sr-yang
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
SPRING Working Group S. Litkowski
Internet-Draft Orange Business Service
Intended status: Standards Track Y. Qu
Expires: January 21, 2016 Cisco Systems
P. Sarkar
Juniper Networks
J. Tantsura
Ericsson
July 20, 2015
YANG Data Model for Segment Routing
draft-ietf-spring-sr-yang-00
Abstract
This document defines a YANG data model ([RFC6020]) for segment
routing ([I-D.ietf-spring-segment-routing]) configuration and
operation. This YANG model is intended to be used on network
elements to configure or operate segment routing. This document
defines also generic containers that SHOULD be reused by IGP protocol
modules to support segment routing.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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 http://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 January 21, 2016.
Litkowski, et al. Expires January 21, 2016 [Page 1]
Internet-Draft sr-yang-cfg July 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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
1.1. Tree diagram . . . . . . . . . . . . . . . . . . . . . . 3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IGP Control plane configuration . . . . . . . . . . . . . . . 6
4.1. IGP interface configuration . . . . . . . . . . . . . . . 6
4.1.1. Adjacency SID properties . . . . . . . . . . . . . . 6
4.1.1.1. Bundling . . . . . . . . . . . . . . . . . . . . 6
4.1.1.2. Protection . . . . . . . . . . . . . . . . . . . 7
5. States . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 7
7. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 20
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
11. Normative References . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
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.
Litkowski, et al. Expires January 21, 2016 [Page 2]
Internet-Draft sr-yang-cfg July 2015
1.1. Tree diagram
A simplified graphical representation of the data model is presented
in Section 2.
The meaning of the symbols in these diagrams is as follows:
Show full document text