netconfcentral logo

ieee802-dot1q-pb

HTML

ieee802-dot1q-pb@2017-09-07



  module ieee802-dot1q-pb {

    yang-version 1;

    namespace
      "urn:ieee:std:802.1Q:yang:ieee802-dot1q-pb";

    prefix dot1q-pb;

    import ieee802-dot1q-bridge {
      prefix dot1q;
    }
    import ieee802-dot1q-types {
      prefix dot1qtypes;
    }
    import ieee802-types {
      prefix ieee;
    }
    import ietf-interfaces {
      prefix if;
    }

    organization
      "Institute of Electrical and Electronics Engineers";

    contact
      "WG-URL: http://grouper.ieee.org/groups/802/1/
    WG-EMail: stds-802-1@ieee.org

    Contact: IEEE 802.1 Working Group Chair
    Postal: C/O IEEE 802.1 Working Group
            IEEE Standards Association
            445 Hoes Lane
            P.O. Box 1331
            Piscataway
            NJ 08855-1331
            USA
 	
    E-mail: STDS-802-1-L@LISTSERV.IEEE.ORG";

    description
      "This YANG module describes the bridge configuration model for
    Provider Bridges.";

    revision "2017-09-07" {
      description
        "Updates based upon comment resolution on draft
      D1.2 of P802.1Qcp.";
      reference
        "IEEE 802.1Q-2017, Media Access Control (MAC) Bridges and
        Virtual Bridged Local Area Networks.";

    }


    augment /if:interfaces/if:interface/dot1q:bridge-port {
      description
        "Augment the interface model with 802.1Q Bridge Port
      configuration specific nodes.";
      leaf svid {
        type ieee:vlanid;
        description
          "Service VLAN identifier.";
        reference
          "IEEE 802.1Q-2017 Clause 12.13.2.1";

      }

      list cvid-registration {
        when
          "../dot1q:component-name = 'dot1q:c-vlan-component' and
            ../dot1q:port-type = 'dot1q:customer-edge-port'" {
          description
            "Applies when the component associated with this interface
          is a C-VLAN component and the port-type is a customer edge
          port.";
        }
        key "cvid";
        description
          "The C-VID Registration Table, provides a mapping between a
        C-VID and the service instance represented by an S-VID
        selected for that C-VLAN. This table provides the equivalent
        functionality of
           1) Configuring the PVID of the internal CNP on the S-VLAN
              component
           2) Adding the corresponding PEP on the C-VLAN component to
              the member set of the C-VLAN
           3) Adding the PEP and/or CEP to the untagged set of the
              C-VLAN (if it is desired that frames forwarded to that
              port are transmitted untagged for this C-VLAN).";
        leaf cvid {
          type ieee:vlanid;
          description
            "Customer VLAN identifiers associated with this bridge
          port.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.2.1";

        }

        leaf svid {
          type ieee:vlanid;
          description
            "Service VLAN identifier.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.2.1";

        }

        leaf untagged-pep {
          type boolean;
          default "true";
          description
            "A boolean indicating frames for this C-VLAN should be
          forwarded untagged through the Provider Edge Port.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.2.1";

        }

        leaf untagged-cep {
          type boolean;
          default "true";
          description
            "A boolean indicating frames for this C-VLAN should be
          forwarded untagged through the Customer Edge Port.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.2.1";

        }
      }  // list cvid-registration

      list service-priority-regeneration {
        when
          "../dot1q:component-name = 'dot1q:c-vlan-component' and
      			../dot1q:port-type = 'dot1q:customer-edge-port'" {
          description
            "Applies when the component associated with this interface
			    is a C-VLAN component and the port-type is a customer edge
			    port.";
        }
        key "svid";
        description
          "The Service Priority Regeneration Table, which provides the
        Priority Regeneration Table (12.6.2) for each internal CNP
        connected to the C-VLAN component associated with the CEP.";
        leaf svid {
          type ieee:vlanid;
          description
            "Service VLAN identifier.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.2.6";

        }

        container priority-regeneration {
          description
            "Contains Service Priority Regeneration table nodal
          information.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.2.6";

          uses dot1qtypes:priority-regeneration-table-grouping;
        }  // container priority-regeneration
      }  // list service-priority-regeneration

      list rcap-internal-interface {
        when
          "../dot1q:component-name = 'dot1q:s-vlan-component' and
     			 ../dot1q:port-type = 'dot1q:remote-customer-access-port'" {
          description
            "Applies when the component associated with this interface
			    is a C-VLAN component and the port-type is a customer edge
			    port.";
        }
        key "external-svid";
        description
          "Designating an external port as an RCAP automatically 
      	creates a Port-mapping S-VLAN component associated with that
      	port. This Port-mapping S-VLAN component includes one internal
        PNP.";
        leaf external-svid {
          type ieee:vlanid;
          description
            "External Service VLAN identifier.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.3.2";

        }

        leaf internal-port-number {
          type dot1qtypes:port-number-type;
          description
            "The number of the RCAP.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.3.2";

        }

        leaf internal-svid {
          type ieee:vlanid;
          description
            "Internal Service VLAN Identifier (not applicable for a
          C-tagged RCSI).";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.3.2";

        }

        leaf internal-interface-type {
          type enumeration {
            enum "port-based-rcsi" {
              value 0;
              description "Port-based RCSI";
            }
            enum "c-tagged-rcsi" {
              value 1;
              description "C-tagged RCSI";
            }
            enum "pnp" {
              value 2;
              description
                "Provider Network Port";
            }
            enum "discard" {
              value 3;
              description
                "Discard (external S-VID is not associated with an
              internal port).";
            }
          }
          description
            "A value indicating the type of internal interface
          associated with the external S-VID.";
          reference
            "IEEE 802.1Q-2017 Clause 12.13.3.2";

        }
      }  // list rcap-internal-interface
    }
  }  // module ieee802-dot1q-pb

Summary

  
  
Organization Institute of Electrical and Electronics Engineers
  
Module ieee802-dot1q-pb
Version 2017-09-07
File ieee802-dot1q-pb.yang
  
Prefix dot1q-pb
Namespace urn:ieee:std:802.1Q:yang:ieee802-dot1q-pb
  
Cooked /cookedmodules/ieee802-dot1q-pb/2017-09-07
YANG /src/ieee802-dot1q-pb@2017-09-07.yang
XSD /xsd/ieee802-dot1q-pb@2017-09-07.xsd
  
Abstract This YANG module describes the bridge configuration model for Provider Bridges.
  
Contact
WG-URL: http://grouper.ieee.org/groups/802/1/
WG-EMail: stds-802-1@ieee.org

Contact: IEEE 802.1 Working Group Chair
Postal: C/O IEEE 802.1 Working Group
 IEEE Standards Association
 445 Hoes Lane
 P.O. Box 1331
 Piscataway
 NJ 08855-1331
 USA

E-mail: STDS-802-1-L@LISTSERV.IEEE.ORG

Description

 
This YANG module describes the bridge configuration model for
Provider Bridges.