[DNSOP] Making domains work even when connectivity fails (Was: the root is not special, everybody please stop obsessing over it

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 15 February 2019 14:34 UTC

Return-Path: <bortzmeyer@nic.fr>
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 381A0124D68 for <dnsop@ietfa.amsl.com>; Fri, 15 Feb 2019 06:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 s4hyeJJCKp4n for <dnsop@ietfa.amsl.com>; Fri, 15 Feb 2019 06:34:49 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 D9DA412008F for <dnsop@ietf.org>; Fri, 15 Feb 2019 06:34:48 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id DC90C2803BB; Fri, 15 Feb 2019 15:34:46 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id D632928054B; Fri, 15 Feb 2019 15:34:46 +0100 (CET)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id CE1712803BB; Fri, 15 Feb 2019 15:34:46 +0100 (CET)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id CA3A7663E080; Fri, 15 Feb 2019 15:34:46 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id C449C401CB; Fri, 15 Feb 2019 15:34:46 +0100 (CET)
Date: Fri, 15 Feb 2019 15:34:46 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Bob Harold <rharolde@umich.edu>
Cc: Paul Vixie <paul@redbarn.org>, IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20190215143446.6vp57cmlsesswnlt@nic.fr>
References: <b45edb5e-1508-0b02-a14c-a5be4ca9c0e6@redbarn.org> <20190215095936.qnxuucn6oezj7tsx@nic.fr> <CA+nkc8BcuaGC4TKUzY429Hh2=dZk2dA48=P2ecjwvhV466hT4Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+nkc8BcuaGC4TKUzY429Hh2=dZk2dA48=P2ecjwvhV466hT4Q@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 9.7
X-Kernel: Linux 4.9.0-8-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.2.15.141516
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-aCF-rf6P59dWXBD7gtRTJmr35Q>
Subject: [DNSOP] Making domains work even when connectivity fails (Was: the root is not special, everybody please stop obsessing over it
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, 15 Feb 2019 14:34:53 -0000

On Fri, Feb 15, 2019 at 09:29:29AM -0500,
 Bob Harold <rharolde@umich.edu> wrote 
 a message of 73 lines which said:

> I think in most solutions, if the name servers for "
> malware-c-and-c-as-a-service.com" and "com" are both unreachable,
> the domain should continue to resolve.  But if "com" is reachable,
> and says " malware-c-and-c-as-a-service.com" no longer exists, it
> should go away.

Any volunteer to write a problem statement for the "VIX.SU issue"?
Short version: "when I'm on the same network that at least one
authoritative name server of VIX.SU, I want this domain to work, even if there
is zero Internet connectivity to the outside world" Longer version:
"TODO (think of: is it automatic or not, does it require prior access
or not, phantom domains, etc)"