Re: [dnsext] Short introduction to zone cuts?

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 17 March 2012 14:41 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9260021F858E; Sat, 17 Mar 2012 07:41:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1331995273; bh=MDr6aBpJB8IwkavmLQPUsSZ+Jz5O1J5q+UmCc8B9VjQ=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=FKMdoSic7VEipjRAF1YZf/6YoAduHBUj6hAvB3Ds90azwhLF9tT6y/JYYAK6L1sEw TPUhfZUT2EYNqJwHNQ6gf60pzEv56WZnIWsmF4Q1elZGwRE++2b609xPq3tIHH2T0F uoXwu0j76NBP9N6A8noq0WW0UgQSuh2kBkxHRLzQ=
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 B812C21F858E for <dnsext@ietfa.amsl.com>; Sat, 17 Mar 2012 07:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.54
X-Spam-Level:
X-Spam-Status: No, score=-101.54 tagged_above=-999 required=5 tests=[AWL=-1.241, BAYES_00=-2.599, MANGLED_REALLY=2.3, 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 CoTyMtg53aTc for <dnsext@ietfa.amsl.com>; Sat, 17 Mar 2012 07:41:11 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id DFAF021F8589 for <dnsext@ietf.org>; Sat, 17 Mar 2012 07:41:10 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q2HEf7Pa080725 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsext@ietf.org>; Sat, 17 Mar 2012 07:41:07 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1257)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20120316233618.16C831E9F8E3@drugs.dv.isc.org>
Date: Sat, 17 Mar 2012 07:41:08 -0700
Message-Id: <68D9EB4A-78FB-428D-B312-165343DDB9FF@vpnc.org>
References: <946E9EC4-9872-4A98-BCEB-3CD7420929A1@vpnc.org> <20120316233618.16C831E9F8E3@drugs.dv.isc.org>
To: DNSEXT Working Group <dnsext@ietf.org>
X-Mailer: Apple Mail (2.1257)
Subject: Re: [dnsext] Short introduction to zone cuts?
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On Mar 16, 2012, at 4:36 PM, Mark Andrews wrote:

> 
> In message <946E9EC4-9872-4A98-BCEB-3CD7420929A1@vpnc.org>, Paul Hoffman writes
> :
>> Over on the dns-operations list, the issue of zone cuts has come up, and even
>> normally-careful people have gotten it wrong. Is there a readable introducti
>> on to zone cuts and how they affect zone operators? If not, someone should re
>> ally consider writing a two-page informational RFC on the subject and have it
>> reviewed here (even if it is after this WG shuts down) before publication. I
>> suspect that such an RFC will be more valuable to the Internet than many of 
>> the ones we have done here.
>> 
>> --Paul Hoffman
> 
> RFC 1034 say all you need to say for zone operators about NS record.

As we have seen, the text in RFC 1034 has not been sufficient to prevent errors. A clearly-written document might help prevent errors. Some of us would prefer to prevent errors rather than just criticize the people who cannot read the source documents as well as you can.

> Nameserver developer need to know more.

And, as such, would be valuable to document in an informational RFC, given that we see errors in that all the time. The two sets of information are quite related.

--Paul Hoffman

_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext