100 likes | 216 Vues
This document discusses use cases for the IEEE 802.1aj standard, focusing on provider-to-provider interactions rather than enterprise-to-provider examples. Annex K invites suggestions for further cases while exploring scenarios involving multiple Transport Provider Management References (TPMRs) and domains. It raises critical questions about the management of these scenarios, the inclusion of new use cases in Annex K, and the implications of end-to-end management. The insights aim to guide improved practices in networking and management under 802.1aj.
E N D
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 • 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
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
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
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
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
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
Options to consider-III User Link User OP1 User SPA SPA’ UNI UNI ENNI ENNI Extension Links Extension Links Extension Links A=A’ Or AA’ Same as option I however limitation with A=A’ No access from SPa(1) to SPa(2) between 1 and 2
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 AA’ Same issues as II
Options to consider-V OAM OP1 SPA SPA ENNI ENNI mgmt mgmt Extension Links Extension Links Extension Links Can this be achieved via hierarchy?