Re: [sipcore] Comments on draft-ietf-sipcore-sec-flows-05
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 19 November 2010 12:08 UTC
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E97D63A6830 for <sipcore@core3.amsl.com>; Fri, 19 Nov 2010 04:08:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWMhriEm4X9M for <sipcore@core3.amsl.com>; Fri, 19 Nov 2010 04:08:27 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id E79A23A686B for <sipcore@ietf.org>; Fri, 19 Nov 2010 04:08:25 -0800 (PST)
X-AuditID: c1b4fb39-b7cabae000005002-b5-4ce668eac45f
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 01.B4.20482.AE866EC4; Fri, 19 Nov 2010 13:09:14 +0100 (CET)
Received: from [131.160.37.44] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.2.234.1; Fri, 19 Nov 2010 13:09:13 +0100
Message-ID: <4CE668E9.80603@ericsson.com>
Date: Fri, 19 Nov 2010 14:09:13 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Brian Hibbard <brian@estacado.net>
References: <4CE3EE96.7080902@ericsson.com> <D7F5FDAA-9B06-4F51-A9EA-D2466C943AED@estacado.net>
In-Reply-To: <D7F5FDAA-9B06-4F51-A9EA-D2466C943AED@estacado.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: SIPCORE <sipcore@ietf.org>, SIPCORE Chairs <sipcore-chairs@tools.ietf.org>
Subject: Re: [sipcore] Comments on draft-ietf-sipcore-sec-flows-05
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2010 12:08:30 -0000
Hi Brian, thanks for your quick response. I have just requested the IETF LC for this draft. Cheers, Gonzalo On 18/11/2010 6:47 PM, Brian Hibbard wrote: > Gonzalo, > > > Thank you for your review. I made these revisions to the newly submitted version draft-ietf-sipcore-sec-flows-06 to address the points you made: > > References are now generated with symrefs="yes", sortrefs="yes", subcompact="no". > > References to ASN.1 (ITU X.683) and ITU X.509 are added. > > Acronyms expanded on first use: EKU, UA, and CPIM. > > "Section" was capitalized in each case when used in a reference. > > A pointer to Section 26.2.1 of RFC 3261 was added for text on page 28, "Some SIP clients incorrectly only do SSLv3 and do not support TLS." > > A pointer to Section 4.1.2.5 of RFC 5280 was added for text on page 28, "Many SIP clients were found to accept expired certificates with no warning or error." > > Reference to Section 3.2 of RFC 5621 for text on page 28, "Some implementations used binary encodings…" > > Thanks, > Brian > > On Nov 17, 2010, at 9:02 AM, Gonzalo Camarillo wrote: > >> Hi, >> >> a few days ago, I received a publication request for the following draft: >> >> http://www.ietf.org/id/draft-ietf-sipcore-sec-flows-05.txt >> >> Please, find below a few minor comments on the draft. >> >> Cheers, >> >> Gonzalo >> >> >> References use the following convention (RFC 5246 [12]). The current >> recommendation is to use [RFC5246] instead. Something like this should >> work in xml2rfc: >> >> <?rfc symrefs="yes"?> >> >> Once you are at it, you may want to also add the following: >> >> <?rfc sortrefs="yes" ?> >> <?rfc subcompact="no" ?> >> >> Add a reference for ASN.1 and X.509 >> >> Expand acronyms on their first use (e.g., UA and EKU). >> >> Page 28. The word "Section" needs to be capitalized when referring to >> particular sections (e.g., Section 6 of RFC 5280). >> >> Page 28. Some paragraphs contain pointers to the relevant normative >> behavior as defined in other RFCs. However, some paragraphs do not >> have those pointers. For example: >> >> Some SIP clients incorrectly only do SSLv3 and do not support TLS. >> >> Many SIP clients were found to accept expired certificates with no >> warning or error. >> >> >> In the next paragraph, add a reference to Section 3.2 of RFC 5621: >> >> Some implementations used binary MIME encodings while others used >> base64. It is advisable that implementations send only binary and >> are prepared to receive either. >> >> >> >> >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore >
- [sipcore] Comments on draft-ietf-sipcore-sec-flow… Gonzalo Camarillo
- Re: [sipcore] Comments on draft-ietf-sipcore-sec-… Brian Hibbard
- Re: [sipcore] Comments on draft-ietf-sipcore-sec-… Gonzalo Camarillo