Hi Russ Thanks for the comment. I have published 4th version of the draft which addresses all of your comments.
Mankamana From: Mankamana Mishra (mankamis) <manka...@cisco.com> Date: Monday, October 23, 2023 at 2:12 PM To: Russ Housley <hous...@vigilsec.com>, gen-...@ietf.org <gen-...@ietf.org> Cc: bess@ietf.org <bess@ietf.org>, draft-ietf-bess-evpn-ac-aware-bundling....@ietf.org <draft-ietf-bess-evpn-ac-aware-bundling....@ietf.org> Subject: Re: Genart early review of draft-ietf-bess-evpn-ac-aware-bundling-03 Thanks for your comment, will be pushing updated version as soon as window opens during IETF. From: Russ Housley via Datatracker <nore...@ietf.org> Date: Friday, October 20, 2023 at 9:02 AM To: gen-...@ietf.org <gen-...@ietf.org> Cc: bess@ietf.org <bess@ietf.org>, draft-ietf-bess-evpn-ac-aware-bundling....@ietf.org <draft-ietf-bess-evpn-ac-aware-bundling....@ietf.org> Subject: Genart early review of draft-ietf-bess-evpn-ac-aware-bundling-03 Reviewer: Russ Housley Review result: Almost Ready I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting a new version of the draft. For more information, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. Document: draft-ietf-bess-evpn-ac-aware-bundling-03 Reviewer: Russ Housley Review Date: 2023-10-20 IETF LC End Date: unknown IESG Telechat date: unknown Summary: Almost Ready Major Concerns: Section 8: Please clearly identify the IANA registry. Minor Concerns: General: Several places, the document includes reference of the form "[RFC7432] section x.y.z". It would be much more clear to use the form "Section x.y.z of [RFC7432]". Section 6.1 has "attachment circuit ID Extended Community" below the figure. Is this a caption? If so, please center the caption and add a figure number. Nits: General: s/draft/document/ (prepare for publication as an RFC) Abstract: s/EVPN (Ethernet VPNs) provides/An EVPN (Ethernet VPN) provides/ Section 1: s/This draft proposes/This document specifies/ Section 1.1: s/MAC-2 it can not determine which AC this MAC belongs to/ /MAC-2, it can not determine the AC associated with this MAC/ Section 1.2: s/which subnet this IGMP membership request belong to/ /which subnet this IGMP membership request belongs/ Section 1.2: s/forearded to/forwarded to/ Section 3: s/multiple VLAN are configured on/multiple VLAN are configured/ Section 3: s/defined in [RFC7432]/defined in [RFC7432]./ Section 4.1.1.2: s/non multihome/non-multihomed/ Section 4.1.1.2: s/defined in [RFC7432]/defined in [RFC7432]./ Section 4.2.1: s/section 13.1/Section 13.1./ Section 4.2.2: s/in [RFC7432]/in [RFC7432]./ Section 5: s/In this case/In this case,/ Section 6.2: s/is faily large/is fairly large/ Section 6.2: s/This approach is complexifying/This approach adds complexity to/ Section 6.2: s/There is drawback/There is a drawback/
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
