[ippm] Re: About RFC 7799 BCP Satus Change
Giuseppe Fioccola <giuseppe.fioccola=40huawei.com-Tr9gZwTxerDR74oF6e/[email protected]> Tue, 16 Jun 2026 10:17:20 +0000
| Newsgroups | gmane.ietf.ippm,gmane.ietf.bmwg |
|---|---|
| Message-ID | <[email protected]> |
--===============9067268059557696692== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_8eff06aa284949d9b139a9a4d114845chuaweicom_" --_000_8eff06aa284949d9b139a9a4d114845chuaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Libin, Thank you for your review. I will address your comments in the next revision. Note that I also created= a GitHub Repository for it (https://github.com/giuseppefioccola/draft-fioc= cola-ippm-rfc7799bis). Please see my additional replies inline tagged as [GF] Regards, Giuseppe From: Libin Liu <[email protected]> Sent: Tuesday, June 16, 2026 7:40 AM To: Giuseppe Fioccola <[email protected]>; mohamed.boucadair@ora= nge.com; ippm <[email protected]>; bmwg <[email protected]> Subject: Re: About RFC 7799 BCP Satus Change 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. [GF]: Yes, correct. I reviewed draft-fioccola-ippm-rfc7799bis-00 and have a few comments. 1. First, Appendix A appears to have a typo issue. It says "The main change= s since [RFC799]", but this should be "[RFC7799]". The corresponding inform= ative reference to RFC799 also seems unintended and can probably be removed= . [GF]: It is a typo. I will replace it with RFC7799 and also remove the refe= rence to RFC799. 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. [GF]: Good point. I can definitely add general operational considerations a= nd then refer to the various documents for the detailed aspects. 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. [GF]: Ok, for the Hybrid method examples, I will further specify that the e= ffects on the measured stream also depend on other conditions. 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. [GF]: Agree, the Security Considerations section will be updated accordingl= y. 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_8eff06aa284949d9b139a9a4d114845chuaweicom_ 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)"> <!--[if !mso]><style>v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style><![endif]--><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; panose-1:0 0 0 0 0 0 0 0 0 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} pre {mso-style-priority:99; mso-style-link:"HTML Preformatted Char"; margin:0in; 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;} 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:1.0in 1.0in 1.0in 1.0in;} 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"blue" vlink=3D"purple" style=3D"word-wrap:brea= k-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Hi Libin,<o:p></o:p></p> <p class=3D"MsoNormal">Thank you for your review.<o:p></o:p></p> <p class=3D"MsoNormal">I will address your comments in the next revision. N= ote that I also created a GitHub Repository for it (<a href=3D"https://gith= ub.com/giuseppefioccola/draft-fioccola-ippm-rfc7799bis">https://github.com/= giuseppefioccola/draft-fioccola-ippm-rfc7799bis</a>).<o:p></o:p></p> <p class=3D"MsoNormal">Please see my additional replies inline tagged as [G= F]<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Regards,<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Giuseppe<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b>From:</b> Libin Liu <[email protected]>= <br> <b>Sent:</b> Tuesday, June 16, 2026 7:40 AM<br> <b>To:</b> Giuseppe Fioccola <[email protected]>; mohamed.= [email protected]; ippm <[email protected]>; bmwg <[email protected]>= ;<br> <b>Subject:</b> Re: About RFC 7799 BCP Satus Change<o:p></o:p></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">Hi Giuseppe,<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">Thanks for taking on the RFC7799 refresh. I un= derstand that this bis document is intended to keep the main Active/Passive= /Hybrid classification guidance unchanged, while refreshing the examples and references so that the document can better sup= port BCP status.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">[GF]: Yes, correct.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">I reviewed draft-fioccola-ippm-rfc7799bis-00 a= nd have a few comments.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">1. First, Appendix A appears to have a typo is= sue. It says “The main changes since [RFC799]”, but this should= be “[RFC7799]”. The corresponding informative reference to RFC799 also seems unintended and can probably be removed.<o:p></o:p></span= ></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">[GF]: It is a typo. I will replace it with RFC= 7799 and also remove the reference to RFC799.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">2. Second, Section 7 currently says that= the document has no Operational Considerations. Since the document is inte= nded as BCP and now includes examples of methods that generate traffic or modify measurement-related fields in user traffic, I t= hink it would be useful to add some general operational considerations. Thi= s does not need to replace the method-specific operational considerations, = but could provide a short checklist covering added measurement traffic, header modifications, MTU or fragmenta= tion effects, possible packet treatment or ECMP effects, measurement export= traffic, and the placement of observation or measurement points.<o:p></o:p= ></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">[GF]: Good point. I can definitely add general= operational considerations and then refer to the various documents for the= detailed aspects.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">3. Third, for the Hybrid Type I examples in Se= ction 5, especially Alternate-Marking, IOAM, and PDM, the text says that th= ese methods intend to have a minor effect on the measured stream and the network. I think this is reasonable as an intent, = but the text could more clearly state that the actual effect depends on dep= loyment conditions. For example, adding or modifying measurement-related fi= elds may affect MTU, encapsulation, forwarding behavior, ECMP hashing, middlebox handling, or hardware fast-pa= th processing. This would make the classification more robust without chang= ing the classification itself.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">[GF]: Ok, for the Hybrid method examples, I wi= ll further specify that the effects on the measured stream also depend on o= ther conditions.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">4. Forth, the Security Considerations currentl= y mainly refer to LMAP. Since the refreshed examples include methods that a= dd, modify, or expose measurement-related information in packets, it may be useful to add a short general note that such methods= can expose topology, timing, path, traffic pattern, or other operational i= nformation, and that each method specification should discuss the correspon= ding security and privacy risks.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">[GF]: Agree, the Security Considerations secti= on will be updated accordingly.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">If I had any misunderstandings, please point o= ut. Thank you very much for the effort.<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">Best,<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black">Libin<o:p></o:p></span></p> </div> <div> <p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:"Ap= tos",serif;color:black"><o:p> </o:p></span></p> </div> <div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"> <hr size=3D"2" width=3D"98%" align=3D"center"> </div> <div id=3D"divRplyFwdMsg"> <div> <p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span= style=3D"color:black"> Giuseppe Fioccola <giuseppe.fioccola=3D40hu= awei.com-Tr9gZwTxerDR74oF6e/[email protected]><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<o:p></o:p><= /span></p> </div> <div> <p class=3D"MsoNormal"> <o:p></o:p></p> </div> </div> <p>Hi All,<span style=3D"font-family:"Aptos",serif"><o:p></o:p></= span></p> <p>To follow up on the status change of RFC7799 as BCP, I just published an= initial version of RFC7799bis, as suggested by the IESG:<span style=3D"fon= t-family:"Aptos",serif"><o:p></o:p></span></p> <p><a href=3D"https://datatracker.ietf.org/doc/draft-fioccola-ippm-rfc7799b= is/"><span style=3D"color:#467886">https://datatracker.ietf.org/doc/draft-f= ioccola-ippm-rfc7799bis/</span></a><span style=3D"font-family:"Aptos&q= uot;,serif"><o:p></o:p></span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <p>I would greatly appreciated your reviews and contributions.<span style= =3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <p>Regards,<span style=3D"font-family:"Aptos",serif"><o:p></o:p><= /span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <p>Giuseppe<span style=3D"font-family:"Aptos",serif"><o:p></o:p><= /span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p><b>From:</b> Giuseppe Fioccola <giuseppe.fioccola=3D40huawei.com= @dmarc.ietf.org><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 style= =3D"font-family:"Aptos",serif"><o:p></o:p></span></p> </div> <p><span style=3D"font-family:"Aptos",serif"> <o:p></o:p></s= pan></p> <p>Hi Med,<span style=3D"font-family:"Aptos",serif"><o:p></o:p></= span></p> <p>I can surely volunteer to lead this effort. Based on the feedback from t= he IESG, some sections can be refreshed while other parts of the document c= an be kept unchanged.<span style=3D"font-family:"Aptos",serif"><o= :p></o:p></span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <p>Regards,<span style=3D"font-family:"Aptos",serif"><o:p></o:p><= /span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <p>Giuseppe<span style=3D"font-family:"Aptos",serif"><o:p></o:p><= /span></p> <p> <span style=3D"font-family:"Aptos",serif"><o:p></o:p></s= pan></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p><b>From:</b> <a href=3D"mailto:[email protected]"><span style= =3D"color:#467886">[email protected]</span></a> <<a href= =3D"mailto:[email protected]"><span style=3D"color:#467886">moha= [email protected]</span></a>><br> <b>Sent:</b> Friday, May 22, 2026 11:06 AM<br> <b>To:</b> ippm <<a href=3D"mailto:[email protected]"><span style=3D"co= lor:#467886">[email protected]</span></a>>; bmwg <<a href=3D"mailto:bmwg@= ietf.org"><span style=3D"color:#467886">[email protected]</span></a>><br> <b>Subject:</b> [bmwg] About RFC 7799 BCP Satus Change<span style=3D"f= ont-family:"Aptos",serif"><o:p></o:p></span></p> </div> <p><span style=3D"font-family:"Aptos",serif"> <o:p></o:p></s= pan></p> <p><span style=3D"font-family:"Courier New"">Hi all,</span><span = style=3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New""> </span><span s= tyle=3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New"">Some ADs think that = it is better to have a refresh/cleanup of RFC7799 instead of proceeding wit= h the status change as initially planned by BMWG/IPPM WGs. The refresh woul= d be mainly picking more recent illustration examples and update some references in Section 4. That clean-up does not a= lter/impact the main guidance.</span><span style=3D"font-family:"Aptos= ",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New""> </span><span s= tyle=3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New"">If you volunteer to = lead this refresh, please let ippm/bmwg know. Thank you.</span><span style= =3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New""> </span><span s= tyle=3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New"">Cheers,</span><span = style=3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <p><span style=3D"font-family:"Courier New"">Med</span><span styl= e=3D"font-family:"Aptos",serif"><o:p></o:p></span></p> <div> <pre>______________________________________________________________________= ______________________________________<o:p></o:p></pre> </div> <div> <pre>Ce message et ses pieces jointes peuvent contenir des informations con= fidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre> </div> <div> <pre>pas etre diffuses, exploites ou copies sans autorisation. <span lang= =3D"IT">Si vous avez recu ce message par erreur, veuillez le signaler<o:p><= /o:p></span></pre> </div> <div> <pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag= es electroniques etant susceptibles d'alteration,<o:p></o:p></pre> </div> <div> <pre><span lang=3D"IT">Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. </span>Merci.<o:p></o:p></pre> </div> <div> <pre> <o:p></o:p></pre> </div> <div> <pre>This message and its attachments may contain confidential or privilege= d information that may be protected by law;<o:p></o:p></pre> </div> <div> <pre>they should not be distributed, used or copied without authorisation.<= o:p></o:p></pre> </div> <div> <pre>If you have received this email in error, please notify the sender and= delete this message and its attachments.<o:p></o:p></pre> </div> <div> <pre>As emails may be altered, Orange is not liable for messages that have = been modified, changed or falsified.<o:p></o:p></pre> </div> <div> <pre>Thank you.<o:p></o:p></pre> </div> </div> </body> </html> --_000_8eff06aa284949d9b139a9a4d114845chuaweicom_-- --===============9067268059557696692== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IGlwcG0tbGVhdmVAaWV0Zi5vcmcK --===============9067268059557696692==--