Re: [DNSOP] Current DNS standards, drafts & charter

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 27 March 2018 16:41 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8A512946D for <dnsop@ietfa.amsl.com>; Tue, 27 Mar 2018 09:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REz-Pcipn5Lv for <dnsop@ietfa.amsl.com>; Tue, 27 Mar 2018 09:41:52 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF40E126C89 for <dnsop@ietf.org>; Tue, 27 Mar 2018 09:41:51 -0700 (PDT)
Received: from [10.32.60.121] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w2RGf5BJ058662 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 27 Mar 2018 09:41:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [10.32.60.121]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: dnsop@ietf.org
Date: Tue, 27 Mar 2018 09:41:40 -0700
X-Mailer: MailMate (1.11r5462)
Message-ID: <BB0A8875-9B60-4808-A2D5-0633EEAD756E@vpnc.org>
In-Reply-To: <20180327160216.et4zlmqdytdzvucg@mx4.yitter.info>
References: <20180326154645.GB24771@server.ds9a.nl> <20180327160216.et4zlmqdytdzvucg@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qix3d2rH76UYaqYuSbU1tQvfzXc>
Subject: Re: [DNSOP] Current DNS standards, drafts & charter
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2018 16:41:54 -0000

On 27 Mar 2018, at 9:02, Andrew Sullivan wrote:

> On Mon, Mar 26, 2018 at 05:46:45PM +0200, bert hubert wrote:
>> So my first suggested action is: could we write a document that has a 
>> core
>> introduction of DNS and then provides a recommended (not) reading 
>> list.
>
> Maybe we could, but we failed at that once before.

Oh, there you go again with that operational history lesson. :-)

> After the DNSSEC work wound down, around IETF 68, DNSEXT went
> "dormant".  But it was apparent that the DNS protocol was complicated
> and difficult to understand, so the WG was rechartered partly to try
> to get some clarity to the standards.  The document the WG hung its
> efforts on was
> https://tools.ietf.org/html/draft-ietf-dnsext-dns-protocol-profile-01.
>
> The problem, of course, was that nobody had the time required to
> complete this.

We hope that someone does, but rarely can we find someone whose boss 
will give them the (literally) hundreds of hours that would take to do 
this right.

> I have no idea how the SMTP crowd at the IETF managed
> to get the cycles to update 821/822 several times, but we were unable
> to get this energy.

OK, my turn. I ran the Internet Mail Consortium during the timeframe of 
that work, and helped shepherd some of the discussions and the interop 
testing. It was grueling even though that was a group of people where 
pretty much everyone liked each other and listened politely.

> The last update to that draft came in January
> 2008, and by IETF 72 (in July of '08) Olafur and I concluded that, if
> we couldn't get any activity, then we'd try to focus the WG on places
> where it could make progress.  We took that decision in the fall of
> 2008.
>
> Now, I don't think that the work was bad or wrong, and I think that
> draft remains a useful place to start if people want to pick up that
> work again.  But I'm not super convinced that this or any other WG
> really will have the desire to undertake it.  Maintenance is no fun,
> and inventing new stuff is more entertaining.
>
> But, by all means, if people want to revisit that effort, I think it
> would be a fine thing.  I think, however, that someone should contact
> a friendly neighbourhood AD to try to determine where the work should
> be chartered.  I do _not_ think it is operations and management work.

 From the SMTP work above, I would also say "...and unless you have an 
author who can commit a lot of time over the course of two years".

> One thing that would be interesting to explore in taking that effort
> up is whether DNS should really be considered INT or ART.  DNS lives
> squarely in the application layer and isn't really like the other
> things that fit in INT.  OTOH, it's more a service to other parts of
> the network than it is an application the way ordinary application
> layer things are.  The misfit of the model to the world strikes again!

This was another area where the SMTP work had an advantage: we got good 
help from others in the Apps Area at the time.

--Paul Hoffman