draft-ietf-mpls-static-yang-06.txt   draft-ietf-mpls-static-yang-07.txt 
MPLS Working Group T. Saad MPLS Working Group T. Saad
Internet-Draft K. Raza Internet-Draft K. Raza
Intended status: Standards Track R. Gandhi Intended status: Standards Track R. Gandhi
Expires: April 13, 2019 Cisco Systems, Inc. Expires: May 8, 2019 Cisco Systems, Inc.
X. Liu X. Liu
Volta Networks Volta Networks
V. Beeram V. Beeram
Juniper Networks Juniper Networks
H. Shah H. Shah
Ciena Ciena
I. Bryskin I. Bryskin
Huawei Technologies Huawei Technologies
October 10, 2018 November 04, 2018
A YANG Data Model for MPLS Static LSPs A YANG Data Model for MPLS Static LSPs
draft-ietf-mpls-static-yang-06 draft-ietf-mpls-static-yang-07
Abstract Abstract
This document contains the specification for the MPLS Static Label This document contains the specification for the MPLS Static Label
Switched Paths (LSPs) YANG model. The model allows for the Switched Paths (LSPs) YANG model. The model allows for the
provisioning of static LSP(s) on LER(s) and LSR(s) devices along a provisioning of static LSP(s) on LER(s) and LSR(s) devices along a
LSP path without the dependency on any signaling protocol. The MPLS LSP path without the dependency on any signaling protocol. The MPLS
Static LSP model augments the MPLS base YANG model with specific data Static LSP model augments the MPLS base YANG model with specific data
to configure and manage MPLS Static LSP(s). to configure and manage MPLS Static LSP(s).
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 13, 2019. This Internet-Draft will expire on May 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3 1.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3
2. MPLS Static LSP Model . . . . . . . . . . . . . . . . . . . . 4 2. MPLS Static LSP Model . . . . . . . . . . . . . . . . . . . . 4
2.1. Model Organization . . . . . . . . . . . . . . . . . . . 4 2.1. Model Organization . . . . . . . . . . . . . . . . . . . 4
2.2. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 4 2.2. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 4
2.3. Model Overview . . . . . . . . . . . . . . . . . . . . . 6 2.3. Model Overview . . . . . . . . . . . . . . . . . . . . . 6
2.4. Model YANG Module(s) . . . . . . . . . . . . . . . . . . 7 2.4. Model YANG Module(s) . . . . . . . . . . . . . . . . . . 7
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 4. Security Considerations . . . . . . . . . . . . . . . . . . . 16
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1. Normative References . . . . . . . . . . . . . . . . . . 15 5.1. Normative References . . . . . . . . . . . . . . . . . . 16
5.2. Informative References . . . . . . . . . . . . . . . . . 16 5.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
This document describes a YANG [RFC7950] data model for configuring This document describes a YANG [RFC7950] data model for configuring
and managing the Multiprotocol Label Switching (MPLS) [RFC3031] and managing the Multiprotocol Label Switching (MPLS) [RFC3031]
Static LSPs. The model allows the configuration of LER and LSR Static LSPs. The model allows the configuration of LER and LSR
devices with the necessary MPLS cross-connects or bindings to realize devices with the necessary MPLS cross-connects or bindings to realize
an end-to-end LSP service. an end-to-end LSP service.
A static LSP is established by manually specifying incoming and A static LSP is established by manually specifying incoming and
skipping to change at page 4, line 48 skipping to change at page 4, line 48
Static LSP +---------------------------+ Static LSP +---------------------------+
module module
Figure 1: Relationship between MPLS modules Figure 1: Relationship between MPLS modules
2.2. Model Tree Diagram 2.2. Model Tree Diagram
The MPLS Static and extended LSP tree diagram as per [RFC8340] is The MPLS Static and extended LSP tree diagram as per [RFC8340] is
shown in Figure 2. shown in Figure 2.
module: ietf-mpls-static module: ietf-mpls-static
augment /rt:routing/mpls:mpls: augment /rt:routing/mpls:mpls:
+--rw static-lsps +--rw static-lsps
+--rw static-lsp* [name] +--rw static-lsp* [name]
| +--rw name string | +--rw name string
| +--rw operation? mpls:mpls-operations-type | +--rw operation? mpls:mpls-operations-type
| +--rw in-segment | +--rw in-segment
| | +--rw fec | | +--rw fec
| | +--rw (type)? | | +--rw (type)?
| | | +--:(ip-prefix) | | | +--:(ip-prefix)
| | | | +--rw ip-prefix? inet:ip-prefix | | | | +--rw ip-prefix? inet:ip-prefix
| | | +--:(mpls-label) | | | +--:(mpls-label)
| | | | +--rw incoming-label? rt-types:mpls-label | | | | +--rw incoming-label? rt-types:mpls-label
| | | +--:(tunnel) | | | +--:(tunnel)
| | | +--rw tunnel? te:tunnel-ref | | | +--rw tunnel? te:tunnel-ref
| | +--rw incoming-interface? if:interface-ref | | +--rw incoming-interface? if:interface-ref
| +--rw out-segment | +--rw out-segment
| +--rw (out-segment)? | +--rw (out-segment)?
| +--:(nhlfe-single) | +--:(nhlfe-single)
| | +--rw nhlfe-single | | +--rw nhlfe-single
| | +--rw remote-labels | | +--rw mpls-label-stack
| | | +--rw remote-label* [index] | | | +--rw entry* [id]
| | | +--rw index uint8 | | | +--rw id uint8
| | | +--rw label? rt-types:mpls-label | | | +--rw label? rt-types:mpls-label
| | +--rw outgoing-interface? if:interface-ref | | | +--rw ttl? uint8
| +--:(nhlfe-multiple) | | | +--rw traffic-class? uint8
| +--rw nhlfe-multiple | | +--rw outgoing-interface? if:interface-ref
| +--rw nhlfe* [index] | +--:(nhlfe-multiple)
| +--rw index string | +--rw nhlfe-multiple
| +--rw backup-index? string | +--rw nhlfe* [index]
| +--rw loadshare? uint16 | +--rw index string
| +--rw role? nhlfe-role | +--rw backup-index? string
| +--rw remote-labels | +--rw loadshare? uint16
| | +--rw remote-label* [index] | +--rw role? nhlfe-role
| | +--rw index uint8 | +--rw mpls-label-stack
| | +--rw label? rt-types:mpls-label | | +--rw entry* [id]
| +--rw outgoing-interface? if:interface-ref | | +--rw id uint8
+--rw mpls-static-ext:bandwidth? uint32 | | +--rw label? rt-types:mpls-label
+--rw mpls-static-ext:lsp-priority-setup? uint8 | | +--rw ttl? uint8
+--rw mpls-static-ext:lsp-priority-hold? uint8 | | +--rw traffic-class? uint8
| +--rw outgoing-interface? if:interface-ref
module: ietf-mpls-static-extended +--rw mpls-static-ext:bandwidth? uint32
augment /rt:routing/mpls:mpls: +--rw mpls-static-ext:lsp-priority-setup? uint8
+--rw bidir-static-lsps +--rw mpls-static-ext:lsp-priority-hold? uint8
+--rw bidir-static-lsp* [name]
+--rw name string
+--rw forward-lsp? mpls-static:static-lsp-ref
+--rw reverse-lsp? mpls-static:static-lsp-ref
module: ietf-mpls-static-extended
augment /rt:routing/mpls:mpls:
+--rw bidir-static-lsps
+--rw bidir-static-lsp* [name]
+--rw name string
+--rw forward-lsp? mpls-static:static-lsp-ref
+--rw reverse-lsp? mpls-static:static-lsp-ref
Figure 2: MPLS Static LSP tree diagram Figure 2: MPLS Static LSP tree diagram
2.3. Model Overview 2.3. Model Overview
This document defines two YANG modules for MPLS Static LSP(s) This document defines two YANG modules for MPLS Static LSP(s)
configuration and management: ietf-mpls-static.yang and ietf-mpls- configuration and management: ietf-mpls-static.yang and ietf-mpls-
static-extended.yang. static-extended.yang.
The ietf-mpls-static module imports the followinig modules: The ietf-mpls-static module imports the followinig modules:
skipping to change at page 6, line 25 skipping to change at page 6, line 26
o ietf-routing defined in [RFC8349] o ietf-routing defined in [RFC8349]
o ietf-routing-types defined in [RFC8294] o ietf-routing-types defined in [RFC8294]
o ietf-interfaces defined in [RFC8343] o ietf-interfaces defined in [RFC8343]
o ietf-mpls defined in [I-D.ietf-mpls-base-yang] o ietf-mpls defined in [I-D.ietf-mpls-base-yang]
o ietf-te defined in [I-D.ietf-teas-yang-te] o ietf-te defined in [I-D.ietf-teas-yang-te]
ietf-mpls-static module contains the following high-level types and The ietf-mpls-static module contains the following high-level types
groupings: and groupings:
static-lsp-ref: static-lsp-ref:
A YANG reference type for a static LSP that can be used by data A YANG reference type for a static LSP that can be used by data
models to reference a configured static LSP. models to reference a configured static LSP.
in-segment: in-segment:
A YANG grouping that describes parameters of an incoming class of A YANG grouping that describes parameters of an incoming class of
FEC associated with a specific LSP as described in the MPLS FEC associated with a specific LSP as described in the MPLS
skipping to change at page 7, line 9 skipping to change at page 7, line 9
out-segment: out-segment:
A YANG grouping that describes parameters for the forwarding A YANG grouping that describes parameters for the forwarding
path(s) and their associated attributes for an LSP. The model path(s) and their associated attributes for an LSP. The model
allows for the following cases: allows for the following cases:
o single forwarding path or NHLFE o single forwarding path or NHLFE
o multiple forwarding path(s) or NHLFE(s), each of which can o multiple forwarding path(s) or NHLFE(s), each of which can
serve a primary, backup or both role(s). serve a primary, backup or both role(s).
The ietf-mpls-static-extended module imports the followinig modules:
o ietf-mpls defined in [I-D.ietf-mpls-base-yang]
o ietf-mpls-static defined in this document
o ietf-routing defined in [RFC8349]
The ietf-mpls-static-extended module contains the following high-
level types and groupings:
bidir-static-lsp:
A YANG grouping that describes list of static bidirectional LSPs
The ietf-mpls-static-extended augments the ietf-mpls-static model
with additional parameters to configure and manage:
o Bidirectional Static LSP(s)
o Defining Static LSP bandwidth allocation
o Defining Static LSP preemption priorities
2.4. Model YANG Module(s) 2.4. Model YANG Module(s)
Configuring LSPs through an LSR/LER involves the following steps: Configuring LSPs through an LSR/LER involves the following steps:
o Enabling MPLS on MPLS capable interfaces. o Enabling MPLS on MPLS capable interfaces.
o Configuring in-segments and out-segments on LER(s) and LSR(s) o Configuring in-segments and out-segments on LER(s) and LSR(s)
traversed by the LSP. traversed by the LSP.
o Setting up the cross-connect per LSP to associate segments and/or o Setting up the cross-connect per LSP to associate segments and/or
to indicate connection origination and termination. to indicate connection origination and termination.
o Optionally specifying label stack actions. o Optionally specifying label stack actions.
o Optionally specifying segment traffic parameters. o Optionally specifying segment traffic parameters.
The objects covered by this model are derived from the Incoming Label The objects covered by this model are derived from the Incoming Label
Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as specified in Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as specified in
the MPLS architecture document [RFC3031]. the MPLS architecture document [RFC3031].
The MPLS Static LSP module is shown in Figure 3. The MPLS Static LSP and Extended Static LSP modules are shown in
Figure 3 and Figure 4 below respectively.
<CODE BEGINS> file "ietf-mpls-static@2018-10-04.yang" <CODE BEGINS> file "ietf-mpls-static@2018-11-04.yang"
module ietf-mpls-static { module ietf-mpls-static {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static";
prefix "mpls-static"; prefix "mpls-static";
import ietf-mpls { import ietf-mpls {
prefix "mpls"; prefix "mpls";
reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model";
} }
skipping to change at page 8, line 27 skipping to change at page 9, line 4
reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces"; Engineering Tunnels and Interfaces";
} }
organization "IETF MPLS Working Group"; organization "IETF MPLS Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/mpls/> "WG Web: <http://tools.ietf.org/wg/mpls/>
WG List: <mailto:mpls@ietf.org> WG List: <mailto:mpls@ietf.org>
WG Chair: Loa Andersson WG Chair: Loa Andersson
<mailto:loa@pi.nu> <mailto:loa@pi.nu>
WG Chair: Nic Leymann
<mailto:N.Leymann@telekom.de>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Kamran Raza Editor: Kamran Raza
<mailto:skraza@cisco.com> <mailto:skraza@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Xufeng Liu Editor: Xufeng Liu
skipping to change at page 9, line 7 skipping to change at page 9, line 33
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto: Igor.Bryskin@huawei.com>"; <mailto: Igor.Bryskin@huawei.com>";
description description
"This YANG module augments the 'ietf-routing' module with basic "This YANG module augments the 'ietf-routing' module with basic
configuration and operational state data for MPLS static"; configuration and operational state data for MPLS static
The model fully conforms to the Network Management Datastore
Architecture (NMDA).
revision "2018-10-04" { Copyright (c) 2018 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this
// note.
// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
revision "2018-11-04" {
description description
"Latest revision: "Latest revision:
- Addressed MPLS-RT review comments"; - Addressed MPLS-RT review comments";
reference "RFC 3031: Multiprotocol Label Switching Architecture"; reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs";
} }
typedef static-lsp-ref { typedef static-lsp-ref {
type leafref { type leafref {
path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" +
"mpls-static:static-lsp/mpls-static:name"; "mpls-static:static-lsp/mpls-static:name";
} }
description description
"This type is used by data models that need to reference "This type is used by data models that need to reference
configured static LSP."; configured static LSP.";
skipping to change at page 11, line 31 skipping to change at page 12, line 30
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 3: MPLS Static LSP YANG module Figure 3: MPLS Static LSP YANG module
The extended MPLS Static LSP module is shown in Figure 4. The extended MPLS Static LSP module is shown in Figure 4.
<CODE BEGINS> file "ietf-mpls-static-extended@2018-10-04.yang" <CODE BEGINS> file "ietf-mpls-static-extended@2018-11-04.yang"
module ietf-mpls-static-extended { module ietf-mpls-static-extended {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended";
namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; prefix "mpls-static-ext";
prefix "mpls-static-ext"; import ietf-mpls {
prefix "mpls";
reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model";
}
import ietf-mpls { import ietf-routing {
prefix "mpls"; prefix "rt";
} reference "RFC6991: Common YANG Data Types";
}
import ietf-routing { import ietf-mpls-static {
prefix "rt"; prefix "mpls-static";
} reference "draft-ietf-mpls-static-yang: A YANG Data Model for MPLS
Static LSPs";
}
organization "IETF MPLS Working Group";
import ietf-mpls-static { contact
prefix "mpls-static"; "WG Web: <http://tools.ietf.org/wg/mpls/>
}
organization "IETF MPLS Working Group"; WG List: <mailto:mpls@ietf.org>
contact
"WG Web: <http://tools.ietf.org/wg/mpls/>
WG List: <mailto:mpls@ietf.org> WG Chair: Loa Andersson
<mailto:loa@pi.nu>
WG Chair: Loa Andersson WG Chair: Nic Leymann
<mailto:loa@pi.nu> <mailto:N.Leymann@telekom.de>
Editor: Tarek Saad Editor: Tarek Saad
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Kamran Raza Editor: Kamran Raza
<mailto:skraza@cisco.com> <mailto:skraza@cisco.com>
Editor: Rakesh Gandhi Editor: Rakesh Gandhi
<mailto:rgandhi@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto: xufeng.liu.ietf@gmail.com> <mailto: xufeng.liu.ietf@gmail.com>
Editor: Vishnu Pavan Beeram Editor: Vishnu Pavan Beeram
<mailto:vbeeram@juniper.net> <mailto:vbeeram@juniper.net>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Igor Bryskin Editor: Igor Bryskin
<mailto: Igor.Bryskin@huawei.com>"; <mailto: Igor.Bryskin@huawei.com>";
description description
"This module contains the Extended MPLS YANG data model."; "This YANG module contains the Extended MPLS Static LSP YANG
data model. The model fully conforms to the Network Management
Datastore Architecture (NMDA).
revision "2018-10-04" { Copyright (c) 2018 IETF Trust and the persons
description "Latest revision of MPLS extended yang module."; identified as authors of the code. All rights reserved.
reference "RFC2205";
}
/* RSVP features */ Redistribution and use in source and binary forms, with or
feature bandwidth { without modification, is permitted pursuant to, and subject
description to the license terms contained in, the Simplified BSD License
"Indicates support for static LSP bandwidth allocation"; set forth in Section 4.c of the IETF Trust's Legal Provisions
} Relating to IETF Documents
(https://trustee.ietf.org/license-info).
grouping bidir-static-lsp { This version of this YANG module is part of RFC XXXX; see
description the RFC itself for full legal notices.";
"grouping for top level list of static bidirectional LSPs";
leaf forward-lsp {
type mpls-static:static-lsp-ref;
description
"Reference to a configured static forward LSP";
}
leaf reverse-lsp {
type mpls-static:static-lsp-ref;
description
"Reference to a configured static reverse LSP";
}
}
augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { // RFC Ed.: replace XXXX with actual RFC number and remove this
description // note.
"Augmentation for static MPLS LSPs";
leaf bandwidth { // RFC Ed.: update the date below with the date of RFC publication
type uint32; // and remove this note.
description
"bandwidth in Mbps, e.g., using offline calculation";
}
leaf lsp-priority-setup {
type uint8 {
range "0..7";
}
description "LSP setup priority";
}
leaf lsp-priority-hold {
type uint8 {
range "0..7";
}
description "LSP hold priority";
}
}
augment "/rt:routing/mpls:mpls" { revision "2018-11-04" {
description "Augmentations for MPLS Static LSPs"; description "Latest revision of MPLS extended yang module.";
container bidir-static-lsps { reference "RFC XXXX: Extended YANG Data Model for MPLS Static LSPs";
description }
"Statically configured LSPs, without dynamic signaling";
list bidir-static-lsp {
key name;
description "list of defined static LSPs";
leaf name { grouping bidir-static-lsp {
type string; description
description "name to identify the LSP"; "grouping for top level list of static bidirectional LSPs";
} leaf forward-lsp {
uses bidir-static-lsp; type mpls-static:static-lsp-ref;
description
"Reference to a configured static forward LSP";
}
leaf reverse-lsp {
type mpls-static:static-lsp-ref;
description
"Reference to a configured static reverse LSP";
}
}
} augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" {
} description
} "Augmentation for static MPLS LSPs";
}
<CODE ENDS> leaf bandwidth {
type uint32;
units mbps;
description
"Bandwidth in Mbps, e.g., using offline calculation";
}
leaf lsp-priority-setup {
type uint8 {
range "0..7";
}
description "LSP setup priority";
}
leaf lsp-priority-hold {
type uint8 {
range "0..7";
}
description "LSP hold priority";
}
}
augment "/rt:routing/mpls:mpls" {
description "Augmentations for MPLS Static LSPs";
container bidir-static-lsps {
description
"Statically configured bidirectional LSPs";
list bidir-static-lsp {
key name;
description "List of static bidirectional LSPs";
leaf name {
type string;
description "Name that identifies the bidirectional LSP";
}
uses bidir-static-lsp;
}
}
}
}
<CODE ENDS>
Figure 4: Extended MPLS Static LSP YANG module Figure 4: Extended MPLS Static LSP YANG module
3. IANA Considerations 3. IANA Considerations
This document registers the following URIs in the IETF XML registry This document registers the following URIs in the IETF XML registry
[RFC3688]. Following the format in [RFC3688], the following [RFC3688]. Following the format in [RFC3688], the following
registration is requested to be made. registration is requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static
Registrant Contact: The MPLS WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended
Registrant Contact: The MPLS WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
This document registers two YANG modules in the YANG Module Names This document registers two YANG modules in the YANG Module Names
registry [RFC6020]. registry [RFC6020].
name: ietf-mpls-static name: ietf-mpls-static
namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static
prefix: ietf-mpls-static prefix: ietf-mpls-static
reference: RFC3031 // RFC Ed.: replace XXXX with RFC number and remove this note
reference: RFCXXXX
name: ietf-mpls-static-extended name: ietf-mpls-static-extended
namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended
prefix: ietf-mpls-static prefix: ietf-mpls-static-extended
reference: RFC3031 // RFC Ed.: replace XXXX with RFC number and remove this note
reference: RFCXXXX
4. Security Considerations 4. Security Considerations
The YANG module defined in this document is designed to be accessed The YANG module defined in this document is designed to be accessed
via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The NETCONF access control model transport is SSH [RFC6242]. The NETCONF access control model
[RFC8341] provides means to restrict access for particular NETCONF [RFC8341] provides means to restrict access for particular NETCONF
users to a pre-configured subset of all available NETCONF protocol users to a pre-configured subset of all available NETCONF protocol
operations and content. operations and content.
skipping to change at page 15, line 16 skipping to change at page 16, line 43
the provisioning of MPLS LSP(s) and associated parameters on a LSR the provisioning of MPLS LSP(s) and associated parameters on a LSR
can potentially have disastrous results. can potentially have disastrous results.
5. References 5. References
5.1. Normative References 5.1. Normative References
[I-D.ietf-mpls-base-yang] [I-D.ietf-mpls-base-yang]
Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A
YANG Data Model for MPLS Base", draft-ietf-mpls-base- YANG Data Model for MPLS Base", draft-ietf-mpls-base-
yang-07 (work in progress), October 2018. yang-08 (work in progress), October 2018.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and
I. Bryskin, "A YANG Data Model for Traffic Engineering I. Bryskin, "A YANG Data Model for Traffic Engineering
Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work Tunnels and Interfaces", draft-ietf-teas-yang-te-17 (work
in progress), July 2018. in progress), October 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, Label Switching Architecture", RFC 3031,
DOI 10.17487/RFC3031, January 2001, DOI 10.17487/RFC3031, January 2001,
<https://www.rfc-editor.org/info/rfc3031>. <https://www.rfc-editor.org/info/rfc3031>.
 End of changes. 47 change blocks. 
169 lines changed or deleted 246 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/