Re: [GROW] I-D Action: draft-ietf-grow-wkc-behavior-03.txt

2019-03-10 Thread Jay Borkenhagen
internet-dra...@ietf.org writes: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Global Routing Operations WG of the IETF. > > Title : Well-Known Community Policy Behavior >

Re: [GROW] I-D Action: draft-ietf-grow-wkc-behavior-02.txt

2019-01-22 Thread Jay Borkenhagen
Jay B. internet-dra...@ietf.org writes: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Global Routing Operations WG of the IETF. > > Title : Wel

Re: [GROW] I-D Action: draft-ietf-grow-wkc-behavior-01.txt

2019-01-07 Thread Jay Borkenhagen
ternet-dra...@ietf.org writes: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Global Routing Operations WG of the IETF. > > Title : Well-Known Community Policy Behavior > Au

Re: [GROW] I-D Action: draft-ymbk-grow-wkc-behavior-00.txt

2018-02-28 Thread Jay Borkenhagen
> > >> i did not realize this was going on. jay, who discovered it, was > > >> surprised. > > > > > > NTT noticed this type of inconsistency between some vendors somewhere > > > in July 2016. [...] [...] > I know of other carriers who are not interested in preserving any > community inf

Re: [GROW] Opsdir last call review of draft-ietf-grow-bgp-gshut-13

2018-01-18 Thread Jay Borkenhagen
Distro cut *way* down. Regarding the suggestion for "logging knobs": - if it's just logging that a gshut action was taken, that's a local implementation decision -- no need to mention it in the draft. - if it's "Possibly raising alarms when something seems wrong", that would be a bad idea.

Re: [GROW] Opsdir last call review of draft-ietf-grow-bgp-gshut-13

2018-01-18 Thread Jay Borkenhagen
[resend - apologies for any dupes] Distro cut *way* down. Regarding the suggestion for "logging knobs": - if it's just logging that a gshut action was taken, that's a local implementation decision -- no need to mention it in the draft. - if it's "Possibly raising alarms when something seems w

Re: [GROW] Genart last call review of draft-ietf-grow-bgp-gshut-11

2017-10-10 Thread Jay Borkenhagen
Job Snijders writes: > > The LOCAL_PREF choice here is a simple thing -- don't make it more > > complicated than it needs to be. > > > > Job's suggested text says all that's necessary: > > > > "The LOCAL_PREF value SHOULD be lower than any of the alternative > > paths. Zero being

Re: [GROW] Genart last call review of draft-ietf-grow-bgp-gshut-11

2017-10-10 Thread Jay Borkenhagen
David Farmer writes: > I would prefer a normative RECOMMENDED, the rest of the sentence in > RFC2119, just means you should explain the constraints on the alternatives. > How about something like this; > > "The LOCAL_PREF value SHOULD be lower than any of the alternative > paths. A LOCAL_PR

Re: [GROW] working group last call draft-ietf-grow-bgp-gshut

2017-09-21 Thread Jay Borkenhagen
Thanks, Chris. With the draft-ietf-grow-bgp-gshut-11 that Bruno posted earlier today, I fully support moving ahead with publication. Jay B. On 17-Aug-2017, Christopher Morrow writes: > I agree the document is almost done, I think there's one comm

Re: [GROW] I-D Action: draft-ietf-grow-blackholing-02.txt

2016-07-07 Thread Jay Borkenhagen
Christopher Morrow writes: > On Tue, Jul 5, 2016 at 10:24 AM, Jay Borkenhagen wrote: > > > confusion and disappointment: "I sent the BLACKHOLE community to > > upstream-X and to upstream-Y, and I got different results. How come?" > > > > Doesn&#

Re: [GROW] I-D Action: draft-ietf-grow-blackholing-02.txt

2016-07-05 Thread Jay Borkenhagen
My comments on draft-ietf-grow-blackholing-02: - If the only purpose of the draft is to standardize the RTBH signaling community, wouldn't a better approach be to attempt to update RFC5635? - Standardizing the RTBH signaling community is insufficient, as the party who wants to use it also n