Re: [GROW] WGLC: draft-ietf-grow-route-leak-problem-definition (ends: 8/24/2015 - Aug 24)
joel jaeggli <joelja@bogus.com> Mon, 02 November 2015 00:17 UTC
Return-Path: <joelja@bogus.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 674C01A010F; Sun, 1 Nov 2015 16:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 w3zN5bcONQ19; Sun, 1 Nov 2015 16:17:43 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10B971A010D; Sun, 1 Nov 2015 16:17:43 -0800 (PST)
Received: from dhcp-28-39.meeting.ietf94.jp (t20010c4000003024392d7fef4df340d5.v6.meeting.ietf94.jp [IPv6:2001:c40:0:3024:392d:7fef:4df3:40d5]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id tA20Hak7070174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 2 Nov 2015 00:17:40 GMT (envelope-from joelja@bogus.com)
To: Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@instituut.net>
References: <CAL9jLaaOPvY2WZtunCOkuuCDV5-Do+cpHBfa8eEhquGdzSLVuA@mail.gmail.com> <20151030141520.GF1334@22.rev.meerval.net> <CAL9jLaa_GNXRi38-6x4PTs4Dy2T2AAwzmu1ok6QOWERzBshZuQ@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <5636AB9F.10500@bogus.com>
Date: Mon, 02 Nov 2015 09:17:35 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Thunderbird/42.0
MIME-Version: 1.0
In-Reply-To: <CAL9jLaa_GNXRi38-6x4PTs4Dy2T2AAwzmu1ok6QOWERzBshZuQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="dv0RLc0TGnXmpSLok7tgJnEpxtLm7cwx2"
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/ck-F5gk5qdm0Hfi2dcJNOuCPhhg>
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: Mon, 02 Nov 2015 00:17:44 -0000
On 11/2/15 8:39 AM, Christopher Morrow wrote: > oh well, since this conversation got re-ingnited.. > > On Sat, Oct 31, 2015 at 1:15 AM, Job Snijders <job@instituut.net> wrote: >> I think "type 5: U-Shaped Turn with More Specific Prefix" should be >> removed from the document. >> >> Given the description: >> >> "A multi-homed AS learns a route from one upstream ISP and announces >> a subprefix (subsumed in the prefix) to another upstream ISP." >> >> I'd classify this type of announcement a "hijack" or "attack", not a >> route leak. > > this makes sense to me, this is the equivalent of several well known > instances of someone's 'internap' box leaking outside their span of > control. So, I agree this is a hijack, not a leak... though clearly > the subnets were 'leaked' outside the span of control, the effect is > really a hijack of the remote prefix. hijack is the practical result of the more specific. intent is of course something else. > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow >
- [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