[OPSAWG]PW Operational Status in RFC9291 (was: Re: PW Op erational Status in RFC 9251)
"Joe Clarke \(jclarke\)" <jclarke=40cisco.com-Tr9gZwTxerDR74oF6e/[email protected]> Mon, 11 Aug 2025 13:25:42 +0000
| Newsgroups | gmane.ietf.opsawg,gmane.ietf.pwe3 |
|---|---|
| Message-ID | <CH2PR11MB8867CBE6C714161245F84689B828A@CH2PR11MB8867.namprd11.prod.outlook.com> |
--===============3807931438830445750== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CH2PR11MB8867CBE6C714161245F84689B828ACH2PR11MB8867namp_" --_000_CH2PR11MB8867CBE6C714161245F84689B828ACH2PR11MB8867namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 <Alexander.Vainshtein=3D40rbbn.com-Tr9gZwTxerCJKFBe7AYdWQ@public.gmane.org= g> Date: Sunday, August 10, 2025 at 07:27 To: [email protected] <[email protected]>, oscar.gonz= [email protected] <[email protected]>, samir.barg= [email protected] <[email protected]>, luis-angel.munoz-ANTagKRnAhdWk0Htik3J/[email protected] <lui= s-angel.munoz-ANTagKRnAhdWk0Htik3J/[email protected]> Cc: [email protected] <[email protected]>, Pseudowire And LDP-enabled Services = Discussion List <[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. --_000_CH2PR11MB8867CBE6C714161245F84689B828ACH2PR11MB8867namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc= hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of= fice/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:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:Aptos; panose-1:2 11 0 4 2 2 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:10.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:#467886; text-decoration:underline;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style> </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-size:11.0pt;font-family:"Ca= libri",sans-serif">As a contributor of opsawg (authors of 9291 can cor= rect 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 abst= racting various L2VPN network services and is designed to be implemented on= a network controller. Therefore, the oper-status is not specifically= tied to a pseudowire class and not tied to a particular device-level implementation (i.e., it applies to the network-= level L2VPN).<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif">The intent of YANG network and service data models = is that they abstract capabilities to a customer-facing or network-facing p= ortal/controller and ultimately rely on device-level interfaces (hopefully standards-based, device-level YANG data models, but = maybe proprietary YANG data models or CLI) to do the configuration and perf= orm the monitoring across the full service implementation. It would b= e 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 style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",sans-serif">Joe<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca= libri",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 0in = 0in 0in"> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;mar= gin-bottom:12.0pt;margin-left:.5in"> <b><span style=3D"font-size:12.0pt;color:black">From: </span></b><span styl= e=3D"font-size:12.0pt;color:black">Alexander Vainshtein <Alexander.Vains= htein=3D40rbbn.com-Tr9gZwTxerDR74oF6e/[email protected]><br> <b>Date: </b>Sunday, August 10, 2025 at 07:27<br> <b>To: </b>[email protected] <[email protected]>= ;, [email protected] <oscar.gonzalezdedios@telefonica.= com>, [email protected] <[email protected]>, luis-ange= l.munoz-ANTagKRnAhdWk0Htik3J/[email protected] <luis-angel.munoz-ANTagKRnAhdWk0Htik3J/[email protected]><br> <b>Cc: </b>[email protected] <[email protected]>, Pseudowire And LDP-enab= led Services Discussion List <[email protected]><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:.5in"><span style=3D"font-size:= 11.0pt">Dear authors of <a href=3D"https://datatracker.ietf.org/doc/html/rfc9291">RFC 9291</a>,</sp= an><span style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt"> </span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt">I have looked up the standard and found that it presumably mentions= Operational Status of a pseudowire as </span><span style=3D"font-family:"Courier New"">oper-status</spa= n><span style=3D"font-size:11.0pt"> without any clarifications and/or refer= ences, and, specifically, without any association with various indicators i= n the PW Status TLV.</span><span style=3D"font-size:12.0pt"><o:p></o:p></sp= an></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt"> </span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=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 style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt"> </span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529"> pwOperStat= us OBJECT-TYPE</span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; SYNTAX PwOperStatusTC</sp= an><span style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; MAX-ACCESS read-only</span><span style=3D"font-si= ze:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; STATUS current</span><spa= n style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; DESCRIPTION</span><span style=3D"font-size:12.0pt"><o:p></o:p></spa= n></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; "This object indicates the opera= tional status of the PW; it</span><span style=3D"font-size:12.0pt"><o:p></o= :p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; does not reflect the status of = the Customer Edge (CE) bound</span><span style=3D"font-size:12.0pt"><o:p></= o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; interface. It is set to d= own only if pwNotForwarding,</span><span style=3D"font-size:12.0pt"><o:p></= o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; psnFacingPwRxFault, or psnFacin= gPwTxFault indications are</span><span style=3D"font-size:12.0pt"><o:p></o:= p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; set in pwLocalStatus or pwRemot= eStatus.</span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; It indicates 'lowerLayerDown' i= f the only reason for</span><span style=3D"font-size:12.0pt"><o:p></o:p></s= pan></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; not being in the 'up' state is = that either the outer tunnel</span><span style=3D"font-size:12.0pt"><o:p></= o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; or physical layer of the networ= k side is in the 'down'</span><span style=3D"font-size:12.0pt"><o:p></o:p><= /span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; state.</span><span style=3D"fon= t-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; All other states are declared b= ased on the description</span><span style=3D"font-size:12.0pt"><o:p></o:p><= /span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; of the PwOperStatusTC.</span><s= pan style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in;background:white"><span st= yle=3D"font-family:"Courier New";color:#212529">  = ; "</span><span style=3D"fon= t-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt"> </span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt">I wonder whether, from your POV, the quoted definition of the PW Op= eratonal Status is still applicable or not.</span><span style=3D"font-size:= 12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt"> </span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt"> </span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p= > <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt">Regards, and lots of thanks in advance,</span><span style=3D"font-s= ize:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 11.0pt">Sasha</span><span style=3D"font-size:12.0pt"><o:p></o:p></span></p> <p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:= 12.0pt"> <o:p></o:p></span></p> </div> <p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;mar= gin-bottom:12.0pt;margin-left:.5in"> <span style=3D"font-size:12.0pt"><o:p> </o:p></span></p> <p style=3D"margin-left:.5in"><b><span style=3D"font-size:10.0pt;font-famil= y:"Verdana",sans-serif;color:#666666">Disclaimer</span></b><span = style=3D"font-size:10.0pt;font-family:"Verdana",sans-serif;color:= #666666"><o:p></o:p></span></p> <p style=3D"margin-left:.5in"><span style=3D"font-size:8.0pt;font-family:&q= uot;Verdana",sans-serif;color:#666666">This e-mail together with any a= ttachments may contain information of Ribbon Communications Inc. and its Af= filiates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, relian= ce or distribution by others or forwarding without express permission is st= rictly prohibited. If you are not the intended recipient, please notify the= sender immediately and then delete all copies, including any attachments. <o:p></o:p></span></p> </div> </div> </div> </div> </body> </html> --_000_CH2PR11MB8867CBE6C714161245F84689B828ACH2PR11MB8867namp_-- --===============3807931438830445750== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTQVdHIG1h aWxpbmcgbGlzdCAtLSBvcHNhd2dAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp bCB0byBvcHNhd2ctbGVhdmVAaWV0Zi5vcmcK --===============3807931438830445750==--