RE: [Sip] (no subject)

"Peterson, Jon" <jon.peterson@neustar.biz> Fri, 01 November 2002 17:16 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23324 for <sip-archive@odin.ietf.org>; Fri, 1 Nov 2002 12:16:47 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA1HIjB00661 for sip-archive@odin.ietf.org; Fri, 1 Nov 2002 12:18:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1HHEv00455; Fri, 1 Nov 2002 12:17:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1HGrv00437 for <sip@optimus.ietf.org>; Fri, 1 Nov 2002 12:16:53 -0500
Received: from oak.neustar.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23235 for <sip@ietf.org>; Fri, 1 Nov 2002 12:14:24 -0500 (EST)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id gA1HGnb16628; Fri, 1 Nov 2002 17:16:49 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19) id <VLY1KV5W>; Fri, 1 Nov 2002 12:17:27 -0500
Message-ID: <15A2739B7DAA624D8091C65981D7DA815EB358@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: 'Janne Kario' <jkario78@hotmail.com>, sip@ietf.org
Subject: RE: [Sip] (no subject)
Date: Fri, 01 Nov 2002 12:17:25 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA1HGrv00438
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
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-Transfer-Encoding: 8bit

Yes, they have overlapping functions, but their implementation strategies
reflect two different sets of requirements for identity management in SIP.
The asserted-identity-02 assumes a 'walled-garden' hop-by-hop network of
trusted proxy servers (see the sipping-nai-reqs-02 document for more
details). draft-ietf-sip-identity-00 (which has superseded the
'draft-peterson' document below) attempts to find an end-to-end
cryptographic identity solution. For various reasons, the 'walled garden'
approach to identity was not considered suitable for widespread Internet
deployment; hence its reliance on P- headers and so on.

In fact, there is now some text at the beginning of sip-identity-00 that
briefly discusses the differences between its approach and the approach in
asserted-identity-02.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Janne Kario [mailto:jkario78@hotmail.com]
> Sent: Thursday, October 31, 2002 1:25 PM
> To: sip@ietf.org
> Subject: [Sip] (no subject)
> 
> 
> A quick question. What is the relation between
> 
> draft-ietf-sip-asserted-identity-02
> 
> and
> 
> draft-peterson-sip-identity-01
> 
> It seems to me that they have some overlapping functions.
> 
> _________________________________________________________________
> Surf the Web without missing calls! Get MSN Broadband.  
> http://resourcecenter.msn.com/access/plans/freeactivation.asp
> 
> _______________________________________________
> 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
> 
_______________________________________________
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