Re: [Sip] IETF solution for pairing cellular hosts

On 9/28/07, Pars Mutaf <pars.mutaf@gmail.com> wrote:
>
> Hello,
>
> Thanx for the message, I hope you and (other SIP experts)
> subscribe to the ML:
>
> https://www1.ietf.org/mailman/listinfo/humanresolvers
>
> Personally, I'm not sure if we need a store/forward
> solution. We probably don't want to store a pairing
> request message while the user is off-line. Because
> the request message itself can be used for SPAM.
>
> Maybe a real-time solution is preferable. I.e., if
> the target user is off-line we don't care. The querier
> needs to try later to get the user's consent.
>
> Personally, I'm also against a SIP-based solution.
> This is my personal opinion and of course open to
> discussion.

Hello,
I'll feel more comfortable if I explain the above statement
to SIP folks. I'm not defending any particular design, I'm trying
to start some discussion and get more people to the list,
and hoping to find the right choices together.

For example there is also a serverless design possibility
(for local use only) which also deserves attention IMHO,
because of the obvious advantages of a serverless design:

-I have a new phone, I want to pair it with that of a friend.
-I type his name.
-My phone issues a local multicast DNS query to his name
over WiFi or WiMax.
-Using multicast DNS my phone scans his name.
-His phone returns an IP address (possibly a local/temporary one)
and perhaps other info helping me deal with name collisions.
-We use the proposed pairing protocol for exchanging our
SIP URIs, fixed MIPv6 home addresses, create an IPsec SA etc.

This is also another obvious design with pros and cons IMHO.

Thanks,
pars

I really hope we can talk about these issues.
>
> Thanks,
> pars
>
> On 9/28/07, Dean Willis <dean.willis@softarmor.com> wrote:
> >
> >
> > On Sep 27, 2007, at 4:38 PM, Dale.Worley@comcast.net wrote:
> >
> > >    From: "Pars Mutaf" <pars.mutaf@gmail.com>
> > >
> > >    The following is a new abstract solution, a third alternative, a
> > > protocol
> > >    for "pairing" two cellular hosts:
> > >
> > >    Model of operation
> > >
> > >    1. The querier user types the target user's "human name" (as if
> > > he were
> > >       consulting a phonebook), or a pseudoynm.
> > >    2. The pairing request is forwarded to the target phone.
> > >    3. The query, along with the querier user's name, are displayed
> > > on the
> > >       target phone's screen.
> > >    4. The target user approves the request in real-time by pushing
> > > on the YES
> > >       button of the phone.
> > >    5. The two phones exchange their Mobile IPv6 home addresses, SIP
> > > URIs, and
> > >       establish an IPsec security association (using IKEv2).
> > >
> > > How do you make this work?  Step 2 seems to require that you have
> > > already located the target phone, whereas the protocol's *purpose* is
> > > to locate the target phone.
> > >
> >
> >
> > One possibility is that the directory service is operating on behalf
> > of the target, not the searcher. As such, the directory service is
> > trusted to know the display name to userID binding. When it receives
> > a query, the directory service uses the target's SIP contact
> > registration to send a consent request to the target user. If the
> > target user response positively, then the directory service returns
> > the directory's query result to the searcher.
> >
> > Basically, another layer of indirection (directory) in front of a
> > watcher pattern.
> >
> > There are probably other embodiments, but that's the obvious one.
> >
> > --
> > Dean
> >
> >
> >
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >
>
>