[Sip] Re: Comments on draft-ietf-sip-acr-code-02
Jonathan Rosenberg <jdrosen@cisco.com> Wed, 04 October 2006 03:08 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUx7T-00083o-2c; Tue, 03 Oct 2006 23:08:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUx7I-0007l2-1D for sip@ietf.org; Tue, 03 Oct 2006 23:08:16 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUwxw-0002fH-0q for sip@ietf.org; Tue, 03 Oct 2006 22:58:37 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 03 Oct 2006 19:58:35 -0700
X-IronPort-AV: i="4.09,252,1157353200"; d="scan'208"; a="344486251:sNHT55170986"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k942wZM0020611; Tue, 3 Oct 2006 19:58:35 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k942wWJr014606; Tue, 3 Oct 2006 19:58:35 -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 19:58:33 -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 19:58:32 -0700
Message-ID: <45232357.3030100@cisco.com>
Date: Tue, 03 Oct 2006 22:58:31 -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: "Drage, Keith (Keith)" <drage@lucent.com>
References: <5D1A7985295922448D5550C94DE291804684A3@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE291804684A3@DEEXC1U01.de.lucent.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Oct 2006 02:58:32.0828 (UTC) FILETIME=[FA4413C0:01C6E760]
DKIM-Signature: a=rsa-sha1; q=dns; l=3094; t=1159930715; x=1160794715; c=relaxed/simple; s=sjdkim3002; 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=20Comments=20on=20draft-ietf-sip-acr-code-02; X=v=3Dcisco.com=3B=20h=3D13Q7L30VWi+VDCFkBTMfN8XWc50=3D; b=k7MvktUZ+ylwBikPHv69VKUZqkQFbYMg02p3dMw6mXtm3JiQMGMOQ+o4g7Kb8qj7CCNnfmuZ My884fRcmCSs1uxh9NaVpRG4SFmSh+v2hszE9EY0sqeEyCkLL18UeDT/;
Authentication-Results: sj-dkim-3.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: sip@ietf.org
Subject: [Sip] Re: Comments on draft-ietf-sip-acr-code-02
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
Drage, Keith (Keith) wrote: > I have reviewed the entire draft. > > 1) In section 3, I wondered if it would be appropriate to have a > couple more key statements of when it does not apply. > > For example, if we are using RFC 4474, and the recipient of the SIP > request has received the identity but has been unable to obtain the > certificate for the identity, then the proposed 433 response code is > inappropriate, and indeed RFC 4474 specifies response codes for this > situation, which should always be used in preference. OK. I added this: <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> > > 2) Section 3. > > o The request contained a Privacy header field whose value was 'id' > [3] or 'user'. This explicitly excludes the 'header' and > 'session' privacy services, since those do not directly convey the > identity of the requestor. > > I have noted the ongoing discussion on this, and certainly my > interpretation was that the "header" value in the Privacy header could > cover the P-Asserted-Identity header. However I think we should avoid > that this draft attempts to fix unclear specification in RFC 3323 and > (and possibly RFC 3325). I would therefore suggest that we strike the > offending words. Fine. In the interests of forward progress I will strike the offending sentence. > > 3) Section 4. > > This section seems to be the one that should talk about dialog usage. > While identities are usefully provided in the initial transaction in a > dialog, there is nothing that prevents them being exchanged in later > transactions, and indeed for the support of some services it is > necessary, as the identity will have changed. > > The document should indicate the effect of receiving a 433 response to a > request sent within an existing dialog, where the implementation does > support this extension, which I assume should be the defauly 4xx > response treatment. I've added the following: <t> Receipt of a 433 response to a mid-dialog request SHOULD NOT cause the dialog to terminate, and SHOULD NOT cause the specific usage of that dialog to terminate <xref target="I-D.ietf-sipping-dialogusage"/>. </t> 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
- [Sip] Comments on draft-ietf-sip-acr-code-02 Drage, Keith (Keith)
- AW: [Sip] Comments on draft-ietf-sip-acr-code-02 Jesske, R
- RE: [Sip] Comments on draft-ietf-sip-acr-code-02 Drage, Keith (Keith)
- [Sip] Re: Comments on draft-ietf-sip-acr-code-02 Jonathan Rosenberg
- [Sip] RE: Comments on draft-ietf-sip-acr-code-02 Drage, Keith (Keith)