Re: [Doh] Running code

- goto <minami.hiroy@gmail.com> Fri, 12 January 2018 18:08 UTC

Return-Path: <minami.hiroy@gmail.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 A3D3512785F for <doh@ietfa.amsl.com>; Fri, 12 Jan 2018 10:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7apve-0z5gj7 for <doh@ietfa.amsl.com>; Fri, 12 Jan 2018 10:07:54 -0800 (PST)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (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 13F9F12D856 for <doh@ietf.org>; Fri, 12 Jan 2018 10:07:54 -0800 (PST)
Received: by mail-ot0-x231.google.com with SMTP id f6so5737974oti.13 for <doh@ietf.org>; Fri, 12 Jan 2018 10:07:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Cgnpzij2EZXVhBuQCTjGLAbUQrWpCtlgSwpqzlKSOeQ=; b=aeT1W1E9rA3YlVn07ZVUNz58uZe9TfCp+BmHVTtv7iv/JOSdN+/hmjdnmfbwbYLczd YeqNCquKn3QJeyAMEzuSLIGtTE/8abUPg6jZYXd2Cgo3Kj8dndwLPbz0rQZJuHnlhpdt jes85aGQ6COQQtQZ7SAf205OawODHgqqrhQgAwdnbdfBPcOYd0/8j+3+OWTvObyc98wD eicLFcS0TD4O5Lr1k6Yul2Cj6FkCEPLAshpRCe5kV/oac5p6n4QfiK7f1C685q/mQ5oM Jh5hGQPMWbWa5GLlmtwk3jQWJgkyvG1qPOn6LM5SUABkqITO9FafBuM5bgINypbpqpNI p8WQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Cgnpzij2EZXVhBuQCTjGLAbUQrWpCtlgSwpqzlKSOeQ=; b=iUZvUNdfEfH17/crOX6P2Uil+BqZo3l6HQS4Rxcab9nrQ2juQ2lmJhHNDZNxEef/8G oU7CaW8XTeu2um70iyeVvJXA+poHAltZs+oTtWkRmL8zs6sTxd64KaidRWqD4vQ+gUcm NIVlk5+F2oFjzZQFjylb/aAbC/ItYORL6TSpJd4AQMHbLiYDTnm+MiprEgUwD6r0QqEt NG1f14PIShbRwuhurdmYr0fVK+xOL34woYlWQ6MGb2JTSwZURiY0pPrcAT4d57XSZp/S a+B6ZboG9o2LipcG6uCergWKTABKg/XippU1azcrD+VPHq+AjZ6rsJ4TuPFmTGt64Pcm hqTw==
X-Gm-Message-State: AKwxytd/y0hxhmrYajW1KBxY27l0XUTqOcapF8lk+5N0/UzGKHexNhFB ofj4fjVkkZh/3cmd1Ii3I2j+jbCbXbEHVo64x2xWsg==
X-Google-Smtp-Source: ACJfBovCjZWFO6o59+9BxXOwj7oaI7QM4dqyUNh/Vc2ruCe+X+s6ity9RCcy6eoqdB+W0Ys7jYY4CW97lK1tCMg23fU=
X-Received: by 10.157.81.69 with SMTP id u5mr15938159oti.20.1515780473125; Fri, 12 Jan 2018 10:07:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.144.232 with HTTP; Fri, 12 Jan 2018 10:07:52 -0800 (PST)
From: - goto <minami.hiroy@gmail.com>
Date: Sat, 13 Jan 2018 03:07:52 +0900
Message-ID: <CAK3uxukFYcAhuiEGhR0rs0hqVOdGsQF77AoP9wZqiuXSh1mW-A@mail.gmail.com>
To: doh@ietf.org
Content-Type: multipart/alternative; boundary="001a114f1e26a880d50562982440"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/PwKhexPpSl9rrSGfJLSIDPNPO7g>
Subject: Re: [Doh] Running code
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: Fri, 12 Jan 2018 18:26:29 -0000

Hi Ben Schwartz and DOH wg folks

https://dns.google.com/experimental is great work !

so, I have a question about error handlings.

if client sends an invalid request like a below, Server responses a html
(Content-Type: text/html) to Client.
curl "https://dns.google.com/experimental?ct&body=Invalid" -H
"accept:application/dns-udpwireformat, application/simpledns+json"

I think there are some options
- request with "accept: */*" : server can responses a html with 400 status
code
- request with "accept:application/dns-udpwireformat" : server responses
dns response with rcode=1 (HTTP status code is ???)

if my understanding is correct, It is not written in the specification
draft-02.

In any case, I think clarifying error handlings (and reration between HTTP
status code and DNS rcode) is reasonable in the spec. Is this out of scope
of the spec?

thanks,

Yuki