There's seemingly 1 comment set not responded to on-list (job's last), but overall support seems positive. I'll ship a document shepherd review northbound post-ietf-meeting week.
by then sriram should have an updated revision with comments dealt with as well I beleive? On Sat, Oct 31, 2015 at 11:07 PM, Sriram, Kotikalapudi <[email protected]> wrote: > Wes, > > Thanks, Wes, for taking another look. > And thanks for laying out some interesting (and entertaining) alternative > names > that can to used instead of "U-Turn". > Like we discussed in the hallway this morning, it makes sense to use "Hairpin > Turn" > instead of "U-Turn", especially considering "Hairpin Turn" has been used in > the VPN context. > > Sriram > > > ________________________________________ > From: George, Wes <[email protected]> > Sent: Friday, October 30, 2015 10:01 AM > To: Sriram, Kotikalapudi > Cc: [email protected]; [email protected] [email protected]; [email protected] > Subject: Re: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition > (ends: 8/24/2015 - Aug 24) > > On 10/12/15, 11:40 PM, "Sriram, Kotikalapudi" > <[email protected]> wrote: > > > Sriram, this is significantly improved. One substantial comment that I > still have with this version: > >>>It is also unclear from the text exactly what you mean by U-Turn >>>(it's not going back the way it came, so actually hairpin might be a >>>better term), >>>so a few words to clarify might be useful. >> >>Hairpin seems to have a connotation that the turn is tight/constricted. >>So now I use the phrase “U-shaped turn” instead of “U-turn”. > > WG] This may be nitpicking, but I don't think that adding "shaped" is > actually much of an improvement. I was thinking of hairpin from the way > that it is used in VPNs, as in data that enters and leaves the network via > the same edge device, but typically on a different physical or logical > interface (instead of entering on one PE and leaving via another), rather > than the way that it is used on racetracks to describe a near 180 degree > turn. > Here are a few ideas I had of other ways to refer to this: > > - a "detour leak", in that traffic will be detouring through the leaking > ASN > - "ASN-in-the-middle leak" - similar to MiTM such that invoking the > concept is useful, but it's necessary to disambiguate the two since the > latter has a specific and well-known meaning > - "parrotting leak" or "game of telephone leak" in that it is repeating > something it learned elsewhere, but introducing a mistake, not unlike the > grade school game of telephone (if you're up for a reference to The > Simpsons, you could call it a "purple monkey dishwasher leak" but that > would likely require too much explanation ;-) ) > - "[accidental | unintentional] transit leak" since the net result of the > leak is that traffic will transit the leaking AS rather than its normal > path > > > Thanks, > > Wes > > > Anything below this line has been added by my company’s mail server, I > have no control over it. > ----------- > > > ________________________________ > > This E-mail and any of its attachments may contain Time Warner Cable > proprietary information, which is privileged, confidential, or subject to > copyright belonging to Time Warner Cable. This E-mail is intended solely for > the use of the individual or entity to which it is addressed. If you are not > the intended recipient of this E-mail, you are hereby notified that any > dissemination, distribution, copying, or action taken in relation to the > contents of and attachments to this E-mail is strictly prohibited and may be > unlawful. If you have received this E-mail in error, please notify the sender > immediately and permanently delete the original and any copy of this E-mail > and any printout. _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
