Thanks Med, for taking my comments into consideration! On Fri, Feb 11, 2022 at 6:38 PM <[email protected]> wrote:
> Hi Dhruv, > > A candidate version that takes into account your comments can be seen at: > https://github.com/IETF-OPSAWG-WG/lxnm/blob/master/I-D-sap/draft-ietf-opsawg-sap.txt > > As a reminder, your previous comments were: > > == > * Figure 1 uses the term "Service Network Models" which is not defined and > not aligned to RFC 8309. > * Is the attachment-id the key via which the SAP is linked to the physical > topology? More text on this would be useful. > * Consider adding an example (JSON or XML) of how this model would be used > alongside L3SM. > * Can SAP be used for NNI? Some clarification would be nice! > == > > The candidate version clarifies how to bind a SAP to the physical > topology, discusses how tag the interface role of a SAP whether it is used > for UNI or NNI, add many examples, etc. > > Please let us know if you have any further comments. > > Thank you. > > Cheers, > Med > > > -----Message d'origine----- > > De : OPSAWG <[email protected]> De la part de > > [email protected] > > Envoyé : mardi 25 janvier 2022 13:20 > > À : [email protected] > > Cc : [email protected] > > Objet : Re: [OPSAWG] I-D Action: draft-ietf-opsawg-sap-00.txt > > > > Hi all, > > > > This version does not address any of the comments raised during the call > > for adoption. We are planning to do so in the coming weeks. > > > > The comments raised by Benoît, Daniel, Dhruv, and Bo are recorded at: > > https://github.com/IETF-OPSAWG-WG/lxnm/issues?q=label%3AI-D.sap > > > > Please use that repo to flag your issues. Thanks. > > > > Cheers, > > Med > > > > > -----Message d'origine----- > > > De : I-D-Announce <[email protected]> De la part de > > > [email protected] Envoyé : mardi 25 janvier 2022 13:02 À : > > > [email protected] Cc : [email protected] Objet : I-D Action: > > > draft-ietf-opsawg-sap-00.txt > > > > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > > directories. > > > This draft is a work item of the Operations and Management Area > > > Working Group WG of the IETF. > > > > > > Title : A Network YANG Model for Service Attachment > > > Points > > > Authors : Oscar Gonzalez de Dios > > > Samier Barguil > > > Qin Wu > > > Mohamed Boucadair > > > Victor Lopez > > > Filename : draft-ietf-opsawg-sap-00.txt > > > Pages : 21 > > > Date : 2022-01-25 > > > > > > Abstract: > > > This document defines a YANG data model for representing an > > abstract > > > view of the provider network topology containing the points from > > > which its services can be attached (e.g., basic connectivity, VPN, > > > network slices). The data model augments the 'ietf-network' data > > > model by adding the concept of service attachment points (SAPs). > > The > > > service attachment points are the points to which network services > > > (such as L3VPN or L2VPN) can be attached. The customer endpoint of > > > an attachment circuits are not covered in the SAP network topology. > > > > > > > > > The IETF datatracker status page for this draft is: > > > https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/ > > > > > > There is also an htmlized version available at: > > > https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-sap-00 > > > > > > > > > Internet-Drafts are also available by rsync at > > > rsync.ietf.org::internet- drafts > > > > > > > > > _______________________________________________ > > > I-D-Announce mailing list > > > [email protected] > > > 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. > > > > _______________________________________________ > > OPSAWG mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/opsawg > > > _________________________________________________________________________________________________________________________ > > 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. > >
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
