IETF Logo Mail Archive

Re: [dnsext] WGLC: RFC6195bis IANA guidance

Donald Eastlake <d3e3e3@gmail.com> Fri, 22 June 2012 18:11 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47AE011E8080 for <dnsext@ietfa.amsl.com>; Fri, 22 Jun 2012 11:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.521
X-Spam-Level:
X-Spam-Status: No, score=-103.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSPmB8YfMD2O for <dnsext@ietfa.amsl.com>; Fri, 22 Jun 2012 11:11:18 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0FEF021F871C for <dnsext@ietf.org>; Fri, 22 Jun 2012 11:11:18 -0700 (PDT)
Received: by yenq13 with SMTP id q13so1953192yen.31 for <dnsext@ietf.org>; Fri, 22 Jun 2012 11:11:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=vDyNAKSQlpZhJ6X+XEGdloJbI8Y7TH1aoLWS8SMwBWI=; b=WERs1DpkuIs0AKknaXVm1oUDvD2x18Q6Q+GbpG+HPhIy8x4DKUbBu8VQ8xBH7pBxC6 e/yOIwp39iYsN8jWX2n0XnDnOQqYCvqQviUeUjMctrOhPe9PbLB20YII3VA39ccORb1g b/CDLWl2WDHf8eHGXWbHlF1O/eo/QvQjCKKJ5U2wf4WkqgAMJebKYY9I4Mpi7xPNiTD6 8kyiGaZ7lLKQd5KVcdvKutCfjzNOyhhW3sUHqbyxoeQcFdOnrkxum9oOFzJYMPGJyTGb ooNGAS1Rr4I11FiJF5Y5rbUdez/wR2UWbykKyZUXtFbrek9i+35DKI9pdKQ6JpytPHDA Ux1w==
Received: by 10.50.212.98 with SMTP id nj2mr2622286igc.35.1340388677446; Fri, 22 Jun 2012 11:11:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Fri, 22 Jun 2012 11:10:57 -0700 (PDT)
In-Reply-To: <CAKW6Ri5=c9N+wo_EUn7WrvzNZFVJkpfHcv0OKx8OBJ9ZLzJdGw@mail.gmail.com>
References: <4FD62E4E.4020007@ogud.com> <CAKW6Ri5=c9N+wo_EUn7WrvzNZFVJkpfHcv0OKx8OBJ9ZLzJdGw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 22 Jun 2012 14:10:57 -0400
Message-ID: <CAF4+nEEqn-S6+8oTvmjeF6eKq+hmiov+AG+S3O41Nq12eUxDCw@mail.gmail.com>
To: Dick Franks <rwfranks@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: dnsext@ietf.org, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [dnsext] WGLC: RFC6195bis IANA guidance
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jun 2012 18:11:22 -0000

Hi Dick,

On Tue, Jun 19, 2012 at 11:33 AM, Dick Franks <rwfranks@acm.org> wrote:
> Olafur,
>
> I have reviewed draft-ietf-dnsext-rfc6195bis-02 and offer the
> following observations:
>
>
> [3.1 paragraph 4]
> and [3.2 paragraph 4]
>
> Regexes:
>
>                         [A-Z][A-Z0-9\-]*[A-Z0-9]
>
>                        (TYPE|CLASS)(0|[1-9][0-9]*)
>
> could be simplified to:
>
>                         [A-Z][A-Z0-9]*
>
>                        (TYPE|CLASS)[0-9]*

That's not simplification, that's change.

> Previous RFC authors have abstained from using the hyphen when
> specifying RRTYPE and CLASS mnemonics. Regex 1 should constrain future
> authors and IANA to follow established custom and practice. The only
> historical exception (NSAP-PTR) lived quietly in RFC1348 and became
> obsolete in 1994.

I believe that internal hyphens should be allowed within RRTPE and
CLASS mnemonics. We do not know what future mnemonics or sets of
mnemonics will be required. Better to remain more flexible here.

> Regex 2, as written, fails to match unknown type and class identifiers
> having leading zeroes in the numeric part, which is not explicitly
> disallowed by RFC3597.  IMHO the mnemonics CLASS and TYPE (no digits)
> should also be disallowed to avoid accidental ingestion of
> place-holders if/when any part of this process becomes automated.

I have no problem with making the Regex 2 exclusion slightly stronger
so going with your changed Regex 2 is fine with me.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Dick
>
>
>
>
>
> On 11 June 2012 18:43, Olafur Gudmundsson <ogud@ogud.com> wrote:
>>
>>
>>
>> Dear colleagues
>>
>>
>>
>> This message starts a 2 week WGLC for RFC6195bis ending at midnight UTZ June 28'th 2012.
>>
>> http://tools.ietf.org/html/draft-ietf-dnsext-rfc6195bis-02
>>
>>
>>
>> This document addresses known flaws in the RFC6195 (see appendix A).
>>
>>
>>
>> Please review the document and post a note that you have reviewed the document we need a minimum of 5 reviewers.
>>
>>
>>
>>     Olafur & Andrew
>>
>> _______________________________________________
>>
>> dnsext mailing list
>>
>> dnsext@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/dnsext
>>

v2.23.0 | Report a Bug | By Email