Re: [Sip] WGLC: draft-ietf-sip-acr-code

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUxPd-0003Xz-Q3; Tue, 03 Oct 2006 23:27:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUxPc-0003Xs-Dk for sip@ietf.org; Tue, 03 Oct 2006 23:27:12 -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 1GUxPb-0000ck-2X for sip@ietf.org; Tue, 03 Oct 2006 23:27:12 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 03 Oct 2006 20:27:11 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k943RAd0019546; Tue, 3 Oct 2006 20:27:10 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k943RAql007915; Tue, 3 Oct 2006 20:27:10 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Oct 2006 20:27:10 -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 20:27:09 -0700
Message-ID: <45232A0C.3050000@cisco.com>
Date: Tue, 03 Oct 2006 23:27:08 -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: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sip] WGLC: draft-ietf-sip-acr-code
References: <50B1CBA96870A34799A506B2313F266709C88371@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F266709C88371@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Oct 2006 03:27:10.0077 (UTC) FILETIME=[F9D37AD0:01C6E764]
DKIM-Signature: a=rsa-sha1; q=dns; l=2462; t=1159932430; x=1160796430; c=relaxed/simple; s=sjdkim2002; 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:Re=3A=20[Sip]=20WGLC=3A=20draft-ietf-sip-acr-code; X=v=3Dcisco.com=3B=20h=3DnxIjVrrqRrBbgPNnfPbRyBjbeJo=3D; b=br2spXwLwouJI8anovEgmU9uAlRbYzYTrifxU58W83vFnQoX4Wh2gy3HZhGhNz+U/OJqfRB1 iiwuBbpeYs1u53Tu8yyQ/F6q7nf7KnBEgqu0QgwdeMwXr4u7eSMIeKFZ;
Authentication-Results: sj-dkim-2.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: IETF SIP List <sip@ietf.org>, "Drage, Keith (Keith)" <drage@lucent.com>
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


Elwell, John wrote:

> 1. Section 1, first paragraph. Would it be beneficial to mention the
> anonymity provisions of RFC 4474, i.e., a signature that says the request
> originated at the domain indicated in the From header field but the specific
> user is not disclosed? If so, then RFC 4474 would need to be added as an
> informative reference.

I think its worth mentioning 4474 but not here; rather, its worth 
clarifying later in the document that if the From contains an indication 
of an anonymous URI within a domain, yet identity is still there and 
validated, the request is anonymous. The spec now reads:

<t>The From or  P-Asserted-Identity header field contains a URI which has an
explicit indication that it is anonymous. One such example of a
mechanism that would meet this criteria is <xref
target="I-D.rosenberg-sip-identity-privacy"/>. This criteria is true
even if the request has a validated Identity header field <xref
target="RFC4474"/>, which can be used in concert with anonymized From
header fields.
</t>



> 
> 2. Section 1, 2nd paragraph "that reason phrase is not useful for automata".
> Add "or where the caller speaks a different language". 

changed.

> 
> 3. I am not sure where it fits, but should there be mention of the HERFP
> problem, i.e. 433 being masked by some other response code at a forking
> proxy?

This is a generic problem with 4xx as we know; I don't see what usefully 
can be said here.

> 
> NITS:
> 4. Section 4, first paragraph: "if user continues" - change to "if the user
> continues".
> 
> 5. Section 4, second paragraph: "A UAC the does not understand" - change to
> "A UAC that does not understand".

> 
> 6. Section 5: "the server refused the fulfill" - change to "the server
> refused to fulfill".
> 
> 7. Section 7: "an request" - change to "a request".
> 
> 8. Section 7, second paragraph "this has the desired effect" - change to
> "anonymous call rejection has the desired effect". ("this" looks like it
> refers to the fact that telemarketeers frequently withhold their identity).

all fixed.

-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