On Mar 13, 2013, at 8:11 PM, Noel Chiappa <[email protected]> wrote:
>> From: John Curran <[email protected]> >> if there is any reason not to take the time to fully plan out the >> management approach as the initial _production_ solution (not >> experimental), then it has not been expressed on the mailing list. >> ... >> Since we are actually establishing the management approach for the >> identifier space of the future Internet, the task should be scoped >> accordingly > > I'm not sure I agree that that's reasonable. To me, it's like asking Paul > Mockapetris to design the ICANN/IANA/RIR structure when he was doing DNS. > > I know _I'm_ not equipped to design the business/etc framework you're to a > degree talking of. Apologies, I was unclear - what I meant by "the management approach" was with respect to the technical requirements for management of the EID block (i.e. "eid-block-mgmnt"), not business/political framework. Example of possible technical requirements to get nailed down include: (borrowing slightly from Joel and David's earlier emails) - What technical policy requirements are there are there on EID prefix issuance to end-sites? - What size IED prefixes do end-sites receive? Fixed or variable in size, one or multiple per org, contiguous or doesn't matter, etc. - What services need to be provided by any registry issuing EID prefixes? - Do any services need to be provided by orgs receiving EID prefixes? - Are there any technical constraints on movement/transfer/redelegation of EID prefixes, and/or service continuity issues to worry about? All of the above answered to make sure that the issued EID prefixes can technically work the way they are expected to, and without postulating on who the registry/registries should be, if there should be a split registry/registrar model, and related policy/business issues. Getting the technical constraints down will allow creation of working registry system; the necessary policy/business discussions are different scope. /John Disclaimers: My views alone. Declared value of content is zero. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
