Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt

The name is unique as it is the key of the list.

-----Original Message-----
From: Scharf, Michael (Michael) [mailto:michael.scharf@alcatel-lucent.com] 
Sent: Wednesday, August 19, 2015 14:48
To: LITKOWSKI Stephane SCE/IBNF; l3sm@ietf.org
Subject: RE: I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt

Hi Stephane,

> -----Original Message-----
> From: stephane.litkowski@orange.com
> [mailto:stephane.litkowski@orange.com]
> Sent: Wednesday, August 19, 2015 2:11 PM
> To: Scharf, Michael (Michael); l3sm@ietf.org
> Subject: RE: I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt
> 
> Hi,
> 
> No there's no reason, it's inconsistent. I will fix it.
> And I'm also wondering if we need to keep both vpn name and vpn id 
> (redundant?).

If name is unique, which seems to be implied in the examples in the document, the id could indeed be redundant.

Michael

> Thanks for pointing it
> 
> Stephane
> 
> -----Original Message-----
> From: Scharf, Michael (Michael) [mailto:michael.scharf@alcatel- 
> lucent.com]
> Sent: Wednesday, August 19, 2015 12:08
> To: LITKOWSKI Stephane SCE/IBNF; l3sm@ietf.org
> Subject: RE: I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt
> 
> Hi Stephane,
> 
> I think the model is indeed a bit more elegant with separate templates.
> 
> After quickly scanning the model again, I have run into a small nit:
> 
>   leaf id {
>               type uint32;
>               description
>               "VPN identifier. Local administration meaning.";
>           }
> 
> Is there a particular reason why this id has to be of type "uint32"?
> Most other related identifiers in the model are strings (e.g., 
> site-id, cloud-identifier, ...).
> 
> Thanks!
> 
> Michael
> 
> 
> > -----Original Message-----
> > From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of 
> > stephane.litkowski@orange.com
> > Sent: Monday, August 03, 2015 1:11 PM
> > To: l3sm@ietf.org
> > Subject: Re: [L3sm] I-D Action: draft-ietf-l3sm-l3vpn-service-model-
> > 01.txt
> >
> > Hi WG,
> >
> > Here is a new version of our draft fitting some comments received on 
> > the list or during IETF meeting.
> > - First level of modularization has been done , is it enough ?
> > - Site templates putted as a separate list
> > - More abstracted VPN policy and removal of native VPN
> > - Add MPLS leaf in vpn-svc for the CsC case
> > - some renaming
> > ...
> >
> > Multicast comments are not addressed yet.
> >
> > Please provide your comments on this new proposal.
> >
> >
> >
> >
> > -----Original Message-----
> > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf
> Of
> > internet-drafts@ietf.org
> > Sent: Monday, August 03, 2015 13:08
> > To: i-d-announce@ietf.org
> > Cc: l3sm@ietf.org
> > Subject: I-D Action: draft-ietf-l3sm-l3vpn-service-model-01.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> >  This draft is a work item of the L3VPN Service Model  Working Group 
> > of the IETF.
> >
> >         Title           : YANG Data Model for L3VPN service delivery
> >         Authors         : Stephane Litkowski
> >                           Rob Shakir
> >                           Luis Tomotaki
> >                           Kevin D'Souza
> > 	Filename        : draft-ietf-l3sm-l3vpn-service-model-01.txt
> > 	Pages           : 94
> > 	Date            : 2015-08-03
> >
> > Abstract:
> >    This document defines a YANG data model that can be used to
> deliver
> > a
> >    Layer 3 Provider Provisioned VPN service.  The document is 
> > limited to
> >    the BGP PE-based VPNs as described in RFC4110 and RFC4364.  This
> >    model is intended to be instantiated at management system to
> deliver
> >    the overall service.  This model is not a configuration model to
> be
> >    used directly on network elements.  This model provides an 
> > abstracted
> >    view of the Layer 3 IPVPN service configuration components.  It
> will
> >    be up to a management system to take this as an input and use
> >    specific configurations models to configure the different network
> >    elements to deliver the service.  How configuration of network
> >    elements is done is out of scope of the document.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-l3sm-l3vpn-service-model
> > /
> >
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-ietf-l3sm-l3vpn-service-model-01
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-l3sm-l3vpn-service-
> model-
> > 01
> >
> >
> > Please note that it may take a couple of minutes from the time of 
> > submission until the htmlized version and diff are available at 
> > tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or 
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> ______________________________________________________________________
> > _ __________________________________________________
> >
> > 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.
> >
> > _______________________________________________
> > L3sm mailing list
> > L3sm@ietf.org
> > https://www.ietf.org/mailman/listinfo/l3sm
> 
> ______________________________________________________________________
> _ __________________________________________________
> 
> 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.