Re: [L3sm] Inventory ops state

[Qin Wu <[e-mail]>]

From the example below, I tend to agree native-vpn is not needed.
It seems to me vpn policy can also be used to specify which VPNs are attached to a particular site or specify one site belonging to multiple VPN,
Do we need to add association between site and VPN also in the operational state subtree?

In addition, I feel, entries list should be entry list, when  VPN-policy as container contains multiple entries, e.g.,
<vpn-policy>
       <entry>
           <id>1</id>
           <vpn>
               <vpn>VPN1</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entry>
       <entry>
           <id>2</id>
           <vpn>
               <vpn>VPN2</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entry>
   </vpn-policy>
The Corresponding service model structure for VPN policy should be

         |  +--rw vpn-policy
         |  |  +--rw entry* [id]

-Qin
发件人: [e-mail] [mailto:[e-mail]]
发送时间: 2015年8月18日 19:14
收件人: Qin Wu; [e-mail]
主题: RE: Inventory ops state

PVN policy is used to attach a site to one or multiple VPNs.

Example :
                Site attached to a single VPN :
<vpn-policy>
       <entries>
           <id>1</id>
           <vpn>
               <vpn>VPN1</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entries>
   </vpn-policy>

Site attached to a multiple VPNs :

<vpn-policy>
       <entries>
           <id>1</id>
           <vpn>
               <vpn>VPN1</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entries>
       <entries>
           <id>2</id>
           <vpn>
               <vpn>VPN2</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entries>
   </vpn-policy>

Site attached to a multiple VPNs with LAN separation :

<vpn-policy>
       <entries>
           <id>1</id>
           <filter>
               <lan-tag>LAN1</lan-tag>
           </filter>
           <vpn>
               <vpn>VPN1</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entries>
       <entries>
           <id>2</id>
           <filter>
               <lan-tag>LAN2</lan-tag>
           </filter>
           <vpn>
               <vpn>VPN2</vpn>
               <site-role>any-to-any-role</site-role>
           </vpn>
       </entries>
   </vpn-policy>


From: Qin Wu [mailto:[e-mail]]
Sent: Tuesday, August 18, 2015 12:58
To: LITKOWSKI Stephane SCE/IBNF; [e-mail]<mailto:[e-mail]>
Subject: RE: Inventory ops state

发件人: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
发送时间: 2015年8月18日 18:48
收件人: Qin Wu; [e-mail]<mailto:[e-mail]>
主题: RE: Inventory ops state

Some people told that the notion of native VPN was not really clear, especially for the management of a site belonging to multiple VPNs.
So rather than having native VPN+vpn policy, I just kept a simplified vpn policy where we can express rules for VPN attachment.
The VPN policy is a list of entry, where a site or LAN of the site is attached to a VPN (using a ref) and adding its role within the VPN.

[Qin]: To a VPN or To multiple VPN?, can VPN policy still be applied to multiple VPNs?

Since Section 5.2.2 of draft-ietf-l3sm-l3vpn-service-model-01 said:
“

The VPN policy defines the route exchange between multiple VPNs. A
vpn-policy configuration MUST be configured to attach a site to one
or multiple VPNs.
”

From: Qin Wu [mailto:[e-mail]]
Sent: Tuesday, August 18, 2015 11:57
To: LITKOWSKI Stephane SCE/IBNF; [e-mail]<mailto:[e-mail]>
Subject: RE: Inventory ops state

Hi, Stephane:
Before considering Inventory ops state, can you tell me why native-vpn is removed from the (v-01), for better VPN policy abstraction?
Or path statement within the native-vpn is not sufficient to associate one VPN with one site?
Can native-vpn in the earlier version be used to identify the specific VPN one site is belong to? It seems native-vpn parameter can tell us
Which VPN is associated with which site?

-Qin
发件人: L3sm [mailto:[e-mail]] 代表 [e-mail]<mailto:[e-mail]>
发送时间: 2015年8月17日 17:55
收件人: [e-mail]<mailto:[e-mail]>
主题: [L3sm] Inventory ops state

Hi WG,

Discussing with some colleagues, we were wondering if we can integrate some kind of inventory as operational state within the model.
The idea would be to know easily the sites attached to a particular VPN, which is not easy with the current configuration structure but we can add it in an operational state structure.
Also for cloud services being able to know quickly what VPNs are subscribing to a particular Cloud service.

Thoughts ?


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

Stephane Litkowski
Network Architect
Orange/SCE/EQUANT/IBNF/ENDD/NDE
Orange Expert Future Networks
phone: [phone] <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: [phone] <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>
[e-mail]<mailto:[e-mail]>



_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________



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.