Re: [DNSOP] Fwd: New Version Notification for draft-reddy-dnsop-error-page-00.txt

tirumal reddy <kondtir@gmail.com> Mon, 27 July 2020 05:17 UTC

Return-Path: <kondtir@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A49833A0AAB for <dnsop@ietfa.amsl.com>; Sun, 26 Jul 2020 22:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 sAnd09V80rog for <dnsop@ietfa.amsl.com>; Sun, 26 Jul 2020 22:17:28 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 1D6A73A0AA7 for <dnsop@ietf.org>; Sun, 26 Jul 2020 22:17:28 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id s189so8401777iod.2 for <dnsop@ietf.org>; Sun, 26 Jul 2020 22:17:28 -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=X0qFLwD4ZhpHI5udUyqYZk5xAXGw1C6K/o281DjnhGI=; b=oVfiMOTNZp5qo61FYkuSSu0CS1mPk7IozjLaO/LkaGJKJ6U4sNHVmgaugle4wzYcto X8C/qZzRaZk8ADUd3n+GDwWoVQzxV/HcPqkcSLWhjU58aQ52+yZX16ekqha76aDwZHKk NGyyP8nwChoRp39q4V9AlbDXU/3QIru63w1Z9g7WFRc0v+Gid6sUC4OD6bZNxCy3qYX7 uMid/BDhGkVkdWj8R97Q3iinDG+Mli548LBac8pwfioQ++xhZjLlnkkTG3h87a+hzR9p O0hYN4X9y49QNHt1kErNGQOuAuRAKK529R999fbrTPqZY93EQL0ea+nwjhAmJqKjWL5u Fsgg==
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=X0qFLwD4ZhpHI5udUyqYZk5xAXGw1C6K/o281DjnhGI=; b=NMphDtPeEoHWtBqFs3Q/qNQ7SSiu8VgxKjzl6/sDkipHiBEAj3wnOuQAYLrjiifXtc vDxdYiBurGQDS2MVxl4BTaZmcGLyuGHucbHVk+B0B+M2Zdh/PIKCiPQ/1UN3ba+TeAad 1LvEJLXUhx6AiEdjeZvGrWdiT4SY+/1GuFBiiH5LE++hrEI/oX99WYDufFm3sPoCf1WZ uf+OzO2oFp1+XvTZCu0EyXk0w7Mtbv9RUdhPe/5YiuIQGUJJ0Qzj3I5WMTjS5NRWHuWN vcTrnPCzmMunYRhW+aIy5GO9+E4p7r2df4zxKxK/euA08F3nUgVDvnM9A7MWbovdic77 7zpA==
X-Gm-Message-State: AOAM530uJRPI/8YxCESRD/NVDsiv+t+TC9KbQZ5vDnrFoVU1eCcYUVfH PXIDI3tBo6YTt8d5uRbvlkN9URXkjoI1rjPJpK2hgwjS
X-Google-Smtp-Source: ABdhPJwf5QNqy4MBvd0buM6hf7/sJQUHFSJIQQJwePOrvbUEN5cqw0s7ow0O8TqJ2MyZ/RUzTLmpIFeM86LXNBTWALY=
X-Received: by 2002:a5e:8611:: with SMTP id z17mr4824037ioj.177.1595827047320; Sun, 26 Jul 2020 22:17:27 -0700 (PDT)
MIME-Version: 1.0
References: <159419312721.4560.7461331648236111056@ietfa.amsl.com> <CAFpG3gcKVHxQo0USq-K3-jYnVUULiHU=asBx4P8bFm0Rw6V42Q@mail.gmail.com> <ybl5zadnggb.fsf@w7.hardakers.net>
In-Reply-To: <ybl5zadnggb.fsf@w7.hardakers.net>
From: tirumal reddy <kondtir@gmail.com>
Date: Mon, 27 Jul 2020 10:47:15 +0530
Message-ID: <CAFpG3gd4WyB0rM+jTg_uaKG_tgfwPTNqeVEoEo05Lh+Vyf7APA@mail.gmail.com>
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004750e905ab657048"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3v8WQvGfSatCg_GcfSmbNXMnZ-M>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-reddy-dnsop-error-page-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 05:17:30 -0000

Hi Wes,

Please see inline

On Fri, 24 Jul 2020 at 19:49, Wes Hardaker <wjhns1@hardakers.net> wrote:

> tirumal reddy <kondtir@gmail.com> writes:
>
> > This draft https://tools.ietf.org/html/draft-reddy-dnsop-error-page-00
> > discusses a method to return an URL that explains the reason the DNS
> > query was filtered.
>
> Interesting idea.


Thanks.


> A couple of points:
>
> 1) The document doesn't state where the HTTPS record should go.  I
> assume in the additional section (it's not an answer).
>

Yes, will update text.


>
> 2) It doesn't talk about what the name should be for the record.  I
> assume it must match the name that was requested (IE, the question
> section name).
>

Yup, the name of the record must match the original QNAME in the DNS
request; will add clarifying text.


>
> 3) WRT DNSSEC and this statement:
>
>        but DNSSEC signing and validation
>        is not possible for the HTTPS record returning the error page URL
>        along with the "Forged Answer" extended error.
>
>    You should probably also insert a MUST / MUST NOT about these errors
>    and how they must only come from the resolver the client is talking
>    to and must not be forwarded from something upstream (double hops
>    provide no trust in DOH (or any other secured transport) without
>    DNSSEC or some other signing mechanism)
>

Good point, added following text to security considerations section:

The DNS resolver MUST NOT forward the "Forged Answer" extended error and
the HTTPS record from an upstream resolver as an attacker (e.g., MiTM)
could insert a fake extended error response and HTTPS record into the DNS
response.

Cheers,
-Tiru


>
> --
> Wes Hardaker
> USC/ISI
>