Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice

manning bill <bmanning@isi.edu> Fri, 30 May 2014 14:21 UTC

Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 189B31A0916 for <ietf@ietfa.amsl.com>; Fri, 30 May 2014 07:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.551
X-Spam-Level:
X-Spam-Status: No, score=-4.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 ZRKCNgjuJV46 for <ietf@ietfa.amsl.com>; Fri, 30 May 2014 07:21:50 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 825FE1A0918 for <ietf@ietf.org>; Fri, 30 May 2014 07:21:45 -0700 (PDT)
Received: from [192.168.0.2] (cpe-23-241-118-60.socal.res.rr.com [23.241.118.60]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s4UEKvAr000342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 30 May 2014 07:21:07 -0700 (PDT)
Subject: Re: Last Call: <draft-iab-2870bis-01.txt> (DNS Root Name Service Protocol and Deployment Requirements) to Best Current Practice
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Content-Type: text/plain; charset="windows-1252"
From: manning bill <bmanning@isi.edu>
In-Reply-To: <B5C09A91-F8B4-4F36-BB52-24E798024588@frobbit.se>
Date: Fri, 30 May 2014 07:20:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <367FC10E-9F31-444B-9669-D281ED4DE71F@isi.edu>
References: <20140520204238.21772.64347.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140521194638.06eaf508@resistor.net> <1111FB79-012A-414B-B8CD-0BBDAE8BD6A8@hopcount.ca> <6.2.5.6.2.20140522095317.0c5fd648@elandnews.com> <5C02BCCA-79D7-40A5-BFB0-26284A667E78@vpnc.org> <DC9ED318-2352-4AF0-8A43-29D237C32B64@vigilsec.com> <924045CD-DC34-423B-8702-CD99CF687D46@vpnc.org> <31344.1401304682@sandelman.ca> <850B843A-3346-408B-9D8B-65D0879A2498@virtualized.org> <C8E791BD-E0A6-437E-B531-A1274DAED970@frobbit.se> <BAE7E773-EAE6-4E81-826C-AAA5AF8F5519@virtualized.org> <41C69E89-26DA-45EB-BDC6-38C404C615F2@frobbit.se> <32E01C2E-1D13-482A-AB44-FF45A556EAF5@virtualized.org> <B5C09A91-F8B4-4F36-BB52-24E798024588@frobbit.se>
To: Patrik Fältström <paf@frobbit.se>
X-Mailer: Apple Mail (2.1878.2)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qRYWXRCdzSjkZ-wAmhls1eEd_L4
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 30 May 2014 14:21:54 -0000

the problem here is that rarely has the IETF managed to actually map its expectations to operational reality.
RFC 2010 did, for about 60 days.   RFC 2870 never did.  And neither does this document.
the trend line is away from credibility, which is not really where I think the ietf should be headed, but ymmv.

if this document were to be recast as “Protocol Requirements for DNS Servers” - that would be a valuable 
document.  in its current form, not so much.


/bill
Neca eos omnes.  Deus suos agnoscet.

On 29May2014Thursday, at 23:38, Patrik Fältström <paf@frobbit.se> wrote:

> 
> On 29 maj 2014, at 22:48, David Conrad <drc@virtualized.org> wrote:
> 
>> I'm disappointed that people would argue that Yet Another IETF RFC is required to get folks to do stuff they already know they should be doing.
> 
> Aha, then here is where I think we have different opinion.
> 
> I do not see this draft be anything people think will change things. I see personally this be an updated version of the RFC stating what IETF do believe should be implemented.
> 
> Once again, the enforcement is somewhere else.
> 
> But if whatever the enforcement is to refer to is not correct, then it is absolutely for certain the enforcement will not happen.
> 
> So, phew, I do not think we are very far away from each other this time either. ;-)
> 
>   Patrik
>