Hi Tom, Patrick and I are finalizing the revision of the NSF-Facing Interface YANG Data Model Draft this week. After this revision, we will reflect the comments from IESG on this Consumer-Facing Interface YANG Data Model Draft.
Thanks for your comments. Best Regards, Paul On Wed, Mar 2, 2022 at 9:31 PM t petch <[email protected]> wrote: > > On 17/02/2022 17:00, Linda Dunbar wrote: > > Hello Working Group, > > > > Many thanks to the authors to address all the comments from YANG Doctor > review. > > > > This email starts a three-weeks Working Group Last Call for > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-consumer-facing-interface-dm/ > > I think that this is premature. As ever, there is substantial overlap > with other I-D in the set, notably nsf-facing, and, as ever, the two I-D > do things differently which I think can only confuse. If there is a > reason for the differences, then that needs calling out IMHO; at the > moment it seems arbitrary, such as which ...art reviewer last saw the I-D! > > Further, nsf-facing has just attracted a large number of comments from > IESG Review, many if not most of which apply here. I think it wrong for > the IESG to be asked to do the same work all over again so I think that > the IESG comments on nsf-facing need resolving with the IESG first and > then the agreed solution - I expect that most of the comments by the > IESG will be accepted - can be incorporated into this I-D. > > Choice of protocols, reference for protocols, way of specifying ranges > of numbers, indeed way of specifying at all, string language, volte, > RFC793 redundant, all those comments by Alexey on lack of clarity, Rob's > comments on identity descriptions, example labelling and so on. > > Tom Petch > > > This poll runs until March 10, 2022. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this Document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as an Author or a Contributor of this Document, please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > > > If you are not listed as an Author or a Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet been > disclosed in conformance with IETF rules. > > > > Thank you. > > > > Linda > > > > > > > > > > _______________________________________________ > > I2nsf mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/i2nsf > > > > _______________________________________________ > I2nsf mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2nsf >
_______________________________________________ I2nsf mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2nsf
