Re: [Sip] IETF solution for pairing cellular hosts

"Pars Mutaf" <pars.mutaf@gmail.com> Fri, 28 September 2007 11:18 UTC

Return-path: <humanresolvers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbDrg-0004Le-LY; Fri, 28 Sep 2007 07:18:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbDrf-0004Bu-DY for humanresolvers@ietf.org; Fri, 28 Sep 2007 07:18:35 -0400
Received: from fk-out-0910.google.com ([209.85.128.187]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbDrZ-00053p-0H for humanresolvers@ietf.org; Fri, 28 Sep 2007 07:18:35 -0400
Received: by fk-out-0910.google.com with SMTP id z23so3029422fkz for <humanresolvers@ietf.org>; Fri, 28 Sep 2007 04:18:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=cMILQ40zaiPGDHQSyGUUXI8AIdPRqzeOz/RSVJfmQWY=; b=urvK3VZ22/jCfeNrWVY05qB+TBjqnaNxb7Oazg0wOUUMfjgt1FzBF293/f+FUqGhUr7DVZ7NnlJcJMpLck3cy2JYFI/NDPZSv2r3lqcUvjgb4cMSATdtRePGPNK02yxths4L++cOMpG9G4Ebz8QSo83o2yfoJCKZYTZTYGeeX+Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=tRyMLUTMctXmoE67u//T4Na9JanjOxRg2NavlZre/8Ol8gMdiwL237Y7BGr5AlLp9n5fylkrKMZVGMTUIzGWXWnjc//wxyEWrsr2nmCEjAGWRIhj2vNJq9JOqbVJ021MY2rACsreO/c4OUmwO2uYCj+Ety+jUG2Momq+2GfvsSU=
Received: by 10.82.186.5 with SMTP id j5mr7066166buf.1190978276580; Fri, 28 Sep 2007 04:17:56 -0700 (PDT)
Received: by 10.82.169.20 with HTTP; Fri, 28 Sep 2007 04:17:56 -0700 (PDT)
Message-ID: <18a603a60709280417x75a7e937y55254def4491496a@mail.gmail.com>
Date: Fri, 28 Sep 2007 13:17:56 +0200
From: "Pars Mutaf" <pars.mutaf@gmail.com>
To: "Dean Willis" <dean.willis@softarmor.com>
In-Reply-To: <F6FDE115-CA0D-496E-90E0-59A62183C546@softarmor.com>
MIME-Version: 1.0
References: <18a603a60709270649j2f6b19d3w77cc244f8403bd6c@mail.gmail.com> <200709272138.l8RLcBLC028711@dragon.ariadne.com> <F6FDE115-CA0D-496E-90E0-59A62183C546@softarmor.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: sip@ietf.org, Dale.Worley@comcast.net, humanresolvers@ietf.org
Subject: Re: [Sip] IETF solution for pairing cellular hosts
X-BeenThere: humanresolvers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pairing cellular hosts <humanresolvers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/humanresolvers>, <mailto:humanresolvers-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/humanresolvers>
List-Post: <mailto:humanresolvers@ietf.org>
List-Help: <mailto:humanresolvers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/humanresolvers>, <mailto:humanresolvers-request@ietf.org?subject=subscribe>
Errors-To: humanresolvers-bounces@ietf.org

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.

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
>
_______________________________________________
humanresolvers mailing list
humanresolvers@ietf.org
https://www1.ietf.org/mailman/listinfo/humanresolvers