80 likes | 193 Vues
This document explores inter-carrier NNI (Network-to-Network Interface) issues encountered when delivering end-to-end services across diverse carrier domains. It discusses the necessity of well-defined external interfaces and examines existing standards such as GMPLS and OIF E-NNI, highlighting their limitations in inter-carrier contexts. The analysis focuses on critical aspects such as addressing, signalling, and routing, emphasizing the need for solutions that ensure path diversity, protection, and security across multilayer networks. The ultimate goal is to derive actionable insights for better inter-carrier connectivity.
E N D
End-to-end services over multiple carrier domains • section 6.2 of "use case examples" • Which services ? • switched L1 connections only ? • all L1, L2, L3 services in NOBEL ?
One carrier's perspective • We have control over our own network, but • we don't know the other networks • and we don't trust them • need well defined external interfaces
Looking for standards • CP standards for transport networks ? • there are standards for the UNI • GMPLS was made for intra-domain • OIF E-NNI is explicitly intra-carrier • none of them is for the inter-carrier interface
Analyse – what do we need? • Addressing • Signalling • Routing • which information? • full path or next hop? • avoid loops?
Compare - what can we use ? • BGP ? • inter-carrier - but only for connectionless IP • E-NNI routing ? • for connections - but intra-carrier
Things to look at • Assuming we can handle them in our network, what more is needed for inter-carrier ? • path diversity • protection / restoration • multilayer networks • (address mapping, security, policy control, business models)
Our draft • rather general analysis • not applied to NOBEL scenarios yet • focus on switched L1 connections • intentions: • problem statement into D18 • results and conclusions into D25 • decisions into implementations.