Re: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)
Christopher Morrow <christopher.morrow@gmail.com> Sun, 01 November 2015 04:45 UTC
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8362E1B5EB3; Sat, 31 Oct 2015 21:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyPqE7HZ2dF3; Sat, 31 Oct 2015 21:45:51 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DAC41B5EBB; Sat, 31 Oct 2015 21:45:40 -0700 (PDT)
Received: by ykft191 with SMTP id t191so111514969ykf.0; Sat, 31 Oct 2015 21:45:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=JsHjenmT0i2/QBj6XlpDmY+Zl9Fws3m9PyHLIjljdBo=; b=dClOq2AfNzZ5l+VLGwsOh4cs6eroysnkUfWAv18iLcJfnMUrSSrK3+s2qEVj3GJT3J tfHsng3fr0cOSqRs6rVlfkp+YVIV7EXt1QSRVk1Zw7VJ80m6dYudCA7JC2xpogELSHgA v/TmrX9L9B+AVGtU0kaoNXFnWG+XkIc0fYoH+iqOrG5zMDSbn+6d/rFNqxEZDNC72S3Q GpaZMwoPFDnD7YV9pxnGSOuoC2qvSJmx1x8Vw4CTVsdo2IEZZc2Hvg4vZFT7jIxGEdb4 NHVtIJTJ07CSTLFO3jJoNdIDjLBwGVTs3M1Nimvr+8d+12odPzT/I+v11tqfTIpWQbf9 EENQ==
MIME-Version: 1.0
X-Received: by 10.13.243.135 with SMTP id c129mr13097792ywf.113.1446353139632; Sat, 31 Oct 2015 21:45:39 -0700 (PDT)
Received: by 10.13.202.16 with HTTP; Sat, 31 Oct 2015 21:45:39 -0700 (PDT)
In-Reply-To: <CY1PR09MB079391D1277246C2EC609F47842D0@CY1PR09MB0793.namprd09.prod.outlook.com>
References: <CAL9jLaaOPvY2WZtunCOkuuCDV5-Do+cpHBfa8eEhquGdzSLVuA@mail.gmail.com> <20150929204612.GC5754@pfrc.org> <CY1PR09MB07930CE654F0C23B035D4F3484300@CY1PR09MB0793.namprd09.prod.outlook.com> <D257B8B1.6E937%wesley.george@twcable.com> <CY1PR09MB079391D1277246C2EC609F47842D0@CY1PR09MB0793.namprd09.prod.outlook.com>
Date: Sun, 01 Nov 2015 00:45:39 -0400
Message-ID: <CAL9jLaaEuV6A8v=2Z5A4VO-XTJhs7DBVGYbFRaNH-mfEqidEiw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/vuvQMrsDoifNSezOJuZs39ASM-s>
Cc: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "grow-ads@tools.ietf.org" <grow-ads@tools.ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 04:45:53 -0000
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 <kotikalapudi.sriram@nist.gov> 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 <wesley.george@twcable.com> > Sent: Friday, October 30, 2015 10:01 AM > To: Sriram, Kotikalapudi > Cc: grow-chairs@ietf.org; grow@ietf.org grow@ietf.org; grow-ads@tools.ietf.org > 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" > <kotikalapudi.sriram@nist.gov> 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] WGLC: draft-ietf-grow-route-leak-problem-d… Christopher Morrow
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… George, Wes
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Susan Hares
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Christopher Morrow
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Andrei Robachevsky
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Jeffrey Haas
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… George, Wes
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Job Snijders
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Christopher Morrow
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… George, Wes
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… David Farmer
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Christopher Morrow
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… joel jaeggli
- Re: [GROW] WGLC: draft-ietf-grow-route-leak-probl… Sriram, Kotikalapudi