Re: [arch-d] [DNSOP] Call for Comment: <draft-iab-arpa-authoritative-servers-00> (Nameservers for the Address and Routing Parameter Area ("arpa") Domain)

Eliot Lear <lear@cisco.com> Thu, 06 May 2021 19:12 UTC

Return-Path: <lear@cisco.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 949963A2D2E; Thu, 6 May 2021 12:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 LcNB54uUftoT; Thu, 6 May 2021 12:12:30 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 671AD3A2D30; Thu, 6 May 2021 12:12:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2668; q=dns/txt; s=iport; t=1620328349; x=1621537949; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=9sa7LxVyB7L3MIRkY0279Gnrh1Vz+sQ3I95NjJDHiuA=; b=l74Mm38t1fO9Kj+7CS58b4eWwp+FGPDLTU1GVy0xiTH+TVZVL/Yn6SdK +7JlezklnMlwjGTY9rF6stSpWejHERjxiBLrwHIpaTwz0h/lCf2nq8HlB ALVJzU6exy9p8cYDRCB/YbKy5WI4GiCH72Wt/mex51ErIaOHm0SnDrgNl 0=;
X-Files: signature.asc : 488
X-IPAS-Result: A0AJAAAuP5RglxbLJq1aGwEBAQEBAQEBBQEBARIBAQEDAwEBAYIFBAEBAQsBgyFWATkxhESJBIh0A5sDgXwEBwEBAQoDAQEdCwwEAQGEDEQCggQmNgcOAgQBAQEDAgMBAQEBAQUBAQECAQYEFAEBAQEBAQEBaIVQDYZEAQEBAwEBARsGSwsFCwsMBgYjBwICJxYMDgYTgnEBgmYhD6gCeoEygQGDXkFEhHMQgToBgVKMDEOCC4E8HIJfPoJgAQEDhHQ2gisEgVWBVQRDEFuBAgdNnROBKp0dgxuDSYFJhGuTNgUjg1SLD4YdkCahMpNaAYQHAgQGBQIWgVsJKIFbMxoIGxU7KgGCPgk1EhkOjjgegWmGZIVLPwMvOAIGAQkBAQMJjQ8BAQ
IronPort-HdrOrdr: A9a23:AeSSFqF7i/Oz+FT4pLqE7ceALOsnbusQ8zAXPo5KOH9om62j+/ xG88576faZslwssTQb+exoRpPsfZqsz/FICOAqVN/IYOClghrMEGgI1+XfKlPbak/DH5ZmpM Ndm2wUMqyXMbC85vyKhzWFLw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.82,278,1613433600"; d="asc'?scan'208";a="35786458"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 May 2021 19:12:25 +0000
Received: from smtpclient.apple ([10.61.144.52]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 146JCO9Z028654 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 6 May 2021 19:12:24 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <91283FBB-FD45-4A11-B68C-1D120C7B2B8A@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_340000BE-ED9D-47DF-A4F4-392D86ADA0BD"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Date: Thu, 06 May 2021 21:12:23 +0200
In-Reply-To: <215E1379-D6CB-40F8-8A16-3E574D798CC5@vigilsec.com>
Cc: architecture-discuss@ietf.org, IAB <iab@iab.org>, dnsop@ietf.org
To: Russ Housley <housley@vigilsec.com>
References: <162032688379.30751.17216920147784179639@ietfa.amsl.com> <215E1379-D6CB-40F8-8A16-3E574D798CC5@vigilsec.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
X-Outbound-SMTP-Client: 10.61.144.52, [10.61.144.52]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/b8qCowIrjQa0BBB6lcWzA50Zj-Y>
Subject: Re: [arch-d] [DNSOP] Call for Comment: <draft-iab-arpa-authoritative-servers-00> (Nameservers for the Address and Routing Parameter Area ("arpa") Domain)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 19:12:36 -0000

+1.  I think it looks good.

One very minor comment (more a question): if I read between the lines, it seems that some thought went into the use of the term “name space” in Section 3.1 regarding there not being a zone cut for ns.arpa (not that it’s anyone’s business, I suppose).  Would it be reasonable to make more plain the logic for that decision?  I could envision at least two reasons, but my own logic could be faulty.

Eliot

> On 6 May 2021, at 20:52, Russ Housley <housley@vigilsec.com> wrote:
> 
> I have read this document, and this seems like a fine way to separate the .arpa servers from the root servers.
> 
> Russ
> 
> 
>> On May 6, 2021, at 2:48 PM, IAB Executive Administrative Manager <execd@iab.org> wrote:
>> 
>> This is an announcement of an IETF-wide Call for Comment on
>> draft-iab-arpa-authoritative-servers-00.
>> 
>> The document is being considered for publication as an Informational RFC
>> within the IAB stream, and is available for inspection at:
>> <https://datatracker.ietf.org/doc/draft-iab-arpa-authoritative-servers/>
>> 
>> The Call for Comment will last until 2021-06-03. Please send comments to
>> architecture-discuss@ietf.org and iab@iab.org.
>> 
>> Abstract:
>> 
>>  This document describes revisions to operational practices to
>>  separate function of the "arpa" top-level domain in the DNS from its
>>  historical operation alongside the DNS root zone.
>> 
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss