[ippm] Re: About RFC 7799 BCP Satus Change
Giuseppe Fioccola <giuseppe.fioccola=40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> Fri, 12 Jun 2026 09:59:56 +0000
| Newsgroups | gmane.ietf.ippm,gmane.ietf.bmwg |
|---|---|
| Message-ID | <[email protected]> |
--===============3425554013637422234== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_5ef585afb5764478970ba7515ebe5b23huaweicom_" --_000_5ef585afb5764478970ba7515ebe5b23huaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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_5ef585afb5764478970ba7515ebe5b23huaweicom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4;} @font-face {font-family:Aptos;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:Aptos; mso-ligatures:standardcontextual;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#467886; text-decoration:underline;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New";} span.HTMLPreformattedChar {mso-style-name:"HTML Preformatted Char"; mso-style-priority:99; mso-style-link:"HTML Preformatted"; font-family:Consolas; mso-ligatures:standardcontextual;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-US" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:= break-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Hi All,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">To follow up on the status change of RFC7799 as BCP, I just publishe= d an initial version of RFC7799bis, as suggested by the IESG:<o:p></o:p></s= pan></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><a href=3D"https://datatracker.ietf.org/doc/draft-fioccola-ippm-rfc7= 799bis/">https://datatracker.ietf.org/doc/draft-fioccola-ippm-rfc7799bis/</= a><o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">I would greatly appreciated your reviews and contributions.<o:p></o:= p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Regards,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Giuseppe<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-family:"Calibri",sa= ns-serif;mso-ligatures:none">From:</span></b><span style=3D"font-family:&qu= ot;Calibri",sans-serif;mso-ligatures:none"> Giuseppe Fioccola <gius= eppe.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]>; bmwg &= lt;[email protected]><br> <b>Subject:</b> [bmwg] Re: About RFC 7799 BCP Satus Change<o:p></o:p></span= ></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Hi Med,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">I can surely volunteer to lead this effort. Based on the feedback fr= om the IESG, some sections can be refreshed while other parts of the docume= nt can be kept unchanged.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Regards,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif">Giuseppe<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Calibri",sans-= serif"><o:p> </o:p></span></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b><span style=3D"font-family:"Calibri",sa= ns-serif;mso-ligatures:none">From:</span></b><span style=3D"font-family:&qu= ot;Calibri",sans-serif;mso-ligatures:none"> </span><a href=3D"mailto:[email protected]"><span style=3D"font-= family:"Calibri",sans-serif;mso-ligatures:none">mohamed.boucadair= @orange.com</span></a><span style=3D"font-family:"Calibri",sans-s= erif;mso-ligatures:none"> <</span><a href=3D"mailto:mohamed.boucadair@or= ange.com"><span style=3D"font-family:"Calibri",sans-serif;mso-lig= atures:none">[email protected]</span></a><span style=3D"font-fam= ily:"Calibri",sans-serif;mso-ligatures:none">> <br> <b>Sent:</b> Friday, May 22, 2026 11:06 AM<br> <b>To:</b> ippm <</span><a href=3D"mailto:[email protected]"><span style=3D"= font-family:"Calibri",sans-serif;mso-ligatures:none">[email protected]= g</span></a><span style=3D"font-family:"Calibri",sans-serif;mso-l= igatures:none">>; bmwg <</span><a href=3D"mailto:[email protected]"><span= style=3D"font-family:"Calibri",sans-serif;mso-ligatures:none">bm= [email protected]</span></a><span style=3D"font-family:"Calibri",sans-s= erif;mso-ligatures:none">><br> <b>Subject:</b> [bmwg] About RFC 7799 BCP Satus Change<o:p></o:p></span></p= > </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-family:"Courier= New"">Hi all,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"FR" style=3D"font-family:"Courier= New""><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= 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 and update some references in Section 4. That clean-= up does not alter/impact the main guidance.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= If you volunteer to lead this refresh, please let ippm/bmwg know. Thank you= .<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= <o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= Cheers,<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">= Med<o:p></o:p></span></p> <pre><span lang=3D"FR">____________________________________________________= ________________________________________________________<o:p></o:p></span><= /pre> <pre><span lang=3D"FR">Ce message et ses pieces jointes peuvent contenir de= s informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p= ></span></pre> <pre><span lang=3D"FR">pas etre diffuses, exploites ou copies sans autorisa= tion. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o= :p></span></pre> <pre><span lang=3D"FR">a l'expediteur et le detruire ainsi que les pieces j= ointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o= :p></span></pre> <pre><span lang=3D"FR">Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre> <pre><span lang=3D"FR"><o:p> </o:p></span></pre> <pre><span lang=3D"FR">This message and its attachments may contain confide= ntial or privileged information that may be protected by law;<o:p></o:p></s= pan></pre> <pre><span lang=3D"FR">they should not be distributed, used or copied witho= ut authorisation.<o:p></o:p></span></pre> <pre><span lang=3D"FR">If you have received this email in error, please not= ify the sender and delete this message and its attachments.<o:p></o:p></spa= n></pre> <pre><span lang=3D"FR">As emails may be altered, Orange is not liable for m= essages that have been modified, changed or falsified.<o:p></o:p></span></p= re> <pre><span lang=3D"FR">Thank you.<o:p></o:p></span></pre> </div> </body> </html> --_000_5ef585afb5764478970ba7515ebe5b23huaweicom_-- --===============3425554013637422234== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IGlwcG0tbGVhdmVAaWV0Zi5vcmcK --===============3425554013637422234==--