1 / 28

IEEE 802.1ah First Draft

IEEE 802.1ah First Draft. Paul Bottorff March 14, 2005. 06. 05. 07. N. N. N. D. D. D. J. J. J. O. F. F. F. M. M. M. A. A. A. M. M. M. J. J. J. J. A. A. S. S. Legend 802 Plenary 802.1 Interim IEEE-SA Standards Board.

xerxes
Download Presentation

IEEE 802.1ah First Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IEEE 802.1ah First Draft Paul Bottorff March 14, 2005

  2. 06 05 07 N N N D D D J J J O F F F M M M A A A M M M J J J J A A S S Legend 802 Plenary 802.1 Interim IEEE-SA Standards Board P802.1ah - Provider Backbone Bridges –Targeted Timeline WG ballot Sponsor ballot Task Force Proposals TF ballot Standard! PAR D1.0 D1.5 D2.0 D2.5 D3.0 D4.0

  3. Provider Backbone Bridge Network (802.1ah) Provider Bridge Network (802.1ad) Provider Bridge Network (802.1ad) IEEE 802.1ah (Provider Backbone Bridge) Context 802.1ad Interfaces Provider Bridge Network (802.1ad) 802.1aj CFM(802.1ag) Runs End-to-end MRP(802.1ak) Runs in 802.1ad & 802.1ah

  4. Draft 0 Content • Draft 0 available at: http://www.ieee802.org/1/files/private/ah-drafts/d0 • Much of P802.1ad is included within editor’s notes • Added clauses 23, 24, and 25 • Clause 23: Support of the MAC Service by Provider Backbone Bridged Networks • Clause 24: Principles of Provider Backbone Bridged network operation • Clause 25: Principles of Provider Backbone Bridge operation • Clause 1 contains some suggestions for scope • Clause 3/4 contains new Provider Backbone Bridge definitions and acronyms • Clause 9 contains I-TAG VCI format

  5. Open items in Draft 0 • Clause 5: Conformance statement • Clause 12: Management for PBB bridges • Clause 23: • Port based interface description • I-Frame based interface description • Clause 24: • Interaction of Provider Backbone Edge Bridges with Provider Bridge spanning trees • Operation of Provider Backbone Bridge spanning trees • Clause 25: • Details of I Component and B Component operation • Operation of address correlation data base • Informative annex on an integrated C-VLAN aware component

  6. Backup Slides

  7. PB Provider Backbone Bridge Network (PBBN) PB PB PBB PBB PB PB PBB PBB • PB: Provider Bridge (as defined by 802.1ad) • PBB: Provider Backbone Bridge Edge (as defined by 802.1ah)

  8. PBB PB PEB PB PB PB PB PB PB PB PB PEB CE CE CE CE CE PBB PBB B B B B B B B B P A C A D D C C C A P P P P P A D C D P D A P B P PB PBB PBB Provider Edge Bridge Provider Backbone Bridge Provider Network Example Customer Equipment Provider Bridged Network Provider Backbone Bridged Network Legend: Customer LAN Boundary LAN Access LAN Provider LAN Backbone LAN Customer Equipment Provider Bridge Provider Network Port Customer Network Port

  9. PBBN Provides Multi-Point tunnels between PBNs PBN PBN B-VLANX PBB S-VLAN4 BBN PBB S-VLAN3 PBB PBN PBB PBB PBB B-VLANY PBN S-VLAN2 S-VLAN1 • BB PB: Provider Backbone Bridge Edge • Each B-VLAN carries many S-VLANs • S-VLANs may be carried on a subset of a B-VLAN (i.e. all P-P S-VLANs could be carried on a single MP B-VLAN providing connection to all end points.

  10. Agreed Terminology • IEEE 802.1ad Terminology • C-TAG Customer VLAN TAG • C-VLAN Customer VLAN • C-VID Customer VLAN ID • S-TAG Service VLAN TAG • S-VLAN Service VLAN • S-VID Service VLAN ID • Additional Provider Backbone Bridge Terminology • I-TAG Extended Service TAG • I-SID Extended Service ID • C-MAC Customer MAC Address • B-MAC Backbone MAC Address • B-VLAN Backbone VLAN (tunnel) • B-TAG Backbone TAG Field • B-VID Backbone VLAN ID (tunnel)

  11. Extended Service VLAN IDs In Backbone B-VLANX S-VID32 BB PB S-VLAN4 S-VID41 BBN S-VLAN3 I-SID4 BB PB S-VID33 BB PB I-SID3 BB PB S-VID31 BB PB BB PB B-VLANY S-VID42 S-VLAN1 S-VLAN2 • BB PB: Provider Backbone Bridge Edge • An I-SID uniquely identifies a S-VLAN within the Backbone • The MAP Shim translates between S-VID and I-SID • The I-SID to(from) S-VID mapping is provisioned when a new service instance is created

  12. Single I-SID per S-VLAN S-VID2 BB PB • Regardless of the I-SID address size the map tables only have 4096 entries since only one I-SID exists per S-VLAN and only 4096 S-VLANs exist per Provider Bridge. • A different S-VID in each PBN maps to the I-SID BBN S-VID3 BB PB BB PB I-SID S-VID1 BB PB

  13. Site Connectivity B-VLAN ID B-VLANX BB PB S-VLAN4 • B-VLANs are addressed like regular VLANs with a 12 bit B-VID • B-VID and I-SID need to be separate ID spaces to allow many S-VLANs to be carried in a single B-VLAN BBN BB PB S-VLAN3 BB PB BB PB BB PB BB PB B-VLANY S-VLAN2 S-VLAN1

  14. Frame Frame Frame Backbone POP MAC Address BB PB • B-MAC Addresses identify the Edge Provider Backbone Bridges (BB PB) • B-MAC Addresses are learned by other Edge Backbone Edge Bridges • The backbone edge MAC address determines which edge on the B-VLAN will receive the frame. • Frames may be flooded by sending with broadcast or multicasts DA B-MACs to the B-VLAN. • Map shims filter based on the I-SID removing any misaddressed frames BBN BB PB B-MAC4 BB PB DA <- B-MAC4 SA <- B-MAC1 B-MAC1 BB PB

  15. MAP Shim Correlation Table Provisioned Provider Addresses Customer Addresses • In the beginning the MAP Shim is provisioned with the correlation between the S-VID, I-SID, and B-VID • During operation the MAP Shim learns both B-MAC addresses and C-MAC addresses • The MAP Shim keeps track of which C-MAC addresses are behind which B-MAC • The correlation data is used to encapsulate frames from the PBNs

  16. PB QB QB PB QB QB QB QB QB QB PB BB PB QB QB PB PB BB Customer, PB, BB Spanning Trees Customer Spanning Trees • Customer spanning trees may extend over Provider Network • PB Network and BB Network spanning trees must be decoupled to scale the provider network • Provider Backbone Bridge may conform to the requirements for an Interconnect Medium PB-BB PB-BB PB PB PB PB PB-BB PB Spanning Trees PB Spanning Trees BB Spanning Trees

  17. Relay MCF Relay MAC (802.3) MCF MAC (802.3) PBB Shim Functions 802.1ad • S-Shim Operations • Maps S-VID from 802.1ad into larger Extended Service VID (I-SID) • Filters L2 control packets sourced by core relays or by provider bridge relays (divides spanning trees) MIF MIF 802.1ad PB PBB S-shim MIF MIF BB PBB T-shim • T-Shim Operations • Does encap/decap of 802.1ad frame • Learns and Correlates Backbone POP and Customer MAC addresses • Filters L2 control packets sourced by core relays or by provider bridge relays (divides spanning trees) Virtual MAC Backbone Edge

  18. Ethernet Service TypesMEF Ethernet Virtual Connections (EVCs) Pt-Pt, Like Duplex Ethernet Any-to-any E-LINE Router Mesh Pt-MPt, Like EPON Ethernet, Root-to-Leaf and Leaf-to-Root E-TREE Hub & Spoke E-LAN Multi-Site MPt, Like VLAN, Any-to-any

  19. E-LINE Dominates Today • E-LINE is a natural leased line replacement for subscribers • Ethernet leased lines offer high bandwidth • Lines provide bandwidth on demand • Interfaces are compatible with off the shelf Ethernet switches/routers • Best for router mesh • E-LINE provides natural migration for carriers • Consistent with current operations model • Allows carrier equipment reductions • Bill models can follow well understood FR services • Current QoS models allow both traffic control and service monitoring of E-LINE service offerings • Service OAM models for E-LINE are relatively straightforward • Each E-LINE service instance requires 1 S-VLAN

  20. E-TREE Ideal For ISP Connect • E-TREE Future Service With Great Promise • Useful as a multiplexed connection to an application service provider like an ISP • Service is unlike traditional Ethernet since leaf nodes can not talk with each other • E-TREE has deployment issues • No clear billing model • For instance if one leaf is disconnected is the circuit down? • What is the distance of the tree? • OAM management not fully understood • QoS model non-existant, SLAs can only provide Best Effort

  21. E-TREE S-VLAN Mapping • Each E-TREE service instance requires 2 S-VLANs • Both S-VLANs comprising an E-TREE S-VLANs are unidirectional • The S-VLANs of and E-TREE service instance are typically on the multiplexed on the same port Pt-MPt, Like EPON Ethernet, Root-to-Leaf and Leaf-to-Root E-TREE Hub & Spoke Hub Port Spoke Ports

  22. Some Carriers Will Use E-LINE in Hub and Spoke Arrangement • Hub port would usually be multipexed to allow the multiple Pt-Pt attachments. • Each E-LINE is a seperate managed S-VLAN • This arrangement allows use of E-LINE management, billing, and QoS • Many more S-VLANs are required Pt-Pt Root-to-Leaf and Leaf-to-Root E-LINE Hub & Spoke Hub Port Spoke Ports

  23. E-LAN Many Future Applications • E-LAN is deployed for broad connectivity in select network • Interconnect of multiple corporate sites • Multi-player gaming • Ubiquitous any-to-any connectivity • E-LAN has many future applications • E-LAN has deployment issues • Deployments are very spotty • Unclear billing model • How is availability defined? • No definitions for QoS or performance measurement • What is the distance of a E-LAN • Unclear management models • Unlike existing carrier service offerings • Each E-LAN service instance is a single S-VLAN

  24. Prototypical Major Metro Area • Business Subscriber Population 100K-2M • San Jose Yellow Pages ~100K businesses • The SF Bay Area lists ~1M businesses • Large Business Sites 500-5,000 • Residential Subscriber Population 1M-20M • Leased Line Density 10K-200K • Roughly 1/10 Yellow Page Listings • Application Service Provider Sites 100-2000 • Large APSPs sites may service residental

  25. Major MSA Networks Typical Metropolitan Serving Area – MSA • MSA example shown • ASIA/PAC more CO/MSA • Europe less CO/MSA

  26. Support 1,000,000 Service Instances • Must be able to support E-LINE service for leased line replacement for entire MSA • This is the way Ethernet is entering the markets • The objective is 200K E-LINE instances • Must support E-LINE for APSP to Subscribers • Not all service providers will allow E-TREE because of deployment problems • The objective of an additional 200K E-LINE is adequate for transition until E-TREE • Requirements for around 10K E-TREE instances • Requires 20K S-VLANs • Must support E-LAN for APSP and B-B • Advanced peer applications • Number of service instances speculative, however could be large • Totals • 200K E-LINE S-VLANs for leased line replacement • 200K E-LINE S-VLANs for APSP • 20K E-TREE S-VLANs • ? E-LAN Service Instances • Designing Into A Corner Will Not Instill Confidence In Future • Set Objectives to at least 1,000,000 service instances E-LINE, E-TREE, E-LAN • E-LAN service will eventually become important for coupling small groups • Allow E-TREE and E-LAN service scaling to at least 100,000 for future growth

More Related