Hi Benoit, Thank you for this clarification.
If Juergen is OK to provide his review before the WGLC, I would prefer to go that path. That is, wait for his early review, fix any comments from Juergen, and then go for a last call. Obviously, this is only my preference as an editor. I will defer to the chairs to decide. Cheers, Med > -----Message d'origine----- > De : Benoit Claise [mailto:bcla...@cisco.com] > Envoyé : lundi 16 octobre 2017 12:24 > À : BOUCADAIR Mohamed IMT/OLN; opsawg@ietf.org > Cc : JACQUENET Christian IMT/OLN; Juergen Schoenwaelder > Objet : Re: [OPSAWG] New Version Notification for draft-ietf-opsawg-nat- > yang-06.txt > > Dear all, > > Historically, the MIB doctor reviews would happen during IETF LC. > Because YANG was new, we started early YANG doctor reviews. Those > reviews don't have to occur in sequence, i.e. before the IETF LC starts. > In fact, at some point in time in the future (when the YANG knowledge > will be widely spread), the YANG doctor reviews will be triggered by the > IETF LC. > Bottom line: if the OPSAWG chairs believe this document is ready, it can > progress to IETF LC now. > > Regards, Benoit. > > Dear all, > > > > The new version fixes some cosmetic issues (mainly, indentation of the > YANG module) and points to YANG1.1 RFC as per a comment received from > Mahesh Jethanandani. > > > > We are waiting for the yang doctors review. > > > > Cheers, > > Med > > > >> -----Message d'origine----- > >> De : internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] > >> Envoyé : jeudi 12 octobre 2017 16:02 > >> À : Qin Wu; Senthil Sivakumar; BOUCADAIR Mohamed IMT/OLN; Suresh > >> Vinapamula; JACQUENET Christian IMT/OLN > >> Objet : New Version Notification for draft-ietf-opsawg-nat-yang-06.txt > >> > >> > >> A new version of I-D, draft-ietf-opsawg-nat-yang-06.txt > >> has been successfully submitted by Mohamed Boucadair and posted to the > >> IETF repository. > >> > >> Name: draft-ietf-opsawg-nat-yang > >> Revision: 06 > >> Title: A YANG Data Model for Network Address Translation (NAT) > >> and Network Prefix Translation (NPT) > >> Document date: 2017-10-11 > >> Group: opsawg > >> Pages: 78 > >> URL: https://www.ietf.org/internet-drafts/draft-ietf-opsawg- > >> nat-yang-06.txt > >> Status: https://datatracker.ietf.org/doc/draft-ietf-opsawg-nat- > >> yang/ > >> Htmlized: https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang- > 06 > >> Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf- > opsawg- > >> nat-yang-06 > >> Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg- > nat- > >> yang-06 > >> > >> Abstract: > >> For the sake of network automation and the need for programming > >> Network Address Translation (NAT) function in particular, a data > >> model for configuring and managing the NAT is essential. This > >> document defines a YANG module for the NAT function. > >> > >> NAT44, Network Address and Protocol Translation from IPv6 Clients > to > >> IPv4 Servers (NAT64), Customer-side transLATor (CLAT), Explicit > >> Address Mappings for Stateless IP/ICMP Translation (SIIT EAM), and > >> IPv6 Network Prefix Translation (NPTv6) are covered in this > document. > >> > >> > >> > >> > >> 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. > >> > >> The IETF Secretariat > > _______________________________________________ > > OPSAWG mailing list > > OPSAWG@ietf.org > > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
