Subject: [L3sm] L3SM pending question :Do we model option B/C NNI and how ?

From: <[email-masked]>
Date: Fri, 10 Jun 2016 07:13:18 +0000

Hi,

Starting v07 we described the NNI scenarios.
NNI option A is modeled as a site.
NNI option B and C are described but not modeled yet but the requirements are expressed :

-          Need to authorize the route-target

-          Need to associate RT value in one network with the value in the other network (optional). One of the issue that the current model does not deal with RT.

1)      Do we model it ?

2)      How ? here are two proposals :

a)      Creating a new top-level container called optionbc-nni like :

Optionbc-nni {

        List nni {

                        Leaf nni-reference {

                                        // There is a need of discussion between SP to agree on nni-references to use

                        }

                        Container authorized-rts {

                                        List rt {

                                                        Leaf rt {

                                                        }

                                                        Leaf translate-to {

                                                        }

                                        }

                        }

}

}

b)      Renaming site container to vpn-connection and site-network-access to vpn-access, add a flavor nni-optionbc and add a container within vpn-connection to describe the connection. This container is only usable when flavor is nni-optionbc, other containers of the vpn-connection cannot be used when flavor is nni-optionbc

Thoughts ?
[Orange logo]<http://www.orange.com/>

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/OINIS/NET
Orange Expert Future Networks
phone: +33 2 23 28 49 83 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2023%2028%2049%2083%20>
mobile: +33 6 37 86 97 52 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2037%2086%2097%2052%20>
[email-masked]<mailto:[email-masked]>

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.