draft-ietf-netmod-sub-intf-vlan-model-05.txt   draft-ietf-netmod-sub-intf-vlan-model-06.txt 
Internet Engineering Task Force R. Wilton, Ed. Internet Engineering Task Force R. Wilton, Ed.
Internet-Draft D. Ball Internet-Draft D. Ball
Intended status: Standards Track T. Singh Intended status: Standards Track T. Singh
Expires: September 7, 2019 Cisco Systems Expires: May 7, 2020 Cisco Systems
S. Sivaraj S. Sivaraj
Juniper Networks Juniper Networks
March 6, 2019 November 4, 2019
Sub-interface VLAN YANG Data Models Sub-interface VLAN YANG Data Models
draft-ietf-netmod-sub-intf-vlan-model-05 draft-ietf-netmod-sub-intf-vlan-model-06
Abstract Abstract
This document defines YANG modules to add support for classifying This document defines YANG modules to add support for classifying
traffic received on interfaces as Ethernet/VLAN framed packets to traffic received on interfaces as Ethernet/VLAN framed packets to
sub-interfaces based on the fields available in the Ethernet/VLAN sub-interfaces based on the fields available in the Ethernet/VLAN
frame headers. These modules allow configuration of Layer 3 and frame headers. These modules allow configuration of Layer 3 and
Layer 2 sub-interfaces (e.g. attachment circuits) that can Layer 2 sub-interfaces (e.g. attachment circuits) that can
interoperate with IETF based forwarding protocols; such as IP and interoperate with IETF based forwarding protocols; such as IP and
L3VPN services; or L2VPN services like VPWS, VPLS, and EVPN. The L3VPN services; or L2VPN services like VPWS, VPLS, and EVPN. The
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 September 7, 2019. This Internet-Draft will expire on May 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 2, line 35 skipping to change at page 2, line 35
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Interoperability with IEEE 802.1Q compliant bridges . . . 4 2.1. Interoperability with IEEE 802.1Q compliant bridges . . . 4
3. L3 Interface VLAN Model . . . . . . . . . . . . . . . . . . . 4 3. L3 Interface VLAN Model . . . . . . . . . . . . . . . . . . . 4
4. Flexible Encapsulation Model . . . . . . . . . . . . . . . . 5 4. Flexible Encapsulation Model . . . . . . . . . . . . . . . . 5
5. L3 Interface VLAN YANG Module . . . . . . . . . . . . . . . . 7 5. L3 Interface VLAN YANG Module . . . . . . . . . . . . . . . . 7
6. Flexible Encapsulation YANG Module . . . . . . . . . . . . . 10 6. Flexible Encapsulation YANG Module . . . . . . . . . . . . . 10
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1. Layer 3 sub-interfaces with IPv6 . . . . . . . . . . . . 19 7.1. Layer 3 sub-interfaces with IPv6 . . . . . . . . . . . . 19
7.2. Layer 2 sub-interfaces with L2VPN . . . . . . . . . . . . 21 7.2. Layer 2 sub-interfaces with L2VPN . . . . . . . . . . . . 21
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
9. ChangeLog . . . . . . . . . . . . . . . . . . . . . . . . . . 24 9. ChangeLog . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1. WG version -05 . . . . . . . . . . . . . . . . . . . . . 24 9.1. WG version -05 . . . . . . . . . . . . . . . . . . . . . 24
9.2. WG version -04 . . . . . . . . . . . . . . . . . . . . . 24 9.2. WG version -04 . . . . . . . . . . . . . . . . . . . . . 24
9.3. WG version -03 . . . . . . . . . . . . . . . . . . . . . 24 9.3. WG version -03 . . . . . . . . . . . . . . . . . . . . . 24
9.4. WG version -02 . . . . . . . . . . . . . . . . . . . . . 24 9.4. WG version -02 . . . . . . . . . . . . . . . . . . . . . 24
9.5. WG version -01 . . . . . . . . . . . . . . . . . . . . . 24 9.5. WG version -01 . . . . . . . . . . . . . . . . . . . . . 24
9.6. Version -04 . . . . . . . . . . . . . . . . . . . . . . . 24 9.6. Version -04 . . . . . . . . . . . . . . . . . . . . . . . 24
9.7. Version -03 . . . . . . . . . . . . . . . . . . . . . . . 25 9.7. Version -03 . . . . . . . . . . . . . . . . . . . . . . . 24
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
11. Security Considerations . . . . . . . . . . . . . . . . . . . 25 11. Security Considerations . . . . . . . . . . . . . . . . . . . 25
11.1. if-l3-vlan.yang . . . . . . . . . . . . . . . . . . . . 25 11.1. if-l3-vlan.yang . . . . . . . . . . . . . . . . . . . . 25
11.2. flexible-encapsulation.yang . . . . . . . . . . . . . . 26 11.2. flexible-encapsulation.yang . . . . . . . . . . . . . . 26
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
12.1. Normative References . . . . . . . . . . . . . . . . . . 28 12.1. Normative References . . . . . . . . . . . . . . . . . . 27
12.2. Informative References . . . . . . . . . . . . . . . . . 28 12.2. Informative References . . . . . . . . . . . . . . . . . 28
Appendix A. Comparison with the IEEE 802.1Q Configuration Model 29 Appendix A. Comparison with the IEEE 802.1Q Configuration Model 29
A.1. Sub-interface based configuration model overview . . . . 29 A.1. Sub-interface based configuration model overview . . . . 29
A.2. IEEE 802.1Q Bridge Configuration Model Overview . . . . . 30 A.2. IEEE 802.1Q Bridge Configuration Model Overview . . . . . 30
A.3. Possible Overlap Between the Two Models . . . . . . . . . 31 A.3. Possible Overlap Between the Two Models . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
This document defines two YANG [RFC7950] modules that augment the This document defines two YANG [RFC7950] modules that augment the
skipping to change at page 4, line 40 skipping to change at page 4, line 40
3. L3 Interface VLAN Model 3. L3 Interface VLAN Model
The L3 Interface VLAN model provides appropriate leaves for The L3 Interface VLAN model provides appropriate leaves for
termination of an 802.1Q VLAN tagged segment to a sub-interface based termination of an 802.1Q VLAN tagged segment to a sub-interface based
L3 service. It allows for termination of traffic with up to two L3 service. It allows for termination of traffic with up to two
802.1Q VLAN tags. 802.1Q VLAN tags.
The "if-l3-vlan" YANG module has the following structure: The "if-l3-vlan" YANG module has the following structure:
module: ietf-if-l3-vlan module: ietf-if-l3-vlan
augment /if:interfaces/if:interface/if-cmn:encapsulation/ augment /if:interfaces/if:interface/if-ext:encapsulation
if-cmn:encaps-type: /if-ext:encaps-type:
+--:(dot1q-vlan) +--:(dot1q-vlan)
+--rw dot1q-vlan +--rw dot1q-vlan
+--rw outer-tag +--rw outer-tag
| +--rw tag-type dot1q-tag-type | +--rw tag-type dot1q-tag-type
| +--rw vlan-id vlanid | +--rw vlan-id vlanid
+--rw second-tag! +--rw second-tag!
+--rw tag-type dot1q-tag-type +--rw tag-type dot1q-tag-type
+--rw vlan-id vlanid +--rw vlan-id vlanid
4. Flexible Encapsulation Model 4. Flexible Encapsulation Model
skipping to change at page 5, line 41 skipping to change at page 5, line 41
The final aim for the model design is for it to be cleanly extensible The final aim for the model design is for it to be cleanly extensible
to add in additional match and rewrite criteria of the layer 2 to add in additional match and rewrite criteria of the layer 2
header, such as matching on the source or destination MAC address, header, such as matching on the source or destination MAC address,
PCP or DEI fields in the 802.1Q tags, or the EtherType of the frame PCP or DEI fields in the 802.1Q tags, or the EtherType of the frame
payload. Rewrites can also be extended to allow for modification of payload. Rewrites can also be extended to allow for modification of
other fields within the layer 2 frame header. other fields within the layer 2 frame header.
The "flexible-encapsulation" YANG module has the following structure: The "flexible-encapsulation" YANG module has the following structure:
module: ietf-flexible-encapsulation module: ietf-flexible-encapsulation
augment /if:interfaces/if:interface/if-cmn:encapsulation/ augment /if:interfaces/if:interface/if-ext:encapsulation
if-cmn:encaps-type: /if-ext:encaps-type:
+--:(flexible) +--:(flexible)
+--rw flexible +--rw flexible
+--rw match +--rw match
| +--rw (match-type) | +--rw (match-type)
| +--:(default) | +--:(default)
| | +--rw default? empty | | +--rw default? empty
| +--:(untagged) | +--:(untagged)
| | +--rw untagged? empty | | +--rw untagged? empty
| +--:(dot1q-priority-tagged) | +--:(dot1q-priority-tagged)
| | +--rw dot1q-priority-tagged | | +--rw dot1q-priority-tagged
skipping to change at page 7, line 14 skipping to change at page 7, line 14
| +--rw vlan-id vlanid | +--rw vlan-id vlanid
+--rw second-tag! +--rw second-tag!
+--rw tag-type dot1q-tag-type +--rw tag-type dot1q-tag-type
+--rw vlan-id vlanid +--rw vlan-id vlanid
5. L3 Interface VLAN YANG Module 5. L3 Interface VLAN YANG Module
This YANG module augments the encapsultion container defined in This YANG module augments the encapsultion container defined in
Interface Extensions YANG [I-D.ietf-netmod-intf-ext-yang]. Interface Extensions YANG [I-D.ietf-netmod-intf-ext-yang].
<CODE BEGINS> file "ietf-if-l3-vlan@2019-03-05.yang" <CODE BEGINS> file "ietf-if-l3-vlan@2019-11-04.yang"
module ietf-if-l3-vlan { module ietf-if-l3-vlan {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-if-l3-vlan"; namespace "urn:ietf:params:xml:ns:yang:ietf-if-l3-vlan";
prefix if-l3-vlan; prefix if-l3-vlan;
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
} }
import iana-if-type { import iana-if-type {
prefix ianaift; prefix ianaift;
} }
import ieee802-dot1q-types { import ieee802-dot1q-types {
prefix dot1q-types; prefix dot1q-types;
} }
import ietf-interfaces-common { import ietf-if-extensions {
prefix if-cmn; prefix if-ext;
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: Lou Berger
<mailto:lberger@labn.net>
WG Chair: Joel Jaeggli
<mailto:joelja@gmail.com>
WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net>
Editor: Robert Wilton Editor: Robert Wilton
<mailto:rwilton@cisco.com>"; <mailto:rwilton@cisco.com>";
description description
"This YANG module models L3 VLAN sub-interfaces"; "This YANG module models L3 VLAN sub-interfaces
Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved.
revision 2019-03-05 { Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices.";
revision 2019-11-04 {
description "Latest draft revision"; description "Latest draft revision";
reference reference
"Internet-Draft draft-ietf-netmod-sub-intf-vlan-model-05"; "Internet-Draft draft-ietf-netmod-sub-intf-vlan-model-06";
} }
/* /*
* Add support for the 802.1Q VLAN encapsulation syntax on layer 3 * Add support for the 802.1Q VLAN encapsulation syntax on layer 3
* terminated VLAN sub-interfaces. * terminated VLAN sub-interfaces.
*/ */
augment "/if:interfaces/if:interface/if-cmn:encapsulation/" + augment "/if:interfaces/if:interface/if-ext:encapsulation/" +
"if-cmn:encaps-type" { "if-ext:encaps-type" {
when when
"derived-from-or-self(../if:type, "derived-from-or-self(../if:type,
'ianaift:ethernetCsmacd') or 'ianaift:ethernetCsmacd') or
derived-from-or-self(../if:type, derived-from-or-self(../if:type,
'ianaift:ieee8023adLag') or 'ianaift:ieee8023adLag') or
derived-from-or-self(../if:type, derived-from-or-self(../if:type,
'if-cmn:ethSubInterface')" { 'if-ext:ethSubInterface')" {
description description
"Applies only to Ethernet-like interfaces and "Applies only to Ethernet-like interfaces and
sub-interfaces"; sub-interfaces";
} }
description description
"Augment the generic interface encapsulation with an "Augment the generic interface encapsulation with an
basic 802.1Q VLAN encapsulation for sub-interfaces."; basic 802.1Q VLAN encapsulation for sub-interfaces.";
/* /*
* Matches a single VLAN Id, or a pair of VLAN Ids to classify * Matches a single VLAN Id, or a pair of VLAN Ids to classify
* traffic into an L3 service. * traffic into an L3 service.
*/ */
case dot1q-vlan { case dot1q-vlan {
container dot1q-vlan { container dot1q-vlan {
must must
'count(../../if-cmn:forwarding-mode) = 0 or ' + 'count(../../if-ext:forwarding-mode) = 0 or ' +
'derived-from-or-self(../../if-cmn:forwarding-mode,' + 'derived-from-or-self(../../if-ext:forwarding-mode,' +
'"if-cmn:layer-3-forwarding")' { '"if-ext:layer-3-forwarding")' {
error-message error-message
"If the interface forwarding-mode leaf is set then it "If the interface forwarding-mode leaf is set then it
must be set to an identity that derives from must be set to an identity that derives from
layer-3-forwarding"; layer-3-forwarding";
description description
"The forwarding-mode leaf on an interface can "The forwarding-mode leaf on an interface can
optionally be used to enforce consistency of optionally be used to enforce consistency of
configuration"; configuration";
} }
skipping to change at page 10, line 29 skipping to change at page 10, line 34
<CODE ENDS> <CODE ENDS>
6. Flexible Encapsulation YANG Module 6. Flexible Encapsulation YANG Module
This YANG module augments the encapsultion container defined in This YANG module augments the encapsultion container defined in
Interface Extensions YANG [I-D.ietf-netmod-intf-ext-yang]. Interface Extensions YANG [I-D.ietf-netmod-intf-ext-yang].
This YANG module also augments the interface container defined in This YANG module also augments the interface container defined in
[RFC8343]. [RFC8343].
<CODE BEGINS> file "ietf-flexible-encapsulation@2019-03-05.yang" <CODE BEGINS> file "ietf-flexible-encapsulation@2019-11-04.yang"
module ietf-flexible-encapsulation { module ietf-flexible-encapsulation {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-flexible-encapsulation"; "urn:ietf:params:xml:ns:yang:ietf-flexible-encapsulation";
prefix flex; prefix flex;
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
} }
import iana-if-type { import iana-if-type {
prefix ianaift; prefix ianaift;
} }
import ietf-interfaces-common { import ietf-if-extensions {
prefix if-cmn; prefix if-ext;
} }
import ieee802-dot1q-types { import ieee802-dot1q-types {
prefix dot1q-types; prefix dot1q-types;
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: Lou Berger
<mailto:lberger@labn.net>
WG Chair: Joel Jaeggli
<mailto:joelja@gmail.com>
WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net>
Editor: Robert Wilton Editor: Robert Wilton
<mailto:rwilton@cisco.com>"; <mailto:rwilton@cisco.com>";
description description
"This YANG module describes interface configuration for flexible "This YANG module describes interface configuration for flexible
VLAN matches and rewrites."; VLAN matches and rewrites.
revision 2019-03-05 { Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices.";
revision 2019-11-04 {
description "Latest draft revision"; description "Latest draft revision";
reference reference
"Internet-Draft draft-ietf-netmod-sub-intf-vlan-model-05"; "Internet-Draft draft-ietf-netmod-sub-intf-vlan-model-06";
} }
feature flexible-rewrites { feature flexible-rewrites {
description description
"This feature indicates whether the network element supports "This feature indicates whether the network element supports
specifying flexible rewrite operations"; specifying flexible rewrite operations";
} }
feature asymmetric-rewrites { feature asymmetric-rewrites {
description description
"This feature indicates whether the network element supports "This feature indicates whether the network element supports
specifying different rewrite operations for the ingress specifying different rewrite operations for the ingress
rewrite operation and egress rewrite operation."; rewrite operation and egress rewrite operation.";
} }
feature dot1q-tag-rewrites { feature dot1q-tag-rewrites {
description description
"This feature indicates whether the network element supports "This feature indicates whether the network element supports
skipping to change at page 16, line 31 skipping to change at page 16, line 39
* All tag rewrites are formed using a combination of pop-tags * All tag rewrites are formed using a combination of pop-tags
* and push-tags operations. * and push-tags operations.
*/ */
container dot1q-tag-rewrite { container dot1q-tag-rewrite {
if-feature dot1q-tag-rewrites; if-feature dot1q-tag-rewrites;
description "Tag rewrite. Translate operations are expressed description "Tag rewrite. Translate operations are expressed
as a combination of tag push and pop operations."; as a combination of tag push and pop operations.";
uses dot1q-tag-rewrite; uses dot1q-tag-rewrite;
} }
} }
augment "/if:interfaces/if:interface/if-cmn:encapsulation/" + augment "/if:interfaces/if:interface/if-ext:encapsulation/" +
"if-cmn:encaps-type" { "if-ext:encaps-type" {
when when
"derived-from-or-self(../if:type, "derived-from-or-self(../if:type,
'ianaift:ethernetCsmacd') or 'ianaift:ethernetCsmacd') or
derived-from-or-self(../if:type, derived-from-or-self(../if:type,
'ianaift:ieee8023adLag') or 'ianaift:ieee8023adLag') or
derived-from-or-self(../if:type, derived-from-or-self(../if:type,
'if-cmn:ethSubInterface')" { 'if-ext:ethSubInterface')" {
description description
"Applies only to Ethernet-like interfaces and "Applies only to Ethernet-like interfaces and
sub-interfaces"; sub-interfaces";
} }
description description
"Add flexible match and rewrite for VLAN sub-interfaces"; "Add flexible match and rewrite for VLAN sub-interfaces";
/* /*
* A flexible encapsulation allows for the matching of ranges and * A flexible encapsulation allows for the matching of ranges and
* sets of VLAN Ids. The structure is also designed to be * sets of VLAN Ids. The structure is also designed to be
skipping to change at page 17, line 4 skipping to change at page 17, line 13
} }
description description
"Add flexible match and rewrite for VLAN sub-interfaces"; "Add flexible match and rewrite for VLAN sub-interfaces";
/* /*
* A flexible encapsulation allows for the matching of ranges and * A flexible encapsulation allows for the matching of ranges and
* sets of VLAN Ids. The structure is also designed to be * sets of VLAN Ids. The structure is also designed to be
* extended to allow for matching/rewriting other fields within * extended to allow for matching/rewriting other fields within
* the L2 frame header if required. * the L2 frame header if required.
*/ */
case flexible { case flexible {
description "Flexible encapsulation and rewrite"; description "Flexible encapsulation and rewrite";
container flexible { container flexible {
must
'count(../../if-cmn:forwarding-mode) = 0 or ' +
'derived-from-or-self(../../if-cmn:forwarding-mode,' +
'"if-cmn:layer-2-forwarding")' {
error-message
"If the interface forwarding-mode leaf is set then it
must be set to an identity that derives from
layer-2-forwarding";
description
"The forwarding-mode leaf on an interface can
optionally be used to enforce consistency of
configuration";
}
description "Flexible encapsulation and rewrite"; description "Flexible encapsulation and rewrite";
container match { container match {
description description
"The match used to classify frames to this interface"; "The match used to classify frames to this interface";
uses flexible-match; uses flexible-match;
} }
container rewrite { container rewrite {
if-feature flexible-rewrites; if-feature flexible-rewrites;
skipping to change at page 28, line 44 skipping to change at page 28, line 40
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
12.2. Informative References 12.2. Informative References
[dot1Qcp] Holness, M., "IEEE 802.1Qcp-2018 Bridges and Bridged [dot1Qcp] Holness, M., "IEEE 802.1Qcp-2018 Bridges and Bridged
Networks - Amendment: YANG Data Model", 2018. Networks - Amendment: YANG Data Model", 2018.
[I-D.ietf-bess-l2vpn-yang] [I-D.ietf-bess-l2vpn-yang]
Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B., Shah, H., Brissette, P., Chen, I., Hussain, I., Wen, B.,
and K. Tiruveedhula, "YANG Data Model for MPLS-based and K. Tiruveedhula, "YANG Data Model for MPLS-based
L2VPN", draft-ietf-bess-l2vpn-yang-09 (work in progress), L2VPN", draft-ietf-bess-l2vpn-yang-10 (work in progress),
October 2018. July 2019.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <https://www.rfc-editor.org/info/rfc2460>. December 1998, <https://www.rfc-editor.org/info/rfc2460>.
[RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron, [RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron,
"Encapsulation Methods for Transport of Ethernet over MPLS "Encapsulation Methods for Transport of Ethernet over MPLS
Networks", RFC 4448, DOI 10.17487/RFC4448, April 2006, Networks", RFC 4448, DOI 10.17487/RFC4448, April 2006,
<https://www.rfc-editor.org/info/rfc4448>. <https://www.rfc-editor.org/info/rfc4448>.
 End of changes. 30 change blocks. 
71 lines changed or deleted 62 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/