IETF Logo Mail Archive

Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC

Dino Farinacci <farinacci@gmail.com> Thu, 15 November 2012 21:25 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F283E21F896C; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.487
X-Spam-Level:
X-Spam-Status: No, score=-3.487 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLwXTv5ZKvVj; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 812EB21F8947; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id h15so849384dan.31 for <multiple recipients>; Thu, 15 Nov 2012 13:25:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=oBFS7tz/G6QqiQoKH7YZ6EBcKZXZlYCChCgmv7AcgCg=; b=vbDKVXSYuku3KOSEyoQU/mkwzSS7IMtFDy8tTjQIfgQb3OnEEHbZNxlGRWUmaYceYI sZrxJW9kBZ1RCHYmHEt5OnyRZV5SF6zPHJhJWprp83EnJYnyR0ie9E4CnMPwYdUgVgoj 1YYAVSmiR/4hNN5Vgb69SJhP9pXD43GfFY9qujwSGUZnxKcn2DS5UtpV1o7fBeRNAo6l XHflhTuIjMVz3Pnc8hj9+3Yy3l3toEZVHAvrfMyYovLYV9vLIwOkE4FQkBu9xnprLXXg JLb1r2Y7rVQ2BU2Kb/+ma+0vxP0NBOEzCTcFU37kW/S2ZJTrxOyQb51H0GiJPTwXXUXS +Dlg==
Received: by 10.66.74.40 with SMTP id q8mr6877478pav.29.1353014738896; Thu, 15 Nov 2012 13:25:38 -0800 (PST)
Received: from dhcp-10-155-59-220.cisco.com (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPS id pv8sm10062749pbc.26.2012.11.15.13.25.36 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 13:25:37 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
Date: Thu, 15 Nov 2012 13:25:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5958FE99-2975-490A-9F51-E56CFD9D384B@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <00C0245E-59D7-4552-8BB4-1C0099513D1D@steffann.nl> <6E5736BD68F770449C74FBAD975F807C94AA4F0C@NYDC-EXCH01.vinci-consulting-corp.local>
To: Paul Vinciguerra <pvinci@VinciConsulting.com>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: Sander Steffann <sander@steffann.nl>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 21:25:40 -0000

And you do not want to tie addresses to topological entities. Or you will lose the mobility capabilities that Locator/ID separation can bring.

Dino

On Nov 15, 2012, at 12:21 PM, Paul Vinciguerra <pvinci@VinciConsulting.com> wrote:

>> One thing we have to be very careful with here is that EIDs are not directly
>> allocated/assigned to end sites from this block. That will cause everyone to
>> independently find (different) PITRs for their space, which will make a mess
>> of the global IPv6 routing table...
>> 
>> Thanks,
>> Sander
> 
> I don't think that (by definition) there is any way to cleanly aggregate PI space.  Legacy advertisements are going to be done by their LISP provider and will have to match the endpoint's PI allocations.

v2.23.0 | Report a Bug | By Email