RE: [Sip] WGLC for auth-id body
"Peterson, Jon" <jon.peterson@neustar.biz> Fri, 13 June 2003 15:48 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 LAA10276 for <sip-archive@odin.ietf.org>; Fri, 13 Jun 2003 11:48:20 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DFlqF22681 for sip-archive@odin.ietf.org; Fri, 13 Jun 2003 11:47:52 -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 h5D745a11814; Fri, 13 Jun 2003 03:04:05 -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 h5D73fm11795 for <sip@optimus.ietf.org>; Fri, 13 Jun 2003 03:03:41 -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 DAA23460 for <sip@ietf.org>; Fri, 13 Jun 2003 03:03:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QiZ1-0002CH-00 for sip@ietf.org; Fri, 13 Jun 2003 03:01:31 -0400
Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx with esmtp (Exim 4.12) id 19QiZ0-0002CD-00 for sip@ietf.org; Fri, 13 Jun 2003 03:01:30 -0400
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11]) by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h5D72rC25510; Fri, 13 Jun 2003 07:02:53 GMT
Received: by stntimc1.va.neustar.com with Internet Mail Service (5.5.2653.19) id <ZH2KJFCW>; Fri, 13 Jun 2003 03:03:18 -0400
Message-ID: <0449D80A0E9B614A83FA9031B07E8D3B257B2B@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: 'Robert Sparks' <rsparks@dynamicsoft.com>, Rohan Mahy <rohan@cisco.com>
Cc: sip@ietf.org, 'Dean Willis' <dean.willis@softarmor.com>, Gonzalo.Camarillo@ericsson.com
Subject: RE: [Sip] WGLC for auth-id body
Date: Fri, 13 Jun 2003 03:03:16 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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>
Thanks for these comments. A few notes below. Jon Peterson NeuStar, Inc. [snip] > 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. > Yes, I do think it is important to capture the idea that there may be multiple AIBs in a SIP message that identify different parties. The text given above looks good to me. > - 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"? > Well, although REFER-instigated INVITEs might not be a special case as such, most would probably say that 3PCC is a special case. But still, we need a section title that accommodates both, so I think that's fair; a better title for this section is probably in order. I think we need something with the sense "Use of AIBs to express the identity of someone other than the sender of the INVITE". I'll try to figure out a way to compress that to header-size. > - 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. > Okay, fine. > - 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/ > Thanks, I'll take care of all of those. > 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