draft-ietf-mpls-mldp-yang-05.txt   draft-ietf-mpls-mldp-yang-06.txt 
MPLS Working Group K. Raza MPLS Working Group K. Raza
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems
Intended status: Standards Track Intended status: Standards Track
Expires: April 25, 2019 X. Liu Expires: December 2, 2019 X. Liu
Volta Networks Volta Networks
S. Esale S. Esale
Juniper Networks Juniper Networks
L. Andersson L. Andersson
Huawei Technologies Huawei Technologies
J. Tantsura J. Tantsura
Nuage Networks Nuage Networks
S. Krishnaswamy S. Krishnaswamy
Individual Individual
October 22, 2018 May 31, 2019
YANG Data Model for MPLS mLDP YANG Data Model for MPLS mLDP
draft-ietf-mpls-mldp-yang-05 draft-ietf-mpls-mldp-yang-06
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.
The YANG modules in this document conform to the Network Management The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA). Datastore Architecture (NMDA).
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 25, 2019. This Internet-Draft will expire on December 2, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
(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 2, line 50 skipping to change at page 2, line 50
5.3.1. Root state . . . . . . . . . . . . . . . . . . . . . 17 5.3.1. Root state . . . . . . . . . . . . . . . . . . . . . 17
5.3.2. Bindings state . . . . . . . . . . . . . . . . . . . 18 5.3.2. Bindings state . . . . . . . . . . . . . . . . . . . 18
5.3.3. Capabilities state . . . . . . . . . . . . . . . . . 21 5.3.3. Capabilities state . . . . . . . . . . . . . . . . . 21
6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21 6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 21 6.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 22 6.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 22
7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8. Open Items . . . . . . . . . . . . . . . . . . . . . . . . . 23 8. Open Items . . . . . . . . . . . . . . . . . . . . . . . . . 23
9. YANG Specification . . . . . . . . . . . . . . . . . . . . . 23 9. YANG Specification . . . . . . . . . . . . . . . . . . . . . 23
9.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 33 9.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 34
10. Security Considerations . . . . . . . . . . . . . . . . . . . 55 10. Security Considerations . . . . . . . . . . . . . . . . . . . 55
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
13.1. Normative References . . . . . . . . . . . . . . . . . . 57 13.1. Normative References . . . . . . . . . . . . . . . . . . 57
13.2. Informative References . . . . . . . . . . . . . . . . . 59 13.2. Informative References . . . . . . . . . . . . . . . . . 60
Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 60 Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 60
Appendix B. Additional Contributors . . . . . . . . . . . . . . 68 Appendix B. Additional Contributors . . . . . . . . . . . . . . 68
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 68
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 the LDP YANG data model [I-D.ietf-mpls-ldp-yang]. This dependent on the LDP YANG data model [I-D.ietf-mpls-ldp-yang]. This
implies that an operator will need to use the base LDP module to implies that an operator will need to use the base LDP module to
skipping to change at page 25, line 42 skipping to change at page 25, line 42
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
// RFC Editor: replace XXXX with actual RFC number and remove // RFC Editor: replace XXXX with actual RFC number and remove
// this note // this note
revision 2018-10-22 { revision 2018-10-22 {
// RFC Editor: replace the above date 2018-10-22 with the date of
// publication and remove this note.
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Base YANG Data Model for MPLS mLDP"; "RFC XXXX: Base YANG Data Model for MPLS mLDP";
// RFC Editor: replace XXXX with actual RFC number and remove // RFC Editor: replace XXXX with actual RFC number and remove
// this note // this note
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef multipoint-type { typedef multipoint-type {
type enumeration { type enumeration {
enum p2mp { enum p2mp {
description "Point to multipoint"; description "Point to multipoint";
} }
enum mp2mp { enum mp2mp {
description "Multipoint to multipoint"; description "Multipoint to multipoint";
} }
} }
description description
skipping to change at page 36, line 7 skipping to change at page 36, line 14
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
// RFC Editor: replace XXXX with actual RFC number and remove // RFC Editor: replace XXXX with actual RFC number and remove
// this note // this note
revision 2018-10-22 { revision 2018-10-22 {
// RFC Editor: replace the above date 2018-10-22 with the date of
// publication and remove this note.
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Extended YANG Data Model for MPLS mLDP"; "RFC XXXX: Extended YANG Data Model for MPLS mLDP";
// RFC Editor: replace XXXX with actual RFC number and remove // RFC Editor: replace XXXX with actual RFC number and remove
// this note // this note
} }
/* /*
* Features * Features
skipping to change at page 57, line 12 skipping to change at page 57, line 17
The authors would like to acknowledge Ladislav Lhotka and Acee Lindem The authors would like to acknowledge Ladislav Lhotka and Acee Lindem
for their review and comments. for their review and comments.
13. References 13. References
13.1. Normative References 13.1. 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-04 (work in progress), March 2018. yang-06 (work in progress), May 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, 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, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
skipping to change at page 68, line 17 skipping to change at page 68, line 23
Appendix B. Additional Contributors Appendix B. Additional Contributors
Matthew Bocci Matthew Bocci
Nokia Nokia
Email: matthew.bocci@nokia.com Email: matthew.bocci@nokia.com
Authors' Addresses Authors' Addresses
Kamran Raza Kamran Raza
Cisco Systems, Inc. Cisco Systems
2000 Innovation Drive
Kanata, ON K2K-3E8
CA
Email: skraza@cisco.com Email: skraza@cisco.com
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
Email: xufeng.liu.ietf@gmail.com Email: xufeng.liu.ietf@gmail.com
Santosh Esale Santosh Esale
Juniper Networks Juniper Networks
Email: sesale@juniper.net Email: sesale@juniper.net
 End of changes. 15 change blocks. 
16 lines changed or deleted 17 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/