> Dino, > > On Mar 3, 2013, at 12:24 PM, Dino Farinacci <[email protected]> wrote: >>> - requirements for allocation MUST be the same globally, no >>> regional/national/local variation >> I won't disagree. But if we say the EID-prefixes are globally unique then >> how could they be different. There is no provider variable here to >> complicate matters. > > Currently the rules by which you obtain provider independent IP addresses (v4 > or v6) differ depending on the RIR region (that is, geo-political location) > in which you reside. That is, if you live in (say) Boliva, the required > information you must supply to LACNIC and other requirements you must meet in > order to justify an allocation differ than that the info you must provide to > APNIC if you live in (say) Japan. > > At this point in LISP development/deployment, I would assume you'd want the > rules by which you can get an EID allocation to be the same regardless of > where you live and for the requirements to be as minimal as possible (e.g., > "I'm Dino and I want an EID").
Yes that's correct. But I am not sure in later changes we'll need anything different but ill wait for experience to tell us that. >>> - allocation service MUST be provided at no more than cost >> Agree in that. But you shouldn't dictate a cost though. Some may want to >> bundle allocation with something else so their costs could be more but they >> cover with different revenue sources. > > I agree that costs shouldn't be dictated. More specifically, I don't think > the draft should get into how the service is funded other than to say the > allocation service can't charge more than the cost to provide the service. Agree. > >>> - registration data MUST be maintained and be made publicly available via >>> <something, e.g., whois> >>> - registration maintenance MUST be provided at no more than cost >> If you are talking about Mapping Database registration? > > No. I was talking about a the data that would be made available via a Whois > service, i.e., how does someone on the Internet find out the contact info for > who 'owns' an EID. Okay. > >>> - reverse dns SHOULD be provided >>> - the service MUST be available <service level commitments> >> >> I view EID assignment as a one-time transaction and not a continual service. > > EID allocation is a one-time service, but to meet requirements like global > uniqueness and providing registration data via Whois (or whatever), somebody > has to maintain a database and a DNS server (if rDNS is used) which is a > continual service subject to a service level commitment. Right - understand you now. > >> Here are the entires: >> >> (1) Data-plane service provider (an ISP). >> (2) Control-plane Mapping Service Provider (MSP). >> (3) A one-time transaction EID-prefix allocator. >> (4) A DNS service provider. > (5) A registration data maintenance service. Ack. > >>> Once you define the minimal policy, I personally believe the right answer >> From our email exchanges thus far, do you think we have? > > Outstanding questions I see: > > - Size of allocation? > - Confirmation that there should be no regional/national/local variation on > allocation policy? > - Should Reverse DNS be implemented? > - What kind of Whois service (port 43, restful, something else)? I hope Luigi is taking note. All points are reasonable I think. > >>> Why? What benefit does this provide? Is it (e.g.) a policy goal for EIDs >>> to have different allocation requirements based on geo-political location >>> of requester? >> No - no geo-political requirement. So we could have the IANA do all >> allocations. > > ICANN, as the provider of IANA functions according to RFC 2860, might be one > option, particularly as this is experimental, however here there may be some > dragons and pragmatic constraints that might not make them the best. I guess > I'd probably put something in the IANA considerations section saying > something like: > > "There is an operational requirement for an EID allocation service that > ensures EIDs allocated according to the requirements previously described are > unique. In addition, there is an operational requirement for EID registration > service that allows a lookup of the contact information of the entity to > which the EID was allocated given only that EID. IANA must ensure both of > these services are provided in a globally uniform fashion for the duration of > the experiment." Makes sense to me. > Or something like that (that's probably not the right wording but hopefully > you get the idea). I imagine there are a number of folks who IANA could ask > to provide the service if they don't want to or can't do it themselves. > > Regards, > -drc > Maybe someone from ICANN can respond. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
