第1页 / 共1365页
第2页 / 共1365页
第3页 / 共1365页
第4页 / 共1365页
第5页 / 共1365页
第6页 / 共1365页
第7页 / 共1365页
第8页 / 共1365页
IEEE 802.1Q.pdf
Cover
Title page
Introduction
Notice to users
Laws and regulations
Copyrights
Updating of IEEE documents
Errata
Interpretations
Patents
Participants
Historical participants
Contents
Figures
Tables
Important notice
1. Overview
1.1 Scope
1.2 Purpose
1.3 Introduction
1.4 VLAN aims and benefits
2. Normative references
3. Definitions
4. Abbreviations
5. Conformance
5.1 Requirements terminology
5.2 Conformant components and equipment
5.3 Protocol Implementation Conformance Statement (PICS)
5.4 VLAN-aware Bridge component requirements
5.5 C-VLAN component conformance
5.6 S-VLAN component conformance
5.7 I-component conformance
5.8 B-component conformance
5.9 VLAN Bridge conformance
5.10 Provider Bridge conformance
5.11 Backbone Edge Bridge conformance
5.12 VLAN-unaware Bridge component requirements
5.13 TPMR component conformance
5.14 TPMR conformance
5.15 T-component conformance
5.16 End station requirements for MMRP, MVRP, and MSRP
5.17 VLAN-aware end station requirements for Connectivity Fault Management
5.18 End station requirements—forwarding and queuing for time-sensitive streams
5.19 End station requirements for congestion notification
5.20 MAC-specific bridging methods
6. Support of the MAC Service
6.1 Basic architectural concepts and terms
6.2 Provision of the MAC service
6.3 Support of the MAC service
6.4 Preservation of the MAC service
6.5 Quality of service maintenance
6.6 Internal Sublayer Service
6.7 Support of the Internal Sublayer Service by specific MAC procedures
6.8 Enhanced Internal Sublayer Service
6.9 Support of the EISS
6.10 Support of the ISS/EISS by Provider Instance Ports
6.11 Support of the EISS by Customer Backbone Ports
6.12 Protocol VLAN classification
6.13 Support of the ISS for attachment to a Provider Bridged Network
6.14 Support of the ISS within a system
6.15 Support of the ISS by additional technologies
6.16 Filtering services in Bridged Local Area Networks
6.17 EISS Multiplex Entity
6.18 Backbone Service Instance Multiplex Entity
6.19 TESI Multiplex Entity
6.20 Support of the ISS with signaled priority
7. Principles of network operation
7.1 Network overview
7.2 Use of VLANs
7.3 VLAN topology
7.4 Locating end stations
7.5 Ingress, forwarding, and egress rules
8. Principles of bridge operation
8.1 Bridge operation
8.2 Bridge architecture
8.3 Model of operation
8.4 Active topologies, learning, and forwarding
8.5 Bridge Port Transmit and Receive
8.6 The Forwarding Process
8.7 The Learning Process
8.8 The Filtering Database
8.9 MST and ESP configuration information
8.10 Spanning Tree Protocol Entity
8.11 MRP Entities
8.12 Bridge Management Entity
8.13 Addressing
9. Tagged frame format
9.1 Purpose of tagging
9.2 Representation and encoding of tag fields
9.3 Tag format
9.4 Tag Protocol Identifier (TPID) formats
9.5 Tag Protocol Identification
9.6 VLAN Tag Control Information
9.7 Backbone Service Instance Tag Control Information
10. Multiple Registration Protocol (MRP) and Multiple MAC Registration Protocol (MMRP)
10.1 MRP overview
10.2 MRP architecture
10.3 MRP Attribute Propagation (MAP)
10.4 Requirements to be met by MRP
10.5 Requirements for interoperability between MRP Participants
10.6 Protocol operation
10.7 Protocol specification
10.8 Structure and encoding of MRP Protocol Data Units
10.9 Multiple MAC Registration Protocol (MMRP)—Purpose
10.10 Model of operation
10.11 Default Group filtering behavior and MMRP propagation
10.12 Definition of the MMRP application
11. VLAN topology management
11.1 Static and dynamic VLAN configuration
11.2 Multiple VLAN Registration Protocol
12. Bridge management
12.1 Management functions
12.2 VLAN-aware bridge objects
12.3 Data types
12.4 Bridge Management Entity
12.5 MAC entities
12.6 Forwarding process
12.7 Filtering Database
12.8 Bridge Protocol Entity
12.9 MRP Entities
12.10 Bridge VLAN managed objects
12.11 MMRP entities
12.12 MST configuration entities
12.13 Provider Bridge management
12.14 CFM entities
12.15 Backbone Core Bridge management
12.16 Backbone Edge Bridge management
12.17 DDCFM entities
12.18 PBB-TE Protection Switching managed objects
12.19 TPMR managed objects
12.20 Management entities for forwarding and queueing for time-sensitive streams
12.21 Congestion notification managed objects
12.22 SRP entities
13. Spanning Tree Protocols
13.1 Protocol design requirements
13.2 Protocol support requirements
13.3 Protocol design goals
13.4 RSTP overview
13.5 MSTP overview
13.6 Compatibility and interoperability
13.7 MST Configuration Identifier
13.8 Spanning Tree Priority Vectors
13.9 CIST Priority Vector calculations
13.10 MST Priority Vector calculations
13.11 Port Role assignments
13.12 Stable connectivity
13.13 Communicating Spanning Tree information
13.14 Changing Spanning Tree information
13.15 Changing Port States with RSTP or MSTP
13.16 Managing spanning tree topologies
13.17 Updating learned station location information
13.18 Managing reconfiguration
13.19 Partial and disputed connectivity
13.20 In-service upgrades
13.21 Fragile bridges
13.22 Spanning tree protocol state machines
13.23 State machine timers
13.24 Per bridge variables
13.25 Per port variables
13.26 State machine conditions and parameters
13.27 State machine procedures
13.28 The Port Timers state machine
13.29 Port Receive state machine
13.30 Port Protocol Migration state machine
13.31 Bridge Detection state machine
13.32 Port Transmit state machine
13.33 Port Information state machine
13.34 Port Role Selection state machine
13.35 Port Role Transitions state machine
13.36 Port State Transition state machine
13.37 Topology Change state machine
13.38 Layer 2 Gateway Port Receive state machine
13.39 Customer Edge Port Spanning Tree operation
13.40 Virtual Instance Port Spanning Tree operation
14. Use of BPDUs by MSTP
14.1 BPDU Structure
14.2 Encoding of parameter types
14.3 BPDU formats and parameters
14.4 Validation of received BPDUs
14.5 Transmission of BPDUs
14.6 Encoding and decoding of STP Configuration, RST, and MST BPDUs
15. Support of the MAC Service by Provider Bridged Networks
15.1 Service transparency
15.2 Customer service interfaces
15.3 Port-based service interface
15.4 C-tagged service interface
15.5 S-tagged service interface
15.6 Service instance segregation
15.7 Service instance selection and identification
15.8 Service priority selection
15.9 Service access protection
15.10 Connectivity Fault Management
15.11 Data-driven and data-dependent connectivity fault management (DDCFM)
16. Principles of Provider Bridged Network operation
16.1 Provider Bridged Network overview
16.2 Provider Bridged Network
16.3 Service instance connectivity
16.4 Service provider learning of customer end station addresses
16.5 Detection of connectivity loops through attached networks
16.6 Network management
17. Management Information Base (MIB)
17.1 Internet Standard Management Framework
17.2 Structure of the MIB
17.3 Relationship to other MIBs
17.4 Security considerations
17.5 Dynamic component and Port creation
17.6 MIB operations for service interface configuration
17.7 MIB modules
18. Principles of Connectivity Fault Management operation
18.1 Maintenance Domains and Domain Service Access Points
18.2 Service instances and Maintenance Associations
18.3 Maintenance Domain Levels
19. Connectivity Fault Management Entity operation
19.1 Maintenance Points
19.2 Maintenance association End Point
19.3 MIP Half Function
19.4 Maintenance Point addressing
19.5 Linktrace Output Multiplexer
19.6 Linktrace Responder
20. Connectivity Fault Management protocols
20.1 Continuity Check protocol
20.2 Loopback protocol
20.3 Linktrace protocol
20.4 Connectivity Fault Management state machines
20.5 CFM state machine timers
20.6 CFM procedures
20.7 Maintenance Domain variable
20.8 Maintenance Association variables
20.9 MEP variables
20.10 MEP Continuity Check Initiator variables
20.11 MEP Continuity Check Initiator procedures
20.12 MEP Continuity Check Initiator state machine
20.13 MHF Continuity Check Receiver variables
20.14 MHF Continuity Check Receiver procedures
20.15 MHF Continuity Check Receiver state machine
20.16 MEP Continuity Check Receiver variables
20.17 MEP Continuity Check Receiver procedures
20.18 MEP Continuity Check Receiver state machine
20.19 Remote MEP variables
20.20 Remote MEP state machine
20.21 Remote MEP Error variables
20.22 Remote MEP Error state machine
20.23 MEP Cross Connect variables
20.24 MEP Cross Connect state machine
20.25 MEP Mismatch variables
20.26 MEP Mismatch state machines
20.27 MP Loopback Responder variables
20.28 MP Loopback Responder procedures
20.29 MP Loopback Responder state machine
20.30 MEP Loopback Initiator variables
20.31 MEP Loopback Initiator transmit procedures
20.32 MEP Loopback Initiator transmit state machine
20.33 MEP Loopback Initiator receive procedures
20.34 MEP Loopback Initiator receive state machine
20.35 MEP Fault Notification Generator variables
20.36 MEP Fault Notification Generator procedures
20.37 MEP Fault Notification Generator state machine
20.38 MEP Mismatch Fault Notification Generator variables
20.39 MEP Mismatch Fault Notification Generator procedures
20.40 MEP Mismatch Fault Notification Generator state machine
20.41 MEP Linktrace Initiator variables
20.42 MEP Linktrace Initiator procedures
20.43 MEP Linktrace Initiator receive variables
20.44 MEP Linktrace Initiator receive procedures
20.45 MEP Linktrace Initiator receive state machine
20.46 Linktrace Responder variables
20.47 LTM Receiver procedures
20.48 LTM Receiver state machine
20.49 LTR Transmitter procedure
20.50 LTR Transmitter state machine
20.51 CFM PDU validation and versioning
20.52 PDU identification
20.53 Use of transaction IDs and sequence numbers
21. Encoding of CFM Protocol Data Units
21.1 Structure, representation, and encoding
21.2 CFM encapsulation
21.3 CFM request and indication parameters
21.4 Common CFM Header
21.5 TLV Format
21.6 Continuity Check Message format
21.7 Loopback Message and Loopback Reply formats
21.8 Linktrace Message Format
21.9 Linktrace Reply Format
22. Connectivity Fault Management in systems
22.1 CFM shims in Bridges
22.2 Maintenance Entity creation
22.3 MPs, Ports, and MD Level assignment
22.4 Stations and Connectivity Fault Management
22.5 Scalability of Connectivity Fault Management
22.6 CFM in Provider Bridges
22.7 Management Port MEPs and CFM in the enterprise environment
22.8 Implementing CFM on existing Bridges
23. MAC status propagation
23.1 Model of operation
23.2 MAC status protocol (MSP) overview
23.3 MAC status protocol state machines
23.4 State machine timers
23.5 MSP performance parameters
23.6 State machine variables
23.7 State machine procedures
23.8 Status Transition state machine
23.9 Status Notification state machine
23.10 Receive Process
23.11 Transmit Process
23.12 Management of MSP
23.13 MSPDU transmission, addressing, and protocol identification
23.14 Representation and encoding of octets
23.15 MSPDU structure
23.16 Validation of received MSPDUs
23.17 Other MSP participants
24.
25. Support of the MAC Service by Provider Backbone Bridged Networks
25.1 Service transparency
25.2 Customer service interface
25.3 Port-based service interface
25.4 S-tagged service interface
25.5 I-tagged service interface
25.6 Service instance segregation
25.7 Service instance selection and identification
25.8 Service priority and drop eligibility selection
25.9 Service access protection
25.10 Support of the MAC Service by a PBB-TE Region
25.11 Transparent service interface
26. Principles of Provider Backbone Bridged Network operation
26.1 Provider Backbone Bridged Network overview
26.2 Provider Backbone Bridged Network example
26.3 Backbone VLAN connectivity
26.4 Backbone addressing
26.5 Detection of connectivity loops through attached networks
26.6 Scaling of Provider Backbone Bridges
26.7 Network Management
26.8 Connectivity Fault Management in Provider Backbone Bridges
26.9 Connectivity Fault Management in a PBB-TE Region
26.10 Protection switching for point-to-point TESIs
26.11 Mismatch defect
27.
28.
29. DDCFM operations and protocols
29.1 Principles of DDCFM operation
29.2 DDCFM Entity operation
29.3 DDCFM protocols
29.4 Encoding of DDCFM Protocol Data Units
30. Principles of congestion notification
30.1 Congestion notification design requirements
30.2 Quantized Congestion Notification protocol
30.3 Congestion Controlled Flow
30.4 Congestion Notification Priority Value
30.5 Congestion Notification Tag
30.6 Congestion Notification Domain
30.7 Multicast data
30.8 Congestion notification and additional tags
31. Congestion notification entity operation
31.1 Congestion aware Bridge Forwarding Process
31.2 Congestion aware end station functions
32. Congestion notification protocol
32.1 Congestion Notification Domain operations
32.2 CN component variables
32.3 Congestion notification per-CNPV variables
32.4 CND defense per-Port per-CNPV variables
32.5 Congestion Notification Domain defense procedures
32.6 Congestion Notification Domain defense state machine
32.7 Congestion notification protocol
32.8 Congestion Point variables
32.9 Congestion Point procedures
32.10 Reaction Point per-Port per-CNPV variables
32.11 Reaction Point group variables
32.12 Reaction Point timer
32.13 Reaction Point variables
32.14 Reaction Point procedures
32.15 RP rate control state machine
32.16 Congestion notification and encapsulation interworking function
33. Encoding of congestion notification Protocol Data Units
33.1 Structure, representation, and encoding
33.2 Congestion Notification Tag format
33.3 Congestion Notification Message
33.4 Congestion Notification Message PDU format
34. Forwarding and queuing for time-sensitive streams
34.1 Overview
34.2 Detection of SRP domains
34.3 The bandwidth availability parameters
34.4 Deriving actual bandwidth requirements from the size of the MSDU
34.5 Mapping priorities to traffic classes for time-sensitive streams
34.6 End station behavior
35. Stream Registration Protocol (SRP)
35.1 Multiple Stream Registration Protocol (MSRP)
35.2 Definition of the MSRP application
Annex A (normative) PICS proforma—Bridge implementations
Annex B (normative) PICS proforma—End station implementations
Annex C (normative) DMN (Designated MSRP Node) Implementations
Annex D (normative) IEEE 802.1 Organizationally Specific TLVs
Annex E (normative) Notational conventions used in state diagrams
Annex F (informative) Shared and Independent VLAN Learning
Annex G (informative) MAC method dependent aspects of VLAN support
Annex H (informative) Interoperability considerations
Annex I (informative) Priority and drop precedence
Annex J (informative) Connectivity Fault Management protocol design and use
Annex K (informative) TPMR use cases
Annex L (informative) Operation of the credit-based shaper algorithm
Annex M (informative) Bibliography
IEEE Standard for
Local and metropolitan area networks—
Media Access Control (MAC) Bridges and
Virtual Bridge Local Area Networks
IEEE Computer Society
Sponsored by the
LAN/MAN Standards Committee
IEEE
3 Park Avenue
New York, NY 10016-5997
USA
31 August 2011
IEEE Std 802.1Q™Ǧ2011
(Revision of
IEEE Std 802.1Q-2005)
IEEE Std 802.1Q™-2011
(Revision of
IEEE Std 802.1Q-2005)
IEEE Standard for
Local and metropolitan area networks—
Media Access Control (MAC) Bridges and
Virtual Bridged Local Area Networks
Sponsor
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 16 May 2011
IEEE-SA Standards Board
Abstract: This standard specifies how the MAC Service is supported by Virtual Bridged Local Area
Networks, the principles of operation of those networks, and the operation of VLAN-aware Bridges,
including management, protocols, and algorithms.
Keywords: Bridged Local Area Networks, local area networks (LANs), MAC Bridges, metropolitan
area networks, Multiple Spanning Tree Protocol (MSTP), Rapid Spanning Tree Protocol (RSTP),
Virtual Bridged Local Area Networks (virtual LANs)
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
Copyright © 2011 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 31 August 2011. Printed in the United States of America.
IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and
Electronics Engineers, Incorporated.
ISBN 978-0-7381-6708-4
PDF:
Print:
ISBN 978-0-7381-6709-1
IEEE prohibits discrimination, harassment and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
STD97139
STDPD97139
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of
the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus
development process, approved by the American National Standards Institute, which brings together volunteers
representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the
Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote
fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of
any of the information contained in its standards.
Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other
damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly
resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document.
The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims
any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or
that the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied
“AS IS.”
The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase,
market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint
expressed at the time a standard is approved and issued is subject to change brought about through developments in the
state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least
every five years for revision or reaffirmation, or every ten years for stabilization. When a document is more than five
years old and has not been reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to conclude
that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to
check to determine that they have the latest edition of any IEEE Standard.
In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services
for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or
entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon his or her
independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of
a competent professional in determining the appropriateness of a given IEEE standard.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to
specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate
action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is
important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason,
IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant
response to interpretation requests except in those cases where the matter has previously received formal consideration.
A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual
shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be
relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an individual
presenting information on IEEE standards shall make it clear that his or her views should be considered the personal
views of that individual rather than the formal position, explanation, or interpretation of the IEEE.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation
with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Recommendations to change the status of a stabilized standard should include a
rationale as to why a revision or withdrawal is required. Comments on standards and requests for interpretations should
be addressed to:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854-4141
USA
Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of
Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To
arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,
Danvers, MA 01923 USA; (978) 750-8400. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.
Introduction
This introduction is not part of IEEE Std 802.1Q-2011, IEEE Standard for Local and metropolitan area networks—
Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks.
The MAC Bridge standardization activities that resulted in the development of IEEE Std 802.1D™, 1993
Edition [B9],a introduced the concept of Filtering Services in Bridged Local Area Networks, and
mechanisms whereby filtering information in such LANs may be acquired and held in a Filtering Database.
IEEE Std 802.1D, 1998 Edition, a revision of IEEE Std 802.1D, 1993 Edition, extended this concept of
Filtering Services to define additional capabilities aimed at
a)
b)
c)
d)
The provision of expedited traffic capabilities, to support the transmission of time-critical
information in a LAN environment.
The use of signaled priority information as the basis for identifying expedited classes of traffic.
The provision of filtering services that support the dynamic definition and establishment of Groups
in a LAN environment, and the filtering of frames by Bridges such that frames addressed to a
particular Group are forwarded only on those LANs that are required to reach members of that
Group.
The provision of a Generic Attribute Registration Protocol (GARP) that is used to support the
mechanism for providing Group filtering capability and is made available for use in other attribute
registration applications.
This standard, first published as IEEE Std 802.1Q-1998, makes use of the concepts and mechanisms of LAN
Bridging that were introduced by IEEE Std 802.1D, and it defines additional mechanisms that allow the
implementation of Virtual Bridged Local Area Networks. The following mechanisms are described:
e) Virtual LAN Services.
f)
g)
h)
The operation of the Forwarding Process that is required.
The structure of the Filtering Database that is required.
The nature of the protocols and procedures that are required to provide Virtual LAN services,
including the definition of the frame formats used to represent VLAN identification information,
and the procedures used to insert and remove VLAN identifiers (VIDs) and the headers in which
they are carried.
The ability to support end-to-end signaling of priority information regardless of the intrinsic ability
of the underlying MAC protocols to signal priority information.
The management services and operations that are required to configure and administer networks.
i)
j)
The 2005 Revision of the standard incorporated three amendments, IEEE Std 802.1u™-2001,
IEEE Std 802.1v™-2001, and IEEE Std 802.1s™-2002, into the text of IEEE Std 802.1Q-1998. These
amendments describe enhancements to the standard to allow
k) Dynamic Group and VLAN registration to be restricted, based on the contents of static filtering
entries.
VLAN classification according to link layer protocol type.
l)
m) Support for VLANs carried over multiple Spanning Tree instances.
aNumbers in brackets correspond to the number in the bibliography in Annex M.
iv
Copyright © 2011 IEEE. All rights reserved
This revision of the standard incorporates amendments IEEE Std 802.1ad™-2005, IEEE Std 802.1ak™-
2007, IEEE Std 802.1ag™-2007, IEEE Std 802.1ah™-2008, IEEE Std 802-1Q-2005/Cor-1-2008,
IEEE Std 802.1ap™-2008, IEEE Std 802.1Qaw™-2009, IEEE Std 802.1Qay™-2009, IEEE Std 802.1aj™-
2009, IEEE Std 802.1Qav™-2009, IEEE Std 802.1Qau™-2010, and IEEE Std 802.1Qat™-2010 into the
text of IEEE Std 802.1Q-2005. These amendments describe enhancements to the standard to allow
o)
p)
q)
n) A service provider to use the architecture and protocols defined in this standard to offer the
equivalent of separate LANs, Bridged Local Area Networks, or Virtual Bridged Local Area
Networks to a number of customers, while requiring no cooperation between the customers, and
minimal cooperation between each customer and the service provider.
The distribution and registration of VLAN membership information using the Multiple VLAN
Registration Protocol (MVRP), and the distribution of group membership information using the
Multiple MAC Registration Protocol (MMRP), replacing the previous protocols, GVRP and GMRP.
Support of Connectivity Fault Management (CFM) capabilities for detecting, isolating, and
reporting connectivity faults.
Interconnection of multiple Provider Bridged Networks, allowing a Provider to support up to 224
service instances.
r) Management of VLAN Bridges via SNMP MIB modules.
s)
t)
u)
v)
w)
Diagnosis of data-dependent connectivity faults.
Support for traffic engineering.
The use of Bridging technology as a two-port MAC relay.
Support for the relay of time sensitive data streams.
Support for congestion management of long-lived data flows within network domains of limited
bandwidth-delay product. This is achieved by enabling bridges to signal congestion to end stations
capable of transmission rate limiting to avoid frame loss.
x) Network resources to be reserved for specific traffic streams traversing a bridged local area network.
y)
The use of IEEE 802.17™ and IEEE 802.20™ media in bridged local area networks.
As part of this revision of the standard, Clause 13 was extensively revised in order to integrate the
description of the Rapid Spanning Tree Protocol (RSTP) into the text of the standard rather than including it
by reference to IEEE Std 802.1D.
This standard contains state-of-the-art material. The area covered by this standard is undergoing evolution.
Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, and
to incorporate new related material. Information on the current revision state of this and other IEEE 802
standards may be obtained from
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854-4141
USA
Notice to users
Laws and regulations
Users of these documents should consult all applicable laws and regulations. Compliance with the
provisions of this standard does not imply compliance to any applicable regulatory requirements.
Implementers of the standard are responsible for observing or referring to the applicable regulatory
requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in
compliance with applicable laws, and these documents may not be construed as doing so.
Copyright © 2011 IEEE. All rights reserved.
v
相关推荐
2023年江西萍乡中考道德与法治真题及答案.doc
2012年重庆南川中考生物真题及答案.doc
2013年江西师范大学地理学综合及文艺理论基础考研真题.doc
2020年四川甘孜小升初语文真题及答案I卷.doc
2020年注册岩土工程师专业基础考试真题及答案.doc
2023-2024学年福建省厦门市九年级上学期数学月考试题及答案.doc
2021-2022学年辽宁省沈阳市大东区九年级上学期语文期末试题及答案.doc
2022-2023学年北京东城区初三第一学期物理期末试卷及答案.doc
2018上半年江西教师资格初中地理学科知识与教学能力真题及答案.doc
2012年河北国家公务员申论考试真题及答案-省级.doc
2020-2021学年江苏省扬州市江都区邵樊片九年级上学期数学第一次质量检测试题及答案.doc
2022下半年黑龙江教师资格证中学综合素质真题及答案.doc
