Re: [lisp] WG Last Call draft-ietf-lisp-impact-01

Ross Callon <rcallon@juniper.net> Fri, 10 April 2015 03:29 UTC

Return-Path: <rcallon@juniper.net>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B93751AC3D7 for <lisp@ietfa.amsl.com>; Thu, 9 Apr 2015 20:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 gzR2aBzrYDWO for <lisp@ietfa.amsl.com>; Thu, 9 Apr 2015 20:29:02 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0126.outbound.protection.outlook.com [65.55.169.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE09A1AC3D5 for <lisp@ietf.org>; Thu, 9 Apr 2015 20:29:01 -0700 (PDT)
Received: from BY1PR0501MB1430.namprd05.prod.outlook.com (25.160.107.152) by BY1PR0501MB1430.namprd05.prod.outlook.com (25.160.107.152) with Microsoft SMTP Server (TLS) id 15.1.130.23; Fri, 10 Apr 2015 03:29:00 +0000
Received: from BY1PR0501MB1430.namprd05.prod.outlook.com ([25.160.107.152]) by BY1PR0501MB1430.namprd05.prod.outlook.com ([25.160.107.152]) with mapi id 15.01.0130.020; Fri, 10 Apr 2015 03:29:00 +0000
From: Ross Callon <rcallon@juniper.net>
To: Dino Farinacci <farinacci@gmail.com>, Darrel Lewis <darlewis@cisco.com>
Thread-Topic: [lisp] WG Last Call draft-ietf-lisp-impact-01
Thread-Index: AQHQWnSPQbPJi+hgVUqTeQIKhdZvrp00M8ZggAArMgCAAAJBgIAFE3wAgAqKBzCAASgAAIAABvIAgABnF8A=
Date: Fri, 10 Apr 2015 03:29:00 +0000
Message-ID: <BY1PR0501MB14304FB52B725B42A2A8ADF4A5FA0@BY1PR0501MB1430.namprd05.prod.outlook.com>
References: <B339BFE7-7E19-4AAA-8B2C-276402024C74@gigix.net> <BY1PR0501MB14304477BFF1F86BAFC810B3A5F50@BY1PR0501MB1430.namprd05.prod.outlook.com> <5518A89C.3090108@joelhalpern.com> <BY1PR0501MB14306D728BC2F0CAE037DE58A5F50@BY1PR0501MB1430.namprd05.prod.outlook.com> <5C76220B-7DC6-46B9-8C57-A30D977FA7C8@gmail.com> <BY1PR0501MB1430FCF009B4994C006EB3A4A5FB0@BY1PR0501MB1430.namprd05.prod.outlook.com> <E0766E5C-8CCB-4523-85B6-540126925B78@cisco.com> <2B837AD6-2751-4E08-814E-3F109B481612@gmail.com>
In-Reply-To: <2B837AD6-2751-4E08-814E-3F109B481612@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.11]
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1430;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(13464003)(51704005)(24454002)(377454003)(87936001)(106116001)(2656002)(19580395003)(33656002)(93886004)(99286002)(230783001)(62966003)(77156002)(76576001)(102836002)(86362001)(46102003)(92566002)(54356999)(19580405001)(74316001)(40100003)(2900100001)(66066001)(2950100001)(50986999)(122556002)(15975445007)(76176999); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1430; H:BY1PR0501MB1430.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-microsoft-antispam-prvs: <BY1PR0501MB14305868E6303CDDCE343014A5FA0@BY1PR0501MB1430.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:BY1PR0501MB1430; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1430;
x-forefront-prvs: 054231DC40
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2015 03:29:00.3290 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1430
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/lcKEz8v_Jnw11JQNQ29KRKfuNQw>
Cc: LISP mailing list list <lisp@ietf.org>, "draft-ietf-lisp-impact@tools.ietf.org" <draft-ietf-lisp-impact@tools.ietf.org>
Subject: Re: [lisp] WG Last Call draft-ietf-lisp-impact-01
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 03:29:03 -0000

I understand that the ETR could send a different response to different ITRs. 

However, there is a reason that some more specific prefixes are advertised (in addition to a covering less specific prefix). One reason is that some service providers want incoming traffic delivered to them via different interconnects based on the destination. Even if you are doing traffic engineering with LISP, then this reason doesn't go away, and isn't solved by sending only the less specific prefix in the map reply. Of course there are other reasons to advertise more specific prefixes, and on the most part these don't go away either. I therefore feel that it was an error for the study discussed in [CCD12] to "... filter out more specific prefixes". 

Perhaps a more serious problem is that "BGP-prefix granularity" is not likely to be even remotely close to correct, with or without filtering out more specifics.  

Ross

-----Original Message-----
From: Dino Farinacci [mailto:farinacci@gmail.com] 
Sent: Thursday, April 09, 2015 2:16 PM
To: Darrel Lewis
Cc: Ross Callon; LISP mailing list list; draft-ietf-lisp-impact@tools.ietf.org
Subject: Re: [lisp] WG Last Call draft-ietf-lisp-impact-01

And to add to what Darrel said, the policy control can be provided at the LISP site or by the MSP (Mapping Service Provider). It depends who is jockeying for control or who wants features out-sourced.

Dino

> On Apr 9, 2015, at 10:51 AM, Darrel Lewis (darlewis) <darlewis@cisco.com> wrote:
> 
> 
> On Apr 8, 2015, at 5:29 PM, Ross Callon <rcallon@juniper.net> wrote:
> 
>> My understanding of this is that what some service providers do today is to announce some more specific prefixes (that match a PA prefix assigned to them) at some interconnection points and some different more specific prefixes at other interconnection points in order to draw in traffic where they want to draw it in. If with LISP you were to map all of these prefixes in one mapping table entry then you would be mapping them all to the same RLOC (or set of RLOCs). 
> 
> 
> This is not correct, there is no requirement for an ETR to provide the same answer to one requesting ITR as it does another.  Quite the opposite, replies can be customized depending on many possible variables.
> 
> -Darrel
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp