[ippm] Re: About RFC 7799 BCP Satus Change
Libin Liu <[email protected]> Tue, 16 Jun 2026 05:40:09 +0000
| Newsgroups | gmane.ietf.ippm,gmane.ietf.bmwg |
|---|---|
| Message-ID | <TY4PR01MB12668FA0435D6AAD5FCBF506DE2E52@TY4PR01MB12668.jpnprd01.prod.outlook.com> |
--===============5347800202789576684== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_TY4PR01MB12668FA0435D6AAD5FCBF506DE2E52TY4PR01MB12668jp_" --_000_TY4PR01MB12668FA0435D6AAD5FCBF506DE2E52TY4PR01MB12668jp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Giuseppe, Thanks for taking on the RFC7799 refresh. I understand that this bis docume= nt is intended to keep the main Active/Passive/Hybrid classification guidan= ce unchanged, while refreshing the examples and references so that the docu= ment can better support BCP status. I reviewed draft-fioccola-ippm-rfc7799bis-00 and have a few comments. 1. First, Appendix A appears to have a typo issue. It says =93The main chan= ges since [RFC799]=94, but this should be =93[RFC7799]=94. The correspondin= g informative reference to RFC799 also seems unintended and can probably be= removed. 2. Second, Section 7 currently says that the document has no Operational C= onsiderations. Since the document is intended as BCP and now includes examp= les of methods that generate traffic or modify measurement-related fields i= n user traffic, I think it would be useful to add some general operational = considerations. This does not need to replace the method-specific operation= al considerations, but could provide a short checklist covering added measu= rement traffic, header modifications, MTU or fragmentation effects, possibl= e packet treatment or ECMP effects, measurement export traffic, and the pla= cement of observation or measurement points. 3. Third, for the Hybrid Type I examples in Section 5, especially Alternate= -Marking, IOAM, and PDM, the text says that these methods intend to have a = minor effect on the measured stream and the network. I think this is reason= able as an intent, but the text could more clearly state that the actual ef= fect depends on deployment conditions. For example, adding or modifying mea= surement-related fields may affect MTU, encapsulation, forwarding behavior,= ECMP hashing, middlebox handling, or hardware fast-path processing. This w= ould make the classification more robust without changing the classificatio= n itself. 4. Forth, the Security Considerations currently mainly refer to LMAP. Since= the refreshed examples include methods that add, modify, or expose measure= ment-related information in packets, it may be useful to add a short genera= l note that such methods can expose topology, timing, path, traffic pattern= , or other operational information, and that each method specification shou= ld discuss the corresponding security and privacy risks. If I had any misunderstandings, please point out. Thank you very much for t= he effort. Best, Libin ________________________________ From: Giuseppe Fioccola <giuseppe.fioccola=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> Sent: Friday, June 12, 2026 5:59 PM To: Giuseppe Fioccola <giuseppe.fioccola=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]>; mo= [email protected] <[email protected]>; ippm <ippm@ietf.= org>; bmwg <[email protected]> Subject: [bmwg] Re: About RFC 7799 BCP Satus Change Hi All, To follow up on the status change of RFC7799 as BCP, I just published an in= itial version of RFC7799bis, as suggested by the IESG: https://datatracker.ietf.org/doc/draft-fioccola-ippm-rfc7799bis/ I would greatly appreciated your reviews and contributions. Regards, Giuseppe From: Giuseppe Fioccola <giuseppe.fioccola=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> Sent: Friday, May 22, 2026 11:23 AM To: [email protected]; ippm <[email protected]>; bmwg <[email protected]= > Subject: [bmwg] Re: About RFC 7799 BCP Satus Change Hi Med, I can surely volunteer to lead this effort. Based on the feedback from the = IESG, some sections can be refreshed while other parts of the document can = be kept unchanged. Regards, Giuseppe From: [email protected]<mailto:[email protected]> <mo= [email protected]<mailto:[email protected]>> Sent: Friday, May 22, 2026 11:06 AM To: ippm <[email protected]<mailto:[email protected]>>; bmwg <[email protected]<mailto:= [email protected]>> Subject: [bmwg] About RFC 7799 BCP Satus Change Hi all, Some ADs think that it is better to have a refresh/cleanup of RFC7799 inste= ad of proceeding with the status change as initially planned by BMWG/IPPM W= Gs. The refresh would be mainly picking more recent illustration examples a= nd update some references in Section 4. That clean-up does not alter/impact= the main guidance. If you volunteer to lead this refresh, please let ippm/bmwg know. Thank you= . Cheers, Med ___________________________________________________________________________= _________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. --_000_TY4PR01MB12668FA0435D6AAD5FCBF506DE2E52TY4PR01MB12668jp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Hi Giuseppe,</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Thanks for taking on the RFC7799 refresh. I understand that this bis docume= nt is intended to keep the main Active/Passive/Hybrid classification guidan= ce unchanged, while refreshing the examples and references so that the docu= ment can better support BCP status.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> I reviewed draft-fioccola-ippm-rfc7799bis-00 and have a few comments.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> 1. First, Appendix A appears to have a typo issue. It says =93The main chan= ges since [RFC799]=94, but this should be =93[RFC7799]=94. The correspondin= g informative reference to RFC799 also seems unintended and can probably be= removed.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> 2. Second, Section 7 currently says that the document has no Operatio= nal Considerations. Since the document is intended as BCP and now includes = examples of methods that generate traffic or modify measurement-related fie= lds in user traffic, I think it would be useful to add some general operational considerations. This does not ne= ed to replace the method-specific operational considerations, but could pro= vide a short checklist covering added measurement traffic, header modificat= ions, MTU or fragmentation effects, possible packet treatment or ECMP effects, measurement export traffic, and= the placement of observation or measurement points.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> 3. Third, for the Hybrid Type I examples in Section 5, especially Alternate= -Marking, IOAM, and PDM, the text says that these methods intend to have a = minor effect on the measured stream and the network. I think this is reason= able as an intent, but the text could more clearly state that the actual effect depends on deployment cond= itions. For example, adding or modifying measurement-related fields may aff= ect MTU, encapsulation, forwarding behavior, ECMP hashing, middlebox handli= ng, or hardware fast-path processing. This would make the classification more robust without changing the classi= fication itself.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> 4. Forth, the Security Considerations currently mainly refer to LMAP. Since= the refreshed examples include methods that add, modify, or expose measure= ment-related information in packets, it may be useful to add a short genera= l note that such methods can expose topology, timing, path, traffic pattern, or other operational information,= and that each method specification should discuss the corresponding securi= ty and privacy risks.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> If I had any misunderstandings, please point out. Thank you very much for t= he effort.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Best,</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Libin</div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <hr style=3D"display: inline-block; width: 98%;"> <div id=3D"divRplyFwdMsg"> <div style=3D"direction: ltr; font-family: Calibri, sans-serif; font-size: = 11pt; color: rgb(0, 0, 0);"> <b>From:</b> Giuseppe Fioccola <giuseppe.fioccola=3D40huawei.com@dm= arc.ietf.org><br> <b>Sent:</b> Friday, June 12, 2026 5:59 PM<br> <b>To:</b> Giuseppe Fioccola <giuseppe.fioccola=3D40huawei.com@dmar= c.ietf.org>; [email protected] <[email protected]= om>; ippm <[email protected]>; bmwg <[email protected]><br> <b>Subject:</b> [bmwg] Re: About RFC 7799 BCP Satus Change</div> <div style=3D"direction: ltr;"> </div> </div> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">Hi All,</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">To follow up on the status change of= RFC7799 as BCP, I just published an initial version of RFC7799bis, as sugg= ested by the IESG:</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif; color: rgb(70, 120, 134);"><a href=3D= "https://datatracker.ietf.org/doc/draft-fioccola-ippm-rfc7799bis/" id=3D"OW= A3fed9cc9-9306-07b6-c183-5c84cfdb7080" class=3D"OWAAutoLink" data-auth=3D"N= otApplicable" style=3D"color: rgb(70, 120, 134); margin-top: 0px; margin-bo= ttom: 0px;"><u>https://datatracker.ietf.org/doc/draft-fioccola-ippm-rfc7799= bis/</u></a></span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">I would greatly appreciated your rev= iews and contributions.</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">Regards,</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">Giuseppe</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <div style=3D"padding: 3pt 0in 0in; border-top: 1pt solid rgb(225, 225, 225= );"> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"><b>From:</b> Giuseppe Fioccola = <giuseppe.fioccola=3D40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]><br> <b>Sent:</b> Friday, May 22, 2026 11:23 AM<br> <b>To:</b> [email protected]; ippm <[email protected]>; b= mwg <[email protected]><br> <b>Subject:</b> [bmwg] Re: About RFC 7799 BCP Satus Change</span></p> </div> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"> </p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">Hi Med,</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">I can surely volunteer to lead this = effort. Based on the feedback from the IESG, some sections can be refreshed= while other parts of the document can be kept unchanged.</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">Regards,</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;">Giuseppe</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"> </span></p> <div style=3D"padding: 3pt 0in 0in; border-top: 1pt solid rgb(225, 225, 225= );"> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: Calibri, sans-serif;"><b>From:</b> </span><span style=3D"font-family: Calibri, sans-serif; color: rgb(70, 120,= 134);"><a href=3D"mailto:[email protected]" id=3D"OWAa8ceb96a-6= 75e-cc3b-23d9-d9c7c2d95b4d" class=3D"OWAAutoLink" style=3D"color: rgb(70, 1= 20, 134); margin-top: 0px; margin-bottom: 0px;"><u>mohamed.boucadair@orange= .com</u></a></span><span style=3D"font-family: Calibri, sans-serif;"> = <</span><span style=3D"font-family: Calibri, sans-serif; color: rgb(70, = 120, 134);"><a href=3D"mailto:[email protected]" id=3D"OWA15a037= 7e-7d14-b7ee-125a-d2cda6506380" class=3D"OWAAutoLink" style=3D"color: rgb(7= 0, 120, 134); margin-top: 0px; margin-bottom: 0px;"><u>mohamed.boucadair@or= ange.com</u></a></span><span style=3D"font-family: Calibri, sans-serif;">&g= t;<br> <b>Sent:</b> Friday, May 22, 2026 11:06 AM<br> <b>To:</b> ippm <</span><span style=3D"font-family: Calibri, sans-s= erif; color: rgb(70, 120, 134);"><a href=3D"mailto:[email protected]" id=3D"OWA= 20f3ec00-d1d5-e4e0-6c75-a1d61c3339bc" class=3D"OWAAutoLink" style=3D"color:= rgb(70, 120, 134); margin-top: 0px; margin-bottom: 0px;"><u>[email protected]<= /u></a></span><span style=3D"font-family: Calibri, sans-serif;">>; bmwg <</span><span style=3D"font-family: Calibri, sans-serif; color: rg= b(70, 120, 134);"><a href=3D"mailto:[email protected]" id=3D"OWA60edb910-06e6-e= 22d-75c3-1ca598534aad" class=3D"OWAAutoLink" style=3D"color: rgb(70, 120, 1= 34); margin-top: 0px; margin-bottom: 0px;"><u>[email protected]</u></a></span><= span style=3D"font-family: Calibri, sans-serif;">><br> <b>Subject:</b> [bmwg] About RFC 7799 BCP Satus Change</span></p> </div> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"> </p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";">Hi all,</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";">Some ADs think that it is better= to have a refresh/cleanup of RFC7799 instead of proceeding with the status= change as initially planned by BMWG/IPPM WGs. The refresh would be mainly picking more recent illustration examples and = update some references in Section 4. That clean-up does not alter/impact th= e main guidance.</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";">If you volunteer to lead this re= fresh, please let ippm/bmwg know. Thank you.</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";"> </span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";">Cheers,</span></p> <p style=3D"margin: 0in; font-family: Aptos; font-size: 11pt;"><span style= =3D"font-family: "Courier New";">Med</span></p> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">_______________________________________= _____________________________________________________________________</div>= </pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">Ce message et ses pieces jointes peuven= t contenir des informations confidentielles ou privilegiees et ne doivent d= onc</div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">pas etre diffuses, exploites ou copies = sans autorisation. Si vous avez recu ce message par erreur, veuillez le sig= naler</div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">a l'expediteur et le detruire ainsi que= les pieces jointes. Les messages electroniques etant susceptibles d'altera= tion,</div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">Orange decline toute responsabilite si = ce message a ete altere, deforme ou falsifie. Merci.</div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;"> </div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">This message and its attachments may co= ntain confidential or privileged information that may be protected by law;<= /div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">they should not be distributed, used or= copied without authorisation.</div></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">If you have received this email in erro= r, please notify the sender and delete this message and its attachments.</d= iv></pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">As emails may be altered, Orange is not= liable for messages that have been modified, changed or falsified.</div></= pre> <pre style=3D"margin: 0in 0in 0.0001pt;"><div style=3D"font-family: "C= ourier New"; font-size: 10pt;">Thank you.</div></pre> </body> </html> --_000_TY4PR01MB12668FA0435D6AAD5FCBF506DE2E52TY4PR01MB12668jp_-- --===============5347800202789576684== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IGlwcG0tbGVhdmVAaWV0Zi5vcmcK --===============5347800202789576684==--