[ippm] Re: About RFC 7799 BCP Satus Change
Libin Liu <[email protected]> Wed, 17 Jun 2026 02:48:25 +0000
| Newsgroups | gmane.ietf.ippm,gmane.ietf.bmwg |
|---|---|
| Message-ID | <TY4PR01MB12668D5EB8A047D3D96382A48E2E42@TY4PR01MB12668.jpnprd01.prod.outlook.com> |
--===============4454136442412456298== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_TY4PR01MB12668D5EB8A047D3D96382A48E2E42TY4PR01MB12668jp_" --_000_TY4PR01MB12668D5EB8A047D3D96382A48E2E42TY4PR01MB12668jp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi Giuseppe, Thank you for the quick response and for considering my comments. I read yo= ur inline replies and they look good to me. I will follow the GitHub repo. Best, Libin ________________________________ From: Giuseppe Fioccola <[email protected]> Sent: Tuesday, June 16, 2026 6:17 PM To: Libin Liu <[email protected]>; [email protected] <mohame= [email protected]>; ippm <[email protected]>; bmwg <[email protected]> Subject: RE: About RFC 7799 BCP Satus Change 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 =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. [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_TY4PR01MB12668D5EB8A047D3D96382A48E2E42TY4PR01MB12668jp_ 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"line-height: normal; margin: 0px; fo= nt-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helveti= ca, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Hi Giuseppe,</div> <div class=3D"elementToProof" style=3D"line-height: normal; margin: 0px; fo= nt-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helveti= ca, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"line-height: normal; margin: 0px; fo= nt-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helveti= ca, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Thank you for the quick response and for considering my comments. I read yo= ur inline replies and they look good to me. I will follow the GitHub repo.<= /div> <div class=3D"elementToProof" style=3D"line-height: normal; margin: 0px; mi= n-height: 15px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService= , Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"line-height: normal; margin: 0px; mi= n-height: 15px; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService= , Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"line-height: normal; margin: 0px; fo= nt-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helveti= ca, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Best,<br> Libin</div> <div id=3D"appendonsend"></div> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Giuseppe Fioccola <= ;[email protected]><br> <b>Sent:</b> Tuesday, June 16, 2026 6:17 PM<br> <b>To:</b> Libin Liu <[email protected]>; mohamed.boucadair@orang= e.com <[email protected]>; ippm <[email protected]>; bmw= g <[email protected]><br> <b>Subject:</b> RE: About RFC 7799 BCP Satus Change</font> <div> </div> </div> <style> <!-- @font-face {font-family:"Cambria Math"} @font-face {font-family:Calibri} @font-face {font-family:Consolas} @font-face {font-family:Aptos} p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif} a:link, span.x_MsoHyperlink {color:blue; text-decoration:underline} pre {margin:0in; font-size:10.0pt; font-family:"Courier New"} span.x_HTMLPreformattedChar {font-family:Consolas} span.x_EmailStyle21 {font-family:"Calibri",sans-serif; color:windowtext} .x_MsoChpDefault {font-size:10.0pt} @page WordSection1 {margin:1.0in 1.0in 1.0in 1.0in} div.x_WordSection1 {} --> </style> <div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:break= -word"> <div class=3D"x_WordSection1"> <p class=3D"x_MsoNormal">Hi Libin,</p> <p class=3D"x_MsoNormal">Thank you for your review.</p> <p class=3D"x_MsoNormal">I will address your comments in the next revision.= Note that I also created a GitHub Repository for it (<a href=3D"https://gi= thub.com/giuseppefioccola/draft-fioccola-ippm-rfc7799bis">https://github.co= m/giuseppefioccola/draft-fioccola-ippm-rfc7799bis</a>).</p> <p class=3D"x_MsoNormal">Please see my additional replies inline tagged as = [GF]</p> <p class=3D"x_MsoNormal"> </p> <p class=3D"x_MsoNormal">Regards,</p> <p class=3D"x_MsoNormal"> </p> <p class=3D"x_MsoNormal">Giuseppe</p> <p class=3D"x_MsoNormal"> </p> <div> <div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i= n 0in 0in"> <p class=3D"x_MsoNormal"><b>From:</b> Libin Liu <[email protected]&g= t; <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</p> </div> </div> <p class=3D"x_MsoNormal"> </p> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">Hi Giuseppe,</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">Thanks for taking on the RFC7799 refresh. = I understand that this bis document is intended to keep the main Active/Pas= sive/Hybrid classification guidance unchanged, while refreshing the examples and references so that the document can bett= er support BCP status.</span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">[GF]: Yes, correct.</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">I reviewed draft-fioccola-ippm-rfc7799bis-= 00 and have a few comments.</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">1. First, Appendix A appears to have a typ= o issue. It says =93The main changes since [RFC799]=94, but this should be = =93[RFC7799]=94. The corresponding informative reference to RFC799 also seems unintended and can probably be removed.</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">[GF]: It is a typo. I will replace it with= RFC7799 and also remove the reference to RFC799.</span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">2. Second, Section 7 currently says = that the document has no Operational Considerations. Since the document is = intended as BCP and now includes examples of methods that generate traffic or modify measurement-related fields in user traffic= , I think it would be useful to add some general operational considerations= . This does not need to replace the method-specific operational considerati= ons, 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.</span></p= > </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">[GF]: Good point. I can definitely add gen= eral operational considerations and then refer to the various documents for= the detailed aspects.</span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">3. Third, for the Hybrid Type I examples i= n Section 5, especially Alternate-Marking, IOAM, and PDM, the text says tha= t these methods intend to have a minor effect on the measured stream and the network. I think this is reasonable as an i= ntent, but the text could more clearly state that the actual effect depends= on deployment conditions. For example, adding or modifying measurement-rel= ated fields 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.</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">[GF]: Ok, for the Hybrid method examples, = I will further specify that the effects on the measured stream also depend = on other conditions.</span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">4. Forth, the Security Considerations curr= ently mainly refer to LMAP. Since the refreshed examples include methods th= at add, 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 o= perational information, and that each method specification should discuss t= he corresponding security and privacy risks.</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">[GF]: Agree, the Security Considerations s= ection will be updated accordingly.</span></p> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">If I had any misunderstandings, please poi= nt out. Thank you very much for the effort.</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">Best,</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black">Libin</span></p> </div> <div> <p class=3D"x_MsoNormal"><span style=3D"font-size:12.0pt; font-family:"= ;Aptos",serif; color:black"> </span></p> </div> <div class=3D"x_MsoNormal" align=3D"center" style=3D"text-align:center"> <hr size=3D"2" width=3D"98%" align=3D"center"> </div> <div id=3D"x_divRplyFwdMsg"> <div> <p class=3D"x_MsoNormal"><b><span style=3D"color:black">From:</span></b><sp= an style=3D"color:black"> Giuseppe Fioccola <giuseppe.fioccola=3D40= huawei.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</span></p> </div> <div> <p class=3D"x_MsoNormal"> </p> </div> </div> <p>Hi All,<span style=3D"font-family:"Aptos",serif"></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"></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"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <p>I would greatly appreciated your reviews and contributions.<span style= =3D"font-family:"Aptos",serif"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <p>Regards,<span style=3D"font-family:"Aptos",serif"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <p>Giuseppe<span style=3D"font-family:"Aptos",serif"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i= n 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"></span></p> </div> <p><span style=3D"font-family:"Aptos",serif"> </span></p> <p>Hi Med,<span style=3D"font-family:"Aptos",serif"></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"></= span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <p>Regards,<span style=3D"font-family:"Aptos",serif"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <p>Giuseppe<span style=3D"font-family:"Aptos",serif"></span></p> <p> <span style=3D"font-family:"Aptos",serif"></span></p> <div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i= n 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"></span></p> </div> <p><span style=3D"font-family:"Aptos",serif"> </span></p> <p><span style=3D"font-family:"Courier New"">Hi all,</span><span = style=3D"font-family:"Aptos",serif"></span></p> <p><span style=3D"font-family:"Courier New""> </span><span s= tyle=3D"font-family:"Aptos",serif"></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"></span></p> <p><span style=3D"font-family:"Courier New""> </span><span s= tyle=3D"font-family:"Aptos",serif"></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"></span></p> <p><span style=3D"font-family:"Courier New""> </span><span s= tyle=3D"font-family:"Aptos",serif"></span></p> <p><span style=3D"font-family:"Courier New"">Cheers,</span><span = style=3D"font-family:"Aptos",serif"></span></p> <p><span style=3D"font-family:"Courier New"">Med</span><span styl= e=3D"font-family:"Aptos",serif"></span></p> <div> <pre>______________________________________________________________________= ______________________________________</pre> </div> <div> <pre>Ce message et ses pieces jointes peuvent contenir des informations con= fidentielles ou privilegiees et ne doivent donc</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</span= ></pre> </div> <div> <pre>a l'expediteur et le detruire ainsi que les pieces jointes. Les messag= es electroniques etant susceptibles d'alteration,</pre> </div> <div> <pre><span lang=3D"IT">Orange decline toute responsabilite si ce message a = ete altere, deforme ou falsifie. </span>Merci.</pre> </div> <div> <pre> </pre> </div> <div> <pre>This message and its attachments may contain confidential or privilege= d information that may be protected by law;</pre> </div> <div> <pre>they should not be distributed, used or copied without authorisation.<= /pre> </div> <div> <pre>If you have received this email in error, please notify the sender and= delete this message and its attachments.</pre> </div> <div> <pre>As emails may be altered, Orange is not liable for messages that have = been modified, changed or falsified.</pre> </div> <div> <pre>Thank you.</pre> </div> </div> </div> </body> </html> --_000_TY4PR01MB12668D5EB8A047D3D96382A48E2E42TY4PR01MB12668jp_-- --===============4454136442412456298== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwbSBtYWls aW5nIGxpc3QgLS0gaXBwbUBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IGlwcG0tbGVhdmVAaWV0Zi5vcmcK --===============4454136442412456298==--