IETF solution for pairing cellular hosts
"Pars Mutaf" <pars.mutaf@gmail.com> Tue, 25 September 2007 16:04 UTC
Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaCtK-0007eO-Ml; Tue, 25 Sep 2007 12:04:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaCtF-0007ap-BM for ietf@ietf.org; Tue, 25 Sep 2007 12:04:01 -0400
Received: from el-out-1112.google.com ([209.85.162.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IaCt9-0001Ex-Pt for ietf@ietf.org; Tue, 25 Sep 2007 12:04:01 -0400
Received: by el-out-1112.google.com with SMTP id b25so436381elf for <ietf@ietf.org>; Tue, 25 Sep 2007 09:03:36 -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:mime-version:content-type; bh=m1WfOFa3NWAbOQYTF0DsymdmQ0EL1TQPFKHJL6gh6g4=; b=EuutnF7aA7+KBXs9dt70mugqCdyVy7oVfpe8UAw8zdd4TSZJlQaoV1gHrmFDfsaC3Z/65QfySeOgeN9rNRsxKpffKU5yg2gZ4/cEiHU8yI2rV2RYxq9rknmfGTDr13piDXxiK5Ngxkqt3k9f2lSvYzGetBNnKo1Z0EFIYpIW8Mo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=JgvJFbeHk0fuUm1rBGkcgpB9ACbfBvxlfghsVEf8X3LkbFih0krCk+AW/9DtNPI2O60xHnKtCCfVm5nfSjpPCHVJ0dO5z4sGGrB7OwAVo9GD5kh4HPQ3TkIHMtl3mnlPdlKpFti+u1vxMy9ylUymEFje1m/BHc5f9nagBGz7DZc=
Received: by 10.142.212.19 with SMTP id k19mr2315907wfg.1190736215224; Tue, 25 Sep 2007 09:03:35 -0700 (PDT)
Received: by 10.70.22.4 with HTTP; Tue, 25 Sep 2007 09:03:35 -0700 (PDT)
Message-ID: <18a603a60709250903n6e33a818jcbf2c3a2ef51e148@mail.gmail.com>
Date: Tue, 25 Sep 2007 18:03:35 +0200
From: Pars Mutaf <pars.mutaf@gmail.com>
To: ietf@ietf.org, pars.mutaf@gmail.com
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc:
Subject: IETF solution for pairing cellular hosts
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1930513803=="
Errors-To: ietf-bounces@ietf.org
Hello, Currently there are two approaches for obtaning 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. ------------ Please note that this is an abstract to solution, I personally don't know how to design it (or, which design might be the best one). I hope this would be of interest to the IETF. Comments appreciated either here or please subscribe to the following mailing list: https://www1.ietf.org/mailman/listinfo/humanresolvers Thanks pars mutaf
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts John Levine
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Daniel Senie
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Daniel Senie
- Re: IETF solution for pairing cellular hosts Suresh Krishnan
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts IETF member Dave Aronson
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts John L
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts John L
- Re: IETF solution for pairing cellular hosts John L
- Re: IETF solution for pairing cellular hosts Bill McQuillan
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- RE: IETF solution for pairing cellular hosts michael.dillon
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Virendra Gandhi
- Re: IETF solution for pairing cellular hosts Pars Mutaf
- Re: IETF solution for pairing cellular hosts Spencer Dawkins