Hi John, Just a friendly reminder that we await your approval before continuing with the publication process. Please see the files at the locations listed below.
Thank you, RFC Editor/sg > On Feb 28, 2025, at 11:33 AM, Sandy Ginoza <sgin...@staff.rfc-editor.org> > wrote: > > Hi John, > > We do not believe we have heard from you regarding this document’s readiness > for publication. Please review and let us now if any updates are needed. > > The current files are available here: > https://www.rfc-editor.org/authors/rfc9736.xml > https://www.rfc-editor.org/authors/rfc9736.txt > https://www.rfc-editor.org/authors/rfc9736.pdf > https://www.rfc-editor.org/authors/rfc9736.html > > AUTH48 diffs: > https://www.rfc-editor.org/authors/rfc9736-auth48diff.html > https://www.rfc-editor.org/authors/rfc9736-auth48rfcdiff.html (side by side) > > Comprehensive diffs: > https://www.rfc-editor.org/authors/rfc9736-diff.html > https://www.rfc-editor.org/authors/rfc9736-rfcdiff.html (side by side) > > We will wait to hear from you before continuing with the publication process. > > Thank you, > RFC Editor/sg > > >> On Feb 24, 2025, at 10:11 PM, Sandy Ginoza <sgin...@staff.rfc-editor.org> >> wrote: >> >> Hi Med, >> >> Thanks for verifying that the update is correct. >> >> RFC Editor/sg >> >> >> >>> On Feb 24, 2025, at 6:17 AM, mohamed.boucad...@orange.com wrote: >>> >>> Hi Sandy, >>> >>> I think that you captured the intent. Thanks. >>> >>> Cheers, >>> Med >>> >>>> -----Message d'origine----- >>>> De : Sandy Ginoza <sgin...@staff.rfc-editor.org> >>>> Envoyé : jeudi 20 février 2025 00:05 >>>> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> >>>> Cc : Paolo Lucente <pa...@ntt.net>; RFC Editor <rfc-editor@rfc- >>>> editor.org>; John Scudder <j...@juniper.net>; grow-...@ietf.org; >>>> grow-cha...@ietf.org; j...@sobornost.net; Warren Kumari >>>> <war...@kumari.net>; auth48archive@rfc-editor.org >>>> Objet : Re: AUTH48: RFC-to-be 9736 <draft-ietf-grow-bmp-peer-up- >>>> 05> for your review >>>> >>>> >>>> Hi Med, >>>> >>>> We have updated the document as described below. >>>> >>>> For this one, please review the update closely, as I am not sure >>>> I understood the desired update. >>>> >>>>> (3) S3.2 No explicit mention of the IANA registry in the >>>> description of the info type. >>>>> >>>>> CURRENT: Information Type (2 bytes): defined types are: >>>> >>>> It currently reads as follows: >>>> >>>> * Information Type (2 bytes): types are as defined in the >>>> "BMP Peer >>>> Up Message TLVs" registry: >>>> >>>> >>>> Please review the current files: >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc- >>>> editor.org%2Fauthors%2Frfc9736.xml&data=05%7C02%7Cmohamed.boucada >>>> ir%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b >>>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026572327%7CUnknown%7CTWF >>>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z >>>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=utUOjb7kI >>>> L5KW0mYE%2B4Z%2BTXjaLEtidaxt470vAnBqgk%3D&reserved=0 >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc- >>>> editor.org%2Fauthors%2Frfc9736.txt&data=05%7C02%7Cmohamed.boucada >>>> ir%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b >>>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026585419%7CUnknown%7CTWF >>>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z >>>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1a8zh9VV4 >>>> nI7s%2F7w20ZzEDFs3mK5QzGfRKCMwhgcaJ8%3D&reserved=0 >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc- >>>> editor.org%2Fauthors%2Frfc9736.pdf&data=05%7C02%7Cmohamed.boucada >>>> ir%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b >>>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026593453%7CUnknown%7CTWF >>>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z >>>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1pZxBj3ZV >>>> SqthQIMBMya5eyhzlSrQtra1AUNgJ8KPBQ%3D&reserved=0 >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc- >>>> editor.org%2Fauthors%2Frfc9736.html&data=05%7C02%7Cmohamed.boucad >>>> air%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34 >>>> b40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026601480%7CUnknown%7CTW >>>> FpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4 >>>> zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PYVan2Ef >>>> 0i0zdkhj1e5CgmkEKMQ%2FjXETqxOffMFQv9k%3D&reserved=0 >>>> >>>> Diffs of the most recently updates only: >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> lastdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7 >>>> fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20% >>>> 7C0%7C0%7C638756032026609290%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h >>>> cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsI >>>> ldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XcyLnLDb3yUajXU2ZtITLyeOFlZUq7 >>>> eCN09234Sg%2F2A%3D&reserved=0 >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> lastrfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C >>>> af7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d >>>> 20%7C0%7C0%7C638756032026616983%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e >>>> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbC >>>> IsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=gw%2FVoeKRlvFXCOCR1%2Fiaovd >>>> LKgB4cWgouW44SGEst8A%3D&reserved=0 (side by side) >>>> >>>> AUTH48 diffs: >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ca >>>> f7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d2 >>>> 0%7C0%7C0%7C638756032026624709%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >>>> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI >>>> sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=M%2BeXtNLCH4q%2Bd7AMkgO711hZ >>>> YVdd12Vxg9f06UksMiE%3D&reserved=0 >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> auth48rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com% >>>> 7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f >>>> 5d20%7C0%7C0%7C638756032026632535%7CUnknown%7CTWFpbGZsb3d8eyJFbXB >>>> 0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFp >>>> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FvmSHIYQYvxIrMkoORuoXJm >>>> u5CWw8%2FDsi6yV3YGdcG8%3D&reserved=0 (side by side) >>>> >>>> Comprehensive diffs: >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7fe68 >>>> 48cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0% >>>> 7C0%7C638756032026640395%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >>>> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >>>> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=u0A%2Bzfw6ZhacGVuxyYCd9yzVXaOr%2BK >>>> WFy%2FdOo761l9g%3D&reserved=0 >>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7f >>>> e6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20%7 >>>> C0%7C0%7C638756032026648105%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >>>> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl >>>> dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=sOE3n2NtfnLamB1olgREkW%2B5gWWyV >>>> GgA8ZjoJhRNQmA%3D&reserved=0 (side by side) >>>> >>>> >>>> Please review and let us know if any further updates are needed >>>> or if you approve the RFC for publication. >>>> >>>> Thank you, >>>> RFC Editor/sg >>>> >>>> >>>> >>>> >>>> >>>>> On Feb 11, 2025, at 10:08 PM, mohamed.boucad...@orange.com >>>> wrote: >>>>> >>>>> Hi all, >>>>> >>>>> >>>>> >>>>> Some few comments about the edited version, fwiw: >>>>> >>>>> >>>>> >>>>> (1) S.1 Expand at first use >>>>> >>>>> >>>>> >>>>> CURRENT >>>>> >>>>> [RFC7854] defines a number of different BMP message types. >>>> With >>>>> the >>>>> >>>>> ^^^^ >>>>> >>>>> exception of the Route Monitoring message type, these >>>> messages are >>>>> >>>>> TLV-structured. Most message types have distinct namespaces >>>> and >>>>> IANA >>>>> >>>>> registries. However, the namespace of the Peer Up message >>>> overlaps >>>>> >>>>> that of the Initiation message. As the BGP Monitoring >>>> Protocol has >>>>> >>>>> >>>> ^^^^^^^^^^^^^^^^^^^^^^^^ >>>>> >>>>> >>>>> >>>>> NEW: >>>>> >>>>> [RFC7854] defines a number of different BGP Monitoring >>>> Protocol (BMP) message types. With the >>>>> exception of the Route Monitoring message type, these >>>> messages are >>>>> TLV-structured. Most message types have distinct namespaces >>>> and IANA >>>>> registries. However, the namespace of the Peer Up message >>>> overlaps >>>>> that of the Initiation message. As BMP has >>>>> >>>>> >>>>> (2) S3.1 nit >>>>> >>>>> >>>>> >>>>> CURRENT: provided for here for completeness >>>>> >>>>> NEW: provided for completeness >>>>> >>>>> >>>>> >>>>> (3) S3.2 No explicit mention of the IANA registry in the >>>> description of the info type. >>>>> >>>>> >>>>> >>>>> CURRENT: Information Type (2 bytes): defined types are: >>>>> >>>>> >>>>> Cheers, >>>>> >>>>> Med >>>>> >>>>> >>>>> >>>>> De : Sandy Ginoza <sgin...@staff.rfc-editor.org> Envoyé : >>>> mercredi 12 >>>>> février 2025 00:52 À : Paolo Lucente <pa...@ntt.net> Cc : RFC >>>> Editor >>>>> <rfc-edi...@rfc-editor.org>; John Scudder <j...@juniper.net>; >>>>> grow-...@ietf.org; grow-cha...@ietf.org; j...@fastly.com; Warren >>>> Kumari >>>>> <war...@kumari.net>; auth48archive@rfc-editor.org Objet : Re: >>>> AUTH48: >>>>> RFC-to-be 9736 <draft-ietf-grow-bmp-peer-up-05> for your review >>>>> >>>>> >>>>> >>>>> >>>>> Hi Paolo, >>>>> >>>>> >>>>> >>>>> Thank you for your reply. We have updated the document as >>>> described below. In particular, thank you for your explanation >>>> regarding 3a and 3d. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Regarding item 6, please verify that this is correct, as it's >>>> different from what I see in Section 4.4 of RFC 7854. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 6) <!-- [rfced] Please confirm that the bit ruler appears as >>>> expected. >>>>> Typically the numbers appear over the hyphens. Compare the >>>> alignment >>>>> with the figure in Section 4.4 of RFC 7854 >>>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F% >>>> 2Fwww.rfc-editor.org%2Frfc%2Frfc7854.html%23section- >>>> 4.4&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7fe6848cf14 >>>> d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C >>>> 638756032026655751%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydW >>>> UsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% >>>> 3D%3D%7C0%7C%7C%7C&sdata=KeKb3KsRrdx4WkukBLe39B1ZST26m2DbYND4Fe9W >>>> Afg%3D&reserved=0>. >>>>> Original (this doc): >>>>> 0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 >>>> 8 >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- >>>> +-+ >>>>> --> >>>>> >>>>> >>>>> I confirm it looks good, it was pretty much copy-pasted :-) >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> From Section 4.4 of RFC 7854: >>>>> >>>>> >>>>> 0 1 2 >>>> 3 >>>>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 >>>> 9 0 1 >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- >>>> +-+-+-+ >>>>> | Information Type | Information Length >>>> | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- >>>> +-+-+-+ >>>>> | Information (variable) >>>> | >>>>> ~ >>>> ~ >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- >>>> +-+-+-+ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Also including a snapshot in case the figure above doesn't >>>> display correctly: >>>>> >>>>> >>>>> >>>>> <image001.png> >>>>> >>>>> >>>>> >>>>> >>>>> Please review the current files and let us know if any >>>> additional updates are needed. >>>>> >>>>> >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> rfc- >>>> editor.org%2Fauthors%2Frfc9736.xml&data=05%7C02%7Cmohamed.boucada >>>> i >>>>> >>>> r%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b4 >>>> 0bfbc >>>>> >>>> 48b9253b6f5d20%7C0%7C0%7C638756032026663255%7CUnknown%7CTWFpbGZsb >>>> 3d8ey >>>>> >>>> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjo >>>> iTWFp >>>>> >>>> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=A59WSt7NYWOPXZLGtENej8xZ5 >>>> KQvYc >>>>> Q0nYg58yrb9vo%3D&reserved=0 >>>>> >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc- >>>> editor.org%2Fauthors%2Frfc9736.txt&data=05%7C02%7Cmohamed.boucada >>>> ir%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b >>>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026670733%7CUnknown%7CTWF >>>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z >>>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iRw%2F3tD >>>> %2F0uZAtlfinDkUXAOlcNinAoZ61VRUPA68bRQ%3D&reserved=0 >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc- >>>> editor.org%2Fauthors%2Frfc9736.pdf&data=05%7C02%7Cmohamed.boucada >>>> ir%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b >>>> 40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026678478%7CUnknown%7CTWF >>>> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z >>>> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=DHIqT1HqF >>>> PSOnqbixor6uEuSxd%2B400FKFgg6TAV3GQ8%3D&reserved=0 >>>>> >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> rfc- >>>> editor.org%2Fauthors%2Frfc9736.html&data=05%7C02%7Cmohamed.boucad >>>> a >>>>> >>>> ir%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b >>>> 40bfb >>>>> >>>> c48b9253b6f5d20%7C0%7C0%7C638756032026685957%7CUnknown%7CTWFpbGZs >>>> b3d8e >>>>> >>>> yJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIj >>>> oiTWF >>>>> >>>> pbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=qFEw4JXL%2F65jA8EkHCNFea >>>> h%2FF >>>>> %2FzMuk4QnyKD8Vx%2FJRA%3D&reserved=0 >>>>> >>>>> AUTH48 diffs: >>>>> >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> rfc-editor.org%2Fauthors%2Frfc9736- >>>> auth48diff.html&data=05%7C02%7Cmoha >>>>> >>>> med.boucadair%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C9 >>>> 0c7a2 >>>>> >>>> 0af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026693492%7CUnknown >>>> %7CTW >>>>> >>>> FpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4 >>>> zMiIs >>>>> >>>> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=VxYvYlcuO6s9P >>>> wNqmj >>>>> 9KvI7fvyAO4WgUPEoWvvIbfFY%3D&reserved=0 >>>>> >>>>> >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> rfc-editor.org%2Fauthors%2Frfc9736- >>>> auth48rfcdiff.html&data=05%7C02%7Cm >>>>> >>>> ohamed.boucadair%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39% >>>> 7C90c >>>>> >>>> 7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026702395%7CUnkn >>>> own%7 >>>>> >>>> CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJX >>>> aW4zM >>>>> >>>> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0ZYPl3DxTF >>>> y0nP9 >>>>> uIELu7xenBl6gloOr%2FmRAJ6KUMrI%3D&reserved=0 (side by side) >>>>> >>>>> Comprehensive diffs: >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww.rfc-editor.org%2Fauthors%2Frfc9736- >>>> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7fe68 >>>> 48cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0% >>>> 7C0%7C638756032026710546%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >>>> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >>>> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=DIMHN88WESPYqMepm9e8GK%2BJ%2Fv%2BQ >>>> N%2FvlXJT2mzWf0RM%3D&reserved=0 >>>>> >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> rfc-editor.org%2Fauthors%2Frfc9736- >>>> rfcdiff.html&data=05%7C02%7Cmohamed >>>>> >>>> .boucadair%40orange.com%7Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7 >>>> a20af >>>>> >>>> 34b40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026718077%7CUnknown%7C >>>> TWFpb >>>>> >>>> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMi >>>> IsIkF >>>>> >>>> OIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5w7VtSntk0KhlQFd >>>> a4sl8 >>>>> jwHug2vq5P70mQrFwbx720%3D&reserved=0 (side by side) >>>>> >>>>> >>>>> >>>>> Thank you, >>>>> >>>>> RFC Editor/sg >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Feb 5, 2025, at 12:00 PM, Paolo Lucente <pa...@ntt.net> >>>> wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> Please see inline: >>>>> >>>>> On 4/2/25 00:04, rfc-edi...@rfc-editor.org wrote: >>>>> >>>>> >>>>> Authors, >>>>> While reviewing this document during AUTH48, please resolve (as >>>>> necessary) the following questions, which are also in the XML >>>> file. >>>>> 1) <!-- [rfced] For clarity, may we replace "oversight" with >>>> "overlap"? >>>>> Original: >>>>> As the BGP Monitoring Protocol has >>>>> been extended, this oversight has become problematic. >>>>> Perhaps: >>>>> As the BGP Monitoring Protocol has >>>>> been extended, this overlap has become problematic. >>>>> --> >>>>> >>>>> >>>>> That works! >>>>> >>>>> >>>>> >>>>> >>>>> 2) <!-- [rfced] We find the "corresponding missing registry" >>>> somewhat >>>>> confusing because it seems to refer to the registry being >>>> renamed as >>>>> "missing". Please consider whether the suggested text would be >>>> more clear. >>>>> Original: >>>>> In this >>>>> document, we create a distinct namespace for the Peer Up >>>> message to >>>>> eliminate this overlap, and create the corresponding missing >>>>> registry. >>>>> Perhaps: >>>>> In this >>>>> document, we create distinct namespaces for the Peer Up and >>>> Initiation >>>>> messages to eliminate the overlap. >>>>> --> >>>>> >>>>> >>>>> That works! Thanks! >>>>> >>>>> >>>>> >>>>> >>>>> 3) <!-- [rfced] Section 3: Please review the questions below. >>>>> a) It is unclear to us whether Section 3.1 refers to the >>>> updates to >>>>> the "BMP Initiation Information TLVs" registry [1] or if it >>>> indicates >>>>> that "Initiation" should to be updated to "Initiation >>>> Information" in >>>>> the "BMP Message Types" registry [2], or both. >>>>> Please review the IANA registries and let us know if updates >>>> are needed. >>>>> [1] >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> iana.org%2Fassignments%2Fbmp-parameters%2Fbmp- >>>> parameters.xhtml%23initi >>>>> ation-information- >>>> tlvs&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >>>>> >>>> Caf7fe6848cf14d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5 >>>> d20%7 >>>>> >>>> C0%7C0%7C638756032026725501%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >>>> GkiOn >>>>> >>>> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjo >>>> yfQ%3 >>>>> >>>> D%3D%7C0%7C%7C%7C&sdata=kONuXoBoZbKf%2B%2F81zg3sFobfYl%2FEnTOe%2B >>>> vJ%2F >>>>> oIpTiIE%3D&reserved=0 [2] >>>>> >>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 >>>> Fwww. >>>>> iana.org%2Fassignments%2Fbmp-parameters%2Fbmp- >>>> parameters.xhtml%23messa >>>>> ge- >>>> types&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7fe6848cf >>>> 14 >>>>> >>>> d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C >>>> 63875 >>>>> >>>> 6032026732823%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlY >>>> iOiIw >>>>> >>>> LjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0% >>>> 7C%7C >>>>> >>>> %7C&sdata=PFitO9UHG1aVU5y57k9%2B8logYahgeBxu2y8eFwrC5rs%3D&reserv >>>> ed=0 >>>>> b) If updating the entry in "BMP Message Types" is intended, we >>>>> suggest describing the action in the IANA Considerations >>>> section as >>>>> well. Please provide text. >>>>> >>>>> >>>>> None of the two, we are just updating RFC7854: >>>>> >>>>> in section 4.4 of RFC7854 the optional TLV that can follow an >>>>> Initiation message is called "Information TLV". We are just >>>> changing >>>>> that definition to "Initiation Information TLV" to limit the >>>> scope to >>>>> the Initialization message only. Nothing to do for IANA here as >>>> in >>>>> section 10.5 of RFC7854 the registry is correctly already named >>>> "BMP >>>>> Initiation Message TLVs". (see more in my comment to your point >>>> "d") >>>>> >>>>> >>>>> >>>>> >>>>> c) The section title feels overloaded. May we change it as >>>> follows? >>>>> Original: >>>>> 3.1. Revision to Information TLV, Renamed as Initiation >>>> Information >>>>> TLV >>>>> Perhaps: >>>>> 3.1. Revision to the Information TLV >>>>> >>>>> >>>>> Agree! >>>>> >>>>> >>>>> >>>>> >>>>> d) Somewhat related, Section 3.3 says: >>>>> Original: >>>>> The Peer Up Information TLV is used by the Peer Up message. >>>>> Is the Peer Up Information TLV an IANA-registered value? We >>>> don't see >>>>> "Peer Up Information" in the BMP registry. >>>>> --> >>>>> >>>>> >>>>> Similarly to before, we are just updating RFC7854. In section >>>> 4.10 of RFC7854 we find "Information: Information about the peer, >>>> using the Information TLV (Section 4.4) format. [ .. ]"; so we >>>> are overloading the term Information TLV for two different >>>> message types, Initialization and Peer Up; in this document we >>>> say they are called differently and each will ultimately point to >>>> a different IANA registry: >>>>> >>>>> * Initialization Information TLV field to the existing "BMP >>>> Initiation >>>>> Information TLVs" IANA registry; >>>>> >>>>> * Peer Up Information TLV field to the newly created (as part >>>> of this >>>>> document) "BMP Peer Up Information TLVs" IANA registry; >>>>> >>>>> Hope this makes things more clear. >>>>> >>>>> >>>>> >>>>> >>>>> 4) <!-- [rfced] The text mentions Type 0 being revised, but the >>>> text >>>>> that follows also includes definitions for Types 1 and 2. May >>>> we >>>>> update the text as follows for clarity? >>>>> Original: >>>>> The definition of Type = 0 is revised to be: >>>>> Perhaps: >>>>> The definition of Type = 0 is revised as shown below. >>>>> Type = 1 and Type = 2 are unchanged; they are provided >>>>> for here for completeness. >>>>> --> >>>>> >>>>> >>>>> Agree! >>>>> >>>>> >>>>> >>>>> >>>>> 5) <!-- [rfced] Because this text is supposed to replace text >>>> in RFC >>>>> 9736, we have updated "defined below (Section 3.3)" to read >>>> "defined >>>>> in Section >>>>> 3.3 of RFC 9736." Rationale: if this text were incorporated >>>> into RFC >>>>> 7854, "below (Section 3.3)" would be incorrect. >>>>> Original: >>>>> * Information: Information about the peer, using the Peer >>>> Up >>>>> Information TLV format defined below (Section 3.3). >>>>> --> >>>>> >>>>> >>>>> Agree! >>>>> >>>>> >>>>> >>>>> >>>>> 6) <!-- [rfced] Please confirm that the bit ruler appears as >>>> expected. >>>>> Typically the numbers appear over the hyphens. Compare the >>>> alignment >>>>> with the figure in Section 4.4 of RFC 7854 >>>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F% >>>> 2Fwww.rfc-editor.org%2Frfc%2Frfc7854.html%23section- >>>> 4.4&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Caf7fe6848cf14 >>>> d2f7c6808dd5139ff39%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C >>>> 638756032026740296%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydW >>>> UsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% >>>> 3D%3D%7C0%7C%7C%7C&sdata=tq6jvCUBRj%2F2Q9dibsvlj5TfZXbkrrTRNjMvP% >>>> 2BIroqs%3D&reserved=0>. >>>>> Original (this doc): >>>>> 0 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 >>>> 8 >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- >>>> +-+ >>>>> --> >>>>> >>>>> >>>>> I confirm it looks good, it was pretty much copy-pasted :-) >>>>> >>>>> >>>>> >>>>> >>>>> 7) <!-- [rfced] Some author comments are present in the XML. >>>> Please >>>>> confirm that no updates related to these comments are >>>> outstanding. >>>>> Note that the comments will be deleted prior to publication. >>>>> --> >>>>> >>>>> >>>>> I confirm there are no updates and they can be deleted. >>>>> >>>>> >>>>> >>>>> >>>>> 8) <!-- [rfced] Please review the "Inclusive Language" portion >>>> of the >>>>> online Style Guide >>>>> >>>> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F% >>>> 2Fwww >>>>> .rfc- >>>> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7 >>>>> >>>> C02%7Cmohamed.boucadair%40orange.com%7Caf7fe6848cf14d2f7c6808dd51 >>>> 39ff3 >>>>> >>>> 9%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638756032026747965 >>>> %7CUn >>>>> >>>> known%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsI >>>> lAiOi >>>>> >>>> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2dY >>>> tGB%2 >>>>> FxWrWSE3C19Mx7swQwoGjvjbYMf848gEkj2bE%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. >>>>> --> >>>>> >>>>> >>>>> It seems all fine to me, thanks for bringing this up. >>>>> >>>>> Paolo >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> _________________________________________________________________ >>>> _____ >>>>> _____________________________________ >>>>> _ >>>>> 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. >>>>> >>> >>> ____________________________________________________________________________________________________________ >>> 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 -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
