IETF Logo Mail Archive

Re: [Doh] Changes for draft-ietf-doh-dns-over-https-03

Patrick McManus <pmcmanus@mozilla.com> Thu, 15 February 2018 17:18 UTC

Return-Path: <pmcmanus@mozilla.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 C3FF612D775 for <doh@ietfa.amsl.com>; Thu, 15 Feb 2018 09:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.102
X-Spam-Level: **
X-Spam-Status: No, score=2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SBL_CSS=3.335, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 g5LQMAA6kIJ5 for <doh@ietfa.amsl.com>; Thu, 15 Feb 2018 09:18:13 -0800 (PST)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF311289B0 for <doh@ietf.org>; Thu, 15 Feb 2018 09:18:13 -0800 (PST)
Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by linode64.ducksong.com (Postfix) with ESMTPSA id A82543A085 for <doh@ietf.org>; Thu, 15 Feb 2018 12:18:12 -0500 (EST)
Received: by mail-oi0-f50.google.com with SMTP id 24so334431oij.3 for <doh@ietf.org>; Thu, 15 Feb 2018 09:18:12 -0800 (PST)
X-Gm-Message-State: APf1xPDCsB2XRo9U2RIwd4mDl5qkjptyZdr7i0BSXBDO7zaT04mbyuXo bQXEdILmNS1br8hGcyVKQEb3Hz7m4YHEZFEuNCg=
X-Google-Smtp-Source: AH8x225gxvqRyjFnknV4XGKwMB5s3Vr6Whg71y+WZniVuEeaFDTTgam20wmRK6fSdWLTtJzaGjdx9jjJZcabfI+xW48=
X-Received: by 10.202.74.143 with SMTP id x137mr2389915oia.101.1518715092350; Thu, 15 Feb 2018 09:18:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.66.212 with HTTP; Thu, 15 Feb 2018 09:18:11 -0800 (PST)
In-Reply-To: <6c5d6f3d21aa44d8b18a27fc8a896f0a@ustx2ex-dag1mb3.msg.corp.akamai.com>
References: <CAOdDvNrVdERwtP+74Y=_y9EXLgQ3i3vGmrVuoa1hz9ENjzqh1A@mail.gmail.com> <20180215161425.b3gjam66qnvxqwpe@nic.fr> <69df5d30e4644a01894f4689bfebc029@ustx2ex-dag1mb3.msg.corp.akamai.com> <20180215165720.5qjj43safhvohnup@nic.fr> <6c5d6f3d21aa44d8b18a27fc8a896f0a@ustx2ex-dag1mb3.msg.corp.akamai.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 15 Feb 2018 12:18:11 -0500
X-Gmail-Original-Message-ID: <CAOdDvNoPxEQn1-MOi9NZ9TNsf0OzTvpdXec0=bp1opkrbdChEA@mail.gmail.com>
Message-ID: <CAOdDvNoPxEQn1-MOi9NZ9TNsf0OzTvpdXec0=bp1opkrbdChEA@mail.gmail.com>
To: "Hewitt, Rory" <rhewitt@akamai.com>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Patrick McManus <pmcmanus@mozilla.com>, "doh@ietf.org" <doh@ietf.org>
Content-Type: multipart/alternative; boundary="001a1134ebb89844d40565436920"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/kFTVaQo5hBGafFLoT0VnS4q1nf0>
Subject: Re: [Doh] Changes for draft-ietf-doh-dns-over-https-03
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 15 Feb 2018 17:18:16 -0000

Thank you for these

"Specifications that define media types for use with DOH, such as DNS
Wire Format Section 5.1 of this document, MUST indicate if the body
parameter uses base64url encoding." Isn't it "dns" now and not "body"?

"When using the GET method, the body MUST be encoded with base64url"
Same problem. I believe that, in HTTP, you cannot use the word "body"
for URI parameters.




On Thu, Feb 15, 2018 at 12:00 PM, Hewitt, Rory <rhewitt@akamai.com> wrote:

> Well but from the POV of this doc, we're *only* talking about DOH servers.
> If we were explicitly contrasting them with 'traditional' DNS servers, I'd
> want the difference.
>
> A DNS server is a DNS server is a DNS server. It's how we access them that
> makes a difference...
>
> Thanks,
>
> Rory
>
> Rory Hewitt
> Senior Solutions Architect
> Global Services & Support
> Akamai Technologies
> Tel: (408) 650-0035
>
> -----Original Message-----
> From: Stephane Bortzmeyer [mailto:bortzmeyer@nic.fr]
> Sent: Thursday, February 15, 2018 8:57 AM
> To: Hewitt, Rory <rhewitt@akamai.com>
> Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>; Patrick McManus
> <pmcmanus@mozilla.com>; doh@ietf.org
> Subject: Re: [Doh] Changes for draft-ietf-doh-dns-over-https-03
>
> On Thu, Feb 15, 2018 at 04:53:25PM +0000,  Hewitt, Rory <
> rhewitt@akamai.com>
> wrote  a message of 139 lines which said:
>
> > > (I myself prefer "DOS server", there is nothing really APIesque in
> > > DoH.)
> >
> > Why not just DNS server?
>
> The idea is to find a way to tell apart DNS-over-HTTPS servers from
> "classic" DNS servers.
>

v2.23.0 | Report a Bug | By Email