< draft-ietf-pim-msdp-yang-11.txt   draft-ietf-pim-msdp-yang-12.txt >
PIM WG X. Liu PIM WG X. Liu
Internet-Draft Volta Networks Internet-Draft Volta Networks
Intended status: Standards Track Z. Zhang, Ed. Intended status: Standards Track Z. Zhang, Ed.
Expires: July 25, 2020 ZTE Corporation Expires: July 26, 2020 ZTE Corporation
A. Peter A. Peter
Individual contributor Individual contributor
M. Sivakumar M. Sivakumar
Juniper networks Juniper networks
F. Guo F. Guo
Huawei Technologies Huawei Technologies
P. McAllister P. McAllister
Metaswitch Networks Metaswitch Networks
January 22, 2020 January 23, 2020
A YANG Data Model for Multicast Source Discovery Protocol (MSDP) A YANG Data Model for Multicast Source Discovery Protocol (MSDP)
draft-ietf-pim-msdp-yang-11 draft-ietf-pim-msdp-yang-12
Abstract Abstract
This document defines a YANG data model for the configuration and This document defines a YANG data model for the configuration and
management of Multicast Source Discovery Protocol (MSDP) Protocol. management of Multicast Source Discovery Protocol (MSDP) Protocol.
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.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 July 25, 2020. This Internet-Draft will expire on July 26, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 8, line 14 skipping to change at page 8, line 14
3.3. MSDP RPC 3.3. MSDP RPC
The RPC part is used to define some useful and ordinary operations of The RPC part is used to define some useful and ordinary operations of
protocol management. Network managers can delete all the information protocol management. Network managers can delete all the information
from a given peer by using the clear-peer rpc. And network managers from a given peer by using the clear-peer rpc. And network managers
can delete a given SA cache information by clear-sa-cache rpc. can delete a given SA cache information by clear-sa-cache rpc.
4. MSDP YANG Model 4. MSDP YANG Model
This module references [RFC6991], [RFC8349], [RFC8343], [RFC8344], This module references [RFC3618], [RFC6991], [RFC8177], [RFC8343],
[RFC8177], [RFC3618], [RFC8294], [RFC8519]. [RFC8344], [RFC8349], [RFC8294], [RFC8519].
<CODE BEGINS> file "ietf-msdp@2020-01-23.yang" <CODE BEGINS> file "ietf-msdp@2020-01-24.yang"
module ietf-msdp { module ietf-msdp {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-msdp"; namespace "urn:ietf:params:xml:ns:yang:ietf-msdp";
prefix msdp; prefix msdp;
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
reference "RFC 6991"; reference "RFC 6991: Common YANG Data Types";
} }
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
reference "RFC 6991"; reference "RFC 6991: Common YANG Data Types";
} }
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
reference "RFC 8349"; reference "RFC 8349: A YANG Data Model for Routing Management
(NMDA Version)";
} }
import ietf-interfaces { import ietf-interfaces {
prefix "if"; prefix "if";
reference "RFC 8343"; reference "RFC 8343: A YANG Data Model for Interface Management";
} }
import ietf-ip { import ietf-ip {
prefix "ip"; prefix "ip";
reference "RFC 8344"; reference "RFC 8344: A YANG Data Model for IP Management";
} }
import ietf-key-chain { import ietf-key-chain {
prefix "key-chain"; prefix "key-chain";
reference "RFC 8177"; reference "RFC 8177: YANG Data Model for Key Chains";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix "rt-types";
reference "RFC 8294"; reference "RFC 8294: Common YANG Data Types for the Routing
Area";
} }
import ietf-access-control-list { import ietf-access-control-list {
prefix acl; prefix acl;
reference reference
"RFC 8519"; "RFC 8519: YANG Data Model for Network Access Control Lists
(ACLs)";
} }
organization organization
"IETF PIM (Protocols for IP Multicast) Working Group"; "IETF PIM (Protocols for IP Multicast) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/pim/> "WG Web: <http://tools.ietf.org/wg/pim/>
WG List: <mailto:pim@ietf.org> WG List: <mailto:pim@ietf.org>
Editor: Xufeng Liu Editor: Xufeng Liu
skipping to change at page 10, line 19 skipping to change at page 10, line 23
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
itself for full legal notices. itself for full legal notices.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119) are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all (RFC 8174) when, and only when, they appear in all
capitals, as shown here."; capitals, as shown here.";
revision 2020-01-23 { revision 2020-01-24 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for MSDP."; "RFC XXXX: A YANG Data Model for MSDP.";
} }
/* /*
* Features * Features
*/ */
feature feature-msdp { feature feature-msdp {
skipping to change at page 12, line 16 skipping to change at page 12, line 21
"Support configuration of per peer limit on SA entries."; "Support configuration of per peer limit on SA entries.";
} }
/* /*
* Identities * Identities
*/ */
identity msdp { identity msdp {
if-feature "feature-msdp"; if-feature "feature-msdp";
base rt:control-plane-protocol; base rt:control-plane-protocol;
description "MSDP protocol."; description "Identity for the Multicast Source Discovery
reference Protocol (MSDP).";
"RFC 3618: Multicast Source Discovery Protocol (MSDP)";
} }
/* /*
* Groupings * Groupings
*/ */
grouping authentication-container { grouping authentication-container {
description description
"Authentication attributes."; "Authentication attributes.";
container authentication { container authentication {
description description
skipping to change at page 26, line 30 skipping to change at page 26, line 34
/rt:routing/rt:control-plane-protocols/msdp:clear-peer, /rt:routing/rt:control-plane-protocols/msdp:clear-peer,
/rt:routing/rt:control-plane-protocols/msdp:clear-sa-cache, /rt:routing/rt:control-plane-protocols/msdp:clear-sa-cache,
Unauthorized access to any of the above action operations can Unauthorized access to any of the above action operations can
reconstruct the MSDP peers or delete SA records on this device. reconstruct the MSDP peers or delete SA records on this device.
6. IANA Considerations 6. IANA Considerations
RFC Ed.: Please replace all occurrences of 'XXXX' with the actual RFC
number (and remove this note).
The IANA is requested to assign one new URIs from the IETF XML The IANA is requested to assign one new URIs from the IETF XML
registry [RFC3688]. Authors are suggesting the following URI: registry [RFC3688]. Authors are suggesting the following URI:
URI: urn:ietf:params:xml:ns:yang:ietf-msdp URI: urn:ietf:params:xml:ns:yang:ietf-msdp
Registrant Contact: The IESG Registrant Contact: The IESG
XML: N/A, the requested URI is an XML namespace XML: N/A, the requested URI is an XML namespace
This document also requests one new YANG module name in the YANG This document also requests one new YANG module name in the YANG
 End of changes. 17 change blocks. 
20 lines changed or deleted 24 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/