Dear Jorge: Thank you for addressing my comments. The edits look good, I have no further comments on the draft.
Cheers, - vijay On Thu, Jul 6, 2023 at 12:58 PM Jorge Rabadan (Nokia) < jorge.raba...@nokia.com> wrote: > Hi Vijay, > > > > Thanks very much for reviewing. > > We just published version 11 which addresses all your comments. > > > > Thanks! > > Jorge > > > > *From: *Vijay Gurbani via Datatracker <nore...@ietf.org> > *Date: *Sunday, July 2, 2023 at 12:13 PM > *To: *gen-...@ietf.org <gen-...@ietf.org> > *Cc: *bess@ietf.org <bess@ietf.org>, > draft-ietf-bess-evpn-pref-df....@ietf.org < > draft-ietf-bess-evpn-pref-df....@ietf.org>, last-c...@ietf.org < > last-c...@ietf.org> > *Subject: *Genart last call review of draft-ietf-bess-evpn-pref-df-10 > > > CAUTION: This is an external email. Please be very careful when clicking > links or opening attachments. See the URL nok.it/ext for additional > information. > > > > Reviewer: Vijay Gurbani > Review result: Ready with Nits > > 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 treat these comments just > like any other last call comments. > > For more information, please see the FAQ at > > <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. > > Document: draft-ietf-bess-evpn-pref-df-10 > Reviewer: Vijay K. Gurbani > Review Date: 2023-07-02 > IETF LC End Date: 2023-07-11 > IESG Telechat date: Not scheduled for a telechat > > Summary: The draft is ready for publications as a Proposed Standard with a > few > nite. > > Major issues: 0 > > Minor issues: 1 (please see below) > > Nits/editorial comments: 3 (please see below) > > Minor > > - Sec 2, you may consider ordering the abbreviations alphabetically as it > may > be easier for the reader to find what they are looking for. > > Nits: > > - Sec 1.1, s/two new DF Algs/two new DF algorithms/ (unless, of course, in > your > nomenclature, "Alg" means something specific). > > - Sec 3, the opening sentence is too long. You may consider the following > edit: s/route, by replacing/route. It does so by replacing/ > > - Sec 4.1, bullet d, s/E.g., 50/e.g., 50/ > >
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess