On Mon, Mar 4, 2013 at 8:14 PM, David Conrad <[email protected]> wrote: > I understand what you are saying but believe you're trying to put the cart > before the horse. As things stand now, their is little knowledge of LISP so > you get into the same chicken-or-egg problem we've had with IPv6. For an > experiment, I believe you need to make resources as easy to get as possible > in order to minimize barriers to entry. Every barrier, be it price or > legalese or justification hoops (or even figuring out where to go to get > EIDs), reduces the likelihood people will be interested in playing. Hence my > suggestion the allocation/registration service be no more than cost.
I don't agree that I've put the cart before the horse. What I've suggested is a potentially more efficient way to get EIDs to participants, provide them with a "point-and-click" option for map server, and the items you list below, whois and reverse DNS, without you getting bogged down in the RIR policy process AND without trying to make RIR memberships bear the costs associated with these services. AFRINIC can't afford to spend money on things its members don't want. RIPE NCC just spent a million bucks of members' money on RPKI that it turns out a lot of people don't want, and they have now undertaken an efficiency program to cut programs that members don't want to pay for anymore. ARIN estimated over $50k USD expense just to add password authentication support to its IRR database, a service it already provided, and then took over six months to get it done. Expecting RIRs to be excited about this and do it effectively is expecting a lot from organizations who range from cash-strapped to simply inefficient, but in all cases, their policy processes are going to take very significant time. If you permit domain registrars to offer this service, some of them probably will, and they are able to do it more quickly and cost-effectively than the RIRs. How many people in this discussion actually deal with any RIR on a regular basis? > Perhaps a more interesting question is what services will the EID > allocator/registry need to provide (in addition to allocating EIDs and > keeping registration data). Two services mentioned so far are: > > 1) whois, to lookup the registration data > 2) reverse dns, so people can map EIDs into domain names > > Providing these services has a cost that correlates with a committed service > level (e.g., 5 9s service costs much more than 1 9s service). What level of > service is acceptable for the LISP experiment? I think you need these items to collaborate and troubleshoot problems in a hopefully growing community of users. Both these items are easy and inexpensive. It's more challenging to provide a mapping server because that is a service / technology they are not familiar with, but that should also be relatively easy compared to the policy process. -- Jeff S Wheeler <[email protected]> Sr Network Operator / Innovative Network Concepts _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
