Re: [DNSOP] [Ext] partial glue is not enough, I-D Action: draft-ietf-dnsop-glue-is-not-optional-00.txt

Mukund Sivaraman <muks@mukund.org> Sat, 04 July 2020 01:44 UTC

Return-Path: <muks@mukund.org>
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 D081C3A0868 for <dnsop@ietfa.amsl.com>; Fri, 3 Jul 2020 18:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_PASS=-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=mukund.org
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 13bufmrfV8Kx for <dnsop@ietfa.amsl.com>; Fri, 3 Jul 2020 18:44:07 -0700 (PDT)
Received: from jupiter.mukund.org (jupiter.mukund.org [46.4.226.158]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94C9E3A085F for <dnsop@ietf.org>; Fri, 3 Jul 2020 18:44:02 -0700 (PDT)
Date: Sat, 4 Jul 2020 07:13:51 +0530
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail; t=1593827036; bh=xhcCfpl2TyQlgUjSFpdcdsNX+UgwBpUCOdRqr3hV27M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ZIhUWgIr2ZLLH40wr3AASRD8JDghO9CxHR9wnsWULdK1VayVS65TVjcabyRwEX0wM AkJxqCMSkGZjO6I04YcHiJWHpR64k9YVPue8Qow8cGnn9mIguouijM1kxM1H3lvWtw c/VAv0xKtMviD1Wqaor6a+I4udXO12rwmuFdpMuo=
From: Mukund Sivaraman <muks@mukund.org>
To: John R Levine <johnl@taugh.com>
Cc: Brian Dickson <brian.peter.dickson@gmail.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Message-ID: <20200704014351.GA94106@jurassic.vpn.mukund.org>
References: <CAH1iCirMLsLmohChQCvqiS6ra0MYK40eJsDm_B5pMXAgXRnEpg@mail.gmail.com> <20200703175942.1D0441C485EE@ary.qy> <CAH1iCioMhnb=PthHEP6LB=BZBuB5CQpPzJ7h8uqYAXTjtn_8BQ@mail.gmail.com> <alpine.OSX.2.22.407.2007031758360.2180@ary.qy> <CAH1iCiqui42FdSEXECAMOFfFqHgnbpE6rMW99TgB9wU6JN-kcw@mail.gmail.com> <alpine.OSX.2.22.407.2007032114200.2811@ary.qy>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk"
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.22.407.2007032114200.2811@ary.qy>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yRHX43-gTmiIgEAmQx5j5erpDIE>
Subject: Re: [DNSOP] [Ext] partial glue is not enough, I-D Action: draft-ietf-dnsop-glue-is-not-optional-00.txt
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: Sat, 04 Jul 2020 01:44:14 -0000

On Fri, Jul 03, 2020 at 09:19:48PM -0400, John R Levine wrote:
> > Uh, no. The TC flag means "something didn't fit".
> > It is not restricted to glue, which is only in the additional section.
> > TC can also be set if something from the authority section didn't fit, or
> > if something didn't fit in the answer section.
> > (Obviously it would be the first section where something didn't fit that
> > matters.)
> 
> Well there's a question.  Is there any DNS software that will keeps adding
> new sections to a truncated answer, e.g., a partial authority section but it
> has some additional records anyway.  Seems unlikely but I honestly don't
> know.

Pedantically, yes. OPT and TSIG RRs are added by some implementations
when TC=1, and they may delete answer and authority sections (fully or
in part) if necessary to make room for OPT and TSIG.

> In any event this whols plan still seems way overcomplicated.  In my simple
> world, you can tell that an answer is a referral because it has an empty
> answer section and an non-empty authority section.  A useful referral has some
> NS records in the authority section.

The DNS protocol seems to have jumped the shark. It's becoming more and
more of a rat's nest.

		Mukund