Re: [lisp] LISP EID Block Size (Noel Chiappa) Thu, 31 October 2013 22:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EAE5B11E8254 for <>; Thu, 31 Oct 2013 15:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id M8+r+kZGShXW for <>; Thu, 31 Oct 2013 15:21:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E3C5F11E8244 for <>; Thu, 31 Oct 2013 15:21:04 -0700 (PDT)
Received: by (Postfix, from userid 11178) id 1999F18C180; Thu, 31 Oct 2013 18:21:04 -0400 (EDT)
Message-Id: <>
Date: Thu, 31 Oct 2013 18:21:04 -0400 (EDT)
From: (Noel Chiappa)
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 22:21:22 -0000

    > From: George Michaelson <>

    > code should be written to be agile and be able to be TOLD what prefix
    > is the magic prefix. Nobody should be reifying prefixes into anything

That path makes sense if there's a good chance the experiment is going to
succeed, and the code is going to wind up going into service.

If not, though, you're mandating that _other people_ have to spend more of
their engineering time writing code that's basically totally irrelevant to the
experiment at hand. Hopefully needless to say, you wouldn't like it if other
people started allocating _your_ engineering time in ways that made sense to

But that's not the worst problem with your proposal:

    > And work the experiment in a /32

Let's suppose the experiment is a success (i.e. your suggested coding
investment will have paid off). If a /32 is allocated, you've basically now
mandated that there's going to have to be a flag day, or something, to
transition from the /32 to some more suitable space. That's going to be a
massive hassle.

Look, you can't have it both ways. Your 'make the code flexible' concept only
makes sense if this experiment is going to succeed - but if it succeeds,
allocating such a small prefix is guaranteeing a massive operational headache
down the line.