[Sip] RE: Comments on sip-identity-03

"Peterson, Jon" <jon.peterson@neustar.biz> Mon, 08 November 2004 22:24 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09958 for <sip-web-archive@ietf.org>; Mon, 8 Nov 2004 17:24:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRHwV-0007zg-Ga for sip-web-archive@ietf.org; Mon, 08 Nov 2004 17:24:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRHiY-0005S7-Iz; Mon, 08 Nov 2004 17:10:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRHVt-0002bv-DK for sip@megatron.ietf.org; Mon, 08 Nov 2004 16:57:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07365 for <sip@ietf.org>; Mon, 8 Nov 2004 16:57:22 -0500 (EST)
Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRHWU-0007Gy-Vi for sip@ietf.org; Mon, 08 Nov 2004 16:58:04 -0500
Received: from stntimc1.va.neustar.com (stntimc1.neustar.com [10.31.13.11]) by oak.neustar.com (8.12.8/8.11.0) with ESMTP id iA8Luq10006131; Mon, 8 Nov 2004 21:56:53 GMT
Received: by stntimc1.cis.neustar.com with Internet Mail Service (5.5.2657.72) id <T32LZ9QH>; Mon, 8 Nov 2004 16:56:52 -0500
Message-ID: <7927C67249E4AD43BC05B539AF0D129801AF4347@stntexch04.cis.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: 'Aki Niemi' <aki.niemi@nokia.com>, SIP WG <sip@ietf.org>
Date: Mon, 08 Nov 2004 16:56:49 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="ISO-8859-1"
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: [Sip] RE: Comments on sip-identity-03
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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

Thanks Aki. You are correct that we are not suggesting that the Digest
username match as a literal the username in the local-part of the URI in the
>From header. I mean, I guess that's possible, but certainly not necessary.
What we intend is that an authentication service might persist some mapping
between a Digest username and one or more potential local-parts which are
authorized to appear in the From header field value for that user. I will
attempt to free to language you cite below from the shackles of confusion.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Aki Niemi [mailto:aki.niemi@nokia.com]
> Sent: Monday, November 08, 2004 1:32 PM
> To: SIP WG
> Cc: jon.peterson@neustar.biz
> Subject: Comments on sip-identity-03
> 
> 
> Hi,
> 
> I read the draft and it looks reasonable. One comment though: in section 
> 6 there is a recommended policy which instructs matching the username 
> asserted in the Digest authentication to the From header field.
> 
> I think this needs clarification. Someone might read it to mean the 
> contents of the username param is being matched, which I'm assuming is 
> not the intention. Rather, it should say that the account's URI for 
> which the username/passwd is for is matched against the URI 
> in the From.
> 
> In addition, the section contains text about aliases and matching those 
> usernames, where this passage was quite hard to parse:
> 
>     Accordingly, provided
>     the authentication service is aware of the relationships between
>     these accounts, it might allow a user providing credentials for one
>     account to assert a username associated with another account
>     controlled by the user name.
> 
> I think I got the idea, but rephrasing it would be in order.
> 
> Cheers,
> Aki
> 

_______________________________________________
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