Re: [Sip] WGLC for auth-id body
Robert Sparks <rsparks@dynamicsoft.com> Mon, 09 June 2003 19:44 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 PAA18948 for <sip-archive@odin.ietf.org>; Mon, 9 Jun 2003 15:44:33 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h59Ji5b31188 for sip-archive@odin.ietf.org; Mon, 9 Jun 2003 15:44:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59JhQB31120; Mon, 9 Jun 2003 15:43:26 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59JfZB31057 for <sip@optimus.ietf.org>; Mon, 9 Jun 2003 15:41:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18838 for <sip@ietf.org>; Mon, 9 Jun 2003 15:41:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PSUO-0006WY-00 for sip@ietf.org; Mon, 09 Jun 2003 15:39:32 -0400
Received: from [63.110.3.64] (helo=dyn-tx-arch-crash.dfw.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19PSUN-0006WI-00 for sip@ietf.org; Mon, 09 Jun 2003 15:39:31 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id h59JeZ614524; Mon, 9 Jun 2003 14:40:35 -0500
Subject: Re: [Sip] WGLC for auth-id body
From: Robert Sparks <rsparks@dynamicsoft.com>
To: Rohan Mahy <rohan@cisco.com>
Cc: sip@ietf.org, 'Dean Willis' <dean.willis@softarmor.com>, Gonzalo.Camarillo@ericsson.com, Jon Peterson <jon.peterson@neustar.biz>
In-Reply-To: <9131FA75-85A4-11D7-8E16-0003938AF740@cisco.com>
References: <9131FA75-85A4-11D7-8E16-0003938AF740@cisco.com>
Content-Type: text/plain
Message-Id: <1055187632.936.121.camel@RjS.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4
Date: Mon, 09 Jun 2003 14:40:33 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit
I've reviewed this document (with revision of referredby particularly in mind) and have the following minor comments: - It would help section 4 to more explicitly note that it is discussing using AIBs to do something beyond(besides?) providing integrity protection/authentication for the request it appears in. It would also help to capture that the presence of these other things don't preclude the section 2 use of an AIB. Perhaps this text at end of the first paragraph of section 4: Such information might be carried in one or more supplemental AIBs. The presence of these supplemental AIBs does not preclude the use of AIB as specified in this document to protect the message in which they appear. - Instead of a special case of INVITE (see the heading of section 4), I think this simply a different use of an AIB. This document constrains the use of AIBs for providing integrity protection of messages and authenticating their sender regardless of method type. Section 4 is trying to note that other AIBs might appear that do something different. Perhaps this section could be titled "Potential additional uses of AIBs"? - Section 10 (Security Considerations): The first sentence needs to be scoped to the section 2 use of AIBs, not all uses of AIBs with message/sipfrag in them. - Spelling Nits: * Second sentence, last paragraph Page 4: s/SHOULD be added it to/SHOULD be added to/ * Second sentence, last paragraph, section 4, Page 6: s/harder to correlated an AIB/harder to correlate an AIB/ Other than that, I believe this document is ready to go. RjS On Tue, 2003-05-13 at 19:39, Rohan Mahy wrote: > Hello Everyone, > > I would like to begin Working Group Last Call on > > http://www.ietf.org/internet-drafts/draft-ietf-sip-authid-body-01.txt > > WGLC will end on Friday, June 13, 2003. > > thanks, > -rohan > > _______________________________________________ > 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
- [Sip] WGLC for auth-id body Rohan Mahy
- Re: [Sip] WGLC for auth-id body Cullen Jennings
- Re: [Sip] WGLC for auth-id body Robert Sparks
- RE: [Sip] WGLC for auth-id body Peterson, Jon
- RE: [Sip] WGLC for auth-id body Mary Barnes
- RE: [Sip] WGLC for auth-id body Peterson, Jon