IETF Logo Mail Archive

Re: [DNSOP] Glue is not optional, but sometimes it *is* sufficient...

Joe Abley <jabley@hopcount.ca> Fri, 22 May 2020 14:33 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 E47083A09C6 for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 07:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 RPvyRUnbwR2C for <dnsop@ietfa.amsl.com>; Fri, 22 May 2020 07:33:06 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 7054A3A09B9 for <dnsop@ietf.org>; Fri, 22 May 2020 07:33:06 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id o19so8373522qtr.10 for <dnsop@ietf.org>; Fri, 22 May 2020 07:33:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=v08Zfi61F8PlDrdvk5DnLnVMTyLnwcCJOzQr+JE3D50=; b=fZjkLSffdjsVCxRTugkywzaA4jTpiGz39aJtNuA/tk56hkMam2YUvQGNk8qFEHOyNM N+6ImBIS3qDoa64KWZ3D6NJpKeHxiOrLkYmrTQUx+SBE+MpeccGUmZN059jFNtEyR3AC n2j+cG3NDkOuTSEZ8HbiShia3p/PBeDxDb42I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=v08Zfi61F8PlDrdvk5DnLnVMTyLnwcCJOzQr+JE3D50=; b=doBPILt5LgWR3wEk3eUUnkBQti8ayYfeFPKUMZeEo0336RFm1PYxc1Lox5+YcJvHpl Pq5ytGlVnSKreA0Rdq9y3PsQdsWONXL1eLUUqJYb6UeSvK3DYa5vwmd3zrFEOwk73MKM ED6TH7kRUL00L142o11YoH28uZ2EZf2UDgyEuycYZV04BKMYFzCjyFTxmjgbTKIlQV8d DF4N6l+KGUb1A7JiW4fQWis0Zas5WHzlCOydLQrCnEALCX9NAPU23PNVp22g/ohirpEm qm58pHlsEdHdoD3jWojUQRCc1tfSf65QGJvgs2N+SBQEsJnbm6drGOb7vvQt/l+PWZys dgww==
X-Gm-Message-State: AOAM5321DSbIk2SBGy5ai2tGApuylBeR+s+zTH+V/cEYqZdPLVKoX0Ow uGLnitOV675I3eCINWo40BVobsB23Tr0B9EJ
X-Google-Smtp-Source: ABdhPJwp7YS0SotWShWqQ87AsQP9/0Qq0FphqM3rNSYNdAwy6ZvP5RbqZcsFEZ6atPELYIgsre5IjQ==
X-Received: by 2002:aed:2467:: with SMTP id s36mr16013368qtc.292.1590157985090; Fri, 22 May 2020 07:33:05 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:e784:c7:dc08:d905:3ae2:aab9? ([2607:f2c0:e784:c7:dc08:d905:3ae2:aab9]) by smtp.gmail.com with ESMTPSA id l6sm6549280qkc.59.2020.05.22.07.33.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2020 07:33:03 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <20200521214124.271EC197E0DF@ary.qy>
Date: Fri, 22 May 2020 10:33:01 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <907EFB9A-590D-49B5-B8D9-80D9E38F2D10@hopcount.ca>
References: <20200521214124.271EC197E0DF@ary.qy>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kyUMVA2WiMJMh4bM55c3vkpnQrM>
Subject: Re: [DNSOP] Glue is not optional, but sometimes it *is* sufficient...
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, 22 May 2020 14:33:09 -0000

Hi John,

On 21 May 2020, at 17:41, John Levine <johnl@taugh.com> wrote:

> In article <CAHw9_i+UsV9NkuPM4KYBZhO7_J78MkUEyVR3fr=vOX-vsjJeUA@mail.gmail.com> you write:
>> What if you *only* have glue, and no authoritative answer / server?
>> Can I register example.com, put in www.example.com A 192.0.2.1 as
>> glue, and not bother with this whole annoying authoritative server
>> thing?
> 
> Based on my recent analysis of TLD zones, yes if the zone is managed by
> Afilias, or if you have friends at Nominet.  Otherwise not so much.

I think that some of the things you have been looking at concern orphan glue, John -- glue records that have been promoted to authoritative, signed RRSets in the TLD zone following the removal of a zone cut.

I think what Warren is talking about is the behaviour of the DNS as a whole (stub through authoritative) in the case where the zone cut is still there, so the A/AAAA records he is exercising are glue in the proper sense.


Joe

v2.23.0 | Report a Bug | By Email