Brian, Sriram and Randy:

Let me suggest we take the rest of this discussion on these IDR two = drafts offline from IDR.=C2=A0 The IDR Chairs noted=C2=A0 when the = draft-ietf-idr-route-leak-detection mitigation was adopted =C2=A0that = there was overlap between you two documents.=C2=A0 We also noted = interests in both technical approaches.=C2=A0 We asked to you provide a = combined document that the chairs could present to the IDR WG.=C2=A0 = This IETF is a wonderful time to work on this project. = =C2=A0=C2=A0Chicago has many fine establishments in which to discuss = this combined document. =C2=A0=C2=A0

I suggest we focused on the technical issues on the IDR mail = lists.=C2=A0 For discussions of IDR on the grow list, I suggest that we = listen to the valuable input from the operators on what their needs and = ask clarifying questions. =C2=A0

Thank you,

Sue Hares

From:= = GROW [mailto:grow-bounces@ietf.org] On Behalf Of Brian = Dickson
Sent: Wednesday, March 22, 2017 9:10 PM
To: = Randy Bush
Cc: idr@ietf.org; = draft-ietf-idr-route-leak-detection-mitigation.authors@ietf.org; = grow@ietf.org; sidr wg list (sidr@ietf.org); = sidrops@ietf.org
Subject: Re: [GROW] [Sidrops] operator inputs = -- route leak solution

On Wed, Mar 22, 2017 at 4:50 PM, Randy Bush <randy@psg.com> = wrote:

> SIDR/GROW/IDR = and well documented in IDR (see Section 4)
> ( https://tools.ietf.org/html/draft-ietf-idr-route-leak-d= etection-mitigation-06 ).
> = The solution involves AS-A setting a field (in an optional = transitive
> = attribute)

glad you liked the attribute approach well = enough to plagarize it from
our draft. now you just need to = change from misconfigurable statements
of relationships to plagarize = the bgp open part of our draft and your
golden.

Randy,

With all due respect, your draft fails to acknowledge = the earlier work by me (from 2012), outside of the recent drafts of = which I am a co-author.

Specifically:

draft-dickson-sidr-route-leak-def (which became the = basis for RFC 7908)

draft-dickson-sidr-route-leak-reqts

draft-dickson-sidr-route-leak-solns

So, perhaps it would be best to avoid claims of = plagiarizing, when (a) there is clear evidence that the source of the = material predates your work, and (b) when your work does not credit the = original work by me.

Pot calling the kettle black, throwing stones in glass = houses, and all that.

You might want to also read those (expired) I-Ds, to = get clarity on preserving leak prevention across "special" = peering sessions

They also = cover the ability to prevent leaks, without requiring the disclosure of = customer relationships -- something for which you have expressed a = strong desire.

FWIW, I will be working with my co-authors on the = relationship-disclosure detail.

Maybe we can schedule some white-board time in = Chicago.

Brian

P.S. It is "you're = golden".

------=_NextPart_000_02FB_01D2A3B3.14EEBF30--