Re: [DNSOP] RFC 1035 vs. mandatory NS at apex?

Joe Abley <jabley@hopcount.ca> Fri, 08 February 2019 04:17 UTC

Return-Path: <jabley@hopcount.ca>
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 4DCE9130F23 for <dnsop@ietfa.amsl.com>; Thu, 7 Feb 2019 20:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 pHHzc5yXdTXr for <dnsop@ietfa.amsl.com>; Thu, 7 Feb 2019 20:17:14 -0800 (PST)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68655130E11 for <dnsop@ietf.org>; Thu, 7 Feb 2019 20:17:14 -0800 (PST)
Received: by mail-lf1-x12d.google.com with SMTP id e27so1551114lfj.8 for <dnsop@ietf.org>; Thu, 07 Feb 2019 20:17:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc; bh=B6SnClB63SiC+i/Ziw+gSuyRvT3ALXm2rAE/Y0QsyCk=; b=j44h8UCM6HmmQjUHQDRvhlvR3s2EXDjyFvrYCFm7TnuAYVTpJZntj6J4KxKkosuC83 sMhKDeGtyD+BtFRNr0OC1ONiRwWQtUDFiWIxpp6XzXbfaqRmeXMcQt0XAQuTlz8DSmB2 aoLFG7WegyRMk4SKMmzqVnVTyeClwSRpfiFMc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc; bh=B6SnClB63SiC+i/Ziw+gSuyRvT3ALXm2rAE/Y0QsyCk=; b=idvhrxKzBMKvggBq2j4el73fqfwUap8U20LeXzTexUs5nF0xkiM7/bpJJb0puaj+bK MCNwjcyqUmKTrLn+rYvwSWUA+OcWBdTVgyowzIAbvw8VauN07kGkkedUVJ6CYRmCyR38 8F6D+mGJNo7JQgUz6C35ytfnQx6x6Q1UyEVo6EM3/6W2E7XlOV9NYm1cPohz/UUXJDlS /ujvFgKW+XFP08P9Lb/WTbEKSHPt8jcJHVxK9wE72gHtlGGdXbMX7wmRWPdzrxIF8w4l KBVDGKjsNm1kfD8aaoulrauiv2VWOUX4S7GmBoE1/I4CferJTM8CJ+6LgozFyO3pD1/E rSoA==
X-Gm-Message-State: AHQUAuaTNcHwUCCZ3Wn7Ek5J+AxBRQl0Rmg7HXJrARL7yjGq3eIwJAmt bcjB0gA+mOuw2IkeiMt+kXNFsgoaOquG0ph7LhXSlA==
X-Google-Smtp-Source: AHgI3IYx2p7zu1V9395LfzrL026HQ5c5FKKiP2VnVa/eN6WliB+KCmZIwvSs37glQkTeS2thGO6W9974nf3Q5EmmeqU=
X-Received: by 2002:a19:6001:: with SMTP id u1mr7384255lfb.56.1549599432259; Thu, 07 Feb 2019 20:17:12 -0800 (PST)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Thu, 7 Feb 2019 20:17:11 -0800
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <fcd790a2-414b-491e-01e2-9aa92f7b1c4e@nic.cz> <CAAeHe+xySnrvpD4-nhi3T0qiEmz8h0ZNUE_2kie7ctq8YPGRPA@mail.gmail.com> <56839e19-afe9-df4b-d432-09a949cc658c@nic.cz> <06E02AB3-5E3B-4E1F-9B23-BB0810F73B66@fugue.com> <CA+nkc8BLA1wVSQ6DEbM7py98Rq94P-=XJtEBzcJAD9LOucN2Ew@mail.gmail.com> <8a7a70e4-7214-c127-8542-0131bbc823bc@nic.cz> <dc68fa90-0d4c-b9d6-09cb-eec55b9f9077@necom830.hpcl.titech.ac.jp> <7751AB0C-F738-4270-9C7E-2937F773187F@hopcount.ca> <2B4B9C25-F2CF-43D3-B0CC-64E7D7CA7D6C@isc.org> <eab3b6a6-6032-c09c-7082-95eb295b823f@necom830.hpcl.titech.ac.jp>
In-Reply-To: <eab3b6a6-6032-c09c-7082-95eb295b823f@necom830.hpcl.titech.ac.jp>
Date: Thu, 7 Feb 2019 20:17:11 -0800
Message-ID: <CAJhMdTMcpBGghvgJ-qfsZfm7zC-Ndk0Jar_cRGkfrTvE_NkcyQ@mail.gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: Mark Andrews <marka@isc.org>, dnsop@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BuE-Nkn1DU6QkrF7dyKflDuKzkc>
Subject: Re: [DNSOP] RFC 1035 vs. mandatory NS at apex?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 08 Feb 2019 04:17:16 -0000

On Feb 7, 2019, at 23:12, Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> wrote:

>>> In short, this is an operational question with multiple answers and I don't like the idea of formalising an over-simplistic restriction in the protocol specification.
>
> How do you do IPv6 anycast with L servers?

That question seems a bit tangential, but in any case the simple
answer is I don't. You might ask the people who operate the ICANN root
server if you want a more useful answer; I haven't been in that team
since 2013).


Joe