[bess] Re: FW: I-D Action: draft-ietf-bess-rfc7432bis-09.txt

2024-06-06 Thread Greg Mirsky
Hi Ali, thank you for the detailed response. Please find my follow up notes inlined below under the GIM>> tag. Regards, Greg On Wed, Jun 5, 2024 at 10:51 PM Ali Sajassi (sajassi) wrote: > Hi Greg, > > > > The questions that was asked initially are different that your questions. > But let me ans

[bess] Re: FW: I-D Action: draft-ietf-bess-rfc7432bis-09.txt

2024-06-06 Thread Menachem Dodge
Hello Greg, Ali, I know that there is existing equipment that perform deep packet inspection based on the content of the first nibble and not on whether there is an entropy label present in the MPLS stack. Without a control word, and when the payload is a non-IP packet, such equipment may misi

[bess] Genart early review of draft-ietf-bess-evpn-mh-split-horizon-08

2024-06-06 Thread Jouni Korhonen via Datatracker
Reviewer: Jouni Korhonen Review result: Ready with Nits I am an assigned GEN-ART directorate reviewer for draft-ietf-bess-evpn-mh-split-horizon-08. Summary: Ready with nits Overall I found the document ready for publication. I have not followed the topic thus I abstain myself from technical comm

[bess] Re: Suggested wording to merge the content from draft-wang-bess-secservice to draft-bess-secure-evpn

2024-06-06 Thread Ali Sajassi (sajassi)
Hi Linda, I don’t think we need to put too much explanation wrt SRv6 because with respect to IPsec, it is just a IPv6 encapsulation. So, let me expand on it with respect to your four points below: 1. Scenario description: The rational and the reasons for needing IPsec are basically the same

[bess] Re: FW: I-D Action: draft-ietf-bess-rfc7432bis-09.txt

2024-06-06 Thread Ali Sajassi (sajassi)
Hi Greg, Section 18 of RFC7432bis has been carefully worded to ensure its accuracy specially wrt “SHOULD” and “MUST” keywords. We cannot blindly require the use of control word for all non-IP payloads (e.g., Ethernet payload) as it depends on a) type of tunnels used (TE vs. non-TE), b) unicast