> It is right that IETF alone cannot mandate what operators do. But the > plan according to the earlier charter proposal was for IETF to influence > the behavior of the RIRs through guidelines. And that could have led > operators to take action they otherwise would not have taken. > > One example of such action would be the adoption of LISP by an operator, > not because LISP would have a benefit for the operator, but because the > address space desired by the operator was restricted to be used with > LISP. In this regard, I was in particular thinking of efforts such as > draft-fuller-240space and draft-meyer-lisp-eid-block.
Here are the facts:
(i). the 240/4 draft has nothing to do with LISP
(ii). I wrote the EID block draft on the advice of
an ARIN AC member. It went no where, as you can
see, so we bought an experimental EID prefix from
ARIN.
But again, this is beating a dead horse. If the consenus
is do such a draft (assuming there is somewhere to "do a
draft"), then I assume we (the community) will do
so. Otherwise, we will not. Nuff said?
Dave
signature.asc
Description: Digital signature
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
