1 / 10

Network Demarcation in 802.1aj

Network Demarcation in 802.1aj. Alan McGuire IEEE 802.1 Eilat Interim May 2008. Introduction. Annex K of 802.1aj contains some use cases and invites suggestions for more! Following slides suggest some other scenarios Provider to provider cases rather than enterprise to provider

laksha
Download Presentation

Network Demarcation in 802.1aj

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. Network Demarcation in 802.1aj Alan McGuire IEEE 802.1 Eilat Interim May 2008

  2. Introduction • Annex K of 802.1aj contains some use cases and invites suggestions for more! • Following slides suggest some other scenarios • Provider to provider cases rather than enterprise to provider • Also current models do not consider End 2 End • Discuss • Are they allowed in the 802.1aj model? • Can they be managed? • Should any be included as Use Cases in annex K? • Use Cases • Multiple TPMRs, Multiple Domains • Use with PBB

  3. Multiple TPMRs, Multiple Domains Domain A Domain B NNI NNI 802.1 Provider Bridge 802.1 Provider Bridge TPMR TPMR TPMR TPMR 802.3 Ext Link 802.3 Ext Link 802.3 User Link 802.3 User Link 802.3 Ext Link • Notes • Management of Domain A is separate from that of Domain B • Can TPMRs in Domain B be managed in this scenario? > need something between them • NNI is UNI in Enterprise-Provider examples

  4. Multiple TPMRs, Multiple Domains Domain A Domain B NNI NNI 802.1 Provider Bridge 802.1 Provider Bridge TPMR TPMR TPMR TPMR 802.3 User Link 802.3 User Link 802.3 Ext Link 802.3 Ext Link 802.3 Ext Link • Notes • Management of Domain A is separate from that of Domain B • Can TPMRs in Domain B be managed in this scenario? > need something else

  5. Multiple TPMRs, Multiple Domains Domain A Domain B NNI NNI 802.1 Provider Bridge 802.1 Provider Bridge TPMR TPMR TPMR TPMR 802.1ah encaps 802.3 Ext Link 802.3 Ext Link 802.3 User Link 802.3 User Link 802.3 Ext Link • Notes • Management of Domain A is separate from that of Domain B • Can TPMRs in Domain B be managed in this scenario? • NNI is UNI in Enterprise-Provider examples

  6. Options to consider-I User Link User SP1 SP2 User UNI UNI ENNI Extension Links Extension Links Would seem to be ok since -user link should prevent E-W OAM issues - SNMP issues

  7. Options to consider-II Ext Link User Link User Link User SP1 SP2 User UNI UNI ENNI Extension Links Extension Links Would seem to present problems since Ext Link will likely: -not present SPx access to SPy TPMRs for E-W OAM beyond pt of connectivity -not prevent SPx access via SNMP stack to SPy TPMRs

  8. Options to consider-III User Link User OP1 User SPA SPA’ UNI UNI ENNI ENNI Extension Links Extension Links Extension Links A=A’ Or AA’ Same as option I however limitation with A=A’ No access from SPa(1) to SPa(2) between 1 and 2

  9. Options to consider-IV Ext Link User Link User Link User OP1 User SPA SPA’ UNI UNI ENNI ENNI Extension Links Extension Links Extension Links A=A’ Or AA’ Same issues as II

  10. Options to consider-V OAM OP1 SPA SPA ENNI ENNI mgmt mgmt Extension Links Extension Links Extension Links Can this be achieved via hierarchy?

More Related