How is the agenda in Prague, Tianran? We could run the draft past the meeting to see whether there are any more issues in the room. That could give you an idea about whether the draft is ready.
I do understand Med's point. This document received a fair amount of debate before it got this far. But I also know that you, yourself, have some small concerns, so perhaps a debate would help test the water. Cheers, Adrian PS When WG last call comes, it would be a good idea to cross-post to Netmod. > -----Original Message----- > From: mohamed.boucad...@orange.com > [mailto:mohamed.boucad...@orange.com] > Sent: 30 June 2017 08:43 > To: Tianran Zhou; adr...@olddog.co.uk; opsawg@ietf.org > Subject: RE: [OPSAWG] I-D Action: draft-ietf-opsawg-service-model-explained- > 01.txt > > Re-, > > I confirm my review. The document is ready to move forward. > > That's not fast for such a stable and very scoped document. > > Cheers, > Med > > > -----Message d'origine----- > > De : Tianran Zhou [mailto:zhoutian...@huawei.com] > > Envoyé : vendredi 30 juin 2017 09:27 > > À : BOUCADAIR Mohamed IMT/OLN; adr...@olddog.co.uk; opsawg@ietf.org > > Objet : RE: [OPSAWG] I-D Action: draft-ietf-opsawg-service-model- > > explained-01.txt > > > > Hi Med, > > > > > -----Original Message----- > > > From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of > > > mohamed.boucad...@orange.com > > > Sent: Friday, June 30, 2017 3:15 PM > > > To: adr...@olddog.co.uk; opsawg@ietf.org > > > Subject: Re: [OPSAWG] I-D Action: > > > draft-ietf-opsawg-service-model-explained-01.txt > > > > > > Hi Adrian, all, > > > > > > I reviewed this version. > > > > > > I do think it is ready for a WGLC. > > > > Really? It's surprisingly fast. :-) Though I know this draft evolved > > several versions before WG adoption. > > > > Tianran > > > > > > Cheers, > > > Med > > > > > > > -----Message d'origine----- > > > > De : OPSAWG [mailto:opsawg-boun...@ietf.org] De la part de Adrian > > > > Farrel Envoyé : jeudi 29 juin 2017 18:47 À : opsawg@ietf.org Objet : > > > > Re: [OPSAWG] I-D Action: draft-ietf-opsawg-service-model- > > > > explained-01.txt > > > > > > > > Hi, > > > > > > > > I wouldn't normally flash an I-D this quickly, but Jerry Bonner > > > > spotted a rather important missing "not". Thanks Jerry! > > > > > > > > Cheers, > > > > Adrian > > > > > > > > > -----Original Message----- > > > > > From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of internet- > > > > > dra...@ietf.org > > > > > Sent: 29 June 2017 17:40 > > > > > To: i-d-annou...@ietf.org > > > > > Cc: opsawg@ietf.org > > > > > Subject: [OPSAWG] I-D Action: > > > > > draft-ietf-opsawg-service-model-explained- > > > > 01.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 > > > > > of the IETF. > > > > > > > > > > Title : Service Models Explained > > > > > Authors : Qin Wu > > > > > Will Liu > > > > > Adrian Farrel > > > > > Filename : draft-ietf-opsawg-service-model-explained- > > 01.txt > > > > > Pages : 21 > > > > > Date : 2017-06-29 > > > > > > > > > > Abstract: > > > > > The IETF has produced a considerable number of data modules in > > the > > > > > YANG modelling language. The majority of these modules are used > > to > > > > > construct data models to model devices or monolithic functions > > and > > > > > they allow access for configuration and to read operational > > status. > > > > > > > > > > A small number of YANG modules have been defined to model > > services > > > > > (for example, the Layer Three Virtual Private Network Service > > Model > > > > > produced by the L3SM working group and documented in RFC 8049). > > > > > > > > > > This document briefly sets out the scope of and purpose of an > > IETF > > > > > service model, and it also shows where a service model might fit > > into > > > > > a Software Defined Networking architecture. Note that service > > models > > > > > do not make any assumption of how a service is actually > > engineered > > > > > and delivered for a customer; details of how network protocols > > and > > > > > devices are engineered to deliver a service are captured in other > > > > > models that are not exposed through the Customer-Provider > > Interface. > > > > > > > > > > > > > > > The IETF datatracker status page for this draft is: > > > > > https://datatracker.ietf.org/doc/draft-ietf-opsawg-service-model- > > > > explained/ > > > > > > > > > > There are also htmlized versions available at: > > > > > > > > https://tools.ietf.org/html/draft-ietf-opsawg-service-model-explaine > > > > > d-01 > > > > > > > > https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-service-mode > > > > > l- > > > > > explained-01 > > > > > > > > > > A diff from the previous version is available at: > > > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-service-model- > > > > explained-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/ > > > > > > > > > > _______________________________________________ > > > > > 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 > > > > > > _______________________________________________ > > > 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
