YANG Data Model for MPLS mLDP
draft-ietf-mpls-mldp-yang-01
MPLS Working Group K. Raza
Internet-Draft S. Krishnaswamy
Intended status: Standards Track Cisco Systems, Inc.
Expires: September 14, 2017
X. Liu
Jabil
S. Esale
Juniper Networks
X. Chen
Huawei Technologies
Jeff Tantsura
March 13, 2017
YANG Data Model for MPLS mLDP
draft-ietf-mpls-mldp-yang-01
Abstract
This document describes a YANG data model for Multi-Protocol Label
Switching (MPLS) Multipoint Label Distribution Protocol (mLDP). The
mLDP data model augments the LDP data model.
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 September 14, 2017.
Raza, et al. Expires September 14, 2017 [Page 1]
Internet-Draft YANG Data Model for MPLS mLDP March 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Base and Extended . . . . . . . . . . . . . . . . . . . . 3
2. Specification of Requirements . . . . . . . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. FEC Types . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Configuration Hierarchy . . . . . . . . . . . . . . . . . 7
4.2. mldp global container . . . . . . . . . . . . . . . . . . 9
4.3. Leveraging LDP containers . . . . . . . . . . . . . . . . 9
4.4. Configuration Tree . . . . . . . . . . . . . . . . . . . 10
4.4.1. Base . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4.2. Extended . . . . . . . . . . . . . . . . . . . . . . 11
5. Operational State . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 14
5.3. Derived states . . . . . . . . . . . . . . . . . . . . . 17
5.3.1. Root state . . . . . . . . . . . . . . . . . . . . . 18
5.3.2. Bindings state . . . . . . . . . . . . . . . . . . . 19
5.3.3. Capabilities state . . . . . . . . . . . . . . . . . 22
6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2. Extended . . . . . . . . . . . . . . . . . . . . . . . . 22
7. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8. Open Items . . . . . . . . . . . . . . . . . . . . . . . . . 23
9. YANG Specification . . . . . . . . . . . . . . . . . . . . . 23
9.1. Base . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Show full document text