Re: [secdir] secdir review of draft-ietf-idnabis-rationale-13.txt

Elisabeth Blanconil <eblanconil@gmail.com> Tue, 06 October 2009 15:58 UTC

Return-Path: <eblanconil@gmail.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 5F71928C0D8; Tue, 6 Oct 2009 08:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599]
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 AxI81OWWCQB5; Tue, 6 Oct 2009 08:58:18 -0700 (PDT)
Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228]) by core3.amsl.com (Postfix) with ESMTP id F039728C1DB; Tue, 6 Oct 2009 08:58:17 -0700 (PDT)
Received: by fxm28 with SMTP id 28so3583254fxm.42 for <multiple recipients>; Tue, 06 Oct 2009 08:59:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9T843maL0xDj7CndgiWOYP3jQ+sR9wWPov/n5iR7zYA=; b=kkG/dgV1d6vpmkkr+8PRvT3xYiueodvQUsmIwbO+gpK2iXKjM/fnUzOdSXxUZ64cPm HQaOkFQKNYwnQYu15KKmoswB1W91Ce4nBjghQ5d6X6QXGGm9bIclz1G2bfoZ3f/ZiLmY rgOIU0NipM2KgB8YhWGVm5IgbBf/sh1X7+0Vk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=otjrKBIXeyiZ9F4qOZu8olvQposeYIg6OHHuuUWSUGuoK80z7ZP7cjjB18sAon0zMn rr7p72VMRefOAKH3OSNyczmlUF9pf9durzb21sBqcm1CbMmoeAe6MaPBOnTl5tFDLBEO nyQKLEipbD6OTZLGmy1gYKYPu+17Z4DGLPNIk=
MIME-Version: 1.0
Received: by 10.86.154.32 with SMTP id b32mr688078fge.10.1254844791016; Tue, 06 Oct 2009 08:59:51 -0700 (PDT)
In-Reply-To: <20091006150621.GO27462@shinkuro.com>
References: <D80EDFF2AD83E648BD1164257B9B091208282265@TK5EX14MBXC115.redmond.corp.microsoft.com> <p06240883c6f00ff718bf@10.20.30.163> <D80EDFF2AD83E648BD1164257B9B091208283635@TK5EX14MBXC115.redmond.corp.microsoft.com> <17823AE7FE62B8814BE101BF@PST.JCK.COM> <D80EDFF2AD83E648BD1164257B9B0912082837C2@TK5EX14MBXC115.redmond.corp.microsoft.com> <2FA54714-6D7F-46E3-A2CA-BC9D44CBC29B@google.com> <tslfx9w39h5.fsf@mit.edu> <ECDB2A03D7332EDEB520D80F@PST.JCK.COM> <20091006150621.GO27462@shinkuro.com>
Date: Tue, 06 Oct 2009 17:59:50 +0200
Message-ID: <6589127a0910060859u2da6723k2c00f00ecd1d3722@mail.gmail.com>
From: Elisabeth Blanconil <eblanconil@gmail.com>
To: Andrew Sullivan <ajs@shinkuro.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 06 Oct 2009 11:08:22 -0700
Cc: secdir@ietf.org, Vint Cerf <vint@google.com>, John C Klensin <klensin@jck.com>, iesg@ietf.org, Paul Hoffman <phoffman@imc.org>, idna-update@alvestrand.no, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [secdir] secdir review of draft-ietf-idnabis-rationale-13.txt
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: Tue, 06 Oct 2009 15:58:19 -0000

Full agreement.

Or would we have to update IDNA each time the DNS has an extra
feature? Just to repeat that IDNA respects the DNS? That was it not
supposed to be a multilayer model?

Elisabeth Blanconil



2009/10/6 Andrew Sullivan <ajs@shinkuro.com>:
> On Tue, Oct 06, 2009 at 10:44:56AM -0400, John C Klensin wrote:
>
>> said about this.   If there is consensus that "say nothing" (or
>> "no reference") is an acceptable alternative, I would recommend
>> that we simply remove that entire subsection rather than trying
>> to fine-tune it.
>
> I can support that.
>
>> When the initial form of that paragraph was written a year or
>> two ago, it seemed worthwhile to warn about that situation.
>> However, at this point, maybe it isn't worthwhile enough to
>> justify the effort to fine-tune this section.    In an ideal
>> world, the warning probably belongs in the DNSSEC specs, rather
>> than here, anyway.
>
> Strictly, it's not a protocol issue, but an operations issue, and
> therefore ought probably to be operational advice (likely to be
> reviewed in DNSOP).  I cannot believe I am getting up in public and
> saying this, but if people really need that advice to be written down
> somewhere I am willing to write an I-D to say it.  Especially if that
> clears the issues with the current IDNA drafts.
>
> A
>
> --
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Idna-update mailing list
> Idna-update@alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update
>