[Sip] SIP trapezoid (was Re: IETF solution for pairing cellular hosts)

"Pars Mutaf" <pars.mutaf@gmail.com> Fri, 12 October 2007 13:19 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IgKQQ-0000o1-NB; Fri, 12 Oct 2007 09:19:34 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IgKQO-0000kd-Kt for sip-confirm+ok@megatron.ietf.org; Fri, 12 Oct 2007 09:19:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IgKQO-0000aJ-2H for sip@ietf.org; Fri, 12 Oct 2007 09:19:32 -0400
Received: from wr-out-0506.google.com ([64.233.184.231]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IgKQG-0003oM-Bb for sip@ietf.org; Fri, 12 Oct 2007 09:19:29 -0400
Received: by wr-out-0506.google.com with SMTP id 70so493878wra for <sip@ietf.org>; Fri, 12 Oct 2007 06:19:01 -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=L6z/vkyBizNyP2iy6g0yKS5S0R+EUhTRuSkmRIbL3wY=; b=n4vVzkMfSPeavRPp8HZPtNAGh+QBeRygvUGQNuZPswVINITOFDQxR/a9ZAFWVROlsDsW2o78vPBqcRT3iCbUM1+8txL6KJREQjpVnIAyu0YYdVbNjrBnY1UEho5puMMiFSRyim1UcslspaKOEuQOM91K2lmCPmUUUhmRxuDAqH0=
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=DNS0mB8jLO/eFfgr40u70/oTf3koREZd5rEX8mXacXPikyCI5ruwnFFF2jTvycBrRisGBHY53/4LWFBM9QU4/d37rq1gMqxY2ql1mKCjW8Ts5VgQ0yf1OpadaKJhGSAaqBqiwflio41ZPeVDqmY6mt7Z+UY073KGqEh+HM48aoQ=
Received: by 10.142.73.8 with SMTP id v8mr929251wfa.1192195140673; Fri, 12 Oct 2007 06:19:00 -0700 (PDT)
Received: by 10.70.117.20 with HTTP; Fri, 12 Oct 2007 06:19:00 -0700 (PDT)
Message-ID: <18a603a60710120619h7dba8cabsa49986efa1484664@mail.gmail.com>
Date: Fri, 12 Oct 2007 15:19:00 +0200
From: Pars Mutaf <pars.mutaf@gmail.com>
To: sip@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Subject: [Sip] SIP trapezoid (was Re: IETF solution for pairing cellular hosts)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0955155717=="
Errors-To: sip-bounces@ietf.org

Hello,

Is the SIP trapezoid needed in cellular networks?
This is a deployment question. The very simple logic
of my question is as follows:

For privacy reasons:
- cellular users don't publish their SIP URIs in a
  phonebook.
- unpredictable and long SIP URIs are recommended.

Thus the SIP URI will be:

       n-random-characters@domainname

which may be too long to read/type as we do
today when two cell phone users meet each other?

If so:
Any solution is welcome (e.g. pairing) to help
users exchange their SIP URIs easily. For example,
user names are locally published, I choose the name
of my friend in a wireless network, and get the SIP URI.

If such solution exists:
Why not use it also for exchanging a Mobile IPv6
home address. I.e., I get my friend's SIP URI and
home address concurrently. [bonus result: we can
establish IPsec since we already know our IP addresses].

Conclusion:
By the basic SIP privacy requirement we also came to
solving the routing problem.

What I am missing?

Thanks,
pars
_______________________________________________
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