RE: [P2PSIP] IETF solution for pairing cellular hosts

<marcin.matuszewski@nokia.com> Thu, 27 September 2007 14:26 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 1IauKM-0004o7-OA; Thu, 27 Sep 2007 10:26:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IauKM-0004o1-6P for humanresolvers@ietf.org; Thu, 27 Sep 2007 10:26:54 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IauKL-0002Xg-2f for humanresolvers@ietf.org; Thu, 27 Sep 2007 10:26:54 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l8REQZ71025520; Thu, 27 Sep 2007 17:26:49 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Sep 2007 17:26:36 +0300
Received: from esebe102.NOE.Nokia.com ([172.21.138.217]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Sep 2007 17:26:36 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 27 Sep 2007 17:27:41 +0300
Message-ID: <3F18E76823C95E4795181D74BAC7664F05248C51@esebe102.NOE.Nokia.com>
In-Reply-To: <18a603a60709270649j2f6b19d3w77cc244f8403bd6c@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [P2PSIP] IETF solution for pairing cellular hosts
Thread-Index: AcgBDZp+Bb962Ob3Rh6UW2SobWFc4QAA5+WA
References: <18a603a60709270649j2f6b19d3w77cc244f8403bd6c@mail.gmail.com>
From: <marcin.matuszewski@nokia.com>
To: <pars.mutaf@gmail.com>
X-OriginalArrivalTime: 27 Sep 2007 14:26:36.0853 (UTC) FILETIME=[6958DE50:01C80112]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: humanresolvers@ietf.org
Subject: RE: [P2PSIP] 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

Hi Pars,
 
I was working on solutions for this problem. One solution is presented
in the following paper: "Contacter: an enhanced contact application for
easy update and recovery of contacts using the Session Initiation
Protocol (SIP)"
http://ieeexplore.ieee.org/iel5/4216894/4216895/04216904.pdf
 
Best regards,
Marcin Matuszewski

________________________________

	From: ext Pars Mutaf [mailto:pars.mutaf@gmail.com] 
	Sent: 27 September, 2007 16:49
	To: sip@ietf.org; p2psip@ietf.org
	Subject: [P2PSIP] IETF solution for pairing cellular hosts
	
	
	[sorry for cross posting. this is an invitation]
	
	
	Pairing Cellular Hosts
	
	https://www1.ietf.org/mailman/listinfo/humanresolvers 
	
	Currently there are two approaches for obtaining contact
information for a 
	target cell phone: (i) consulting a phonebook, (ii) manually
exchanging 
	phone numbers upon face-to-face user contact. Both approaches
have 
	their own limitations. 
	
	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). 
	
	The target user does not need to publish his/her private SIP URI
and home 
	address (as recommended in [1] in SIP context). Cell phone users
do not
	publish their phone numbers today.
	
	The users do not need to manually exchange their SIP URIs and
home 
	addresses which are too long (an IPv6 address is 16 bytes long
and random 
	looking, a SIP URI can be very long e.g. up to 30 characters and
even more 
	with a random part for privacy). 
	
	The protocol also works in the absence of user contact, for
example when 
	the target user's SIP URI is lost (loss of state, new phone), or
this is 
	the user's first phone, and hence his/her contact list is
initially empty.
	Thousands of cell phones are sold everyday..
	
	[1] Peterson, J., "A Privacy Mechanism for the Session
Initiation Protocol", 
	    RFC3323, November 2002.
	
	
	=======================
	
	Interested folks could you please subscribe to the mailing list
created
	for this discussion:
	
	https://www1.ietf.org/mailman/listinfo/humanresolvers 
	
	
	
	We already had some discussions on the IETF list recently. 
	You may want to take a look at the archives for an introduction:
	
	http://www1.ietf.org/mail-archive/web/ietf/current/msg48129.html

	
	There is also a side discussion on CAPTCHAs:
	
	http://www1.ietf.org/mail-archive/web/ietf/current/msg48172.html

	
	
	Regards, 
	pars mutaf
	
	
	
	

_______________________________________________
humanresolvers mailing list
humanresolvers@ietf.org
https://www1.ietf.org/mailman/listinfo/humanresolvers