Resending - looks as if my previous email has not been received... Regards, Sasha
From: Alexander Vainshtein Sent: Tuesday, May 20, 2025 12:37 PM To: BESS <bess@ietf.org> Cc: lbur...@cisco.com; pbris...@cisco.com; ta-miyas...@kddi.com; Rabadan, Jorge (Nokia - US/Mountain View) <jorge.raba...@nokia.com>; Yisong Liu <liuyis...@chinamobile.com>; linchangwang.04...@h3c.com; Michael Gorokhovsky <michael.gorokhov...@rbbn.com>; Roger David <roger.da...@rbbn.com>; Nitsan Dolev <nitsan.do...@rbbn.com>; Matthew Bocci (Nokia) <matthew.bo...@nokia.com> Subject: RE: [bess] WG adoption and IPR check for draft-burdet-bess-evpn-fast-reroute-09 Hi all, I support adoption of draft-burdet-bess-evpn-fast-reroute-09. >From my POV it meets the two conditions for adoption: * It tries to address a real problem * It represents a good starting point towards the solution. The issue mentioned by Nitsan exists, and has been acknowledged by the authors<https://mailarchive.ietf.org/arch/msg/bess/7C2W01nGGdpW4ITi0b9iGeAhYhs/>, but, IMHO and FWIW, it can be resolved once the draft becomes a WG document. My 2c, Sasha From: Nitsan Dolev <nitsan.do...@rbbn.com<mailto:nitsan.do...@rbbn.com>> Sent: Tuesday, May 20, 2025 12:09 PM To: Matthew Bocci (Nokia) <matthew.bo...@nokia.com<mailto:matthew.bo...@nokia.com>>; BESS <bess@ietf.org<mailto:bess@ietf.org>> Cc: lbur...@cisco.com<mailto:lbur...@cisco.com>; pbris...@cisco.com<mailto:pbris...@cisco.com>; ta-miyas...@kddi.com<mailto:ta-miyas...@kddi.com>; Rabadan, Jorge (Nokia - US/Mountain View) <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>; Yisong Liu <liuyis...@chinamobile.com<mailto:liuyis...@chinamobile.com>>; linchangwang.04...@h3c.com<mailto:linchangwang.04...@h3c.com>; Alexander Vainshtein <alexander.vainsht...@rbbn.com<mailto:alexander.vainsht...@rbbn.com>>; Michael Gorokhovsky <michael.gorokhov...@rbbn.com<mailto:michael.gorokhov...@rbbn.com>>; Roger David <roger.da...@rbbn.com<mailto:roger.da...@rbbn.com>> Subject: RE: [bess] WG adoption and IPR check for draft-burdet-bess-evpn-fast-reroute-09 Hi, Regarding the adoption of this draft, there seems to be an open issue which may require clarification. As already noted in an email to the WG, the draft-burdet-bess-evpn-fast-reroute-09 draft does not seem to properly address the AC-Aware Bundling Service Interface as described in https://datatracker.ietf.org/doc/html/draft-sajassi-bess-evpn-ac-aware-bundling-06. I proposed to define the behavior on the ERL originator to check the VLAN on the payloads received from the MH-ES mate PEs. Unless we defer this issue due to the fact that ac-aware-bundling service is still a draft... Regards, Nitsan Dolev-Elfassy Ribbon communications From: Matthew Bocci (Nokia) <matthew.bo...@nokia.com<mailto:matthew.bo...@nokia.com>> Sent: Monday, May 19, 2025 12:15 PM To: BESS <bess@ietf.org<mailto:bess@ietf.org>> Subject: [bess] WG adoption and IPR check for draft-burdet-bess-evpn-fast-reroute-09 Hello, This email begins a two-week WG adoption poll for draft-burdet-bess-evpn-fast-reroute-09 [1]. Please review the draft and post any comments to the BESS working group list. We are also polling for knowledge of any undisclosed IPR that applies to this document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an author or a contributor of this document, please respond to this email and indicate whether you are aware of any relevant undisclosed IPR, copying the BESS mailing list. The document will not progress without answers from all the authors and contributors. Currently, there is currently one IPR disclosure against this document. If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. This poll for adoption closes on June 2nd 2025. Regards, Matthew, Stephane and Jeffrey [1] draft-burdet-bess-evpn-fast-reroute-09 - EVPN Fast Reroute<https://datatracker.ietf.org/doc/draft-burdet-bess-evpn-fast-reroute/> 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.
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org