> From: John Curran <[email protected]>
> the reality .. is that we also seem to be planning for a successful
> experiment, which requires that the EID management guidelines specified
> in this document should be fairly complete and robust .. Trying to do
> both of these tasks at the same time (establishing a more robust _but
> still experimental_ EID management framework, as well as defining the
> long-term optimum EID management framework) may be irreconcilable.
I was going to make a related, but different comment, which is that a lot of
the discussion in this thread, towards the end of it, relates to issues and
mechanisms related to EIDs _in general_, not just this specific experimental
IPv6 EID-only block.
(E.g. the discussion about who's going to run the mapping services, and how
they're going to be paid for, etc.)
While I agree that these general topics really are very important, and worthy
of detailed consideration/discussion, let's just keep carefully in mind that
these general issues will exist _whether or not_ this IPv6-only EID block is
allocated, so they are, to a fairly complete degree, orthogonal to the
discussion of whether to allocate that block, how to manage its allocation,
etc, etc.
Noel
PS: I'm mostly offline due to travel this week, so don't expect quick
replies!
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
