draft-ietf-bess-l2vpn-yang-03.txt   draft-ietf-bess-l2vpn-yang-04.txt 
skipping to change at page 1, line 18 skipping to change at page 1, line 18
Jabil Jabil
I. Hussain, Ed. I. Hussain, Ed.
Infinera Corporation Infinera Corporation
B. Wen, Ed. B. Wen, Ed.
Comcast Comcast
K. Tiruveedhula, Ed. K. Tiruveedhula, Ed.
Juniper Networks Juniper Networks
March 13, 2017 March 13, 2017
YANG Data Model for MPLS-based L2VPN YANG Data Model for MPLS-based L2VPN
draft-ietf-bess-l2vpn-yang-03.txt draft-ietf-bess-l2vpn-yang-04.txt
Abstract Abstract
This document describes a YANG data model for Layer 2 VPN (L2VPN) This document describes a YANG data model for Layer 2 VPN (L2VPN)
services over MPLS networks. These services include point-to-point services over MPLS networks. These services include point-to-point
Virtual Private Wire Service (VPWS) and multipoint Virtual Private Virtual Private Wire Service (VPWS) and multipoint Virtual Private
LAN service (VPLS) that uses LDP and BGP signaled Pseudowires. It is LAN service (VPLS) that uses LDP and BGP signaled Pseudowires. It is
expected that this model will be used by the management tools run by expected that this model will be used by the management tools run by
the network operators in order to manage and monitor the network the network operators in order to manage and monitor the network
resources that they use to deliver L2VPN services. resources that they use to deliver L2VPN services.
skipping to change at page 15, line 13 skipping to change at page 15, line 13
+--ro bind-b-component-name? string +--ro bind-b-component-name? string
+--ro bind-b-component-type? identityref +--ro bind-b-component-type? identityref
Figure 2 Figure 2
4. YANG Module 4. YANG Module
The L2VPN configuration container is logically divided into following The L2VPN configuration container is logically divided into following
high level config areas: high level config areas:
(CODE BEGINS) file "ietf-l2vpn@2017-03-06.yang" <CODE BEGINS> file "ietf-l2vpn@2017-03-06.yang"
module ietf-l2vpn { module ietf-l2vpn {
namespace "urn:ietf:params:xml:ns:yang:ietf-l2vpn"; namespace "urn:ietf:params:xml:ns:yang:ietf-l2vpn";
prefix "l2vpn"; prefix "l2vpn";
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
import ietf-yang-types { import ietf-yang-types {
skipping to change at page 38, line 30 skipping to change at page 38, line 30
} }
description "Augment for a VPLS instance's backup pseudowire " + description "Augment for a VPLS instance's backup pseudowire " +
"endpoint operational state"; "endpoint operational state";
leaf precedence { leaf precedence {
type uint32; type uint32;
description "precedence of the pseudowire"; description "precedence of the pseudowire";
} }
} }
} }
(CODE ENDS) <CODE ENDS>
Figure 3 Figure 3
5. Security Considerations 5. Security Considerations
The configuration, state, action and notification data defined in The configuration, state, action and notification data defined in
this document are designed to be accessed via the NETCONF protocol this document are designed to be accessed via the NETCONF protocol
[RFC6241]. The lowest NETCONF layer is the secure transport layer [RFC6241]. The lowest NETCONF layer is the secure transport layer
and the mandatory-to-implement secure transport is SSH [RFC6242]. and the mandatory-to-implement secure transport is SSH [RFC6242].
The NETCONF access control model [RFC6536] provides means to restrict The NETCONF access control model [RFC6536] provides means to restrict
skipping to change at page 43, line 38 skipping to change at page 43, line 38
Email: nick.deregno@verizon.com Email: nick.deregno@verizon.com
Luay Jalil Luay Jalil
Verizon Verizon
Email: luay.jalil@verizon.com Email: luay.jalil@verizon.com
Maria Joecylyn Maria Joecylyn
Verizon Verizon
Email: joecylyn.malit@verizon.com Email: joecylyn.malit@verizon.com
Figure 4
Authors' Addresses Authors' Addresses
Himanshu Shah Himanshu Shah
Ciena Corporation Ciena Corporation
Email: hshah@ciena.com Email: hshah@ciena.com
Patrice Brissette Patrice Brissette
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 4 change blocks. 
5 lines changed or deleted 3 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/