Meral, thanks for your review. Les, thanks for your response. I have entered a No Objection ballot.
Alissa > On Feb 13, 2018, at 10:29 AM, Meral Shirazipour > <meral.shirazip...@ericsson.com> wrote: > > Hi Les, > Thank you for addressing the comments. All good by me. > > Best, > Meral > > From: Les Ginsberg (ginsberg) [mailto:ginsb...@cisco.com > <mailto:ginsb...@cisco.com>] > Sent: Monday, February 12, 2018 9:01 PM > To: Meral Shirazipour <meral.shirazip...@ericsson.com > <mailto:meral.shirazip...@ericsson.com>>; > draft-ietf-bier-isis-extensions....@ietf.org > <mailto:draft-ietf-bier-isis-extensions....@ietf.org>; gen-art@ietf.org > <mailto:gen-art@ietf.org> > Subject: RE: Gen-ART Telechat Call review of > draft-ietf-bier-isis-extensions-06 > > Meral – > > Thanx for the review. > Some of your comments have already been addressed in the latest version (07) > published a few days ago. > > Responses inline. > > From: Meral Shirazipour [mailto:meral.shirazip...@ericsson.com > <mailto:meral.shirazip...@ericsson.com>] > Sent: Monday, February 12, 2018 8:02 PM > To: draft-ietf-bier-isis-extensions....@ietf.org > <mailto:draft-ietf-bier-isis-extensions....@ietf.org>; gen-art@ietf.org > <mailto:gen-art@ietf.org> > Subject: Gen-ART Telechat Call review of draft-ietf-bier-isis-extensions-06 > > 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 > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>>. > > Document: draft-ietf-bier-isis-extensions-06 > Reviewer: Meral Shirazipour > Review Date: 2018-02-12 > IETF LC End Date: 2018-02-22 ? > IESG Telechat date: 2018-02-22 > > Summary: This draft is ready to be published as Standards Track RFC but I > have some comments. > > Major issues: > Minor issues: > Nits/editorial comments: > -please updated references to latest draft version/RFC number > > [Les:] Done in V 07 > > -Section 2 would be clearer is the definitions introduced only in this > document are identified as such > > [Les:] I don’t think there are any introduced by this document. All of the > definitions mentioned in Section 2 come from RFC 8279. > > -Please spell out multi topology, sub-domain at first use for MT SD > [Les:] In Section 4.1 where we introduce the use of <MT,SD> here is what the > text says (emphasis added): > > “Within such a domain, the extensions defined in this document > advertise BIER information for one or more BIER sub-domains. Each > sub-domain is uniquely identified by a subdomain-id. Each subdomain > is associated with a single ISIS topology [RFC5120], which may be any > of the topologies supported by ISIS. Local configuration controls > which <MT,SD> pairs are supported by a router.” > > Do you think further clarification as to the meaning of <MT,SD> is still > needed?? > > -[Page 6], "advertisments."--->"advertisements" > > [Les:] Corrected in V 07. > > -[Page 8], "occurences"--->"occurrences" > > [Les:] The section which contains this misspelling was removed in V 07. > > Les > > Best Regards, > Meral > --- > Meral Shirazipour > Ericsson Research > www.ericsson.com > <http://www.ericsson.com/>_______________________________________________ > Gen-art mailing list > Gen-art@ietf.org <mailto:Gen-art@ietf.org> > https://www.ietf.org/mailman/listinfo/gen-art > <https://www.ietf.org/mailman/listinfo/gen-art>
_______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www.ietf.org/mailman/listinfo/gen-art
