I2NSF WG, Since the comments from Tom Petch haven't been addressed, we can't complete the WGLC for draft-ietf-i2nsf-consumer-facing-interface-dm-16. Agree with Tom, the WG needs to reach consensus if it is necessary for the draft-ietf-i2nsf-consumer-facing-interface-dm to be consistent with the draft-ietf-i2nsf-nsf-facing-interface-dm.
Thank you, Linda Dunbar -----Original Message----- From: I2nsf <[email protected]> On Behalf Of t petch Sent: Wednesday, March 2, 2022 11:20 AM To: Mr. Jaehoon Paul Jeong <[email protected]> Cc: [email protected]; Patrick Lingga <[email protected]>; skku-iotlab-members <[email protected]> Subject: Re: [I2nsf] WGLC for draft-ietf-i2nsf-consumer-facing-interface-dm-16 On 02/03/2022 14:40, Mr. Jaehoon Paul Jeong wrote: > Hi Tom, > Patrick and I are finalizing the revision of the NSF-Facing Interface > YANG Data Model Draft this week. If I read it aright, the cut-off for updated I-D for the upcoming IETF is next Monday. after which the system is in purdah for a while. The IETF website might tell me about the latter (if it had a search engine:-) Tom Petch > 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdat >> atracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-consumer-facing-interface- >> dm%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C0fd53b962cbb4 >> 208379608d9fc70f6f5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6378 >> 18384373805664%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2 >> luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=F7VLxYYqc6kpxD3 >> w15O7Lewbot4zMgkGcozhpKViuJY%3D&reserved=0 >> >> 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww >>> w.ietf.org%2Fmailman%2Flistinfo%2Fi2nsf&data=04%7C01%7Clinda.dun >>> bar%40futurewei.com%7C0fd53b962cbb4208379608d9fc70f6f5%7C0fee8ff2a3b >>> 240189c753a1d5591fedc%7C1%7C0%7C637818384373805664%7CUnknown%7CTWFpb >>> GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M >>> n0%3D%7C3000&sdata=0WQB3KY3kIBLT9Dl5xemMrTLAMYolmsqtXjkTrjDeHk%3 >>> D&reserved=0 >>> >> >> _______________________________________________ >> I2nsf mailing list >> [email protected] >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >> .ietf.org%2Fmailman%2Flistinfo%2Fi2nsf&data=04%7C01%7Clinda.dunba >> r%40futurewei.com%7C0fd53b962cbb4208379608d9fc70f6f5%7C0fee8ff2a3b240 >> 189c753a1d5591fedc%7C1%7C0%7C637818384373805664%7CUnknown%7CTWFpbGZsb >> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D >> %7C3000&sdata=0WQB3KY3kIBLT9Dl5xemMrTLAMYolmsqtXjkTrjDeHk%3D& >> reserved=0 >> > _______________________________________________ I2nsf mailing list [email protected] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fi2nsf&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C0fd53b962cbb4208379608d9fc70f6f5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637818384373805664%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=0WQB3KY3kIBLT9Dl5xemMrTLAMYolmsqtXjkTrjDeHk%3D&reserved=0 _______________________________________________ I2nsf mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2nsf
