Thanks. The intention males sense Med. I did observe In another reviewed document that in the yang model some "descriptions" use the upper case AC while other description used the lower case ac. (I did not check this specific document.. maybe it was intentional too)
Be well and thanks for the swift response G/ -----Original Message----- From: mohamed.boucad...@orange.com <mohamed.boucad...@orange.com> Sent: Monday, January 20, 2025 2:02 PM To: Gunter van de Velde (Nokia) <gunter.van_de_ve...@nokia.com>; The IESG <i...@ietf.org> Cc: draft-ietf-opsawg-ac-lxsm-lxnm-g...@ietf.org; opsawg-cha...@ietf.org; opsawg@ietf.org; bill...@huawei.com Subject: RE: Gunter Van de Velde's No Objection on draft-ietf-opsawg-ac-lxsm-lxnm-glue-13: (with COMMENT) Hi Gunter, Thanks for the review. I like your edited text. I adopted it with some very few adjustments as you can see in the diff: https://author-tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/attachment-circuit-model/draft-ietf-opsawg-ac-lxsm-lxnm-glue.txt&url_2=https://boucadair.github.io/attachment-circuit-model/gunter-edits-iesg-review/draft-ietf-opsawg-ac-lxsm-lxnm-glue.txt > 166 ac: Attachment circuit > > GV> sometimes the AC is upper case (e.g. AC-glue, etc) and > sometimes lower case > (i.e. ac-ntw-ref, etc). Is this intetional? This intentional. Upper case is used in the narrative/description text, while lower case is used when it appears in a data node identifier. Cheers, Med > -----Message d'origine----- > De : Gunter Van de Velde via Datatracker <nore...@ietf.org> Envoyé : > lundi 20 janvier 2025 13:27 À : The IESG <i...@ietf.org> Cc : > draft-ietf-opsawg-ac-lxsm-lxnm-g...@ietf.org; opsawg- cha...@ietf.org; > opsawg@ietf.org; bill...@huawei.com; bill...@huawei.com Objet : Gunter > Van de Velde's No Objection on draft-ietf-opsawg- > ac-lxsm-lxnm-glue-13: (with COMMENT) > > > Gunter Van de Velde has entered the following ballot position for > draft-ietf-opsawg-ac-lxsm-lxnm-glue-13: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut > this introductory paragraph, however.) > > > Please refer to > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling- > ballot- > positions%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C4a56 > b35359a84433da8508dd394dc125%7C90c7a20af34b40bfbc48b9253b6f5d20%7 > C0%7C0%7C638729728307615589%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MmSU3%2BCuwfEKSPdkL2tE6aj8c0IW% > 2FuZHbQIvD%2FOgF1c%3D&reserved=0 > for more information about how to handle DISCUSS and COMMENT > positions. > > > The document, along with other ballot positions, can be found > here: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg-ac-lxsm-lxnm- > glue%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C4a56b3535 > 9a84433da8508dd394dc125%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C638729728307626870%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjo > yfQ%3D%3D%7C0%7C%7C%7C&sdata=Czy9Qw0%2BXnK6ovoLGUX7CItcq9TQqGKmWS > QmO3m3%2F4A%3D&reserved=0 > > > > ----------------------------------------------------------------- > ----- > COMMENT: > ----------------------------------------------------------------- > ----- > > # Gunter Van de Velde, RTG AD, comments for > draft-ietf-opsawg-ac-lxsm-lxnm-glue-13 > > # the referenced line numbers are derived from the idnits tool: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fauthor- > tools.ietf.org%2Fapi%2Fidnits%3Furl%3Dhttps%3A%2F%2Fwww.ietf.org% > 2Farchive%2Fid%2Fdraft-ietf-opsawg-ac-lxsm-lxnm-glue- > 13.txt&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C4a56b35359 > a84433da8508dd394dc125%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0 > %7C638729728307634582%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=1hFvE0MA0X8ryKDOk5ExgkSMlDxZ7gTi%2B4Y > bznqqmNw%3D&reserved=0 > > # This is a well written document. I have few non-blocking editorial > comments > > #DETAILED COMMENTS > #================= > > 18 The document specifies a module that updates existing > service (i.e., > 19 the Layer 2 Service Model (L2SM) and the Layer 3 > Service Model > 20 (L3SM)) and network (i.e., the Layer 2 Network Model > (L2NM) and the > 21 Layer 3 Network Model (L3NM)) Virtual Private Network > (VPN) modules > 22 with the required information to bind specific VPN > services to > 23 attachment circuits (ACs) that are created using the > AC service > 24 ("ietf-ac-svc") and network ("ietf-ac-ntw") models. > > GV> While correct, I did find this abstract not so easy to digest > and i saw no > correlation with the proposed "AC-glue" model. What about the > following alterative. Maybe > > " > This document defines a YANG data model, referred to as the "AC- Glue" > model, to augment the LxSM and LxNM with references to Attachment > Circuits (ACs). The AC-Glue model enables a provider to associate > configured Layer 2 and Layer 3 VPN services (LxVPN) with the > underlying AC infrastructure, thereby facilitating consistent > provisioning and management of new or existing ACs in conjunction with > LxVPN services. By introducing an integrated approach to AC and LxVPN > management, this model supports an Attachment Circuit- as-a-Service > (ACaaS) paradigm and provides a standardized mechanism for aligning AC > requests with the network configurations required to deliver them. " > > 166 ac: Attachment circuit > > GV> sometimes the AC is upper case (e.g. AC-glue, etc) and > sometimes lower case > (i.e. ac-ntw-ref, etc). Is this intetional? > > Many thanks again for this document, > > Kind Regards, > Gunter Van de Velde, > RTG AD > > ____________________________________________________________________________________________________________ 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 To unsubscribe send an email to opsawg-le...@ietf.org
