[bess] Secdir last call review of draft-ietf-bess-srv6-services-08

2021-12-05 Thread Joseph Salowey via Datatracker
Reviewer: Joseph Salowey Review result: Ready I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and

Re: [bess] Query about Ethernet Tag Id for TYpe-5 routes (RFC 9136)

2021-12-05 Thread wang.yubao2
Hi Vinayak, The Bump-in-the-wire with a VLAN-aware BD is just slightly implied in the terminlogy section of RFC9136. It is not mentioned in the main body of RFC9136. So a few critical details are still absent, while there may be already different implementations up to now, I think

Re: [bess] A question about draft-ietf-bess-evpn-lsp-ping

2021-12-05 Thread Alexander Vainshtein
Parag, Lots of thanks for your response. The updates to the draft that you have suggested (in this and previous emails) look good to me However, I am not sure your response to my last question really addresses it – please see inline below. Regards, Sasha Office: +972-39266302 Cell:

Re: [bess] Query about Ethernet Tag Id for TYpe-5 routes (RFC 9136)

2021-12-05 Thread Joshi, Vinayak
Hi Jorge & Yubao, In the most common use cases an IP prefix route has to be unique with an VRF. The VPN Label/L3VNI brings in this separation of IP prefixes even for VLAN-aware bundling. (With all L2 routes the Ethernet Tag has to be non-zero for VLAN-aware BD for sure to distinguish BDs). In