1. 1 2/28/2016 UNI & NNI Operations & Parameters Olivier Duroyon, Alcatel Jim Jones, Alcatel Hirokazu Ishimatsu, Japan Telecom Zhi-Wei Lin, Lucent Technologies Curtis Brownmiller, Worldcom

2. 2 2/28/2016 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 PathTear/Srefresh prior to Path set-up completion Reception of ResvConf when no Path/Resv was issued …

3. 3 2/28/2016 UNI Example Router ONE UNI User domain Service provider domain

4. 4 2/28/2016 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., RS64, MS16, VC-4-4c, ODU2, 1GbE

5. 5 2/28/2016 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 …

6. 6 2/28/2016 NNI Example Router ONE NNI Service provider domain NNI

7. 7 2/28/2016 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?

8. 8 2/28/2016 Using user name User domain Service provider domains A B C D E 1 2 ij 3 4 Route Engine UNI:A->D A,B,C D,E NNI:A->D Route Engine UNI:A->D Names are general – IPv4, IPv6, E.164…

9. 9 2/28/2016 Using ONE name User domain Service provider domains A B C D E 1 2 ij 3 4 Query:D A:1,B:1,C:2 D:3,E:4 Route Engine NNI:1->3 Route Engine UNI:1->3 3 Query:A:1 User has knowledge of specific service provider ONE name ONE name assumes using IPv4 (or IPv6) for RSVP/LDP re-use For multi-provider, each provider has knowledge of others’ ONE name

10. 10 2/28/2016 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