Some of those questions are ones we very much need to answer in defining the policies. That's what I would like to see on the document. I would guess tgat reverse DNS will not be needed, but I could wrll be mistaken.
Yours, Joel Sent from my Samsung smartphone on AT&T -------- Original message -------- Subject: Re: [lisp] I-D Action: draft-iannone-lisp-eid-block-mgmnt-01.txt From: Arturo Servin <[email protected]> To: "Joel M. Halpern" <[email protected]> CC: lisp <[email protected]> On Sat, Mar 2, 2013 at 6:38 AM, Joel M. Halpern <[email protected]> wrote: (Speaking personally, and interested in more data or perspectives.) As far as I can tell, EID space is not Internet routable IPv6 Unicast space. Yes, that is ok, but does it have the same constraints of registration and conservation? Is anybody able to use the whole /16 a piece of it, a /20, /32, /48? It has to be unique? Do we need to register it? If so, do we need a whois/restwhois? reverse dns? who is going to operate those services? And the coordination requirements appear to me to be quite different from those for IPv6 routable unicast addressing. As are the constraints which drive allocation. which are? Which is why I want to spell out the requirements, rather than writing in who will fill those requirements. I am ok with it. I was on the assumption that the WG have a clear idea of those requirements already. Yours, Joel Regards as
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
