Hi Roman, Thanks for your review and comments. I will make some changes and post after the pre-IETF119 quiescence period is over.
Please see zzh> below for some clarifications. Juniper Business Use Only -----Original Message----- From: Roman Danyliw via Datatracker <nore...@ietf.org> Sent: Tuesday, March 5, 2024 8:40 PM To: The IESG <i...@ietf.org> Cc: draft-ietf-bess-evpn-irb-mc...@ietf.org; bess-cha...@ietf.org; bess@ietf.org; manka...@cisco.com; manka...@cisco.com Subject: Roman Danyliw's No Objection on draft-ietf-bess-evpn-irb-mcast-11: (with COMMENT) [External Email. Be cautious of content] Roman Danyliw has entered the following ballot position for draft-ietf-bess-evpn-irb-mcast-11: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!NEt6yMaO-gk!ClajButEf7Y6yic83YRtyz3RrbPLLYNFPnyfi0Da7BFSRs66fzxgissKV741K6byCGd4XHeSEPiWhlI$ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-mcast/__;!!NEt6yMaO-gk!ClajButEf7Y6yic83YRtyz3RrbPLLYNFPnyfi0Da7BFSRs66fzxgissKV741K6byCGd4XHeSsCr3BIY$ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Tiru Reddy for his SECDIR review. I saw not response to his feedback. I have similar feedback. Zzh> Oops. We did work with Tiru (copied) and posted the -09 revision to address his comments, but we forgot to reply to the original email thread after that. ** Section 9 This document uses protocols and procedures defined in the normative references, and inherits the security considerations of those references. -- Please explicitly name the relevant references. Zzh> Sure. -- Do the Security Considerations of [I-D.ietf-bier-evpn] apply? Zzh> I guess. I will also add P2MP tunnel references for the inheritance of security considerations. ** Section 9 Incorrect addition, removal, or modification of those flags and/or ECs will cause the procedures defined herein to malfunction, in which case loss or diversion of data traffic is possible. Implementations should provide tools to easily debug configuration mistakes that cause the signaling of incorrect information. Is this manipulation of flags something done as by an attacker or an unintentional insider misconfiguring a system? Are there any mitigations for this manipulation of flags? Zzh> It'd be unintentional insider misconfiguration or software bugs. The mitigation is basically improving software quality and "provide tools to easily debug configuration mistakes that cause the signaling of incorrect information". ** Section 8. Typo. Wrong registry name. IANA is requested to assign new flags in the "Multicast Flags Extended Community Flags" registry. Zzh> Thanks. Fixed. Zzh> Jeffrey The formal name of the registry is “Multicast Flags Extended Community” (no “Flags”) per https://urldefense.com/v3/__https://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml*multicast-flags__;Iw!!NEt6yMaO-gk!ClajButEf7Y6yic83YRtyz3RrbPLLYNFPnyfi0Da7BFSRs66fzxgissKV741K6byCGd4XHeSHors4cw$ _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
