Hi Jorge, Thanks for addressing my comments. Cheers.
> On Aug 17, 2024, at 6:17 PM, Jorge Rabadan (Nokia) <jorge.raba...@nokia.com> > wrote: > > Hi Mahesh, > > Thak you very much for the review. > Please see in-line with [jorge]. > > Thanks! > Jorge > > From: Mahesh Jethanandani via Datatracker <nore...@ietf.org > <mailto:nore...@ietf.org>> > Date: Tuesday, August 6, 2024 at 12:36 PM > To: The IESG <i...@ietf.org <mailto:i...@ietf.org>> > Cc: draft-ietf-bess-evpn-mh-split-hori...@ietf.org > <mailto:draft-ietf-bess-evpn-mh-split-hori...@ietf.org> > <draft-ietf-bess-evpn-mh-split-hori...@ietf.org > <mailto:draft-ietf-bess-evpn-mh-split-hori...@ietf.org>>, > bess-cha...@ietf.org <mailto:bess-cha...@ietf.org><bess-cha...@ietf.org > <mailto:bess-cha...@ietf.org>>, bess@ietf.org <mailto:bess@ietf.org> > <bess@ietf.org <mailto:bess@ietf.org>>, slitkows.i...@gmail.com > <mailto:slitkows.i...@gmail.com> <slitkows.i...@gmail.com > <mailto:slitkows.i...@gmail.com>>, manka...@cisco.com > <mailto:manka...@cisco.com> <manka...@cisco.com <mailto:manka...@cisco.com>>, > zzh...@juniper.net <mailto:zzh...@juniper.net> <zzh...@juniper.net > <mailto:zzh...@juniper.net>>, Matthew Bocci (Nokia) <matthew.bo...@nokia.com > <mailto:matthew.bo...@nokia.com>>, zzh...@juniper.net > <mailto:zzh...@juniper.net> <zzh...@juniper.net <mailto:zzh...@juniper.net>> > Subject: Mahesh Jethanandani's No Objection on > draft-ietf-bess-evpn-mh-split-horizon-10: (with COMMENT) > > > CAUTION: This is an external email. Please be very careful when clicking > links or opening attachments. See the URL nok.it/ext <http://nok.it/ext> for > additional information. > > > > Mahesh Jethanandani has entered the following ballot position for > draft-ietf-bess-evpn-mh-split-horizon-10: 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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-positions%2F&data=05%7C02%7Cjorge.rabadan%40nokia.com%7C27570b30bfa248dab8e908dcb64f17ed%7C5d4717519675428d917b70f44f9630b0%7C0%7C0%7C638585698049237788%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=epCVm0BxAz9WP18NbB23WRgE1DcpNjhNafY6R8NPzdo%3D&reserved=0 > > <https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/> > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-bess-evpn-mh-split-horizon%2F&data=05%7C02%7Cjorge.rabadan%40nokia.com%7C27570b30bfa248dab8e908dcb64f17ed%7C5d4717519675428d917b70f44f9630b0%7C0%7C0%7C638585698049248316%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=sMSKCGqWAkMIV8e9jXbBRZbUIIiiM9E6eu5D4L8LY7o%3D&reserved=0 > <https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-mh-split-horizon/> > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Section 1.2, paragraph 25 > > This document extends the EVPN multihoming procedures to allow > > operators to select the preferred Split Horizon method for a given > > NVO tunnel according to their specific requirements. The choice > > between Local Bias and ESI Label Split Horizon is now allowed for > > tunnel encapsulations that support both methods, and this selection > > is advertised along with the EVPN A-D per ES route. IP tunnels that > > do not support both methods, such as VXLAN or NVGRE, will continue to > > adhere to the procedures specified in [RFC8365]. > > > How is the operator able to make the selection of Split Horizon? Is there a > YANG model? > > [jorge] No, this “choice” configuration is not defined in any existing IETF > yang model yet, afaik. We modified the second sentence as follows: > > “The choice between Local Bias and ESI Label Split Horizon is now allowed (by > configuration) for tunnel encapsulations that support both methods, and this > selection is advertised along with the EVPN A-D per ES route.” > > > > Found terminology that should be reviewed for inclusivity; see > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fpart2%2F%23inclusive_language&data=05%7C02%7Cjorge.rabadan%40nokia.com%7C27570b30bfa248dab8e908dcb64f17ed%7C5d4717519675428d917b70f44f9630b0%7C0%7C0%7C638585698049255576%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=12ibv%2BEhS6CHw2OF40gbBvX5SplTYPntOMhZKdmtiUs%3D&reserved=0 > <https://www.rfc-editor.org/part2/#inclusive_language> for background and > more > guidance: > > * Term "his"; alternatives might be "they", "them", "their" > * Term "native"; alternatives might be "built-in", "fundamental", > "ingrained", > "intrinsic", "original" > > [jorge] we fixed both, thanks. > > > > ------------------------------------------------------------------------------- > NIT > ------------------------------------------------------------------------------- > > All comments below are about very minor potential issues that you may choose > to > address in some way - or ignore - as you see fit. Some were flagged by > automated tools (via > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flarseggert%2Fietf-reviewtool&data=05%7C02%7Cjorge.rabadan%40nokia.com%7C27570b30bfa248dab8e908dcb64f17ed%7C5d4717519675428d917b70f44f9630b0%7C0%7C0%7C638585698049259933%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=0SGJQlf8PUUEih%2BEdy4KNZ85g4xDg%2BQwm37hrabdUSM%3D&reserved=0) > <https://github.com/larseggert/ietf-reviewtool>, so there > will likely be some false positives. There is no need to let me know what you > did with these suggestions. > > "RED", paragraph 1 > > 0 0 --> Default SHT. Backwards compatible with [RFC8365] and > > [RFC7432] > > > This line in an HTML rendition of the draft appears as truncated. Please > reformat. > Mahesh Jethanandani mjethanand...@gmail.com
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
