UNI NNI Operations Parameters Olivier Duroyon Alcatel Jim
- Slides: 10
UNI & NNI Operations & Parameters Olivier Duroyon, Alcatel Jim Jones, Alcatel Hirokazu Ishimatsu, Japan Telecom Zhi-Wei Lin, Lucent Technologies Curtis Brownmiller, Worldcom 1 6/13/2021
UNI Connection • Need to specify overall signaling requirements – Do we need to list steps taken to set up connection • Do both head-end and tail-end UNI connection get put up first before SP network puts up connection, or vice versa – Is it relevant to specify? • When setting up connection, do we – Reserve resource and then allocate – Allocate on request reception (no reserve) – Is it relevant to specify? • What about anomalous behavior • Reception of Path. Tear/Srefresh prior to Path set-up completion • Reception of Resv. Conf when no Path/Resv was issued • … 2 6/13/2021
UNI Example Service provider domain ONE User domain Router UNI 3 6/13/2021 UNI
UNI Parameters • Is the current set of parameters adequate, overkill, underkill – E. g. , LDP has a good set of parameters • RSVP parameters have some redundancy – maybe OK? – Is separation of signal type/ transparency/ bandwidth appropriate (not aligned with other standards) • E. g. , RS 64, MS 16, VC-4 -4 c, ODU 2, 1 Gb. E 4 6/13/2021
NNI Connection • What is the purpose of NNI signaling – To transport information between connection controllers – Assuming that info from UNI is used as constraint factors in route determination – Need to define signaling behavior to anomalous message receptions • Receipt of delete prior to set-up of connection • Receipt of confirmation with no request • … 5 6/13/2021
NNI Example Service provider domain ONE Router NNI NNI 6 6/13/2021 NNI
NNI Parameters • What is the necessary set of parameters – User name and ONE name? – Explicit route? – Route constraints? • What is the required functionality/ capability • What are the requirements from the service providers – IPO/ CCAMP + coordination with other groups? 7 6/13/2021
Using user name User domain Service provider domains UNI: A->D A NNI: A->D 1 B i 2 C j A, B, C D, E Route Engine Names are general – IPv 4, IPv 6, E. 164… 8 6/13/2021 3 D 4 E
Using ONE name User domain Service provider domains A UNI: 1 ->3 Query: D 3 UNI: 1 ->3 Query: A: 1 NNI: 1 ->3 1 B i 2 C j 3 D 4 E A: 1, B: 1, C: 2 D: 3, E: 4 Route Engine User has knowledge of specific service provider ONE name assumes using IPv 4 (or IPv 6) for RSVP/LDP re-use For multi-provider, each provider has knowledge of others’ ONE name 9 6/13/2021
Proposal • Requirements very important in determining what signaling protocol should/not do • Clear description of the behavior of the signaling protocol • The correct set of attributes for UNI and NNI • (Any) interactions between UNI and NNI 10 6/13/2021
