Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 20 June 2013 16:36 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1BB721F9B5C for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 09:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level:
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
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 qCKWUeKyfYic for <ietf@ietfa.amsl.com>; Thu, 20 Jun 2013 09:36:14 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 378B121F9920 for <ietf@ietf.org>; Thu, 20 Jun 2013 09:36:14 -0700 (PDT)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 72DDC8A031 for <ietf@ietf.org>; Thu, 20 Jun 2013 16:36:13 +0000 (UTC)
Date: Thu, 20 Jun 2013 12:36:12 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
Message-ID: <20130620163611.GB41900@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51C1B235.6020507@bogus.com> <E8415CD2-AC5F-47CF-B740-65C45B181AC8@ogud.com> <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <FA4B2D6DB820F27675F8E13B@JcK-HP8200.jck.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Thu, 20 Jun 2013 16:36:27 -0000

On Thu, Jun 20, 2013 at 11:17:16AM -0400, John C Klensin wrote:
 
> So some review of the DNSEXT-specified procedures and
> expectations may be in order.

I encourage you, then, to organize the BOF session that will spin up
the WG to achieve this.  DNSEXT is only still alive because our last
document hasn't been published.

But more generally, as a practical matter it is better that people
register their stuff with us than that they don't.  We have, in the
wild, a used EDNS0 option code that is all over the Internet.  It is
undocumented, and the code point isn't actually registered.  That
state of affairs is surely worse than that the IETF didn't get to
provide good advice to authors.  DNSEXT already tried to be the DNS
cops, and has failed miserably, partly because of the usual
get-off-my-lawn crowd and partly because people unfamiliar with the
IETF find its procedures a little arcane.

My view is that we need to be more pragmatic.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com