A YANG data model for Protocol-Independent Multicast (PIM)
draft-ietf-pim-yang-08
Document Type Active Internet-Draft (pim WG)
Last updated 2017-08-09 (latest revision 2017-04-08)
Replaces draft-mcallister-pim-yang
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Yang Validation ☯ 23 errors, 0 warnings.
Reviews
YANGDOCTORS Early Review (of -00): Ready with Issues
Stream WG state Submitted to IESG for Publication
Document shepherd Stig Venaas
Shepherd write-up Show (last changed 2017-03-08)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Stig Venaas <stig@venaas.com>
Email authors IPR References Referenced by Nits 
PIM Working Group                                                 X. Liu
Internet-Draft                                                     Jabil
Intended status: Standards Track                           P. McAllister
Expires: October 10, 2017                            Metaswitch Networks
                                                                A. Peter
                                                              Individual
                                                            M. Sivakumar
                                                           Cisco Systems
                                                                  Y. Liu
                                                     Huawei Technologies
                                                                   F. Hu
                                                         ZTE Corporation
                                                           April 8, 2017

       A YANG data model for Protocol-Independent Multicast (PIM)
                         draft-ietf-pim-yang-08

Abstract

   This document defines a YANG data model that can be used to configure
   and manage Protocol Independent Multicast (PIM) devices.  The model
   covers the PIM protocol configuration, operational state, and event
   notifications data.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 10, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Liu, et al.             Expires October 10, 2017                [Page 1]
Internet-Draft                  PIM YANG                      April 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   4
   2.  Design of Data Model  . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Scope of model  . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Optional capabilities . . . . . . . . . . . . . . . . . .   5
     2.3.  Top-level structure . . . . . . . . . . . . . . . . . . .   6
     2.4.  Position of address family in hierarchy . . . . . . . . .   6
   3.  Module Structure  . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  PIM base module . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  PIM RP module . . . . . . . . . . . . . . . . . . . . . .  11
     3.3.  PIM-SM module . . . . . . . . . . . . . . . . . . . . . .  14
     3.4.  PIM-DM module . . . . . . . . . . . . . . . . . . . . . .  15
     3.5.  PIM-BIDIR module  . . . . . . . . . . . . . . . . . . . .  16
   4.  PIM YANG Modules  . . . . . . . . . . . . . . . . . . . . . .  17
     4.1.  PIM base module . . . . . . . . . . . . . . . . . . . . .  17
     4.2.  PIM RP module . . . . . . . . . . . . . . . . . . . . . .  37
     4.3.  PIM-SM module . . . . . . . . . . . . . . . . . . . . . .  52
     4.4.  PIM-DM module . . . . . . . . . . . . . . . . . . . . . .  58
     4.5.  PIM-BIDIR module  . . . . . . . . . . . . . . . . . . . .  60
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .  69
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  69
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  70
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  71
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  71
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  71
Show full document text
ISOC IETF Trust RFC Editor IRTF IESG IETF IAB IASA & IAOC IETF Tools IANA