Re: [lisp] LISP EID Block Size

Roger Jørgensen <rogerj@gmail.com> Sat, 02 November 2013 11:47 UTC

Return-Path: <rogerj@gmail.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 1F13B11E81E9 for <lisp@ietfa.amsl.com>; Sat, 2 Nov 2013 04:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.29
X-Spam-Level:
X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 duQw3tufxovy for <lisp@ietfa.amsl.com>; Sat, 2 Nov 2013 04:47:36 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 741DC11E8102 for <lisp@ietf.org>; Sat, 2 Nov 2013 04:47:35 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id m15so469201wgh.1 for <lisp@ietf.org>; Sat, 02 Nov 2013 04:47:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ORwS6WZPOdKVKvf04choEF4ctmrfKdW+Ds/8skP/nfA=; b=rWjhz3CRbAex/NgyGDLA3Cn0S6u9GUCmiPQCNpZbcfllBi0G7kNeW3Zzv38/07cEvf sL77ewvp3eWrX5sjNZJ92vKv4d3BBO/oQ+cqSmN+w71/Knu2OnD24dmG40lyWp83UcEd M4+WR0ihFo27Dn75wBrojxpeGMraaAXujWuv0XXBkHxEBzpGfEiQqMSRg6ZE49eEluT1 e3d3mffcj4zM893ZnmFx8JfueXlsyymH08R3IXkdMsD2nmgBsVcT/KBfn4EjX3t0Bvww DU59BisA4aIseH9Dyk9L6RDpYXp9ggJVDoqROFgHoR/ZeEeYX9ZoUFd8ocwWlZl3lxwS G5Lg==
MIME-Version: 1.0
X-Received: by 10.180.149.179 with SMTP id ub19mr5414416wib.43.1383392854566; Sat, 02 Nov 2013 04:47:34 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sat, 2 Nov 2013 04:47:34 -0700 (PDT)
In-Reply-To: <FBB83D5B-E5C1-493E-8FAD-2AF489759CBF@steffann.nl>
References: <20131030154454.587D918C143@mercury.lcs.mit.edu> <15CC7F54-075E-4EB8-940B-8DCB198134A2@apnic.net> <E6AD700C-DC48-48DB-9FF5-A24C6121834C@gmail.com> <D68CD130-50BC-42AE-95E5-A4EBEEB20808@apnic.net> <8119249a5b4cb0604726fa7560538cf3@bartschnet.de> <FBB83D5B-E5C1-493E-8FAD-2AF489759CBF@steffann.nl>
Date: Sat, 2 Nov 2013 12:47:34 +0100
Message-ID: <CAKFn1SG2KaKi1iO0m8iO2hqz1MFpc6yzStf0qyMSbRa_-dd1Dw@mail.gmail.com>
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Sander Steffann <sander@steffann.nl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Sat, 02 Nov 2013 11:47:37 -0000

On Fri, Nov 1, 2013 at 1:45 PM, Sander Steffann <sander@steffann.nl> wrote:
> Hi,
>
>> I want to ask everyone on the list: Which facts prevent a scaling experiment with the aim of global production state? In my opinion a /16-EID-prefix is perfect for that goal.
>
> The problem is in that what you describe depends on public PITRs, and we have seen how badly that worked for 6to4 public relays. Running a public relay costs money (equipment, maintenance, bandwidth), and when nobody pays for them then we cannot expect any decent quality. And LISP will be blamed and seen as an unreliable protocol, just like 6to4. Relying on public relays is a very bad idea.


This problem you're touching here is the interconnect, and interaction
between LISP-world and legacy Internet (as I like to cal lit). We all
agree that the 6to4 path will not work, or scale well.

For the experiments we don't really need this interconnect either, and
if the need arise the mgmt-draft can be used anyhow since it don't
really care if there is interaction or not.  However the eid-block
draft do have some text on this, but it's probably not good enough to
get it done properly. Any idea on how to address it better there?



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no