Re: [lisp] LISP EID Block Size

Rene Bartsch <> Thu, 31 October 2013 16:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0975111E817A for <>; Thu, 31 Oct 2013 09:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.939
X-Spam-Status: No, score=-1.939 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NPSgrVK0WBBk for <>; Thu, 31 Oct 2013 09:48:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2879A11E811D for <>; Thu, 31 Oct 2013 09:48:15 -0700 (PDT)
Received: from [] ( by with esmtpa (Exim 4.68) (envelope-from <>) id 1VbvPo-0005SC-Vt for; Thu, 31 Oct 2013 17:48:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 31 Oct 2013 17:48:12 +0100
From: Rene Bartsch <>
In-Reply-To: <>
References: <> <> <> <>
Message-ID: <>
User-Agent: Roundcube Webmail
X-Df-Sender: cmVuZUBiYXJ0c2NobmV0LmRl
Subject: Re: [lisp] LISP EID Block Size
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Oct 2013 16:48:24 -0000

Am 2013-10-31 17:31, schrieb Sander Steffann:
>> 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.
> I understand what the technical idea is. There are already EIDs out
> there (including my own network) that are not in any special prefix.
> Therefore "address is in special prefix" != "address is an EID".
> Unless you break LISP for already existing sites I don't see how
> having a special prefix is going to help in (correctly) determining
> whether an address is an EID.

Consider every consumer gets a random PI-prefix out of the global 
unicast address space. Now you have two problems with a public PITR:

1. What prefixes does the public PITR have to announce? Where to get the 
list from? Scan all Map servers?
2. Billions of random PI-prefixes need millions or even billions of 
BGP-routes to be announced by the public PITR via BGP.

If there's one dedicated EID address space a public PITR only has to 
announce ONE BGP-route to himself.

Best regards,