[Sip] Updated acr-code specification

Jonathan Rosenberg <jdrosen@cisco.com> Wed, 04 October 2006 05:16 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUz7Y-00017p-Ew; Wed, 04 Oct 2006 01:16:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUz7X-00017k-D5 for sip@ietf.org; Wed, 04 Oct 2006 01:16:39 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUz7V-0006CZ-1r for sip@ietf.org; Wed, 04 Oct 2006 01:16:39 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 03 Oct 2006 22:16:37 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k945GahW002238 for <sip@ietf.org>; Tue, 3 Oct 2006 22:16:36 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k945GaYp024668 for <sip@ietf.org>; Tue, 3 Oct 2006 22:16:36 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Oct 2006 22:16:36 -0700
Received: from [10.32.241.149] ([10.32.241.149]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Oct 2006 22:16:35 -0700
Message-ID: <452343B3.1040900@cisco.com>
Date: Wed, 04 Oct 2006 01:16:35 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Oct 2006 05:16:36.0020 (UTC) FILETIME=[436EDF40:01C6E774]
DKIM-Signature: a=rsa-sha1; q=dns; l=2099; t=1159938996; x=1160802996; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:Updated=20acr-code=20specification; X=v=3Dcisco.com=3B=20h=3DU/E2FM5nbxWCxV/yzSOve3eAFqY=3D; b=lYOuTXDjcWWwLtEtAZInAVwIm8O7Ms3nd27mOYTArC5uVWusLUHM6D7RGMn36mogiafoY02d ViyNob1l816NMugXsoPkMF2Kx6Wxh2b4tD7v8CIuMwQJV7EVz0XZHg2l;
Authentication-Results: sj-dkim-1.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Subject: [Sip] Updated acr-code specification
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>
Errors-To: sip-bounces@ietf.org

I've submitted an update to acr-code based on comments received during 
WGLC. Until the draft appaers in the archives, you can pick up a copy here:

http://www.jdrosen.net/papers/draft-ietf-sip-acr-code-03.txt

Here are the diffs:

* if a UAC gets a 433, it MUST NOT retry without anonymity unless user
   has given permission (used to be SHOULD NOT)

* added this text to the server behavior section:

<t>
In addition, requests where the identity of the requestor cannot be 
determined
or validated, but it is not a consequence of an explicit action on the
part of the requestor, are not consider anonymous. For example, if a
request contains a non-anonymous From header field, along with the
Identity and Identity-Info header fields <xref target="RFC4474"/>, but
the certificate could not be obtained from the reference in the
Identity-Info header field, it is not considered an anonymous request,
and the 433 response code SHOULD NOT be used.
</t>


* removed mention of 'header' and 'session' privacy as being
   anonymous, since there was rough consensus that this needed to be
   clarified elsewhere.

* clarified the impact of 433 when received in a mid-dialog response -
   no termiantion of the dialog or usages on the dialog.

* softened wording that seemed to imply only a proxy/UAS in the
   terminating side could use 433.

* added SHOULD strengths to criteria for definining anonymity and
   SHOULD NOT for the case where p-a-id is absent and nothing else in
   the request says its anonymous

* clarified that requests are still anonymous if a validated Identity
   is there and the From indicates anonymous

* changed reference from rosenberg-identity-privacy to
   rosenberg-id-coexistence


Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
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