Sub-interface VLAN YANG Data Models
draft-ietf-netmod-sub-intf-vlan-model-04

Document Type Expired Internet-Draft (netmod WG)
Last updated 2019-01-03 (latest revision 2018-07-02)
Replaces draft-wilton-netmod-intf-vlan-yang
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Yang Validation 8 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-flexible-encapsulation@2017-10-30.yang
- Yang catalog entry for ietf-if-l3-vlan@2017-10-30.yang
- Yang impact analysis for draft-ietf-netmod-sub-intf-vlan-model
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-netmod-sub-intf-vlan-model-04.txt

Abstract

This document defines YANG modules to add support for classifying traffic received on interfaces as Ethernet/VLAN framed packets to sub-interfaces based on the fields available in the Ethernet/VLAN frame headers. These modules allow configuration of Layer 3 and Layer 2 sub-interfaces (e.g. attachment circuits) that can interoperate with IETF based forwarding protocols; such as IP and L3VPN services; or L2VPN services like VPWS, VPLS, and EVPN. The sub-interfaces also interoperate with VLAN tagged traffic orginating from an IEEE 802.1Q compliant bridge. Primarily the classification is based on VLAN identifiers in the 802.1Q VLAN tags, but the model also has support for matching on some other layer 2 frame header fields and is designed to be extensible to match on other arbitrary header fields. The model differs from an IEEE 802.1Q bridge model in that the configuration is interface/sub-interface based as opposed to being based on membership of an 802.1Q VLAN bridge.

Authors

Robert Wilton (rwilton@cisco.com)
David Ball (daviball@cisco.com)
tapsingh@cisco.com (tapsingh@cisco.com)
Selvakumar Sivaraj (ssivaraj@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)