Re: [lisp] LISP EID Block Size

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 31 October 2013 17:14 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 480AF11E8179 for <lisp@ietfa.amsl.com>; Thu, 31 Oct 2013 10:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level:
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAQEmJgupI+M for <lisp@ietfa.amsl.com>; Thu, 31 Oct 2013 10:13:56 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 950B111E8173 for <lisp@ietf.org>; Thu, 31 Oct 2013 10:13:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 6B5C71C9BF1; Thu, 31 Oct 2013 10:13:55 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (c213-89-137-101.bredband.comhem.se [213.89.137.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5D1501C0833; Thu, 31 Oct 2013 10:13:54 -0700 (PDT)
Message-ID: <52728FCF.2060603@joelhalpern.com>
Date: Thu, 31 Oct 2013 13:13:51 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Dino Farinacci <farinacci@gmail.com>
References: <20131031151830.55F9618C168@mercury.lcs.mit.edu> <EA0CEAB9-BD0F-4278-BE30-6D6DB7E7B624@steffann.nl> <FC33A2A0-45EA-424B-8F37-D479131AEDD4@gmail.com>
In-Reply-To: <FC33A2A0-45EA-424B-8F37-D479131AEDD4@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] LISP EID Block Size
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 31 Oct 2013 17:14:01 -0000

Actually, that use case is only helped by the EID block if you can be 
sure that ALL the destination EIDs it will see will come from the block.
Which seems to be impossible to ensure in the general case.  And easy to 
achieve without an allocated block in many of the special cases.

Yours,
Joel

On 10/31/13 11:57 AM, Dino Farinacci wrote:
>> If the implementation is hard to explain, it's a bad idea.
>> If the implementation is easy to explain, it may be a good idea.
>> """
>>
>> If it is difficult to explain what the experiment is about then I understand that people are afraid it might be a bad idea.
>
> I'll explain one experiment and will be crystal ear about it.
>
> (1) We want to have a LISP site send to both LISP sites and not LISP sites.
>
> (2) We want an ITR to do mapping database lookups when the destination address is an EID.
>
> (3) We want the ITR to forward packet s by doing a traditional FIB lookup when the destination is not an EID.
>
> Good Zen?
>
> Dino
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>