Dear all, Quick reminder: the problem that I'm bringing to your attention is:
http://www.ietf.org/internet-drafts/draft-mutaf-piqproblem-00.txt Here is a better formulated question. We have choices (the above cited application largely merits one of them): 1. IETF designs a more general purpose multicast name resolution protocol. Thanks :-) Currently it is too much ZEROCONF-oriented. There are possibly many other applications that will use multicast name resolution. The above cited example is a very good one. The above cited problem is poorly addressed by current multicast name resolution protocols. 2. Otherwise, the above cited application (private information queries) can simply bypass name resolution. It can use name-based IPv6 addresses (or HUMID addresses). No solution will be provided for IPv4. This solution would work as follows (briefly): The responder application run by Alice Collins' cellular host configures a link-local IPv6 address and listens: link-local subnet prefix | 64bithash(alicecollins) where '|' denotes concatenation, and link-local subnet prefix is well-known and constant. 64bithash(alicecollins) is the IPv6 interface ID. The initiator user enters the name Alice Collins and hence the application can generate a query to the above address. The phone number of Alice Collins can be learned from her phone directly (if approved by her). It is also possible to search a host in multiple subnets (using global scope addresses). I can explain this point if you wish. It can also work with localized mobility management and even Mobile IPv6, provided that you have the same home/regional prefix with Alice Collins. This means that we are not limited to link-local scope. But this needs more investigation. Looking forward to your suggestions. Thanks, pars mutaf On Tue, 2007-01-30 at 23:22 +0100, Pars MUTAF wrote: > I would like to bring a new problem statement draft to your > attention (1 page). Until it appears in the I-D rep, please > find it here: > > http://www.freewebs.com/pmutaf/draft-mutaf-piqproblem-00.txt > > I believe that not having this application > would be very unfortunate. (I think this is an INT area topic.) > And currently available name resolution techniques do not > address this problem as they should. > > Do you have any comments on this problem statement? > > Thanks. > pars mutaf -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
