Hi Sasha,

“To me this is equivalent to your definition.”

Sure, however, I was not excluding any LSP type, and I don’t think we need to, 
since the actions are really happening on the PWs riding on those LSPs.
So if your suggestion is that we should add text to restrict this to static PWs 
and MPLS-TP LSPs, I don’t agree. That does not reflect what implementations are 
doing.

Thanks.
Jorge

From: Alexander Vainshtein <alexander.vainsht...@rbbn.com>
Date: Wednesday, April 19, 2023 at 7:47 PM
To: Jorge Rabadan (Nokia) <jorge.raba...@nokia.com>
Cc: bess@ietf.org <bess@ietf.org>, last-c...@ietf.org <last-c...@ietf.org>, 
draft-ietf-bess-evpn-virtual-eth-segm...@ietf.org 
<draft-ietf-bess-evpn-virtual-eth-segm...@ietf.org>
Subject: Re: Last Call: <draft-ietf-bess-evpn-virtual-eth-segment-08.txt> (EVPN 
Virtual Ethernet Segment) to Proposed Standard

CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.


Jorge,
Lots of thanks for your response.

This indeed may be a matter of terminology.
Section 3.1.3 of RFC 
5960<https://datatracker.ietf.org/doc/html/rfc5960#section-3.1.3> says:



   A point-to-point associated bidirectional LSP between LSRs A and B

   consists of two unidirectional point-to-point LSPs, one from A to B

   and the other from B to A, which are regarded as a pair providing a

   single logical bidirectional transport path.

To me this is equivalent to your definition.


Did I miss something substsntial?

Regards,
Sasha





Get Outlook for Android<https://aka.ms/AAb9ysg>

Notice: 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.
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Reply via email to