Re: [Doh] [Ext] [Technical Errata Reported] RFC8484 (5603)

Paul Hoffman <paul.hoffman@icann.org> Tue, 15 January 2019 22:10 UTC

Return-Path: <paul.hoffman@icann.org>
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 5317D1294FA for <doh@ietfa.amsl.com>; Tue, 15 Jan 2019 14:10:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 yu15KE92xXI8 for <doh@ietfa.amsl.com>; Tue, 15 Jan 2019 14:10:52 -0800 (PST)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEAC2127598 for <doh@ietf.org>; Tue, 15 Jan 2019 14:10:52 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 15 Jan 2019 14:10:50 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Tue, 15 Jan 2019 14:10:50 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
CC: Patrick McManus <mcmanus@ducksong.com>, "ben@nostrum.com" <ben@nostrum.com>, "aamelnikov@fastmail.fm" <aamelnikov@fastmail.fm>, "adam@nostrum.com" <adam@nostrum.com>, "bemasc@google.com" <bemasc@google.com>, David Lawrence <tale@dd.org>, Carsten Bormann <cabo@tzi.org>, "doh@ietf.org" <doh@ietf.org>
Thread-Topic: [Ext] [Technical Errata Reported] RFC8484 (5603)
Thread-Index: AQHUrR8F4HHNRabckUevbB6aQUECcqWxajWA
Date: Tue, 15 Jan 2019 22:10:50 +0000
Message-ID: <3D7D49BB-69F2-4976-94BE-2D0685D1E136@icann.org>
References: <20190115220919.1F1B1B8252E@rfc-editor.org>
In-Reply-To: <20190115220919.1F1B1B8252E@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_C834DC74-4F14-4827-8065-4A86DAFD1018"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/2i4zDL7ymxBPdf7_xOu5cLkucXM>
Subject: Re: [Doh] [Ext] [Technical Errata Reported] RFC8484 (5603)
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: Tue, 15 Jan 2019 22:10:55 -0000

I agree with this erratum.

--Paul Hoffman

> On Jan 15, 2019, at 2:09 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC8484,
> "DNS Queries over HTTPS (DoH)".
> 
> --------------------------------------
> You may review the report below and at:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rfc-2Deditor.org_errata_eid5603&d=DwIBaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=yvHk3BrvY-tKWGRmaFbQS1aHXNfQjC40fPfI5u1VsFs&m=VzLcVlbkdAIA49v98uw454RaR0ztfEM47wd9oJ041fA&s=_dbZ0_XVEL_UmId-dnaukR70mWZx3XP4MKQ2blvNYf4&e=
> 
> --------------------------------------
> Type: Technical
> Reported by: Carsten Bormann <cabo@tzi.org>
> 
> Section: 4.1
> 
> Original Text
> -------------
>   The URI Template defined in this document is processed without any
>   variables when the HTTP method is POST.  When the HTTP method is GET,
>   the single variable "dns" is defined as the content of the DNS
>   request (as described in Section 6), encoded with base64url
>   [RFC4648].
> 
> 
> Corrected Text
> --------------
>   The URI Template defined in this document is processed without any
>   variables when the HTTP method is POST.  When the HTTP method is GET,
>   the single variable "dns" is defined as the content of the DNS
>   request (as described in Section 6), encoded with base64url
>   [RFC4648]. Padding characters for base64url MUST NOT be included.
> 
> 
> Notes
> -----
> Note that Section 6 does say the same thing for a different usage of base64url, and note that the examples in 4.1.1 even explicitly state this, but the text that states the usual deviation from the default of RFC 4648 should be in the defining part as well.  (This is almost, but not quite, an editorial erratum.)
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC8484 (draft-ietf-doh-dns-over-https-14)
> --------------------------------------
> Title               : DNS Queries over HTTPS (DoH)
> Publication Date    : October 2018
> Author(s)           : P. Hoffman, P. McManus
> Category            : PROPOSED STANDARD
> Source              : DNS Over HTTPS
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG