draft-ietf-mpls-static-yang-08.txt   draft-ietf-mpls-static-yang-09.txt 
MPLS Working Group T. Saad MPLS Working Group T. Saad
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track R. Gandhi Intended status: Standards Track R. Gandhi
Expires: September 3, 2019 Cisco Systems, Inc. Expires: September 9, 2019 Cisco Systems, Inc.
X. Liu X. Liu
Volta Networks Volta Networks
V. Beeram V. Beeram
Juniper Networks Juniper Networks
I. Bryskin I. Bryskin
Huawei Technologies Huawei Technologies
March 02, 2019 March 08, 2019
A YANG Data Model for MPLS Static LSPs A YANG Data Model for MPLS Static LSPs
draft-ietf-mpls-static-yang-08 draft-ietf-mpls-static-yang-09
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 Label Edge Router(s) LER(s) and provisioning of static LSP(s) on Label Edge Router(s) LER(s) and
Label Switched Router(s) LSR(s) devices along a LSP path without the Label Switched Router(s) LSR(s) devices along a LSP path without the
dependency on any signaling protocol. The MPLS Static LSP model dependency on any signaling protocol. The MPLS Static LSP model
augments the MPLS base YANG model with specific data to configure and augments the MPLS base YANG model with specific data to configure and
manage MPLS Static LSP(s). manage MPLS Static LSP(s).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 http://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 September 3, 2019. This Internet-Draft will expire on September 9, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 7, line 44 skipping to change at page 7, line 44
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]
The ietf-mpls-static module is shown below: The ietf-mpls-static module is shown below:
<CODE BEGINS> file "ietf-mpls-static@2019-02-24.yang" <CODE BEGINS> file "ietf-mpls-static@2019-03-08.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";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC8349: A YANG Data Model for Routing Management"; reference "RFC8349: A YANG Data Model for Routing Management";
skipping to change at page 8, line 15 skipping to change at page 8, line 14
reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC8349: A YANG Data Model for Routing Management"; reference "RFC8349: A YANG Data Model for Routing Management";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix "rt-types";
reference "RFC8294: Common YANG Data Types"; reference "RFC8294: Common YANG Data Types for the Routing Area";
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference "RFC6991: Common YANG Data Types"; reference "RFC6991: Common YANG Data Types";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
reference "RFC7223: A YANG Data Model for Interface Management"; reference "RFC7223: A YANG Data Model for Interface Management";
skipping to change at page 9, line 38 skipping to change at page 9, line 38
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2019-02-24" { revision "2019-03-08" {
description description
"Latest revision of MPLS Static LSP YANG module"; "Latest revision of MPLS Static LSP YANG module";
reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 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";
} }
skipping to change at page 12, line 10 skipping to change at page 12, line 10
The ietf-mpls-static-extended module imports the followinig modules: The ietf-mpls-static-extended module imports the followinig modules:
o ietf-mpls defined in [I-D.ietf-mpls-base-yang] o ietf-mpls defined in [I-D.ietf-mpls-base-yang]
o ietf-mpls-static defined in this document o ietf-mpls-static defined in this document
o ietf-routing defined in [RFC8349] o ietf-routing defined in [RFC8349]
The ietf-mpls-static-extended module is shown below: The ietf-mpls-static-extended module is shown below:
<CODE BEGINS> file "ietf-mpls-static-extended@2019-02-24.yang" <CODE BEGINS> file "ietf-mpls-static-extended@2019-03-08.yang"
module ietf-mpls-static-extended { module ietf-mpls-static-extended {
yang-version 1.1; 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 "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; reference "RFC8349: A YANG Data Model for Routing Management";
} }
import ietf-routing { import ietf-mpls-static {
prefix "rt"; prefix "mpls-static";
reference "RFC6991: Common YANG Data Types"; reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs";
} }
import ietf-mpls-static { organization "IETF MPLS Working Group";
prefix "mpls-static";
reference "draft-ietf-mpls-static-yang: A YANG Data Model for MPLS
Static LSPs";
}
organization "IETF MPLS Working Group"; contact
"WG Web: <http://tools.ietf.org/wg/mpls/>
contact WG List: <mailto:mpls@ietf.org>
"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>
WG Chair: Nic Leymann Editor: Tarek Saad
<mailto:N.Leymann@telekom.de> <mailto:tsaad@cisco.com>
Editor: Tarek Saad Editor: Kamran Raza
<mailto:tsaad@cisco.com> <mailto:skraza@cisco.com>
Editor: Kamran Raza Editor: Rakesh Gandhi
<mailto:skraza@cisco.com> <mailto:rgandhi@cisco.com>
Editor: Rakesh Gandhi Editor: Xufeng Liu
<mailto:rgandhi@cisco.com> <mailto: xufeng.liu.ietf@gmail.com>
Editor: Xufeng Liu Editor: Vishnu Pavan Beeram
<mailto: xufeng.liu.ietf@gmail.com> <mailto:vbeeram@juniper.net>
Editor: Vishnu Pavan Beeram Editor: Himanshu Shah
<mailto:vbeeram@juniper.net> <mailto:hshah@ciena.com>
Editor: Himanshu Shah Editor: Igor Bryskin
<mailto:hshah@ciena.com> <mailto: Igor.Bryskin@huawei.com>";
Editor: Igor Bryskin description
<mailto: Igor.Bryskin@huawei.com>"; "This YANG module contains the Extended MPLS Static LSP YANG
data model. The model fully conforms to the Network Management
Datastore Architecture (NMDA).
description Copyright (c) 2018 IETF Trust and the persons
"This YANG module contains the Extended MPLS Static LSP YANG identified as authors of the code. All rights reserved.
data model. The model fully conforms to the Network Management
Datastore Architecture (NMDA).
Copyright (c) 2018 IETF Trust and the persons Redistribution and use in source and binary forms, with or
identified as authors of the code. All rights reserved. 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.";
Redistribution and use in source and binary forms, with or // RFC Ed.: replace XXXX with actual RFC number and remove this
without modification, is permitted pursuant to, and subject // note.
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 // RFC Ed.: update the date below with the date of RFC publication
// note. // and remove this note.
// RFC Ed.: update the date below with the date of RFC publication revision "2019-03-08" {
// and remove this note. description
"Latest revision of MPLS Static LSP Extended YANG module";
reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs";
}
revision "2019-02-24" { grouping bidir-static-lsp {
description description
"Latest revision of MPLS Static LSP Extended YANG module"; "grouping for top level list of static bidirectional LSPs";
reference "RFC XXXX: Extended YANG Data Model for MPLS Static LSPs"; leaf forward-lsp {
} type mpls-static:static-lsp-ref;
description
"Reference to a configured static forward LSP";
grouping bidir-static-lsp { }
description leaf reverse-lsp {
"grouping for top level list of static bidirectional LSPs"; type mpls-static:static-lsp-ref;
leaf forward-lsp { description
type mpls-static:static-lsp-ref; "Reference to a configured static reverse LSP";
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" { augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" {
description description
"Augmentation for static MPLS LSPs"; "Augmentation for static MPLS LSPs";
leaf bandwidth { leaf bandwidth {
type uint32; type uint32;
units mbps; units "Mbps";
description description
"Bandwidth in Mbps, e.g., using offline calculation"; "Bandwidth in Mbps, e.g., using offline calculation";
} }
leaf lsp-priority-setup { leaf lsp-priority-setup {
type uint8 { type uint8 {
range "0..7"; range "0..7";
} }
description "LSP setup priority"; description "LSP setup priority";
} }
leaf lsp-priority-hold { leaf lsp-priority-hold {
type uint8 { type uint8 {
range "0..7"; range "0..7";
} }
description "LSP hold priority"; description "LSP hold priority";
} }
} }
augment "/rt:routing/mpls:mpls" { augment "/rt:routing/mpls:mpls" {
description "Augmentations for MPLS Static LSPs"; description "Augmentations for MPLS Static LSPs";
container bidir-static-lsps { container bidir-static-lsps {
description description
"Statically configured bidirectional LSPs"; "Statically configured bidirectional LSPs";
list bidir-static-lsp { list bidir-static-lsp {
key name; key name;
description "List of static bidirectional LSPs"; description "List of static bidirectional LSPs";
leaf name { leaf name {
type string; type string;
description "Name that identifies the bidirectional LSP"; description "Name that identifies the bidirectional LSP";
} }
uses bidir-static-lsp; uses bidir-static-lsp;
} }
} }
}
} }
<CODE ENDS> }
<CODE ENDS>
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. 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.
skipping to change at page 16, line 49 skipping to change at page 16, line 44
YANG Data Model for MPLS Base", draft-ietf-mpls-base- YANG Data Model for MPLS Base", draft-ietf-mpls-base-
yang-10 (work in progress), February 2019. yang-10 (work in progress), February 2019.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
Interfaces", draft-ietf-teas-yang-te-19 (work in Interfaces", draft-ietf-teas-yang-te-19 (work in
progress), February 2019. progress), February 2019.
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997,
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, DOI 10.17487/ Label Switching Architecture", RFC 3031,
RFC3031, January 2001, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3031, January 2001,
rfc3031>. <https://www.rfc-editor.org/info/rfc3031>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004,
editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <https://www.rfc- DOI 10.17487/RFC6020, October 2010,
editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc- RFC 6991, DOI 10.17487/RFC6991, July 2013,
editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294, "Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017, <https://www.rfc- DOI 10.17487/RFC8294, December 2017,
editor.org/info/rfc8294>. <https://www.rfc-editor.org/info/rfc8294>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, DOI 10.17487/ Access Control Model", STD 91, RFC 8341,
RFC8341, March 2018, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC8341, March 2018,
rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, DOI Routing Management (NMDA Version)", RFC 8349,
10.17487/RFC8349, March 2018, <https://www.rfc- DOI 10.17487/RFC8349, March 2018,
editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
6.2. Informative References 6.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
Authors' Addresses Authors' Addresses
Tarek Saad Tarek Saad
 End of changes. 46 change blocks. 
148 lines changed or deleted 147 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/