Hi Sasha, Minor comment. In the title you wrote RFC9251, while in the message you refer to RFC9291, it seems the title should be corrected.
Regards, Nitsan From: Alexander Vainshtein <[email protected]> Sent: Sunday, August 10, 2025 2:26 PM To: [email protected]; [email protected]; [email protected]; [email protected] Cc: [email protected]; Pseudowire And LDP-enabled Services Discussion List <[email protected]> Subject: 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 Operational Status of a pseudowire as oper-status without any clarifications and/or references, and, specifically, without any association with various indicators 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 proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
