Re: [DNSOP] Consensus suggestion for EDE and the TC bit

Bob Harold <rharolde@umich.edu> Thu, 21 November 2019 13:44 UTC

Return-Path: <rharolde@umich.edu>
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 E45D8120867 for <dnsop@ietfa.amsl.com>; Thu, 21 Nov 2019 05:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 sDOiCgSbNOtM for <dnsop@ietfa.amsl.com>; Thu, 21 Nov 2019 05:44:31 -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 6A8311208BF for <dnsop@ietf.org>; Thu, 21 Nov 2019 05:44:31 -0800 (PST)
Received: by mail-lf1-x12d.google.com with SMTP id y19so2670381lfl.9 for <dnsop@ietf.org>; Thu, 21 Nov 2019 05:44:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=keN2Nj3NfC1ILrTDxgSqqEEnz/jVPfpT/PF/U7HYGpE=; b=f1VMgJV5pG+Dw4FWPQ29VQK/hF65YS+6chsPjrvGutQ+JkXpjFTc6KSJ87urbuEd1f YffdqxJQwzZEkdJf6DNQLEgfwEk2RiczlR1HAvRy6mDUmnol3SpKzF+cp03GLskpBIys TbnyCDmvC1DhiZndZCcwAjwmPRji82KBR+TdDUEK9sba06NMVeFCe7DsUYJigAqPP3NH g4kyUGJeIkxV9zg04narhij/vVIQhqy6iNzDDx4KGJ+t4vPMhXotbNmUlvOtEliAEIwb EYd214eY2qk3XWbhqKokV5MZwHvXCL10yab8Tf7KQiFzOdpR04o/770tjt9Ap0Z7cLUd gPag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=keN2Nj3NfC1ILrTDxgSqqEEnz/jVPfpT/PF/U7HYGpE=; b=CMzy6fOjgsSdcPiCHUyjUOAPjrBjeLOz/7KGK634VHppuIAVoFWrEr3bdqDmTgptdZ mmipZOSeDOXrQD/HRY+m5UZ1by3gjaOMxeIBVud8Ki8JUJ6T2jGnBW55gxlzIBmdVbCJ igP3zW44t3onG1qrh1hFAAWoWFWFhD2otbf4Wg2OolfjVuUi0sQLvhDXJ7vEmJwLT1cQ eUxF7p2Os2MFKVhM7teGHt0UtOR1zVwFij8/61IRbDoEYHqNWDSWnFpSFkpFDvPpFxNG e3GrSWCB0ho2vCTjQU59FSIZW3pRhwe6Vfc1ltkNsTpk5p13uESGYS9YWq1C1tm9pilp +/iA==
X-Gm-Message-State: APjAAAW2w1vTz+Jb/cckLmzRiVbUUwnTl1JecdE49aTxTWyimVpWPNCm OT3r79Vvut1NJxX1Nl12pVB1sD3njC/NROSHtkcDhUJu
X-Google-Smtp-Source: APXvYqyybYKeNkcVYABxzfouRjbg2ajg3sEM1vMjpbhsy7wqbTYiQvHXyWTjvIZ4E3m1255MevLsZ/RPmHQE0mzhETM=
X-Received: by 2002:ac2:5119:: with SMTP id q25mr7630138lfb.175.1574343869421; Thu, 21 Nov 2019 05:44:29 -0800 (PST)
MIME-Version: 1.0
References: <yblzhgpwwit.fsf@wu.hardakers.net> <CAHbrMsBR6LZ880RXPDW2L+c_gcC6Tpg+L_c78OZvxJs4Gc4pUQ@mail.gmail.com> <yblv9rdwrm3.fsf@wu.hardakers.net> <yblr221wr4s.fsf@wu.hardakers.net> <eaaaebc7-751f-0d55-4f5c-759d61144cc3@nic.cz>
In-Reply-To: <eaaaebc7-751f-0d55-4f5c-759d61144cc3@nic.cz>
From: Bob Harold <rharolde@umich.edu>
Date: Thu, 21 Nov 2019 08:44:18 -0500
Message-ID: <CA+nkc8B7oyQ6u9L1k289uOThfX-+VCw5T8BacW0HqNPfekZuow@mail.gmail.com>
To: Petr Špaček <petr.spacek@nic.cz>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000017716d0597db7f18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KcjvIsE_i0O97ys8oZ5ubSwLERs>
Subject: Re: [DNSOP] Consensus suggestion for EDE and the TC bit
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: Thu, 21 Nov 2019 13:44:34 -0000

On Thu, Nov 21, 2019 at 4:19 AM Petr Špaček <petr.spacek@nic.cz> wrote:

> On 21. 11. 19 9:49, Wes Hardaker wrote:
> > Wes Hardaker <wjhns1@hardakers.net> writes:
> >
> >>> I think our simplest and most appealing option would be to treat EDE
> >>> exactly like any existing EDNS Option (i.e. set the TC bit).
> >>
> >> For the record, I'm just fine with this.  People that *want* a separate
> >> signal should speak up please and voice their reasons why having just
> >> the TC bit is unacceptable too.
> >>
> >> We need to come to a decision about this, and that will require everyone
> >> with an opinion to chime in.
> >
> > Actually, I forgot that one of the primary reasons for separating it was
> > that EDE can go forward and the need for TC/DP bits can be debated
> > longer if need be.
> >
> > So...  anyone that thinks something like the DP bit is needed *and*
> > should be tied to EDE should speak up.  Please.
>
> I will provide the opposite opinion:
> DP bit is not *needed* for EDE.
>
> If I'm proven wrong in future we can specify DP bit in a separate document
> and update EDE RFC.
>
> (Also I've changed my mind when it comes to TC bit - now I believe that
> normal DNS processing is fine and EDE does not need a special case.)
>
> --
> Petr Špaček  @  CZ.NIC
>

Thanks for the discussion and the idea of a separate bit.

My opinion:

Keep TC bit in EDE and move it forward.

I would prefer not to create a DP flag bit yet, until actual measurements
tell us that it makes a measurable difference - let's wait until EDE is
deployed and someone can measure the occurrence of truncating just EDE.
Then we can discuss if the percentage is worth the complexity.

-- 
Bob Harold