draft-ietf-pim-igmp-mld-yang-01.txt   draft-ietf-pim-igmp-mld-yang-02.txt 
PIM Working Group X. Liu PIM Working Group X. Liu
Internet-Draft Ericsson Internet-Draft Ericsson
Intended Status: Standard Track F. Guo Intended Status: Standard Track F. Guo
Expires: April 28, 2017 Huawei Expires: August 8, 2017 Huawei
M. Sivakumar M. Sivakumar
Cisco Cisco
P. McAllister P. McAllister
Metaswitch Networks Metaswitch Networks
A. Peter A. Peter
Juniper Networks Juniper Networks
October 28, 2016 February 7, 2017
A YANG data model for Internet Group Management Protocol (IGMP) and A YANG data model for Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) Multicast Listener Discovery (MLD)
draft-ietf-pim-igmp-mld-yang-01.txt draft-ietf-pim-igmp-mld-yang-02
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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 28, 2017. This Internet-Draft will expire on August 8, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 (http://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 3, line 26 skipping to change at page 3, line 26
This draft employs YANG tree diagrams, which are explained in [I- This draft employs YANG tree diagrams, which are explained in [I-
D.ietf-netmod-rfc6087bis]. D.ietf-netmod-rfc6087bis].
2. Design of Data model 2. Design of Data model
2.1. Scope of model 2.1. Scope of model
The model covers IGMPv1 [RFC1112], IGMPv2[RFC2236], IGMPv3[RFC3376] The model covers IGMPv1 [RFC1112], IGMPv2[RFC2236], IGMPv3[RFC3376]
and MLDv1[RFC2710], MLDv2[RFC3810]. and MLDv1[RFC2710], MLDv2[RFC3810].
The representation of some of extension features is not completely The representation of some extension features of IGMP and MLD is not
specified in this draft of the data model. This model is being specified in this draft of the data model. This model is being
circulated in its current form for early oversight and review of the circulated in its current form for early oversight and review of the
basic hierarchy. basic hierarchy.
The operational state fields and rpcs of this model are also The operational state fields and rpcs of this model can also
incomplete, though the structure of what has been written may be be extended, and the structure of what has been written may be
taken as representative of the structure of the model when complete. taken as representative of the structure of the whole model.
This model does not cover other IGMP and MLD related protocols such This model does not cover other IGMP and MLD related protocols such
as IGMP/MLD Proxy[RFC4605] or IGMP/MLD Snooping[RFC4541] etc., these as IGMP/MLD Proxy[RFC4605] or IGMP/MLD Snooping[RFC4541] etc., these
will be covered by future Internet Drafts. will be specified in separate documents.
2.2. Optional capabilities 2.2. Optional capabilities
This model is designed to represent the capabilities of IGMP and MLD This model is designed to represent the capabilities of IGMP and MLD
devices with various specifications, including some with basic devices with various specifications, including some with basic
subsets of the IGMP and MLD protocols. The main design goals of subsets of the IGMP and MLD protocols. The main design goals of
this draft are that any major now-existing implementation may be this draft are that any major now-existing implementation may be
said to support the basic model, and that the configuration of all said to support the basic model, and that the configuration of all
implementations meeting the specification is easy to express through implementations meeting the specification is easy to express through
some combination of the features in the basic model and simple some combination of the features in the basic model and simple
skipping to change at page 31, line 28 skipping to change at page 31, line 28
/* /*
* Notifications * Notifications
*/ */
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 5. Security Considerations
The data model defined does not introduce any security implications. The data model defined does not introduce any security implications.
This draft does not change any underlying security issues inherent This draft does not change any underlying security issues inherent
in [I-D.ietf-netmod-routing-cfg]. in [RFC8022].
6. IANA Considerations 6. IANA Considerations
TBD RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
actual RFC number (and remove this note).
This document registers the following namespace URIs in the IETF XML
registry [RFC3688]:
--------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang:ietf-igmp-mld
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
This document registers the following YANG modules in the YANG Module
Names registry [RFC7950]:
--------------------------------------------------------------------
name: ietf-igmp-mld
namespace: urn:ietf:params:xml:ns:yang:ietf-igmp-mld
prefix: igmp-mld
reference: RFC XXXX
--------------------------------------------------------------------
7. References 7. References
7.1. Normative References 7.1. Normative References
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004.
[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,
October 2010 October 2010.
[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, June 2011 (NETCONF)", RFC 6241, June 2011.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016.
[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, November
2016.
[I-D.ietf-netmod-rfc6087bis] Bierman, A., "Guidelines for Authors [I-D.ietf-netmod-rfc6087bis] Bierman, A., "Guidelines for Authors
and Reviewers of YANG Data Model Documents", draft-ietf- and Reviewers of YANG Data Model Documents", draft-ietf-
netmod-rfc6087bis-05 (work in progress), October 2015. netmod-rfc6087bis-10 (work in progress), January 2017.
7.2. Informative References 7.2. Informative References
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5, [RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, August 1989. RFC 1112, August 1989.
[RFC2236] Fenner, W., "Internet Group Management Protocol, Version [RFC2236] Fenner, W., "Internet Group Management Protocol, Version
2", RFC 2236, November 1997. 2", RFC 2236, November 1997.
[RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast
 End of changes. 13 change blocks. 
14 lines changed or deleted 44 lines changed or added

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