Make it an allocation for EIDs and ILNP can use it too.
Dino
On Nov 21, 2012, at 12:25 PM, "George, Wes"
<wesley(_dot_)george(_at_)twcable(_dot_)com> wrote:
From: ietf-bounces(_at_)ietf(_dot_)org
[mailto:ietf-bounces(_at_)ietf(_dot_)org] On Behalf Of
Noel Chiappa
If a single permanent allocation that never changes is truly
necessary
Allocation != reservation. Nobody is asking for the entire chunk to be
_allocated_ (i.e. given out), just that it be _reserved_ for this use.
[WEG] You're hairsplitting on semantics in a way that is mostly unhelpful to
the discussion at hand. Reserving the block for LISP means that it cannot be
used for anything else. Whether that's an IANA reservation or an RIR
allocation is really immaterial to the point I was making, which is that if
you truly believe we have to identify a block once and for all for LISP that
is the correct size to be used permanently and indefinitely, you need a
better justification than you've given, and using "experimental" as a
justification for not having the details worked out isn't going to be
acceptable.
Regards,
Wes George
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail
and any printout.
_______________________________________________
lisp mailing list
lisp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/lisp