Hi Alanna, Apologies for the delay to reply as I was out of office.
Please see inline. Cheers, Med > -----Message d'origine----- > De : [email protected] <[email protected]> > Envoyé : mardi 12 août 2025 07:51 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; > [email protected]; [email protected]; > [email protected] > Cc : [email protected]; [email protected]; opsawg- > [email protected]; [email protected]; [email protected]; > [email protected] > Objet : Re: AUTH48: RFC-to-be 9836 <draft-ietf-opsawg-ac-lxsm- > lxnm-glue-14> for your review > > Authors, > > While reviewing this document during AUTH48, please resolve (as > necessary) the following questions, which are also in the XML > file. > > 1) <!--[rfced] May we clarify that the modules in [RFC9834] would > be used to manage ACs across the network? > > Original: > In order to avoid service interference and redundant > information in various locations, a service provider may expose > an > interface to manage ACs network-wide using > [I-D.ietf-opsawg-teas-attachment-circuit]. > > Perhaps: > In order to avoid service interference and redundant > information in various locations, a service provider may expose > an > interface to manage ACs network-wide using the modules in > [RFC9834]. > --> [Med] The proposed wording works for me. > > > 2) <!--[rfced] We note that Figure 3 uses "CE#1" and "CE#2", while > other figures in the document use "CE1" and "CE2". May we update > the CEs in Figure 3 to match the other figures in the document? > > If so, both artworks (svg and ascii-art) will be updated > accordingly. > --> [Med] Let's be consistent with other figures. > > > 3) <!-- [rfced] We have a couple questions about this paragraph: > > Original: > This approach is consistent with the design in > [I-D.ietf-teas-ietf-network-slice-nbi-yang] where an AC > service > reference, called 'ac-svc-name', is used to indicate the > names of > AC services. As per [I-D.ietf-teas-ietf-network-slice-nbi- > yang], > when both 'ac-svc-name' and the attributes of 'attachment- > circuits' are defined, the 'ac-svc-name' takes precedence. > > a) [I-D.ietf-teas-ietf-network-slice-nbi-yang] does not appear to > contain the term "ac-svc-name". It does contain the term "ac-svc- > ref". Should "ac-svc-name" be updated to "ac-svc-ref"? [Med] Good catch. Please make this change. > > b) Additionally, we note that this text was indented. As it is > unclear to us why it was indented, we have removed the > indentation. Was the intent for this to be a "Note"? If yes, this > text can be used in the <aside> element, which is defined as "a > container for content that is semantically less important or > tangential to the content that surrounds it" > (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fauthors.ietf.org%2Fen%2Frfcxml- > vocabulary%23aside&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 > C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C638905746849366903%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xQ9HfY7QppXreqxefGpVAdVXrHZ0J4 > kwBOMBD69T4oA%3D&reserved=0). > > Perhaps: > | This approach is consistent with the design in > | [I-D.ietf-teas-ietf-network-slice-nbi-yang] where an AC > service > | reference, called 'ac-svc-ref', is used to indicate the > names of > | AC services. As per [I-D.ietf-teas-ietf-network-slice-nbi- > yang], > | when both 'ac-svc-ref' and the attributes of 'attachment- > | circuits' are defined, the 'ac-svc-ref' takes precedence. > --> > [Med] The intent was to have this as a note. The proposed aside formatting would be my preference here. Thanks. > > 4) <!--[rfced] May we clarify that the "ietf-ac-ntw" module in > [RFC9835] is used? > > Original: > [I-D.ietf-opsawg-ntw-attachment-circuit] can be > also used to access AC-related details that are bound to the > target > SAP (Figure 12). > > Perhaps: > The "ietf-ac-ntw" module [RFC9835] can be also used to access > AC-related details that are bound to the target SAP (Figure > 12). > --> > [Med] WFM. > > 5) <!-- [rfced] FYI - We updated artwork to sourcecode in Section > 5. Please confirm that this is correct. > > In addition, please consider whether the "type" attribute of each > sourcecode element has been set correctly. > > The current list of preferred values for "type" is available at > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc-editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dsourcecode- > types&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C18303dfb9a9c > 4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C > 638905746849389610%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWU > sIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D > %3D%7C0%7C%7C%7C&sdata=DiTxSqqkgppnYUVjbC4m01Y5mgktfmTJ2ymkz0942Vw > %3D&reserved=0>. > If the current list does not contain an applicable type, feel free > to suggest additions for consideration. Note that it is also > acceptable to leave the "type" attribute not set. > --> [Med] Looks good to me. > > > 6) <!--[rfced] Abbreviations > > a) FYI - We have added expansion for the following abbreviation > per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review > each expansion in the document carefully to ensure correctness. > > Virtual Private LAN Service (VPLS) [Med] ACK. > > b) Both the expansion and the acronym for the following terms are > used throughout the document. Would you like to update to using > the expansion upon first usage and the acronym for the rest of the > document for consistency? > > attachment circuit (AC) > Layer 2 VPN (L2VPN) > Layer 3 VPN (L3VPN) > --> [Med] Yes, please. > > > 7) <!-- [rfced] Please review the "Inclusive Language" portion of > the online Style Guide > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc- > editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C > 02%7Cmohamed.boucadair%40orange.com%7C18303dfb9a9c4e456e3108ddd964 > 4512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6389057468494040 > 14%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA > wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C > &sdata=hJ7BsafT5ol9JoTHkMXt8%2B5aLa%2FoIe8Qr7iOrZz6hBM%3D&reserved > =0> > and let us know if any changes are needed. Updates of this nature > typically result in more precise language, which is helpful for > readers. > > Note that our script did not flag any words in particular, but > this should still be reviewed as a best practice. > --> > > > Thank you. > > RFC Editor/ap/ar > > > On Aug 11, 2025, at 10:50 PM, [email protected] wrote: > > *****IMPORTANT***** > > Updated 2025/08/11 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 > > Your document has now entered AUTH48. Once it has been reviewed > and > approved by you and all coauthors, it will be published as an RFC. > If an author is no longer available, there are several remedies > available as listed in the FAQ > (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc- > editor.org%2Ffaq%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com% > 7C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5 > d20%7C0%7C0%7C638905746849417662%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e > U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI > sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cwOXN6%2Fvtztgt%2Fw0rx9kty634 > 7w0nn5wrVvH2Rz56Z8%3D&reserved=0). > > You and you coauthors are responsible for engaging other parties > (e.g., Contributors or Working Group) as necessary before > providing > your approval. > > Planning your review > --------------------- > > Please review the following aspects of your document: > > * RFC Editor questions > > Please review and resolve any questions raised by the RFC Editor > that have been included in the XML file as comments marked as > follows: > > <!-- [rfced] ... --> > > These questions will also be sent in a subsequent email. > > * Changes submitted by coauthors > > Please ensure that you review any changes submitted by your > coauthors. We assume that if you do not speak up that you > agree to changes submitted by your coauthors. > > * Content > > Please review the full content of the document, as this cannot > change once the RFC is published. Please pay particular > attention to: > - IANA considerations updates (if applicable) > - contact information > - references > > * Copyright notices and legends > > Please review the copyright notice and legends as defined in > RFC 5378 and the Trust Legal Provisions > (TLP - > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > trustee.ietf.org%2Flicense- > info&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C18303dfb9a9c4 > e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > 38905746849430886%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs > IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% > 3D%7C0%7C%7C%7C&sdata=Os24GvzOLksmKQvLeUmJUGtmgZNpE1Wx3NJUnB6ewqg% > 3D&reserved=0). > > * Semantic markup > > Please review the markup in the XML file to ensure that elements > of > content are correctly tagged. For example, ensure that > <sourcecode> > and <artwork> are set correctly. See details at > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fauthors.ietf.org%2Frfcxml- > vocabulary&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C18303df > b9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 > C0%7C638905746849443855%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=VSOvFGcgKi3BKL3WrNyRaIJPRy7TxmWc6oOi6Q > VLsOc%3D&reserved=0>. > > * Formatted output > > Please review the PDF, HTML, and TXT files to ensure that the > formatted output, as generated from the markup in the XML file, > is > reasonable. Please note that the TXT will have formatting > limitations compared to the PDF and HTML. > > > Submitting changes > ------------------ > > To submit changes, please reply to this email using 'REPLY ALL' as > all > the parties CCed on this message need to see your changes. The > parties > include: > > * your coauthors > > * [email protected] (the RPC team) > > * other document participants, depending on the stream (e.g., > IETF Stream participants are your working group chairs, the > responsible ADs, and the document shepherd). > > * [email protected], which is a new archival mailing > list > to preserve AUTH48 conversations; it is not an active > discussion > list: > > * More info: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh- > 4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 > C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C638905746849457617%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Y9ueOJ3vPW8eUqDDwLICLye%2Ff8ZN > EZmGWYQNQRj6QD4%3D&reserved=0 > > * The archive itself: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C > 02%7Cmohamed.boucadair%40orange.com%7C18303dfb9a9c4e456e3108ddd964 > 4512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6389057468494708 > 93%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA > wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C > &sdata=oTCESnW5%2FZy6acGv8jmezlEA4gGGftzJ8%2FeD0PiKgDU%3D&reserved > =0 > > * Note: If only absolutely necessary, you may temporarily opt > out > of the archiving of messages (e.g., to discuss a sensitive > matter). > If needed, please add a note at the top of the message that > you > have dropped the address. When the discussion is concluded, > [email protected] will be re-added to the CC > list and > its addition will be noted at the top of the message. > > You may submit your changes in one of two ways: > > An update to the provided XML file > - OR - > An explicit list of changes in this format > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > You do not need to reply with both an updated XML file and an > explicit > list of changes, as either form is sufficient. > > We will ask a stream manager to review and approve any changes > that seem > beyond editorial in nature, e.g., addition of new text, deletion > of text, > and technical changes. Information about stream managers can be > found in > the FAQ. Editorial changes do not require approval from a stream > manager. > > > Approving for publication > -------------------------- > > To approve your RFC for publication, please reply to this email > stating > that you approve this RFC for publication. Please use 'REPLY > ALL', > as all the parties CCed on this message need to see your approval. > > > Files > ----- > > The files are available here: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9836.xml&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C638905746849489970%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S92ULwjOzzvM7w > jW7jMNDldURejpw4iQcPD4qnqE3Jk%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9836.html&data=05%7C02%7Cmohamed.boucada > ir%40orange.com%7C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C638905746849503790%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=v1PkR%2B5uZ6z > mnVhEZHVo4V80dtptYie5ojEGIVYEKpU%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9836.pdf&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C638905746849516889%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=BpvtwNtIPQiHTH > wgxGWFBxPoCaEIgtZTzAppgiAP3No%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauthors%2Frfc9836.txt&data=05%7C02%7Cmohamed.boucadai > r%40orange.com%7C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C638905746849529948%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Yv1urMGSw0jtIz > osK5cU6gqgkNz%2BeXpSxLKhtDAgvNE%3D&reserved=0 > > Diff file of the text: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9836- > diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C18303dfb > 9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C638905746849542903%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=7mQyZ6wPiootCnahVa5oQAwIenXF7qmMuilUDA6 > gfvI%3D&reserved=0 > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9836- > rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C18303 > dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C638905746849555888%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=ymyxkxX5umw22b6pEQ08aXXPboxICoZSzUXv > T8%2F%2FnpQ%3D&reserved=0 (side by side) > > Diff of the XML: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9836- > xmldiff1.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1830 > 3dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C638905746849569078%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=useoER3DjZaENCh4QwQMlhPELozxhFfzC0t > %2BgwCW6Zo%3D&reserved=0 > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc- > editor.org%2Fauth48%2Frfc9836&data=05%7C02%7Cmohamed.boucadair%40o > range.com%7C18303dfb9a9c4e456e3108ddd9644512%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C638905746849581610%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0UFswTXpoFrj1B2JlMe > ktECOCV%2B5kum7cHvkyoDH%2B4A%3D&reserved=0 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9836 (draft-ietf-opsawg-ac-lxsm-lxnm-glue-14) > > Title : A YANG Data Model for Augmenting VPN Service > and Network Models with Attachment Circuits > Author(s) : M. Boucadair, R. Roberts, S. Barguil Giraldo, > O. Gonzalez de Dios > WG Chair(s) : Joe Clarke, Benoît Claise > Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani ____________________________________________________________________________________________________________ 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. -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
