[Local Address Study Group] . [802 Architecture Group] . [Data Center Bridging Task Group] [Time-Sensitive Networking Task Group]
[Email] . [Ancient Email] . [802.1 MIBs] . [802.1 OIDs] . [IEEE 802] . [IEEE 802 PARs]
TSN:  . [802a] . [802b] . [802.1D] . [802.1D-2004] . [802.1G] . [802.1H-REV] . [802.1Q] . [802.1Q-2014] . [802.1s] . [802.1v] . [802.1w] . [802.1AB-2005] . [802.1AB-2009] . [802.1AC-2012] . [802.1AC-2016] . [802.1ad] . [802.1ag] . [802.1ah] . [802.1aj] . [802.1ak] . [802.1ap] . [802.1aq] . [802.1Qaw] . [802.1AX-2008] . [802.1Qay] . [802.1Qbc] . [802.1Qbe] . [802.1Qbf] . [802.1AXbk] . [802.1Qbp] . [802.1AX-2014] . [802.1AX-Rev] . [802.1Qbz] . [802.1Qca]
[802.1AS] . [802.1AS-Rev] . [802.1Qat] . [802.1Qav] . [802.1BA] . [802.1Qbu] . [802.1Qbv] . [802.1CB] . [802.1Qcc] . [802.1Qch] . [802.1CM] . [802.1Qcn] . [802.1Qcp] . [802.1Qcr]
Security: [802.1X-2001] . [802.1X-2004] . [802.1X-2010] . [802.1AE] . [802.1af] . [802.1AR] . [802.1AEbn] . [802.1AEbw] . [802.1Xbx] . [802.1ARce] . [802.1AEcg] . [802.1Xck] . [802E]
DCB: [802.1Qau] . [802.1Qaz] . [802.1Qbb] . [802.1Qbg] . [802.1Qbh] . [802.3bd] . [802.1BR] . [802.1Qcd] . [802.1Qcj] . [802c] . OmniRAN: [802.1CF]
The full title of this PAR is "IEEE Standard for Local and Metropolitan Area Networks---Virtual Bridged Local Area Networks - Amendment: Provider Bridging - Remote Customer Service Interfaces".
This standard allows a service-tagged (S-tagged) service interface connecting two independently administered Provider Bridged Networks to be used to handle traffic (identified by a single service virtual local area network (S-VLAN) identifier) for a given customer port attached to one provider backbone network (PBN) as if the customer were directly attached to the other PBN using a Port-based or customer tagged (C-tagged) service interface.
Metro Ethernet service providers need to provide service to customer locations not directly accessible to their network. Such "out-of-footprint" access may be obtained via other (access) service providers; however, the primary service provider has an interest in minimizing the amount of provisioning required of an access provider. This standard meets this need by specifying Provider Bridging technology that allows the primary service provider to treat customers connected via an access network as if they were directly connected to the primary service provider's network.
Metro Ethernet service providers need standardized Provider Bridge functionality that allows customers connected via an independently operated access network to be provided service as if they were directly connected to the service provider's network.
|PAR||PAR approved Sep 11th, 2009|
|Status||Standard approved Jun 16th, 2011.|
|22 Oct 2009||802.1Qbc, Editor's draft 0.0|
|18 Nov 2009||802.1bc, Draft 0.0 proposed comment dispositions|
|19 Nov 2009||802.1bc, Draft 0.0 comment dispositions|
|19 Dec 2009||802.1bc, Draft 1.0|
|19 Jan 2010||802.1bc, Draft 1.0 proposed comment dispositions|
|26 Feb 2010||802.1bc, Draft 1.1|
|15 Mar 2010||802.1bc, Draft 1.1 proposed comment dispositions|
|16 Mar 2010||802.1bc, Draft 1.1 comment dispositions|
|21 Apr 2010||802.1bc, Draft 1.2|
|24 May 2010||802.1bc, Draft 1.2 proposed comment dispositions|
|25 May 2010||802.1bc, Draft 1.2 comment dispositions|
|16 Jun 2010||802.1bc, Draft 1.3|
|12 Jul 2010||802.1bc, Draft 1.3 proposed comment dispositions|
|15 Jul 2010||802.1bc, Draft 1.3 comment dispositions|
|14 Sep 2010||802.1bc, Draft 1.3 comment dispositions|
|06 Oct 2010||802.1bc, Draft 1.4|
|07 Apr 2011||802.1bc, Draft 1.5|
|18 Nov 2009||Presentation bc-mackcrane-editor-report-1109.pdf|
Pages copyright © Institute of Electrical and Electronics Engineers, Inc. Please read the rules on Confidentiality Statements and Copyright Notices on Communications. Information on Privacy and opting out of cookies is available. If you have any comments on these pages, please send them to me.