Re: [secdir] secdir review of draft-ietf-idnabis-tables-07

Vint Cerf <vint@google.com> Sat, 17 October 2009 16:01 UTC

Return-Path: <vint@google.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B44D13A6938; Sat, 17 Oct 2009 09:01:07 -0700 (PDT)
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 N5mnkQYq5MsK; Sat, 17 Oct 2009 09:01:07 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.45.13]) by core3.amsl.com (Postfix) with ESMTP id 91DA13A6859; Sat, 17 Oct 2009 09:01:05 -0700 (PDT)
Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97]) by smtp-out.google.com with ESMTP id n9HG19SK029158; Sat, 17 Oct 2009 09:01:10 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1255795270; bh=dj3hrElotREcarE1j7Nqd7uvmE4=; h=DomainKey-Signature:Cc:Message-Id:From:To:In-Reply-To: Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date: References:X-Mailer:X-System-Of-Record; b=bwe+jWQH80kyH48dLA4AOMJm Ihgja7llf6BytPJDeAN6vX0kr5HDcyNPC7p9WR+yP0RPrv0b9vyqQQ1kHhHJfQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=cc:message-id:from:to:in-reply-to:content-type: content-transfer-encoding:mime-version:subject:date:references:x-mailer:x-system-of-record; b=J8rER469yiQ2S09V1ZJPE++/bIEc02Ix7TAv0zU6d8dJlqMkpurgtSsWKMgt6Ud6B LMTpgQ0RLM+8Qow4qI48w==
Received: from qyk9 (qyk9.prod.google.com [10.241.83.137]) by wpaz33.hot.corp.google.com with ESMTP id n9HG16vo016967; Sat, 17 Oct 2009 09:01:07 -0700
Received: by qyk9 with SMTP id 9so2047400qyk.30 for <multiple recipients>; Sat, 17 Oct 2009 09:01:06 -0700 (PDT)
Received: by 10.224.123.154 with SMTP id p26mr1711760qar.218.1255795266603; Sat, 17 Oct 2009 09:01:06 -0700 (PDT)
Received: from vint-macbookpro.home (static-72-66-6-47.washdc.fios.verizon.net [72.66.6.47]) by mx.google.com with ESMTPS id 23sm1903466qyk.7.2009.10.17.09.01.04 (version=SSLv3 cipher=RC4-MD5); Sat, 17 Oct 2009 09:01:05 -0700 (PDT)
Message-Id: <4C70B55D-9260-429A-9B2D-CE355C282BF4@google.com>
From: Vint Cerf <vint@google.com>
To: "Scott G. Kelly" <scott@hyperthought.com>
In-Reply-To: <4AD9BF2E.8010606@hyperthought.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 17 Oct 2009 12:01:03 -0400
References: <4AD9BF2E.8010606@hyperthought.com>
X-Mailer: Apple Mail (2.936)
X-System-Of-Record: true
Cc: idnabis-chairs@tools.ietf.org, paf@cisco.com, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] secdir review of draft-ietf-idnabis-tables-07
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2009 16:01:07 -0000

scott, good point - we will attend to this editorial suggestion.

v

On Oct 17, 2009, at 8:57 AM, Scott G. Kelly wrote:

> 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.
>
> The document specifies rules for deciding whether a code point  
> should be
> included in an Internationalized Domain Name. It's a member of a
> 4-document group, and as Paul pointed out in a related review,  
> should be
> considered as such.
>
> The security considerations section consists of one sentence:
>
> "The security issues associated with this work are discussed in
> [IDNA2008-protocol]."
>
> Following that link to the protocol document's security considerations
> section:
>
> "Security Considerations for this version of IDNA, except for the
> special issues associated with right to left and characters, are
> described in [IDNA2008-Defs].  Specific issues for labels containing
> characters associated with scripts written right to left appear in
> [IDNA2008-BIDI]."
>
> The security considerations in those two documents (especially the
> protocol document) do seem to cover the issues, although like Sam, I
> don't feel qualified to definitively state this, and so I think the
> security ADs should pay some attention to this collection of  
> documents.
>
> Editorially, one might consider removing the reference indirection and
> pointing the reader directly at [IDNA2008-Defs] and [IDNA2008-BIDI].
>
> --Scott