Thanks Med for confirming that all IETF LC comments have been resolved. I've issued the IESG ballot, it should be on the telechat in approx. 2 week's time.
Regards, Rob > -----Original Message----- > From: mohamed.boucad...@orange.com > <mohamed.boucad...@orange.com> > Sent: 10 September 2021 08:07 > To: Rob Wilton (rwilton) <rwil...@cisco.com>; opsawg@ietf.org > Cc: draft-ietf-opsawg-vpn-common....@ietf.org > Subject: RE: [OPSAWG] I-D Action: draft-ietf-opsawg-vpn-common-10.txt > > Hi Rob, all, > > This version integrates the IETF LC comments, mainly those revived from > directorate reviewers. Detailed replies for each review were already sent to > the list. > > We are ready for the IESG review. > > Cheers, > Med > > > -----Message d'origine----- > > De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de internet- > > dra...@ietf.org > > Envoyé : vendredi 10 septembre 2021 07:54 > > À : i-d-annou...@ietf.org > > Cc : opsawg@ietf.org > > Objet : [OPSAWG] I-D Action: draft-ietf-opsawg-vpn-common-10.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 Layer 2/3 VPN Common YANG Model > > Authors : Samier Barguil > > Oscar Gonzalez de Dios > > Mohamed Boucadair > > Qin Wu > > Filename : draft-ietf-opsawg-vpn-common-10.txt > > Pages : 69 > > Date : 2021-09-09 > > > > Abstract: > > This document defines a common YANG module that is meant to be > reused > > by various VPN-related modules such as Layer 3 VPN and Layer 2 VPN > > network models. > > > > Editorial Note (To be removed by RFC Editor) > > > > Please update these statements within the document with the RFC > > number to be assigned to this document: > > > > * "This version of this YANG module is part of RFC XXXX;" > > > > * "RFC XXXX: A Layer 2/3 VPN Common YANG Model"; > > > > * reference: RFC XXXX > > > > Also, please update the "revision" date of the YANG module. > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-opsawg-vpn-common/ > > > > There is also an htmlized version available at: > > https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-vpn-common-10 > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-vpn-common-10 > > > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > _______________________________________________ > > OPSAWG mailing list > > OPSAWG@ietf.org > > 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 OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
