IETF Logo Mail Archive

Re: [Doh] DNSSEC, DOH, and DNS headers

manu tman <chantr4@gmail.com> Mon, 19 March 2018 22:41 UTC

Return-Path: <chantr4@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 9576B124BAC for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 15:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=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 4gGhie-DZvs9 for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 15:41:18 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 B764C1205F0 for <doh@ietf.org>; Mon, 19 Mar 2018 15:41:17 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id z143-v6so21621254lff.3 for <doh@ietf.org>; Mon, 19 Mar 2018 15:41:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zpcSpwq5SVbtaoZvUh+wlKYr1U5f8TRuoU3MKyWQM4Y=; b=JhEE78e8BauL4NJdvpQ7bjQZmyKuLeCtWuG+DbT4KgPHk0qNLJkHTwN2Vc+HEsiKto lucXN64tkUB788I7sbHPUlPn/LSNzwiAmCMFeJHxwCTjWXEWrNn/Er9WcuSoQ0DFce5a HBRa1ZTdYbA//b7jt7Vf9sQmO34vx3AEa5W1Zgpo3y4ZBAPFPmB3tV4ICiIwpihVS7gL 5e383lygXbK/9svjkqyeEbuGiu9LKFVHMtnKHaRat3k0QO9shQ9cjs02ihPDO13RdjKL 2MjfrCtUD/CMdqZrKacLN2QyNO9mez9PoisM6kSyisrQjKEGe92NtAj/xV1V2sQenglt IvFA==
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=zpcSpwq5SVbtaoZvUh+wlKYr1U5f8TRuoU3MKyWQM4Y=; b=eB7Wk20PsMswGvg38Aiq5EC2H2rOd7AGLUa8Z6rzWJlEXupwr64mUAjIkF02piaiN6 892OLgx8FVw55yE4DlG+h4+XQUCVmbA6VSFW9Ij5xTneQ84ZqNiRvBc6Gsr9SQt7l9NL H51K37f7FPTfxm9pGq2g4RDfWOMntNjexDRTGQlwZR2mncDzSpSegmYGjsvm+W7VP8YZ +I9cd5yYYn1kA+xO0HgPipe6rJExHjoMYQRBhnIeai+YVC79QpRM4KzzcQDFy6e0j+Z1 IbLh321+sg7gRiFJHl0tAN0pFj/3NCvZ6G5pn8UrBaAlEJSXtgswwEuQewiUwgvu+zW+ VwvQ==
X-Gm-Message-State: AElRT7GkBQFv7NtNBQ2+iXVqrTKscahlGmT3zsoCPx4gk1bhGMBRX9Fi 7mevZwtJapoulKZgL7HTTNO5Q1BHpaozca7aTW7nSA==
X-Google-Smtp-Source: AG47ELvpHMs+dXQoCwBmJy5wZn4GJLmXLo0lxX0xdiqnjU19a9FksqnifTb80yKcOx9CWUMs1+QAuhySZNuFIIrZcOk=
X-Received: by 10.46.137.203 with SMTP id c11mr9448455ljk.61.1521499275920; Mon, 19 Mar 2018 15:41:15 -0700 (PDT)
MIME-Version: 1.0
References: <20180319143929.tgndmrvdggewpcqv@mx4.yitter.info>
In-Reply-To: <20180319143929.tgndmrvdggewpcqv@mx4.yitter.info>
From: manu tman <chantr4@gmail.com>
Date: Mon, 19 Mar 2018 22:41:04 +0000
Message-ID: <CAArYzr+jbLADJXQR7j_1qLnAVFgqLt_nCP8P62C7fp+w5NgxAw@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: doh@ietf.org
Content-Type: multipart/alternative; boundary="f4f5e80f09e0de0dd20567cba772"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/dN7sqwzc-pfuicdHFSae_abs67E>
Subject: Re: [Doh] DNSSEC, DOH, and DNS headers
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: Mon, 19 Mar 2018 22:41:20 -0000

I think Paul remove the notion of different content type in a recent PR so
we may as well remove this bit from section 6.
Manu

On Mon, Mar 19, 2018 at 2:40 PM Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> Hi,
>
> Section 6 of -03 says this:
>
>    Different response media types will provide more or less information
>    from a DNS response.  For example, one response type might include
>    the information from the DNS header bytes while another might omit
>    it.
>
> But section 9 says
>
>          A DNS API client may also perform full
>    DNSSEC validation of answers received from a DNS API server or it may
>    choose to trust answers from a particular DNS API server, much as a
>    DNS client might choose to trust answers from its recursive DNS
>    resolver.
>
> It seems to me that these are in tension with one another, because the
> AD and CD bits are in the header that the response type is permitted
> to throw away.  Maybe it could be resolved thus:
>
> NEW
>
>          A DNS API client may also perform full
>    DNSSEC validation of answers received from a DNS API server or it may
>    choose to trust answers from a particular DNS API server, much as a
>    DNS client might choose to trust answers from its recursive DNS
>    resolver.  This capability might be affected by the response media
>    type a DNS API server supports.
>
> Best regards,
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>

v2.23.0 | Report a Bug | By Email