2 namespace "http://metroethernetforum.org/ns/yang/mef-types";
\r
4 organization "Metro Ethernet Forum";
\r
6 "Web URL: http://metroethernetforum.org/
\r
7 E-mail: mibs@metroethernetforum.org
\r
8 Postal: Metro Ethernet Forum
\r
9 6033 W. Century Boulevard, Suite 1107
\r
10 Los Angeles, CA 90045
\r
12 Phone: +1 310-642-2800
\r
13 Fax: +1 310-642-2808";
\r
15 "This module defines the YANG Type Definitions and shared
\r
16 (templated) groupings of data elementsused by MEF YANG Modules.
\r
19 A number of base documents have been used to create
\r
20 the MEF Types YANG Module. The following are the
\r
21 abbreviations for the baseline documents:
\r
22 [RFC 6991] refers to IETF RFC 6991 'Common YANG Data Types',
\r
24 [RFC 6643] refers to IETF RFC 6643 'Translation of Structure
\r
25 of Management Information
\r
26 Version 2 (SMIv2) MIB Modules to YANG Modules', 2011-11-25
\r
27 [802.1AB] refers to 'Station and Media Access Control
\r
28 Connectivity Discovery', IEEE 802.1AB-2009, September 2009
\r
29 [802.1q] refers to IEEE 802.1Q-2011 'IEEE Standard for Local
\r
30 and metropolitan area networks --Media Access Control (MAC)
\r
31 Bridges and Virtual Bridged Local Area Networks, August 2011
\r
32 [802-2001] refers to 'IEEE Standard for Local and Metropolitan
\r
33 Area Networks: Overview and Architecture', IEEE 802-2001,
\r
35 [MEF10.3] refers to MEF 10.3
\r
36 'Ethernet Services Attributes Phase 3', October 2013
\r
37 [MEF6.2] refers to MEF 6.2
\r
38 'EVC Ethernet Services Defintions Phase 3', August 2014
\r
39 [MEF40] refers to MEF 40
\r
40 'UNI and EVC Definition of Managed Objects', April 2013
\r
41 [MEF45] refers to MEF 45 'Multi-CEN L2CP', August 2014
\r
42 [MEF7.2] refers to MEF 7.2
\r
43 'Carrier Ethernet Management Information Model', April 2013
\r
44 [MEF7.3] refers to MEF 7.3
\r
45 'Carrier Ethernet Management Information Model',
\r
46 Working Draft #1 2015
\r
47 [RFC 2737] refers to IETF RFC 2737 'Entity MIB (Version 2)',
\r
49 [RFC 2863] refers to IETF RFC 2863 'The Interfaces Group MIB',
\r
51 [RFC 3419] refers to IETF RFC 3419
\r
52 'Textual Conventions for Transport Addresses', December 2002
\r
53 [Y.1731] refers to ITU-T Y.1731
\r
54 'OAM functions and mechanisms for Ethernet based networks',
\r
56 [Q.840.1] refers to ITU-T Q.840.1
\r
57 'Requirements and analysis for NMS-EMS management interface
\r
58 of Ethernet over Transport and Metro Ethernet
\r
59 Network(EoT/MEN)' March 2007";
\r
60 revision 2015-05-26 {
\r
62 "Formal Project Review Draft 1.";
\r
63 reference "EVC Ethernet Services Definitions YANG Modules " +
\r
66 identity ieee-8023-interface-type {
\r
68 "Base identity from which specific IEEE 802.3-2012 " +
\r
69 "interface types are derived. This list was taken " +
\r
70 "from Section 1.4 'Definitions'.";
\r
72 identity ieee8023-10BASE2 {
\r
73 base ieee-8023-interface-type;
\r
77 identity ieee8023-10BASE5 {
\r
78 base ieee-8023-interface-type;
\r
82 identity ieee8023-10BASE-F {
\r
83 base ieee-8023-interface-type;
\r
87 identity ieee8023-10BASE-FB {
\r
88 base ieee-8023-interface-type;
\r
92 identity ieee8023-1000BASE-PX-D {
\r
93 base ieee-8023-interface-type;
\r
97 identity ieee8023-1000BASE-PX-U {
\r
98 base ieee-8023-interface-type;
\r
102 identity ieee8023-10BASE-FL {
\r
103 base ieee-8023-interface-type;
\r
107 identity ieee8023-10BASE-FP {
\r
108 base ieee-8023-interface-type;
\r
112 identity ieee8023-10BASE-T {
\r
113 base ieee-8023-interface-type;
\r
117 identity ieee8023-10BASE-Te {
\r
118 base ieee-8023-interface-type;
\r
122 identity ieee8023-10BROAD36 {
\r
123 base ieee-8023-interface-type;
\r
127 identity ieee8023-10PASS-TS {
\r
128 base ieee-8023-interface-type;
\r
132 identity ieee8023-100BASE-BX10 {
\r
133 base ieee-8023-interface-type;
\r
137 identity ieee8023-100BASE-FX {
\r
138 base ieee-8023-interface-type;
\r
142 identity ieee8023-100BASE-LX10 {
\r
143 base ieee-8023-interface-type;
\r
147 identity ieee8023-100BASE-T {
\r
148 base ieee-8023-interface-type;
\r
152 identity ieee8023-100BASE-T2 {
\r
153 base ieee-8023-interface-type;
\r
157 identity ieee8023-100BASE-T4 {
\r
158 base ieee-8023-interface-type;
\r
162 identity ieee8023-100BASE-TX {
\r
163 base ieee-8023-interface-type;
\r
167 identity ieee8023-100BASE-X {
\r
168 base ieee-8023-interface-type;
\r
172 identity ieee8023-1000BASE-BX10 {
\r
173 base ieee-8023-interface-type;
\r
177 identity ieee8023-1000BASE-CX {
\r
178 base ieee-8023-interface-type;
\r
182 identity ieee8023-1000BASE-KX {
\r
183 base ieee-8023-interface-type;
\r
187 identity ieee8023-1000BASE-LX {
\r
188 base ieee-8023-interface-type;
\r
192 identity ieee8023-1000BASE-LX10 {
\r
193 base ieee-8023-interface-type;
\r
197 identity ieee8023-1000BASE-PX10 {
\r
198 base ieee-8023-interface-type;
\r
202 identity ieee8023-1000BASE-PX20 {
\r
203 base ieee-8023-interface-type;
\r
207 identity ieee8023-1000BASE-SX {
\r
208 base ieee-8023-interface-type;
\r
212 identity ieee8023-1000BASE-T {
\r
213 base ieee-8023-interface-type;
\r
217 identity ieee8023-1000BASE-X {
\r
218 base ieee-8023-interface-type;
\r
222 identity ieee8023-10GBASE-CX4 {
\r
223 base ieee-8023-interface-type;
\r
227 identity ieee8023-10GBASE-E {
\r
228 base ieee-8023-interface-type;
\r
232 identity ieee8023-10GBASE-ER {
\r
233 base ieee-8023-interface-type;
\r
237 identity ieee8023-10GBASE-EW {
\r
238 base ieee-8023-interface-type;
\r
242 identity ieee8023-10GBASE-KR {
\r
243 base ieee-8023-interface-type;
\r
247 identity ieee8023-10GBASE-KX4 {
\r
248 base ieee-8023-interface-type;
\r
252 identity ieee8023-10GBASE-L {
\r
253 base ieee-8023-interface-type;
\r
257 identity ieee8023-10GBASE-LR {
\r
258 base ieee-8023-interface-type;
\r
262 identity ieee8023-10GBASE-LRM {
\r
263 base ieee-8023-interface-type;
\r
267 identity ieee8023-10GBASE-LW {
\r
268 base ieee-8023-interface-type;
\r
272 identity ieee8023-10GBASE-LX4 {
\r
273 base ieee-8023-interface-type;
\r
277 identity ieee8023-10GBASE-PR {
\r
278 base ieee-8023-interface-type;
\r
282 typedef identifier45 {
\r
288 "This type definition accepts any visible ASCII character " +
\r
289 "plus the <space> character.The string must be an RFC 2579 " +
\r
290 "Display String (RFC 854 ASCII 0.00-0.7f) but not contain " +
\r
291 "the characters 0.00 through 0.1f. It does not accept " +
\r
292 "the <delete> character (0.7f) despite the current MEF " +
\r
293 "specification not disallowing it.";
\r
294 reference "[MEF10.3] [R8], [R9]. [RFC2579]. [RFC854].";
\r
296 typedef max-svc-frame-size-type {
\r
298 range "1522..16384";
\r
302 "Max Frame Size Type in bytes. Service Frames larger than " +
\r
303 "this size will be discarded.";
\r
304 reference "[MEF 10.3] Section 8.9 and Section 9.7.";
\r
306 typedef retail-svc-id-type {
\r
309 "General ID used by higher level applications that " +
\r
310 "connect Subscribers information and SLA's with " +
\r
311 "configured Ethernet Services.";
\r
312 reference "[MEF10.3].";
\r
314 typedef svc-provider-type {
\r
317 "Service Provider Type";
\r
318 reference "[MEF10.3].";
\r
324 reference "[MEF10.3].";
\r
326 typedef subscriber-type {
\r
330 reference "[MEF10.3].";
\r
332 typedef evc-id-type {
\r
336 reference "[MEF10.3].";
\r
338 typedef simple-percent {
\r
341 range "0.00 .. 100.00";
\r
343 description "Percent.";
\r
345 typedef vlan-id-type {
\r
350 "The VLAN-ID that uniquely identifies a VLAN. This is the " +
\r
351 "12-bit VLAN-ID used in the VLAN Tag header. The range " +
\r
352 "is defined by the REFERENCED specification. VLAN ID 0 is " +
\r
353 "used for VLAN Unaware Mode.";
\r
354 reference "IEEE Std 802.1Q 2003 Edition, Virtual Bridged " +
\r
355 "Local Area Networks.";
\r
357 typedef vlan-id-or-none-type {
\r
362 "The VLAN-ID that uniquely identifies a VLAN. This is the " +
\r
363 "12-bit VLAN-ID used in the VLAN Tag header. The range is " +
\r
364 "defined by the REFERENCED specification. VLAN ID 0 is " +
\r
365 "used for VLAN Unaware (ie. None) Mode";
\r
366 reference "IEEE Std 802.1Q 2003 Edition, Virtual Bridged " +
\r
367 "Local Area Networks.";
\r
369 typedef vlan-id-or-all-type {
\r
374 "The VLAN-ID that uniquely identifies a VLAN. This is the " +
\r
375 "12-bit VLAN-ID used in the VLAN Tag header. The range " +
\r
376 "is defined by the REFERENCED specification. VLAN ID 4095 " +
\r
377 "is used for VLAN Any Mode";
\r
378 reference "IEEE Std 802.1Q 2003 Edition, Virtual Bridged " +
\r
379 "Local Area Networks.";
\r
381 typedef vlan-id-any-none-type {
\r
386 "The VLAN-ID that uniquely identifies a VLAN. This is the " +
\r
387 "12-bit VLAN-ID used in the VLAN Tag header. The range " +
\r
388 "is defined by the REFERENCED specification. This " +
\r
389 "typedef is for use with Operational Status information " +
\r
390 "where VLAN ID 0 may be used for VLAN Unaware Mode and " +
\r
391 "use of 4095 is Reserved / None.";
\r
392 reference "IEEE Std 802.1Q 2003 Edition, Virtual Bridged " +
\r
393 "Local Area Networks.";
\r
395 typedef ieee-8021-priority {
\r
400 "An 802.1Q user priority value.";
\r
401 reference "IEEE 802.1Q";
\r
403 typedef entity-admin-state-type {
\r
413 enum "shutting-down" {
\r
423 "Represents the various possible administrative states. " +
\r
424 "A value of 'locked' means the resource is " +
\r
425 "administratively prohibited from use. A value of " +
\r
426 "'shuttingDown' means that usage is administratively " +
\r
427 "limited to current instances of use.A value of " +
\r
428 "'unlocked' means the resource is not administratively " +
\r
429 "prohibited from use.A value of 'unknown' means that " +
\r
430 "this resource is unable to report administrative state.";
\r
431 reference "ENTITY-STATE-TC-MIB";
\r
433 typedef performance-metric-type {
\r
435 enum "one-way-frame-delay-performance" {
\r
437 "One-way Frame Delay Performance.";
\r
439 enum "one-way-frame-delay-range-performance" {
\r
441 "One-way Frame Delay Range Performance.";
\r
443 enum "one-way-mean-frame-delay-performance" {
\r
445 "One-way Mean Frame Delay Performance.";
\r
447 enum "one-way-inter-frame-delay-variation-performance" {
\r
449 "One-way Inter-Frame Delay Variation Performance.";
\r
451 enum "one-way-frame-loss-ratio-performance" {
\r
453 "One-way Frame Loss Ratio Performance.";
\r
455 enum "one-way-availability-performance" {
\r
457 "One-way Availability Performance.";
\r
459 enum "one-way-resiliency-performance-hli" {
\r
461 "One-way Resiliency Performance expressed as High " +
\r
464 enum "one-way-resiliency-performance-chli" {
\r
466 "One-way Resiliency Performance expressed as " +
\r
467 "Consecutive High Loss Intervals.";
\r
469 enum "one-way-group-availability-performance" {
\r
471 "One-way Group Availability Performance.";
\r
473 enum "one-way-multiple-evc-group-availability-performance" {
\r
475 "One-way Multiple EVC Group Availability Performance.";
\r
479 "Performance Metrics.";
\r
480 reference "[MEF10.3] Section 8.8 and Section 11.";
\r
484 enum "point-to-point" {
\r
488 enum "multipoint-to-multipoint" {
\r
490 "Multipoint to Multipoint.";
\r
492 enum "rooted-multipoint" {
\r
494 "Rooted Multipoint.";
\r
499 reference "[MEF10.3] Section 8.1.";
\r
501 typedef evc-status-type {
\r
513 "Inactive (Not Active).";
\r
515 enum "partially-active" {
\r
517 "PartiallyActive.";
\r
522 reference "[MEF16] Section 5.3.";
\r
524 typedef evc-uni-role-type {
\r
528 "Root Role for UNI. Valid setting for all service " +
\r
529 "types. A UNI set to this value may send frames " +
\r
530 "to UNIs configured as 'root' or 'leaf'.";
\r
534 "Leaf Role for UNI. Valid setting for Root-Multipoint " +
\r
535 "EVCs only. A UNI set to this value may send frames " +
\r
540 "This object configures UNI type on an EVC.";
\r
541 reference "[MEF10.3] Section 8.1.2.1.";
\r
543 typedef data-svc-frame-delivery-type {
\r
547 "Service Frames are discarded.";
\r
549 enum "unconditional" {
\r
551 "Service Frames are unconditionally
\r
552 delivered no matter the content of the
\r
553 Service Frame. An example of this is
\r
554 a Point-to-Point EVC";
\r
556 enum "conditional" {
\r
558 "Service Frame are conditionally
\r
559 delivered to the destination UNI. The
\r
560 condition is specified, for example via a
\r
561 bandwidth profile or unicast MAC address
\r
566 "A MEF service can have one of three different " +
\r
569 typedef uni-resiliency-type {
\r
573 "No protection mechanism defined.";
\r
575 enum "dual-link-aggregation" {
\r
577 "Protection mechanism is Link Aggreg-
\r
578 ation as specified in [802.3], with one link in
\r
579 active mode and one link in standby mode.";
\r
583 "Protection method defined that is not
\r
584 Link Aggregation active/standby mode.";
\r
588 "This object type of resiliency mechanism for a " +
\r
591 typedef svc-frame-format-type {
\r
595 "No-tag indicates that all data on the interface is " +
\r
596 "as untagged data.";
\r
600 "Ctag indicates that tagged data is associated with " +
\r
601 "CE-VLAN ID or a C-TAG.";
\r
605 "Stag indicates that tagged data is associated with " +
\r
606 "a provider tag or S-TAG.";
\r
610 "Stag-ctag indicates that service traffic identified " +
\r
611 "with both an S-TAG (outer tag) and a C-TAG (inner tag).";
\r
615 "The format must be that of a MAC Frame specified in " +
\r
616 "IEEE Std 802.3-2012 Clause 3.";
\r
617 reference "[MEF10.3] Section 9.6. [MEF15]. [MEF7.2]. " +
\r
618 "[MEF7.3] Section 10.1.1. MEF-UNI-EVC-MIB.yang.";
\r
620 typedef uni-mode-type {
\r
632 "This setting is used to configure a UNI as either a " +
\r
634 reference "[MEF7.3] Section 10.2.2.";
\r
636 typedef evc-cos-identifier-type {
\r
640 "The EVC ID, depends on the CE-VLAN ID / EVC Mapping " +
\r
641 "at the UNI, will be used to map Service Frames to " +
\r
642 "CoS Names/Labels.";
\r
643 reference "MEF 10.3 Section 10.2.1.1 for " +
\r
644 "Data Service Frames.";
\r
648 "The Priority Code Point(PCP) value within the " +
\r
649 "CE-VLAN Tag will be used to map Service Frames " +
\r
650 "to CoS Names/Labels.";
\r
651 reference "MEF 10.3 Section 10.2.1.2: Priority Code " +
\r
652 "Point (PCP) Field in the Customer VLAN Tag " +
\r
653 "in a Tagged Service Frame. ";
\r
657 "The Differentiated Services Code Point(DSCP) value " +
\r
658 "from the IP Packet's IP Header Differentiated " +
\r
659 "Services Group, associated with the Service Frame, " +
\r
660 "will be used to map Service Frames to CoS Names/Labels.";
\r
661 reference "MEF 10.3 Section 10.2.1.3: AKA Internet " +
\r
662 "Protocol. For a Data Service Frame carrying an " +
\r
663 "IPv4 or and IPv6 packet.";
\r
667 "[MEF10.3] Section 10.2.1.";
\r
669 typedef evc-eec-identifier-type {
\r
673 "The Priority Code Point(PCP) value within the " +
\r
674 "CE-VLAN Tag will be used to map Service Frames " +
\r
675 "to CoS Names/Labels.";
\r
676 reference "MEF 10.3 Section 10.2.1.2: Priority Code " +
\r
677 "Point (PCP) Field in the Customer VLAN Tag " +
\r
678 "in a Tagged Service Frame.";
\r
682 "The Differentiated Services Code Point(DSCP) value " +
\r
683 "from the IP Packet's IP Header Differentiated " +
\r
684 "Services Group, associated with the Service Frame, " +
\r
685 "will be used to map Service Frames to CoS Names/Labels.";
\r
686 reference "MEF 10.3 Section 10.2.1.3: AKA Internet " +
\r
687 "Protocol. For a Data Service Frame carrying " +
\r
688 "an IPv4 or and IPv6 packet.";
\r
692 "[MEF10.3] Section 10.2.1.";
\r
694 typedef cos-color-identifier-type {
\r
698 "The EVC ID, depends on the CE-VLAN ID / EVC Mapping " +
\r
699 "at the UNI, will be used to map Service Frames to " +
\r
700 "CoS Names/Labels.";
\r
701 reference "MEF 10.3 Section 10.2.1.1 for Data " +
\r
706 "The Priority Code Point(PCP) value within the " +
\r
707 "CE-VLAN Tag will be used to map Service Frames " +
\r
708 "to CoS Names/Labels.";
\r
709 reference "MEF 10.3 Section 10.2.1.2: Priority Code " +
\r
710 "Point (PCP) Field in the Customer VLAN Tag " +
\r
711 "in a Tagged Service Frame. ";
\r
715 "Drop Eligible Indicator(DEI) field of the CE-VLAN Tag.";
\r
719 "The Differentiated Services Code Point(DSCP) value " +
\r
720 "from the IP Packet's IP Header Differentiated " +
\r
721 "Services Group, associated with the Service " +
\r
722 "Frame, will be used to map Service Frames to " +
\r
723 "CoS Names/Labels.";
\r
724 reference "MEF 10.3 Section 10.2.1.3: AKA Internet " +
\r
725 "Protocol. For a Data Service Frame carrying " +
\r
726 "an IPv4 or and IPv6 packet.";
\r
730 "CoS Color Identification Type.";
\r
731 reference "[MEF23.1].";
\r
733 typedef cos-color-type {
\r
746 reference "[MEF23.1].";
\r
748 typedef bwp-cir-type {
\r
751 "Bandwidth Profile Committed Information Rate in " +
\r
752 "Kilobits Per Second.";
\r
753 reference "[MEF10.3] [R143], [R144].";
\r
755 typedef bwp-cbs-type {
\r
758 "Bandwidth Profile Committed Burst Size in Bytes.";
\r
759 reference "[MEF10.3] [R145].";
\r
761 typedef bwp-eir-type {
\r
764 "Bandwidth Profile Excess Information Rate in " +
\r
765 "Kilobits Per Second.";
\r
766 reference "[MEF10.3] [R146], [R147].";
\r
768 typedef bwp-ebs-type {
\r
770 range "0 .. 10000000";
\r
773 "Excess Burst Size (EBS) in bytes: This parameter limits " +
\r
774 "the maximum number of bytes available for a burst " +
\r
775 "of Service Frames sent at the UNI line rate that " +
\r
776 "will be declared Yellow by the Bandwidth Profile. " +
\r
777 "If this value is 0, then no limit is assumed.";
\r
778 reference "[MEF10.3] [R146], [R147].";
\r
780 typedef elmi-polling-counter-type {
\r
785 "ELMI Polling Counter.";
\r
786 reference "[MEF16] Section 5.6.1.";
\r
788 typedef elmi-status-error-threshold-type {
\r
793 "The count of consecutive ELMI status polling errors " +
\r
794 "before raising an error.";
\r
795 reference "[MEF16] Section 5.6.1.";
\r
797 typedef elmi-polling-timer-type {
\r
802 "The type used for a timer started after tranmitting " +
\r
803 "a Status Enquiry. If the timer expires, record " +
\r
804 "the error if a STATUS message not received and " +
\r
805 "resend Status Enquiry.";
\r
806 reference "[MEF16] Section 5.6.1.";
\r
808 typedef elmi-polling-verification-timer-type {
\r
813 "The type used for a timer started after tranmitting " +
\r
814 "a Status Message. If a Status Enquiry is recieved before " +
\r
815 "this timer expires, record the error.";
\r
816 reference "[MEF16] Section 5.6.1.";
\r
818 typedef bwp-color-mode-type {
\r
820 enum "color-blind" {
\r
822 "Color Blind. Do not use CoS Color Configuration for " +
\r
823 "this Bandwidth Profile.";
\r
825 enum "color-aware" {
\r
827 "Color Aware. Use CoS Color Configuration for this " +
\r
828 "Bandwidth Profile.";
\r
832 "This attribute describes the color mode (CM) to be " +
\r
833 "applied as \"color-blind mode\" or \"color-aware mode\".";
\r
834 reference "[MEF10.3] Section 10.3, [R151].";
\r
836 typedef bwp-coupling-flag-type {
\r
838 enum "yellow-eir-only" {
\r
840 "When CF is set to \"yellow-eir-only\", the volume of " +
\r
841 "the yellow service frames admitted to the network " +
\r
842 "cannot exceed EIR.";
\r
844 enum "yellow-eir-plus-cir" {
\r
846 "When CF is set to \"yellow-eir-plus-cir\", the " +
\r
847 "volume of the yellow service frames admitted to " +
\r
848 "the network is bounded by CIR + EIR depending on " +
\r
849 "volume of the offered green Service Frames.";
\r
853 "The Bandwidth Profile parameter that determines whether " +
\r
854 "or not overflow tokens not used for Service Frames " +
\r
855 "declared Green can be used as Yellow tokens.";
\r
856 reference "[MEF10.3] Section 12.1. [MEF23.1] Section 8.1.";
\r
858 typedef auto-negotiation-type {
\r
862 "Phy Auto-negotiation Enabled.";
\r
866 "Phy Auto-negotiation Disabled.";
\r
870 "Phy Auto-negotiation Enabled/Disabled.";
\r
871 reference "[MEF20].";
\r
873 typedef service-entity-type {
\r
893 "MEF Service Entity Type.";
\r
894 reference "[MEF12.2] Section 7.3, Table 3.";
\r
896 typedef l2cp-handling-type {
\r
900 "Discard - An action taken at a L2CP Decision Point " +
\r
901 "where a L2CP frame is neither delivered to a protocol " +
\r
902 "entity, nor delivered to the External Interface " +
\r
903 "where the L2CP Decision Point is located, nor " +
\r
904 "propagated to L2CP Decision Points at other " +
\r
905 "External Interfaces.";
\r
909 "Pass(Tunnel) - An action taken at a L2CP Decision " +
\r
910 "Point where a L2CP frame is either delivered to " +
\r
911 "the External Interface where the L2CP Decision Point " +
\r
912 "is located, or propagated to the L2CP Decision " +
\r
913 "Points located at all other External Interfaces " +
\r
914 "associated by the EVC or OVC.";
\r
918 "Peer - An action taken at a L2CP Decision Point " +
\r
919 "where a L2CP frame is delivered to a protocol " +
\r
920 "entity determined by the Protocol Identifier " +
\r
921 "in the L2CP Frame.";
\r
925 "L2CP Service Frame handling option.";
\r
926 reference "[MEF45] Table 8.";
\r
928 typedef l2cp-address-set-type {
\r
932 "C-VLAN Tag Aware (CTA), for VLAN-based services where" +
\r
933 " the CE-VLAN ID is used to map a frame to a service.";
\r
937 "C-VLAN Tag Blind (CTB), for Port-based services where " +
\r
938 "the CE-VLAN ID is not used to map a frame to a service.";
\r
940 enum "option2-blind-ctb2" {
\r
942 "C-VLAN Tag Blind Option 2 (CTB-2), for point-to-point " +
\r
943 "Port-based services that support the EPL Option 2 " +
\r
944 "L2CP processing.";
\r
948 "The L2CP Address Set Service Attribute specifies the " +
\r
949 "subset of the Bridge Reserved Addresses that are " +
\r
950 "filtered (i.e. L2CP Frames with this destination " +
\r
951 "address are Peered or Discarded but not Passed) " +
\r
952 "at a L2CP Decision Point.";
\r
953 reference "[MEF10.3] Section 9.19. [MEF45] Section 8.1, " +
\r
954 "[R2] through [R9]. [MEF6.2] Section 8.2.2, [R1]. " +
\r
955 "[MEF45] Section 8.1.";
\r
957 typedef l2cp-peering-protocol-type {
\r
969 "Other: Not using LLC nor Ethertype to specify " +
\r
970 "the Protocol ID.";
\r
974 "The Peering Protocol Identifier is one of Ethertype, " +
\r
976 reference "[MEF45] Section 7.";
\r
978 typedef ieee8021p-priority-type {
\r
983 "IEEE 802.1p VLAN Header Class of Service field. Used for " +
\r
984 "Priority Code Point(PCP) configurations.";
\r
985 reference "[MEF10.3] Section 10.2.1.";
\r
987 typedef mef-service-type {
\r
991 "Ethernet Private Line Service (EPL) Point-to-Point " +
\r
992 "EVC, all to one bundling";
\r
996 "Ethernet Virtual Private Line (EVPL) Point-to-Point " +
\r
997 "EVC, bundling and/or multiplexing";
\r
1001 "Ethernet Private LAN Service (EP-LAN) " +
\r
1002 "Multipoint-to-Multipoint EVC, all to one bundling";
\r
1006 "Ethernet Virtual Private LAN Service (EVP-LAN) " +
\r
1007 "Multipoint-to-Multipoint EVC, bundling and/or " +
\r
1012 "Ethernet Private Tree Service (EP-Tree) " +
\r
1013 "Rooted-Multipoint EVC, all to one bundling";
\r
1017 "Ethernet Virtual Private Tree Service (EVP-Tree) " +
\r
1018 "Rooted-Multipoint EVC, bundling and/or multiplexing";
\r
1022 "This object indicates the specific Ethernet service type.";
\r
1024 typedef ext-if-availability-type {
\r
1025 type enumeration {
\r
1028 "In-test is equivalent to the IETF RFC 2883 " +
\r
1029 "ifOperStatus 'testing' state.";
\r
1033 "Failed is to be interpretted along with " +
\r
1034 "Operational State.";
\r
1036 enum "power-off" {
\r
1038 "Power-off indicates the phy is down.";
\r
1042 "Degraded is to be interpretted along with " +
\r
1043 "Operational State..";
\r
1045 enum "not-installed" {
\r
1047 "Not-installed is equivalent to the " +
\r
1048 "IETF RFC 2883 ifOperStatus 'notPresent' state.";
\r
1052 "Availability of the Physical Interface. The " +
\r
1053 "availability status type indicates that the Phy " +
\r
1054 "is functioning properly. May be mapped to " +
\r
1055 "RFC 2863, The Interfaces Group MIB " +
\r
1056 "IfOperstatus. Values for availability status " +
\r
1057 "include: inTest, failed, powerOff, degraded, " +
\r
1059 reference "[ITU-T X.731]. [MEF7.3] Section 10.1.1, " +
\r
1060 "[MEF15], [MEF7.2] Appendix II.";
\r
1062 typedef virt-cx-availability-type {
\r
1063 type enumeration {
\r
1066 "In-test is equivalent to the " +
\r
1067 "IETF RFC 2883 ifOperStatus 'testing' state.";
\r
1071 "Failed is to be interpretted along " +
\r
1072 "with Operational State.";
\r
1076 "Degraded is to be interpretted along " +
\r
1077 "with Operational State..";
\r
1079 enum "not-installed" {
\r
1081 "Not-installed is equivalent to the " +
\r
1082 "IETF RFC 2883 ifOperStatus 'notPresent' state.";
\r
1086 "Availability of the Virtual Connection. The " +
\r
1087 "availability status type indicates that the " +
\r
1088 "Virtual Connection is functioning properly. " +
\r
1089 "May be mapped to RFC 2863, The Interfaces Group MIB " +
\r
1090 "IfOperstatus. Values for availability status include: inTest," +
\r
1091 " failed, powerOff, degraded, notInstalled.";
\r
1092 reference "[ITU-T X.731]. [MEF7.3] Section 10.1.1, " +
\r
1093 "[MEF15], [MEF7.2] Appendix II.";
\r
1095 typedef svc-endpoint-availability-type {
\r
1096 type enumeration {
\r
1099 "In-test is equivalent to the " +
\r
1100 "IETF RFC 2883 ifOperStatus 'testing' state.";
\r
1104 "Failed is to be interpretted along " +
\r
1105 "with Operational State.";
\r
1109 "Degraded is to be interpretted along " +
\r
1110 "with Operational State..";
\r
1112 enum "not-installed" {
\r
1114 "Not-installed is equivalent to the " +
\r
1115 "IETF RFC 2883 ifOperStatus 'notPresent' state.";
\r
1119 "Availability of the Service Endpoint. The " +
\r
1120 "availability status type indicates that the " +
\r
1121 "Service Endpoint is functioning properly. " +
\r
1122 "May be mapped to RFC 2863. The Interfaces Group MIB " +
\r
1123 "IfOperstatus. Values for availability status include: " +
\r
1124 "inTest, failed, powerOff, degraded, notInstalled.";
\r
1125 reference "[ITU-T X.731]. [MEF7.3] Section 10.1.1, " +
\r
1126 "[MEF15], [MEF7.2] Appendix II.";
\r
1128 typedef ext-if-physical-layer-type {
\r
1129 type enumeration {
\r
1132 "10M bits-per-second.";
\r
1136 "100M bits-per-second.";
\r
1140 "1G bits-per-second.";
\r
1144 "10G bits-per-second.";
\r
1148 "40G bits-per-second.";
\r
1152 "100G bits-per-second.";
\r
1156 "The maximum theoretical bandwidth for the phy.";
\r
1157 reference "MEF 7.3 Section 10.1.1, MEF 6.2, MEF 10.3, MEF 26.1";
\r
1159 typedef device-role {
\r
1160 type enumeration {
\r
1162 description "Customer Edge(CE) Access Device";
\r
1165 description "Aggregation Router";
\r
1168 description "Core Router";
\r