Tim did this 6/7/2019 (june 7) https://tools.ietf.org/html/draft-ietf-grow-bmp-local-rib-04
huazzah! moving forward I think is ok now? -chris co-chairy On Sat, Jun 1, 2019 at 5:23 AM Tim Evens (tievens) <[email protected]> wrote: > > Hi John, > > We will submit a revision update shortly that incorporates the below changes. > > --Tim > > On May 23, 2019, at 9:53 AM, John Scudder <[email protected]> > wrote: > > Hi Job and all, > > On May 22, 2019, at 8:44 PM, Job Snijders <[email protected]> wrote: > > I'd like to ask that folks with skin in the game take a look and share > with the working group whether we are good to go, or follow up with > proposals for changes to the draft, or at least affirm outstanding > issues still remain. > > > The diff resolves the major issue I brought up in my December 15, 2018 email > (https://mailarchive.ietf.org/arch/msg/grow/wA3Nkz2lw6obTH9fF1X2Mkm4INM) > using the solution Paolo and I agreed later > (https://mailarchive.ietf.org/arch/msg/grow/t6LKhCLc-E_awiVHowB4WDnMSps). > > Looks like this minor comment wasn’t addressed: "By the way, shouldn't those > "SHOULDs" be "MUSTs"? If not MUST, under what circumstances MAY they be > omitted?” I did a quick grep of -03 for SHOULDs and to my eye, all of them > can (and therefore SHOULD :-) be MUSTs, other than those in section 5.4.2 of > which I think the first is fine and the second could just as well be “should” > in lowercase. (Opinions vary on the proper use of SHOULD vs. MUST, but this > is mine.) > > This is separate from the best/active topic you asked about, but Jeff replied > to that so I’m going to assume it’s being covered. > > —John > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
