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

[[e-mail] (Noel Chiappa)]

    > From: <[e-mail]>

    > the routing integration between none-LISP and LISP internet, how are
    > that going to work? The current document isn't clear enough on that as
    > I see it.

The way the routing will work would take a couple of PhD theses to fully
cover (I know of one that's already underway). So it's not really a topic
that can be covered in this ID.

Adding to the complexity is that if LISP becomes widely deployed, how the
routing works will likely change over time; in the early stages, when there
are small islands of LISP, it'll be one thing; later on, when there are
islands of legacy stuff, it'll be totally different. Etc, etc.

    > Address these thing somehow in the document, even just mention that
    > it's subject for other document and I'm happy... :-)

The IETF used to have this concept of 'rough consensus and _running code_';
i.e. we tried stuff out to see if it works. When did we change into an
organization that had to have every 'i' dotted, and every 't' crossed, before
we could move an inch? (Saying 'just refer to the document where it is
covered' doesn't help, if the other document isn't written yet.)

All this ID is trying to do is allocate a rather modest chunk (~ one quarter
of one tenth of one percent - .025% - if I've done the math right) of address
space for an experiment; exactly how it will be best used, and what the best
allocation process is, is to some degree part of that experiment.

	Noel