Secdir review of draft-ietf-iptel-tel-reg-05

"Glen Zorn" <gzorn@arubanetworks.com> Mon, 05 May 2008 00:29 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 966993A6F77; Sun, 4 May 2008 17:29:55 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A4973A6F8A; Sun, 4 May 2008 17:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 tvJbIKEIap8g; Sun, 4 May 2008 17:29:50 -0700 (PDT)
Received: from mail.arubanetworks.com (mail.arubanetworks.com [216.31.249.253]) by core3.amsl.com (Postfix) with SMTP id 07CAC3A6FAC; Sun, 4 May 2008 17:28:00 -0700 (PDT)
Received: from aruba-mx1.arubanetworks.com ([10.1.1.17]) by mail.arubanetworks.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 4 May 2008 17:28:00 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Secdir review of draft-ietf-iptel-tel-reg-05
Date: Sun, 04 May 2008 17:27:57 -0700
Message-ID: <A3DA4C2546E1614D8ACC896746CDCF29012D90BA@aruba-mx1.arubanetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Secdir review of draft-ietf-iptel-tel-reg-05
Thread-Index: AciuRt3HMHhMR01jTfCL05P3LdXeLA==
From: Glen Zorn <gzorn@arubanetworks.com>
To: fluffy@cisco.com, vkg@alcatel-lucent.com, iptel-chairs@tools.ietf.org, jon.peterson@neustar.biz, iesg@ietf.org
X-OriginalArrivalTime: 05 May 2008 00:28:00.0517 (UTC) FILETIME=[DFC40B50:01C8AE46]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the IESG.
These comments were written primarily for the benefit of the security
area directors.  Document editors and WG chairs should treat these
comments just like any other last call comments.  

I found no security problems with this draft.  A couple of nits: section
4.1, paragraph 1 says "New tel URI parameters and new values for
existing tel URI parameters MUST be registered by IANA" but I think it
should be "New tel URI parameters and new values for existing tel URI
parameters MUST be registered with IANA"; section 5, last sentence says
"The supporting RFC publications for parameter registrations described
this specification MUST provide detailed security considerations for
them." but it seems like there is at least one word missing after
"described" -- maybe "described in"? 

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf