Re: WGLC for draft-ietf-mboned-dc-deploy and draft-ietf-mboned-deprecate-interdomain-asm
Olufemi Komolafe <[email protected]> Fri, 23 Aug 2019 00:15:48 +0100
| Newsgroups | gmane.ietf.mboned |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the good feedback Lenny. We will make the suggested changes. Regards, Femi > On 13 Aug 2019, at 20:54, Leonard Giuliano <[email protected]> wrote: > > > <chair hat off, speaking as individual contributor> > > I support publication of draft-ietf-mboned-dc-deploy as this document > describes a number of pertinent issues for mcast in a DC environment. > > Some mostly editorial comments below: > > Abstract: "judiciously" misspelled > > Sect 1. Intro, 2nd para: I am confused by the tense used in this para- is > it talking about the current situation, or in the future or even the past? > If the future, how can an assumption of the future be known to be > incorrect in the present? Don't we need to arrive at that future point to > determine how correct this assumption is? Anyway, suggest sticking to the > current state of affairs. > > Sect 2.1, 2nd para: "... there is a consensus..." > -would "expectation" be more appropriate than "consensus" > > Sect 2.2, 1st para: "... overlays mainly simply ..." > -probably just "simply" would be simpler > > Sect 3: "...arguably the intuitive initial course of action for a data > center operator..." > -perhaps better to say: "it makes sense for a data center > operator..." > > Sect 3.3, 1st para, last sentence: "Thus, PIM must be running..." > -"Thus, a multicast routing protocol (typically PIM) must be > running..." > > Sect 4.1: I thought this section was very informative and well-written > > Sect 4.4, 3rd para: "The > deployment envisioned with overlay networks is that the the > encapsulation endpoints would be the BFIR." > -suggest something like the following: "The BFIRs are the > encapsulation endpoints in the deployment envisioned with overlay > networks." > > > > > On Fri, 19 Jul 2019, Leonard Giuliano wrote: > > | > | We would like to officially begin working group last call for BOTH > | draft-ietf-mboned-dc-deploy and draft-ietf-mboned-deprecate-interdomain-asm. > | Please post whether you support/oppose the advancement of either/both of the > | drafts as well as any comments you may have to the list by Aug 16. Also, > | please note if you are aware of any IPR involved in this drafts (we must hear > | from the authors about IPR). > | > | Most recent version of the draft can be found here: > | https://datatracker.ietf.org/doc/draft-ietf-mboned-dc-deploy/ > | https://datatracker.ietf.org/doc/draft-ietf-mboned-deprecate-interdomain-asm/ > | > > _______________________________________________ > MBONED mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/mboned _______________________________________________ MBONED mailing list [email protected] https://www.ietf.org/mailman/listinfo/mboned