Re: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)

"George, Wes" <wesley.george@twcable.com> Fri, 30 October 2015 14:01 UTC

Return-Path: <wesley.george@twcable.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 6843D1A0302; Fri, 30 Oct 2015 07:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.863
X-Spam-Level: **
X-Spam-Status: No, score=2.863 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FH_RELAY_NODNS=1.451, HELO_EQ_MODEMCABLE=0.768, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_LOW=-0.7, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no
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 vtwd9-TQvC69; Fri, 30 Oct 2015 07:01:10 -0700 (PDT)
Received: from cdpipgw01.twcable.com (unknown [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id B91FB1A0233; Fri, 30 Oct 2015 07:01:09 -0700 (PDT)
X-SENDER-IP: 10.136.163.145
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="5.20,218,1444708800"; d="scan'208";a="1043866616"
Received: from unknown (HELO exchpapp04dr.corp.twcable.com) ([10.136.163.145]) by cdpipgw01.twcable.com with ESMTP/TLS/AES256-SHA; 30 Oct 2015 09:54:21 -0400
Received: from EXCHPAPP06.corp.twcable.com (10.64.163.147) by exchpapp04dr.corp.twcable.com (10.136.163.145) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 30 Oct 2015 10:01:07 -0400
Received: from EXCHPAPP06.corp.twcable.com ([10.64.163.147]) by exchpapp06.corp.twcable.com ([10.64.163.147]) with mapi id 15.00.1104.000; Fri, 30 Oct 2015 10:01:07 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
Thread-Topic: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)
Thread-Index: AQHRExtspm+pEAzLa0WKltZDRbANCw==
Date: Fri, 30 Oct 2015 14:01:06 +0000
Message-ID: <D257B8B1.6E937%wesley.george@twcable.com>
References: <CAL9jLaaOPvY2WZtunCOkuuCDV5-Do+cpHBfa8eEhquGdzSLVuA@mail.gmail.com> <20150929204612.GC5754@pfrc.org> <CY1PR09MB07930CE654F0C23B035D4F3484300@CY1PR09MB0793.namprd09.prod.outlook.com>
In-Reply-To: <CY1PR09MB07930CE654F0C23B035D4F3484300@CY1PR09MB0793.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.64.163.239]
x-tm-as-product-ver: SMEX-11.0.0.1191-8.000.1202-21910.005
x-tm-as-result: No--38.989300-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-ID: <8CCDE854FE4B9049AB0065F75D4AB28E@twcable.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/mOhoOJgFLwo__1WqZ-NTHLHVWqY>
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: Fri, 30 Oct 2015 14:01:16 -0000

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.