Amendment Standard – Inactive – Superseded. This amendment specifies changes to IEEE Std 802.1Q-2005, as amended by IEEE Std 802.1ad-2005, IEEE Std 802.1ag-2007, IEEE Std 802.1ak-2007, IEEE Std 802.1ah-2008, and IEEE Std 802.1ap-2008, that support provisioning systems that explicitly select traffic engineered paths within Provider Backbone Bridged Networks. Changes are applied to the base text of IEEE Std 802.1Q-2005 as amended by IEEE Std 802.1ad-2005, IEEE Std 802.1ak-2007, IEEE Std 802.1ag-2007, IEEE Std 802.1ah-2008, and IEEE Std 802.1ap-2008.

PDF Catalog

PDF Pages	PDF Title
1	IEEE Std 802.1Qay-2009 cover page
3	IEEE Std 802.1Qay-2009 title page
6	Introduction Notice to users Laws and regulations Copyrights Updating of IEEE documents Errata Interpretations
7	Patents
8	Participants
11	CONTENTS
13	List of figures
14	List of tables
15	Important Notice
16	1. Overview 1.1 Scope
17	3. Definitions
19	4. Abbreviations
21	5. Conformance 5.6 S-VLAN component conformance 5.6.2 S-VLAN component requirements for PBB-TE 5.8 B-component conformance 5.8.2 B-component requirements for PBB-TE
22	5.11 Backbone Edge Bridge conformance 5.11.1 Backbone Edge Bridge requirements for PBB-TE
23	6. Support of the MAC Service 6.10 Support of the EISS by Provider Instance Ports 6.10.1 Data indications 6.10.2 Data requests 6.11 Support of the EISS by Customer Backbone Ports 6.19 TE Service Instance Multiplex Entity
25	8. Principles of bridge operation 8.4 Port states and the active topologyActive topologies, learning, and forwarding
26	8.6 The Forwarding Process 8.6.1 Active topology enforcement
27	8.6.2 Ingress filtering 8.6.5 Flow classification and metering 8.6.7 Queue management 8.7 The Learning Process 8.8 The Filtering Database
28	8.8.1 Static Filtering Entries 8.8.8 Querying the Filtering Database
31	8.9 MST and ESP configuration information 8.9.1 MST Configuration Table
32	8.13.11 Connectivity Fault Management entities
33	12. Bridge management 12.6 Forwarding process 12.6.1 Port counters 12.6.1.1.2 Inputs 12.14 CFM entities 12.14.2 CFM Stack managed object 12.14.3 Default MD Level managed object 12.14.3.1.1 Purpose 12.14.3.2 Write Default MD Level managed object 12.14.3.2.1 Purpose
34	12.14.4 Configuration Error List managed object 12.14.4.1 Read Configuration Error List managed object 12.14.4.1.1 Purpose 12.14.4.1.2 Inputs 12.14.5 Maintenance Domain managed object 12.14.5.3.3 Outputs
35	12.14.6 Maintenance Association managed object 12.14.6.3.3 Outputs 12.14.7 Maintenance association End Point managed object
36	12.14.7.3 Transmit Loopback Messages 12.14.7.3.3 Outputs 12.14.7.4 Transmit Linktrace Messages 12.14.7.4.3 Outputs
37	12.16 Backbone Edge Bridge management 12.16.3 VIP configuration managed object 12.16.5 CBP Configuration managed object
38	12.16.5.3 TESI assignment managed object 12.18 PBB-TE Protection Switching managed objects 12.18.1 TE protection group list managed object
40	12.18.2 TE protection group managed object
41	12.18.2.2.2 Inputs 12.18.2.2.3 Outputs
43	17. Management information base (MIB) 17.2 Structure of the MIB 17.2.1 Structure of the IEEE8021-TC-MIB
44	17.2.2 Structure of the IEEE8021-CFM-MIB 17.2.10 Structure of the IEEE8021-PBBTE MIB
47	17.2.10.3 Using the MIB to query and configure protection groups 17.2.10.4 Using the MIB to prevent erroneous forwarding in the PBB-TE network 17.3 Relationships to other MIBs 17.3.10 Relationship of the IEEE8021-PBBTE MIB to other MIB modules
48	17.4 Security Considerations 17.4.10 Security considerations of the IEEE8021-PBBTE MIB
49	17.7 MIB modules 17.7.1 Definitions for the IEEEE8021-TC MIB module
52	17.7.7 Definitions for the CFM MIB modules
61	17.7.8 Definitions for the IEEE8021-PBB-MIB module
64	17.7.10 Definitions for the IEEE8021-PBBTE MIB module
83	18. Principles of Connectivity Fault Management operation
85	19. CFM Entity operation 19.2 Maintenance association End Point 19.2.1 MEP identification
86	19.2.7 MP OpCode Demultiplexer 19.2.8 MEP Continuity Check Receiver
87	19.2.10 MP Loopback Responder 19.3 MIP Half Function 19.3.1 MHF identification 19.3.2 MHF functions 19.3.3 MHF architecture
88	19.4 Maintenance Point addressing
89	20. Connectivity Fault Management protocols 20.1 Continuity Check protocol 20.1.1 MAC status reporting in the CCM
90	20.1.2 Defects and Fault Alarms 20.1.3 CCM reception 20.2 Loopback protocol
91	20.2.1 Loopback Message transmission 20.2.2 Loopback Message reception and Loopback Reply transmission
92	20.3 Linktrace protocol 20.3.1 Linktrace Message origination 20.3.2 Linktrace Message reception, forwarding, and replying
94	20.4 Connectivity Fault Management state machines
95	20.5 CFM state machine timers 20.5.7 mmCCMwhile 20.5.8 mmLocwhile 20.5.9 mmFNGwhile 20.9 MEP variables 20.9.7 MEPprimaryVID
96	20.9.8 presentTraffic 20.9.9 presentmmLoc 20.11 MEP Continuity Check Initiator procedures 20.11.1 xmitCCM() 20.16 MEP Continuity Check Receiver variables 20.16.13 rcvdTrafficBit 20.17 MEP Continuity Check Receiver procedures 20.17.1 MEPprocessEqualCCM()
97	20.25 MEP Mismatch variables 20.25.1 mmCCMreceived 20.25.2 mmCCMdefect 20.25.3 mmCCMTime 20.25.4 disableLocdefect
98	20.25.5 mmLocdefect 20.26 MEP Mismatch state machines
99	20.28 MP Loopback Responder procedures 20.28.1 ProcessLBM()
100	20.28.2 xmitLBR() 20.31 MEP Loopback Initiator transmit procedures 20.31.1 xmitLBM()
101	20.38 MEP Mismatch Fault Notification Generator variables 20.38.1 mfngAllowed 20.38.2 mmdefectIndication 20.38.3 mfngAlarmTime 20.38.4 mfngResetTime 20.39 MEP Mismatch Fault Notification Generator procedures 20.39.1 xmitFaultAlarm() 20.40 MEP Mismatch Fault Notification Generator state machine
103	20.42 MEP Linktrace Initiator procedures 20.42.1 xmitLTM() 20.47 LTM Receiver procedures 20.47.1 ProcessLTM()
104	20.47.1.4 LTM is received by a Down MHF or originated by an Up MEP 20.47.3 ForwardLTM() 20.47.4 enqueLTR()
107	21. Encoding of CFM Protocol Data Units 21.3 CFM request and indication parameters 21.3.1 destination_address parameter 21.5 TLV Format
108	21.6 Continuity Check Message format 21.6.1.4 Traffic field 21.7 Loopback Message and Loopback Reply formats 21.7.4 Optional Additional LBM/LBR TLVs
109	21.7.5 PBB-TE MIP TLV
110	21.8 Linktrace Message Format 21.8.7 Additional LTM TLVs
111	22. CFM in systems 22.1 CFM shims in Bridges 22.1.1 Preliminary positioning of Maintenance Points 22.1.3 Up/Down separation of Maintenance Points
112	22.1.5 Multiple VID service instances 22.1.6 Untagged CFM PDUs
113	22.2 Maintenance Entity creation 22.2.1 Creating Maintenance Domains and Maintenance Associations 22.2.2 Creating MEPs
115	22.2.3 Creating MIPs
116	22.2.4 CFM configuration errors
119	25. Support of the MAC Service by Provider Backbone Bridged Networks 25.10 Support of the MAC Service by a PBB-TE Region
120	25.10.1 Provisioning TE service instances
121	25.10.2 ESP forwarding behavior
123	26. Principles of Provider Backbone Bridged Network Operation 26.4 Backbone addressing 26.4.1 Learning individual backbone addresses at a PIP 26.9 Connectivity Fault Management in a PBB-TE Region 26.9.1 Addressing PBB-TE MEPs 26.9.2 TE service instance identification
124	26.9.3 PBB-TE MEP placement in a Bridge Port 26.9.4 PBB-TE MIP placement in a Bridge Port 26.9.5 TESI Maintenance Domains 26.9.6.1 Continuity Check protocol in a PBB-TE MA
125	26.9.6.2 Loopback protocol in a PBB-TE MA
126	26.9.6.3 Linktrace protocol in a PBB-TE MA
127	26.10 Protection switching for point-to-point TE service instances 26.10.1 Introduction
128	26.10.2 1:1 point-to-point TE service instance protection switching
131	26.10.3 Protection Switching state machines
132	26.10.3.1 Notational conventions used in state diagrams 26.10.3.2 State machine timers 26.10.3.2.1 WTRwhile 26.10.3.2.2 HoldOffWhile 26.10.3.3 Protection Switching variables
133	26.10.3.3.1 BEGIN 26.10.3.3.2 SF 26.10.3.3.3 SFH 26.10.3.3.4 LoP 26.10.3.3.5 FS
134	26.10.3.3.6 MStoProtection 26.10.3.3.7 MStoWorking 26.10.3.3.8 WTRTime 26.10.3.3.9 HoldOffTime 26.10.3.4 Protection Switching procedures 26.10.3.4.1 mapDataToWorking()
135	26.10.3.4.2 mapDataToProtection() 26.10.3.5 Protection Switching state machine diagram
136	26.11 Mismatch defect
139	Annex A (normative) PICS proforma A.5 Major capabilities
140	A.8 Basic Filtering Services A.9 Addressing
141	A.14 Bridge Management
142	A.21 VLAN support A.23 Connectivity Fault Management
143	A.24 Management Information Base (MIB)
144	A.25 Protection Switching
145	Annex H (informative) Bibliography

Published By	Publication Date	Number of Pages
IEEE	2009	145


PDF Format	Searchable	Printable	Preview Now

Standard Title	IEEE Standard for Local and metropolitan area networks– Virtual Bridged Local Area Networks Amendment 10: Provider Backbone Bridge Traffic Engineering
Published Code	IEEE
Publication Date	2009
Pages Count	145

IEEE 802.1Qay 2009

PDF Catalog

Related products

IEEE 802.1Q-2011

IEEE 802.1Q 2011

IEEE 802.1Qay-2009

IEEE 802.1Q-2011:2012 Edition