IETF Logo Mail Archive

Re: [Doh] Use of TXT records

"Hewitt, Rory" <rhewitt@akamai.com> Fri, 15 March 2019 16:58 UTC

Return-Path: <rhewitt@akamai.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13ACF129284 for <doh@ietfa.amsl.com>; Fri, 15 Mar 2019 09:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 gusehQUeYyaB for <doh@ietfa.amsl.com>; Fri, 15 Mar 2019 09:58:06 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 72ECE12705F for <doh@ietf.org>; Fri, 15 Mar 2019 09:58:06 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x2FGvS6V013951; Fri, 15 Mar 2019 16:57:45 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=0Im5hy4st1qqpOQWpyIRB81OPHl72X2nsfeeDquQf50=; b=kVy7qhYUHe/lbII94b6S/t6yvs7c4UbB4FINzIL0yO/KWfpK5cnn6OjSJiYraDFnLuFn C/3b+4eHg/RIhgE+ITerwxfhYjXUS4AXH2DCJ1pV/yuI+dJV5aL9QiQjgDRaYox7FuOR ID39iLks+/dOfXlJnX+pAv3ja8dt+E3LbUljKu1MNuIsDzg+HCU9l82vTd4kWBEMfHDy xaqN7VyNZgiNRXkOqggJJLoaZX7KHx2jHnMefAElIcyR10/o8LbC1fqZwfD/sKFBdelH iauotT7F25mKbJWDMKCcRLAk+rxDtwAJ1feOpL+yF6dpyuxmnPwBPh05STogRBuykwPh mw==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0a-00190b01.pphosted.com with ESMTP id 2r7qm5dhhk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 15 Mar 2019 16:57:45 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x2FGl1TP026620; Fri, 15 Mar 2019 12:57:43 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.32]) by prod-mail-ppoint2.akamai.com with ESMTP id 2r49q13hf3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 15 Mar 2019 12:57:43 -0400
Received: from USTX2EX-DAG1MB3.msg.corp.akamai.com (172.27.27.103) by ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 15 Mar 2019 09:57:40 -0700
Received: from USTX2EX-DAG1MB3.msg.corp.akamai.com ([172.27.27.103]) by ustx2ex-dag1mb3.msg.corp.akamai.com ([172.27.27.103]) with mapi id 15.00.1473.003; Fri, 15 Mar 2019 11:57:40 -0500
From: "Hewitt, Rory" <rhewitt@akamai.com>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, Paul Hoffman <paul.hoffman@icann.org>
CC: DoH WG <doh@ietf.org>
Thread-Topic: [Doh] Use of TXT records
Thread-Index: AQHU20wb1BtgZuOodkiHHGX0BN4SLqYNPC0A//+s9ZA=
Date: Fri, 15 Mar 2019 16:57:40 +0000
Message-ID: <0e842b1edfe44bd69e1188e72b8f3873@ustx2ex-dag1mb3.msg.corp.akamai.com>
References: <CAHbrMsCNyeabhk0sVexOHVedVkgG2dvV9T8wWL++om5juAUvEw@mail.gmail.com> <D6D473EB-666A-45B1-9A59-0A7548E0A4DE@icann.org> <CAHbrMsDypWpr4Wz1VDtBhmoiZDTt=NrkK-9T15y69doz1CHA4Q@mail.gmail.com>
In-Reply-To: <CAHbrMsDypWpr4Wz1VDtBhmoiZDTt=NrkK-9T15y69doz1CHA4Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.28.212.170]
Content-Type: multipart/alternative; boundary="_000_0e842b1edfe44bd69e1188e72b8f3873ustx2exdag1mb3msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903150119
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903150120
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/dYzruSb21uSM7EJuInAH0T0n7Yc>
Subject: Re: [Doh] Use of TXT records
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2019 16:58:08 -0000

Ben,

How has the use of TXT been a point of controversy in the past?

Is it a general "TXT records are bad" or "Adding new TXT records is bad" or "TXT records have never been standardized or formatted consistently among their various uses, so there's always the possibility of clashes".

Because I, for one, would agree with the last.

Rory

From: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Sent: Friday, March 15, 2019 9:53 AM
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: DoH WG <doh@ietf.org>
Subject: Re: [Doh] Use of TXT records

To be clear, I'm not objecting to this choice.  I'm merely noting that use of TXT has been a point of controversy in other discussions at the IETF.  Some groups have decided to proceed with TXT, some have preferred to use different or new RRTYPEs, and some have not yet decided.  I would like the working group to consider this question soon so it doesn't delay consensus later.

On Fri, Mar 15, 2019 at 12:27 PM Paul Hoffman <paul.hoffman@icann.org<mailto:paul.hoffman@icann.org>> wrote:
On Mar 15, 2019, at 6:12 AM, Ben Schwartz <bemasc=40google.com@dmarc.ietf..org<mailto:bemasc=40google.com@dmarc.ietf..org>> wrote:
> 5. Machine-readable content in a TXT record

This is the first I had heard that people objected to using a TXT record, but I might have missed that part of the discussion. Given that this query is for a newly-created SUDN that is only used for looking up DoH information, there is no chance that the TXT record would be in use for anything else.

Having said that, it would be quite easy for this document to create a new RRtype for this particular query. (I would not want to re-use the URI RRtype because it would take more effort to explain the priority and weight, as well as dealing with the common error of people not put the URI in quotations marks as is required for the URI RRtype.)

--Paul Hoffman

v2.23.0 | Report a Bug | By Email