[Pals] Re: PW Operational Status in RFC9291 (was: Re: PW Operational Status in RFC 9251)
[email protected] Fri, 19 Sep 2025 12:07:12 +0000
| Newsgroups | gmane.ietf.pwe3,gmane.ietf.opsawg |
|---|---|
| Message-ID | <PR0P264MB28850F971845150E829BE0A88811A@PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM> |
--===============5798202365012417333== Content-Language: fr-FR Content-Type: multipart/alternative; boundary="_000_PR0P264MB28850F971845150E829BE0A88811APR0P264MB2885FRAP_" --_000_PR0P264MB28850F971845150E829BE0A88811APR0P264MB2885FRAP_ Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Sasha, all, (apologies for the delay to reply) (ccing onions) Agree with Joe. That's said, there are few questions that might require some clarifications= vs. the intended use/interpretation of the service ops status. That issue = is tracked at: https://github.com/oscargdd/lxnm-bis/issues/4 or https://ww= w.ietf.org/archive/id/draft-bg-onions-update-network-service-models-00.txt = (Section 4.3). Cheers, Med De : Joe Clarke (jclarke) <[email protected]> Envoy=E9 : lundi 11 ao=FBt 2025 15:26 =C0 : Alexander Vainshtein <[email protected]= g>; BOUCADAIR Mohamed INNOV/NET <[email protected]>; oscar.gonza= [email protected]; [email protected]; luis-angel.munoz@vodafon= e.com Cc : [email protected]; Pseudowire And LDP-enabled Services Discussion List <= [email protected]> Objet : PW Operational Status in RFC9291 (was: Re: PW Operational Status in= RFC 9251) As a contributor of opsawg (authors of 9291 can correct me), the scope of R= FC9291 and RFC5601 are not the same. RFC5601 defines a device-level MIB mo= dule specifically for pseudowires. RFC9291 defines a network-level YANG mo= dule abstracting various L2VPN network services and is designed to be imple= mented on a network controller. Therefore, the oper-status is not specific= ally tied to a pseudowire class and not tied to a particular device-level i= mplementation (i.e., it applies to the network-level L2VPN). The intent of YANG network and service data models is that they abstract ca= pabilities to a customer-facing or network-facing portal/controller and ult= imately rely on device-level interfaces (hopefully standards-based, device-= level YANG data models, but maybe proprietary YANG data models or CLI) to d= o the configuration and perform the monitoring across the full service impl= ementation. It would be up to the device-level pseudowire interface to pro= vide the modeling and documentation that the PW-MIB has. Joe From: Alexander Vainshtein <[email protected]= g<mailto:[email protected]>> Date: Sunday, August 10, 2025 at 07:27 To: [email protected]<mailto:[email protected]> <moha= [email protected]<mailto:[email protected]>>, oscar.gonza= [email protected]<mailto:[email protected]> <oscar= [email protected]<mailto:[email protected]>>= , [email protected]<mailto:[email protected]> <samir.barguil@gm= ail.com<mailto:[email protected]>>, [email protected]<mai= lto:[email protected]> <[email protected]<mailto:lu= [email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:opsawg@= ietf.org>>, Pseudowire And LDP-enabled Services Discussion List <pals@ietf.= org<mailto:[email protected]>> Subject: [OPSAWG]PW Operational Status in RFC 9251 Dear authors of RFC 9291<https://datatracker.ietf.org/doc/html/rfc9291>, I have looked up the standard and found that it presumably mentions Operati= onal Status of a pseudowire as oper-status without any clarifications and/o= r references, and, specifically, without any association with various indic= ators in the PW Status TLV. This is quite different from RFC 5601<https://datatracker.ietf.org/doc/html= /rfc5601>, which explicitly provides such linkage as can be seen from the = quoted text below: pwOperStatus OBJECT-TYPE SYNTAX PwOperStatusTC MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the operational status of the PW; it does not reflect the status of the Customer Edge (CE) bound interface. It is set to down only if pwNotForwarding, psnFacingPwRxFault, or psnFacingPwTxFault indications are set in pwLocalStatus or pwRemoteStatus. It indicates 'lowerLayerDown' if the only reason for not being in the 'up' state is that either the outer tunnel or physical layer of the network side is in the 'down' state. All other states are declared based on the description of the PwOperStatusTC. " I wonder whether, from your POV, the quoted definition of the PW Operatonal= Status is still applicable or not. Regards, and lots of thanks in advance, Sasha Disclaimer This e-mail together with any attachments may contain information of Ribbon= Communications Inc. and its Affiliates that is confidential and/or proprie= tary for the sole use of the intended recipient. Any review, disclosure, re= liance or distribution by others or forwarding without express permission i= s strictly prohibited. If you are not the intended recipient, please notify= the sender immediately and then delete all copies, including any attachmen= ts. ___________________________________________________________________________= _________________________________ 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_PR0P264MB28850F971845150E829BE0A88811APR0P264MB2885FRAP_ Content-Type: text/html; charset="iso-8859-1" MIME-Version: 1.0 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=3Diso-8859-= 1"> <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:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:Aptos;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:10.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#467886; text-decoration:underline;} span.EmailStyle22 {mso-style-type:personal-reply; font-family:"Courier New"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} 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"FR" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:bre= ak-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">Hi Sasha, all, <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">(apologies for t= he delay to reply)<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">(ccing onions)<o= :p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US"><o:p> </o:p= ></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">Agree with Joe. <o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US"><o:p> </o:p= ></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">That’s sai= d, there are few questions that might require some clarifications vs. the i= ntended use/interpretation of the service ops status. That issue is tracked at: <a href=3D"https://github.com/oscargdd/lxnm-bis/= issues/4"> https://github.com/oscargdd/lxnm-bis/issues/4</a> or <a href=3D"https= ://www.ietf.org/archive/id/draft-bg-onions-update-network-service-models-00= .txt"> https://www.ietf.org/archive/id/draft-bg-onions-update-network-service-mode= ls-00.txt</a> (Section 4.3).<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US"><o:p> </o:p= ></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">Cheers,<o:p></o:= p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US">Med<o:p></o:p></= span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Courier New";mso-fareast-language:EN-US"><o:p> </o:p= ></span></p> <div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm = 4.0pt"> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:"= ;Calibri",sans-serif">De :</span></b><span style=3D"font-size:11.= 0pt;font-family:"Calibri",sans-serif"> Joe Clarke (jclarke) <j= [email protected]> <br> <b>Envoy=E9 :</b> lundi 11 ao=FBt 2025 15:26<br> <b>=C0 :</b> Alexander Vainshtein <Alexander.Vainshtein=3D40rbbn.co= [email protected]>; BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@ora= nge.com>; [email protected]; [email protected]; = [email protected]<br> <b>Cc :</b> [email protected]; Pseudowire And LDP-enabled Services Discu= ssion List <[email protected]><br> <b>Objet :</b> PW Operational Status in RFC9291 (was: Re: PW Operation= al Status in RFC 9251)<o:p></o:p></span></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" = style=3D"font-size:12.0pt"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif">As a contributor of opsawg (authors = of 9291 can correct me), the scope of RFC9291 and RFC5601 are not the same.= RFC5601 defines a device-level MIB module specifically for pseudowires. RFC9291 defines a <i>network-level</i> YANG module = abstracting various L2VPN network services and is designed to be implemente= d on a network controller. Therefore, the oper-status is not specific= ally tied to a pseudowire class and not tied to a particular device-level implementation (i.e., it applies to the netwo= rk-level L2VPN).<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif">The intent of YANG network and servi= ce data models is that they abstract capabilities to a customer-facing or n= etwork-facing portal/controller and ultimately rely on device-level interfaces (hopefully standards-based, device-level YANG d= ata models, but maybe proprietary YANG data models or CLI) to do the config= uration and perform the monitoring across the full service implementation.&= nbsp; It would be up to the device-level pseudowire interface to provide the modeling and documentation that the PW= -MIB has.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif">Joe<o:p></o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-= family:"Calibri",sans-serif"><o:p> </o:p></span></p> <div id=3D"mail-editor-reference-message-container"> <div> <div> <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0cm;margin-right:0cm;mar= gin-bottom:12.0pt;margin-left:36.0pt"> <b><span lang=3D"EN-US" style=3D"font-size:12.0pt;color:black">From: </span= ></b><span lang=3D"EN-US" style=3D"font-size:12.0pt;color:black">Alexander = Vainshtein <<a href=3D"mailto:[email protected]= tf.org">[email protected]</a>><br> <b>Date: </b>Sunday, August 10, 2025 at 07:27<br> <b>To: </b><a href=3D"mailto:[email protected]">mohamed.boucadai= [email protected]</a> <<a href=3D"mailto:[email protected]">mohame= [email protected]</a>>, <a href=3D"mailto:[email protected]">oscar.gonzalezdedios= @telefonica.com</a> <<a href=3D"mailto:[email protected]= om">[email protected]</a>>, <a href=3D"mailto:[email protected]">[email protected]</a> <= <a href=3D"mailto:[email protected]">[email protected]</a>>, <a href=3D"mailto:[email protected]">luis-angel.munoz@vodafone.= com</a> <<a href=3D"mailto:[email protected]">luis-angel.mun= [email protected]</a>><br> <b>Cc: </b><a href=3D"mailto:[email protected]">[email protected]</a> <<a hr= ef=3D"mailto:[email protected]">[email protected]</a>>, Pseudowire And LDP-e= nabled Services Discussion List <<a href=3D"mailto:[email protected]">pals@i= etf.org</a>><br> <b>Subject: </b>[OPSAWG]PW Operational Status in RFC 9251<o:p></o:p></span>= </p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt">Dear authors of <a href=3D"https://datatracker.ietf.org/doc/html/rfc9291">RFC 9291</a>,</sp= an><span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt"> </span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt">I have looked up the standard and found that it pr= esumably mentions Operational Status of a pseudowire as </span><span lang=3D"EN-US" style=3D"font-family:"Courier New"">o= per-status</span><span lang=3D"EN-US" style=3D"font-size:11.0pt"> without a= ny clarifications and/or references, and, specifically, without any associa= tion with various indicators in the PW Status TLV.</span><span lang=3D"EN-U= S" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt"> </span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt">This is quite different from <a href=3D"https://datatracker.ietf.org/doc/html/rfc5601">RFC 5601</a>, &nb= sp;which explicitly provides such linkage as can be seen from the quoted te= xt below:</span><span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p>= </span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt"> </span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= pwOperStatus OBJECT-TYPE</span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= SYNTAX P= wOperStatusTC</span><span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></= o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= MAX-ACCESS read-only</span><span= lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= STATUS c= urrent</span><span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></s= pan></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= DESCRIPTION</span><span lang=3D"EN-US" style=3D"fo= nt-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= "This object in= dicates the operational status of the PW; it</span><span lang=3D"EN-US" sty= le=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= does not refle= ct the status of the Customer Edge (CE) bound</span><span lang=3D"EN-US" st= yle=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= interface.&nbs= p; It is set to down only if pwNotForwarding,</span><span lang=3D"EN-US" st= yle=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= psnFacingPwRxF= ault, or psnFacingPwTxFault indications are</span><span lang=3D"EN-US" styl= e=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= set in pwLocal= Status or pwRemoteStatus.</span><span lang=3D"EN-US" style=3D"font-size:12.= 0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= It indicates '= lowerLayerDown' if the only reason for</span><span lang=3D"EN-US" style=3D"= font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= not being in t= he 'up' state is that either the outer tunnel</span><span lang=3D"EN-US" st= yle=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= or physical la= yer of the network side is in the 'down'</span><span lang=3D"EN-US" style= =3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= state.</span><= span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= All other stat= es are declared based on the description</span><span lang=3D"EN-US" style= =3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= of the PwOperS= tatusTC.</span><span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p><= /span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt;background:white"><span = lang=3D"EN-US" style=3D"font-family:"Courier New";color:#212529">= "</span><= span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt"> </span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt">I wonder whether, from your POV, the quoted defini= tion of the PW Operatonal Status is still applicable or not.</span><span la= ng=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt"> </span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt"> </span><span lang=3D"EN-US" style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt">Regards, and lots of thanks in advance,</span><spa= n lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:11.0pt">Sasha</span><span lang=3D"EN-US" style=3D"font-siz= e:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"EN-US" st= yle=3D"font-size:12.0pt"> <o:p></o:p></span></p> </div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0cm;margin-right:0cm;mar= gin-bottom:12.0pt;margin-left:36.0pt"> <span lang=3D"EN-US" style=3D"font-size:12.0pt"><o:p> </o:p></span></p> <p style=3D"margin-left:36.0pt"><b><span lang=3D"EN-US" style=3D"font-size:= 10.0pt;font-family:"Verdana",sans-serif;color:#666666">Disclaimer= </span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:"= ;Verdana",sans-serif;color:#666666"><o:p></o:p></span></p> <p style=3D"margin-left:36.0pt"><span lang=3D"EN-US" style=3D"font-size:8.0= pt;font-family:"Verdana",sans-serif;color:#666666">This e-mail to= gether with any attachments may contain information of Ribbon Communication= s Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclo= sure, reliance or distribution by others or forwarding without express perm= ission is strictly prohibited. If you are not the intended recipient, pleas= e notify the sender immediately and then delete all copies, including any attachments. <o:p></o:p></span><= /p> </div> </div> </div> </div> </div> <pre>_________________<wbr>______________________________<wbr>_____________= _________________<wbr>______________________________<wbr>_ 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.</pre></body> </html> --_000_PR0P264MB28850F971845150E829BE0A88811APR0P264MB2885FRAP_-- --===============5798202365012417333== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUGFscyBtYWls aW5nIGxpc3QgLS0gcGFsc0BpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IHBhbHMtbGVhdmVAaWV0Zi5vcmcK --===============5798202365012417333==--