In a single-domain scenario there are two options possible:
1) MDSC selects the PE-PE tunnel
step 1: MDSC requests the PNC to setup an e2e tunnel
step 2: MDSC requests the PNC to setup a client signal between A and B using the tunnel setup at step 1
2) MDSC delegates the PNC to select the PE-PE tunnel
step 1: MDSC requests the PNC to setup a client signal between A and B without specifying any underlay tunnel
| |
| ------------------------------------------------|
//|/ |\\\\
// | | \\
| +--+-+ +---+ +---+ +---+ +---+ +--+-+ |
| | PE +----+ P +--+ P +------------+ P +---+ P +---+ PE | |
| +----+ +---+ +---+ +---+ +---+ +----+ |
\\ //
\\\\ /////
------------------------------------------------
In the second option:
need to add some information to constraint how the PNC selects the PE-PE tunnel (e.g., protection, latency, ...)
for ethernet services, also the configuration of VLAN operations can be delegated to the PNC. To further investigate if there is a need to specify some VLAN operations constraints
In a single-domain scenario there are two options possible:
1) MDSC selects the PE-PE tunnel step 1: MDSC requests the PNC to setup an e2e tunnel step 2: MDSC requests the PNC to setup a client signal between A and B using the tunnel setup at step 1
2) MDSC delegates the PNC to select the PE-PE tunnel step 1: MDSC requests the PNC to setup a client signal between A and B without specifying any underlay tunnel
In the second option: