In order to make an ID/Loc split work on an Internet-wide ubiquitous scale, we need very good solutions and/or greater understanding to some hard questions such as what will be the granularity of the mapping function (how large will the mapping table be and what granularity of prefix will be in it), how to do the mapping, how to do liveness detection, what the scaling properties of the mapping and liveness detection functions is likely to be, and what the manageability, security, and robustness implications are. I guess that while we are at it we need to figure out if there are other issues, such as MTU, that need consideration.
If you want to do experimentation on a moderate scale, then answers to these questions are not strictly needed. I didn't see any of these "hard issues" explicitly mentioned in the proposed charter (although there is mention of "the LISP+ALT mapping system"). Is this because the effort is intended to be focused on the shorter term experimentation efforts (including experimental protocol specs that allow the immediate experiments to occur), for which these hard issues do not need to be answered? Thanks, Ross -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Eliot Lear Sent: 21 January 2009 08:56 To: PAPADIMITRIOU Dimitri Cc: [email protected]; [email protected]; [email protected] Subject: Re: [lisp] [Int-area] Please respond: Questions from the IESG as to whether aWG forming BOF is necessary for LISP On 1/21/09 2:12 PM, PAPADIMITRIOU Dimitri wrote: > All items in the charter - see below - are exclusively oriented toward > LISP protocols implementation specifics, and interworking: > Right. This is a LISP WG. There is nothing stopping anyone from creating another WG, assuming the work warrants it. And again, the output is experimental docs. No standardization choices are being made. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
