draft-ietf-mpls-mldp-yang-03.txt   draft-ietf-mpls-mldp-yang-04.txt 
MPLS Working Group K. Raza MPLS Working Group K. Raza
Internet-Draft S. Krishnaswamy Internet-Draft S. Krishnaswamy
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: May 15, 2018 Expires: January 17, 2019
X. Liu X. Liu
Jabil Volta Networks
S. Esale S. Esale
Juniper Networks Juniper Networks
L. Andersson L. Andersson
Huawei Technologies Huawei Technologies
Jeff Tantsura J. Tantsura
Individual Nuage Networks
November 11, 2017 July 16, 2018
YANG Data Model for MPLS mLDP YANG Data Model for MPLS mLDP
draft-ietf-mpls-mldp-yang-03 draft-ietf-mpls-mldp-yang-04
Abstract Abstract
This document describes a YANG data model for Multi-Protocol Label This document describes a YANG data model for Multi-Protocol Label
Switching (MPLS) Multipoint Label Distribution Protocol (mLDP). The Switching (MPLS) Multipoint Label Distribution Protocol (mLDP). The
mLDP data model augments the LDP data model. mLDP data model augments the LDP data model.
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
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 May 15, 2018. This Internet-Draft will expire on January 17, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
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
skipping to change at page 3, line 5 skipping to change at page 3, line 5
6.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 21 6.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 21
7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8. Open Items . . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Open Items . . . . . . . . . . . . . . . . . . . . . . . . . 22
9. YANG Specification . . . . . . . . . . . . . . . . . . . . . 23 9. YANG Specification . . . . . . . . . . . . . . . . . . . . . 23
9.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 32 9.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 32
10. Security Considerations . . . . . . . . . . . . . . . . . . . 55 10. Security Considerations . . . . . . . . . . . . . . . . . . . 55
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 55 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 55
13. Normative References . . . . . . . . . . . . . . . . . . . . 55 13. Normative References . . . . . . . . . . . . . . . . . . . . 55
Appendix A. Additional Contributors . . . . . . . . . . . . . . 56 Appendix A. Additional Contributors . . . . . . . . . . . . . . 57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57
1. Introduction 1. Introduction
This document introduces a YANG data model for MPLS Multipoint Label This document introduces a YANG data model for MPLS Multipoint Label
Distribution Protocol (mLDP). The mLDP model being defined here is Distribution Protocol (mLDP). The mLDP model being defined here is
dependent on LDP YANG data model [I-D.ietf-mpls-ldp-yang]. This dependent on LDP YANG data model [I-D.ietf-mpls-ldp-yang]. This
implies that an opertor will need to use base LDP module to configure implies that an opertor will need to use base LDP module to configure
and manage control plane for mLDP. For example, an operator would and manage control plane for mLDP. For example, an operator would
enable LDP discovery on MPLS interface to establish LDP/mLDP peering enable LDP discovery on MPLS interface to establish LDP/mLDP peering
skipping to change at page 3, line 36 skipping to change at page 3, line 36
o Configuration o Configuration
o Operational State o Operational State
o Executables (Actions) o Executables (Actions)
o Notifications o Notifications
The modeling in this document complies with the Network Management The modeling in this document complies with the Network Management
Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores]. Datastore Architecture (NMDA) [RFC8342]. The operational state data
The operational state data is combined with the associated is combined with the associated configuration data in the same
configuration data in the same hierarchy hierarchy [I-D.ietf-netmod-rfc6087bis]. When protocol states are
[I-D.ietf-netmod-rfc6087bis]. When protocol states are retrieved retrieved from the NMDA operational state datastore, the returned
from the NMDA operational state datastore, the returned states cover states cover all "config true" (rw) and "config false" (ro) nodes
all "config true" (rw) and "config false" (ro) nodes defined in the defined in the schema.
schema.
This document is organized to define the data model for each of the This document is organized to define the data model for each of the
above constructs in the sequence as listed above. above constructs in the sequence as listed above.
1.1. Base and Extended 1.1. Base and Extended
Like LDP model, the configuration and state items are divided into Like LDP model, the configuration and state items are divided into
following two broad categories: following two broad categories:
o Base o Base
skipping to change at page 18, line 15 skipping to change at page 18, line 15
and MoFRR (primary or backup). and MoFRR (primary or backup).
Following captures a high level tree hierarchy for mLDP bindings Following captures a high level tree hierarchy for mLDP bindings
state: state:
+--rw mpls-ldp! +--rw mpls-ldp!
+--rw global +--rw global
+--rw mldp +--rw mldp
+--rw address-families +--rw address-families
+--rw ipv4 (or ipv6) +--rw ipv4 (or ipv6)
+--ro state
+--ro roots +--ro roots
+--ro root* [root-address] +--ro root* [root-address]
+--ro .... +--ro ....
+--ro bindings +--ro bindings
+--ro opaque-type-xxx +--ro opaque-type-xxx
| +--ro fec-label* [type-specific-key] | +--ro fec-label* [type-specific-key]
| +--ro some_key_1 ... | +--ro some_key_1 ...
| +--ro some_key_2 ... | +--ro some_key_2 ...
| +--ro multipoint-type? multipoint-type | +--ro multipoint-type? multipoint-type
| +--ro peer* [direction peer advertisement-type] | +--ro peer* [direction peer advertisement-type]
skipping to change at page 55, line 13 skipping to change at page 55, line 13
<CODE ENDS> <CODE ENDS>
Figure 15 Figure 15
10. Security Considerations 10. Security Considerations
This mLDP model shares the same security considerations as captured This mLDP model shares the same security considerations as captured
in LDP Yang model [I-D.ietf-mpls-ldp-yang]. in LDP Yang model [I-D.ietf-mpls-ldp-yang].
11. IANA Considerations 11. IANA Considerations
This document does not extend mLDP protocol specifiction and hence This document requests the registration of the following URIs in the
there are no IANA considerations. IETF "XML registry" [RFC3688]:
Note to the RFC Editor: Please remove IANA section before the +------------------------------------------------+------------+-----+
publication. | URI | Registrant | XML |
+------------------------------------------------+------------+-----+
| urn:ietf:params:xml:ns:yang:ietf-mpls-mldp | The IESG | N/A |
| | | |
| urn:ietf:params:xml:ns:yang:ietf-mpls-mldp- | The IESG | N/A |
| extended | | |
+------------------------------------------------+------------+-----+
This document requests the registration of the following YANG modules
in the "YANG Module Names" registry [RFC6020]:
+----------------+--------------------------------+--------+--------+
| Name | Namespace | Prefix | Refere |
| | | | nce |
+----------------+--------------------------------+--------+--------+
| ietf-mpls-mldp | urn:ietf:params:xml:ns:yang | mldp | This d |
| | :ietf-mpls-mldp | | ocumen |
| | | | t |
| | | | |
| ietf-mpls- | urn:ietf:params:xml:ns:yang | mldp- | This d |
| mldp-extended | :ietf-mpls-mldp-extended | ext | ocumen |
| | | | t |
+----------------+--------------------------------+--------+--------+
12. Acknowledgments 12. Acknowledgments
The authors would like to acknowledge Ladislav Lhotka for his useful The authors would like to acknowledge Ladislav Lhotka for his useful
comments as the YANG Doctor. comments as the YANG Doctor.
13. Normative References 13. Normative References
[I-D.ietf-mpls-ldp-yang] [I-D.ietf-mpls-ldp-yang]
Raza, K., Asati, R., Liu, X., Esale, S., Chen, X., and H. Raza, K., Asati, R., Liu, X., Esale, S., Chen, X., and H.
Shah, "YANG Data Model for MPLS LDP", draft-ietf-mpls-ldp- Shah, "YANG Data Model for MPLS LDP", draft-ietf-mpls-ldp-
yang-02 (work in progress), September 2017. yang-04 (work in progress), March 2018.
[I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-06
(work in progress), October 2017.
[I-D.ietf-netmod-rfc6087bis] [I-D.ietf-netmod-rfc6087bis]
Bierman, A., "Guidelines for Authors and Reviewers of YANG Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", draft-ietf-netmod-rfc6087bis-14 Data Model Documents", draft-ietf-netmod-rfc6087bis-20
(work in progress), September 2017. (work in progress), March 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>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B.
Thomas, "Label Distribution Protocol Extensions for Point- Thomas, "Label Distribution Protocol Extensions for Point-
to-Multipoint and Multipoint-to-Multipoint Label Switched to-Multipoint and Multipoint-to-Multipoint Label Switched
Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011,
<https://www.rfc-editor.org/info/rfc6388>. <https://www.rfc-editor.org/info/rfc6388>.
[RFC6389] Aggarwal, R. and JL. Le Roux, "MPLS Upstream Label [RFC6389] Aggarwal, R. and JL. Le Roux, "MPLS Upstream Label
Assignment for LDP", RFC 6389, DOI 10.17487/RFC6389, Assignment for LDP", RFC 6389, DOI 10.17487/RFC6389,
November 2011, <https://www.rfc-editor.org/info/rfc6389>. November 2011, <https://www.rfc-editor.org/info/rfc6389>.
skipping to change at page 56, line 47 skipping to change at page 57, line 27
[RFC7438] Wijnands, IJ., Ed., Rosen, E., Gulko, A., Joorde, U., and [RFC7438] Wijnands, IJ., Ed., Rosen, E., Gulko, A., Joorde, U., and
J. Tantsura, "Multipoint LDP (mLDP) In-Band Signaling with J. Tantsura, "Multipoint LDP (mLDP) In-Band Signaling with
Wildcards", RFC 7438, DOI 10.17487/RFC7438, January 2015, Wildcards", RFC 7438, DOI 10.17487/RFC7438, January 2015,
<https://www.rfc-editor.org/info/rfc7438>. <https://www.rfc-editor.org/info/rfc7438>.
[RFC7715] Wijnands, IJ., Ed., Raza, K., Atlas, A., Tantsura, J., and [RFC7715] Wijnands, IJ., Ed., Raza, K., Atlas, A., Tantsura, J., and
Q. Zhao, "Multipoint LDP (mLDP) Node Protection", Q. Zhao, "Multipoint LDP (mLDP) Node Protection",
RFC 7715, DOI 10.17487/RFC7715, January 2016, RFC 7715, DOI 10.17487/RFC7715, January 2016,
<https://www.rfc-editor.org/info/rfc7715>. <https://www.rfc-editor.org/info/rfc7715>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
Appendix A. Additional Contributors Appendix A. Additional Contributors
Matthew Bocci Matthew Bocci
Nokia Nokia
matthew.bocci@nokia.com Email: matthew.bocci@nokia.com
Authors' Addresses Authors' Addresses
Kamran Raza Kamran Raza
Cisco Systems, Inc. Cisco Systems, Inc.
2000 Innovation Drive
Kanata, ON K2K-3E8
CA
Email: skraza@cisco.com Email: skraza@cisco.com
Rajiv Asati Rajiv Asati
Cisco Systems, Inc. Cisco Systems, Inc.
Email: rajiva@cisco.com Email: rajiva@cisco.com
Sowmya Krishnaswamy Sowmya Krishnaswamy
Cisco Systems, Inc. Cisco Systems, Inc.
Email: sowkrish@cisco.com Email: sowkrish@cisco.com
Xufeng Liu Xufeng Liu
Jabil Volta Networks
Email: xufeng_liu@jabil.com Email: xufeng.liu.ietf@gmail.com
Jeff Tantsura Jeff Tantsura
Nuage Networks
Email: jefftant.ietf@gmail.com Email: jefftant.ietf@gmail.com
Santosh Esale Santosh Esale
Juniper Networks Juniper Networks
Email: sesale@juniper.net Email: sesale@juniper.net
Xia Chen Xia Chen
Huawei Technologies Huawei Technologies
Email: jescia.chenxia@huawei.com Email: jescia.chenxia@huawei.com
 End of changes. 21 change blocks. 
33 lines changed or deleted 66 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/