Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-svcb-https-05.txt

Joe Abley <> Wed, 12 May 2021 22:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CB7FE3A1BCA for <>; Wed, 12 May 2021 15:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id n_vktJhqCvWg for <>; Wed, 12 May 2021 15:12:47 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::f2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 982723A4EF5 for <>; Wed, 12 May 2021 14:46:29 -0700 (PDT)
Received: by with SMTP id w9so12872471qvi.13 for <>; Wed, 12 May 2021 14:46:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t13ckG9LduT4Ko5h3JxIzicjN1rg7wREhdTBhXZgYcc=; b=OZbuaHf9ACfkw1icvSlim43AmNrLcHcpr8vKfN7wBB0ZvPvp/9chmRxRXRKLYNYy/L +sf6e1tHjevpR5/IBlWiRcIlIxWKCTgDvapUCdaYeh6OYj8SN+6ScU2aNxJleHONq9cr zoGkwmINDMcQaYDFBplfu8aOX7RVOraSvoZMY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t13ckG9LduT4Ko5h3JxIzicjN1rg7wREhdTBhXZgYcc=; b=swdwHqMGDI3094pCAlJ9FbNAGW2dZkXMhv1aLf91+/HqgbnHlQ0NrjVnzP5V/laeb+ mgGJBWtpWBU5mlB80kXHhj4ZhC3e5IgiVFdeWPqR3u6i/WhBP+EOCDHwTLbk/ctmzDeq XU+eCFQicNCh8AcqC7Ck2HHL7e+FAKoY047H96wyzSuH89WgJ6Oq4z3wwmLnS2imcf1D dacxX61IRDmxmeEGFkFfhQaGoHYV3ITI8Y1mOevZ+8MJdNDCf/TxswZwrdhOkozTR10I ibzrhorlseOM62/G/J1bnrRi9y03oA5bLN2BrZ49KOZuzrbFhd8lZFzda2ZlXeWwFZCh w1bQ==
X-Gm-Message-State: AOAM533bsJ1ASuBOZU5Uh0tgI3mPl1InWjwZhxIQ9wuoXz+j9NiwGfhc QAxal7ViH3QLiz1gI+Z9X490oawxJyaiGrjCPu4=
X-Google-Smtp-Source: ABdhPJwCOMudGArCeJb593IWxDa5be4w8DBTZhippDq0zaQV3uWeBVg3WMEfn25b8dxQr8bFEgQ4Ew==
X-Received: by 2002:a05:6214:178b:: with SMTP id ct11mr37649296qvb.37.1620855988039; Wed, 12 May 2021 14:46:28 -0700 (PDT)
Received: from ([2607:f2c0:e784:c7:e085:d30e:1134:8d95]) by with ESMTPSA id z11sm1009907qto.95.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 May 2021 14:46:27 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
From: Joe Abley <>
In-Reply-To: <20210512213903.D5F1F7AA827@ary.qy>
Date: Wed, 12 May 2021 17:46:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <20210512213903.D5F1F7AA827@ary.qy>
To: John Levine <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-svcb-https-05.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 May 2021 22:12:52 -0000

On 12 May 2021, at 17:39, John Levine <> wrote:

> It appears that Joe Abley  <> said:
>> Do you know of an example of a DNS authoritative or recursive server that does return truncated RRSets in the ANSWER section?
> A lot return truncated glue in the ADDITIONAL section.  Are we sure that wouldn't be an issue with SVCB?
> I honestly don't know.

I agree that truncation in the ADDITIONAL section is expected. Since the SVCB is expected to be used in RRSets with more than one member RR (different SVCB RRs with the same owner name and class are explicitly contemplated by the draft) it already has to accommodate that (which I think is probably a noop, since it doesn't seem to me that SVCB has different requirements in that regard to any other RRType).

I think Brian's point was that you can rely upon RRSets being intact in the ANSWER section.