Re: [Add] Fwd: New Version Notification for draft-reddy-add-server-policy-selection-02.txt

tirumal reddy <kondtir@gmail.com> Mon, 01 June 2020 10:22 UTC

Return-Path: <kondtir@gmail.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 081DC3A0F06 for <add@ietfa.amsl.com>; Mon, 1 Jun 2020 03:22:52 -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 6bSUkMkNo5vK for <add@ietfa.amsl.com>; Mon, 1 Jun 2020 03:22:50 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 31EAB3A0F02 for <add@ietf.org>; Mon, 1 Jun 2020 03:22:50 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id c3so10858733wru.12 for <add@ietf.org>; Mon, 01 Jun 2020 03:22:50 -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=JvIB9HV2kUDeB6axUI62hikM2F+eLVdI06XOIlVc84c=; b=vMp1LlqA1V6WAReZR5PUPMXUbeOrpks5rLVHrPMquvTh7I381+7ikd58UljVP4kOE8 BHJ8ukPuJgNL/iR/+qCkq2bvrtpRX/i/P74V8YJUK/Sv+plYxn317NaRBxJn5Wsy+MAH OAXLdMi/pM3I7nmx2BL8YL4I+8HGsfqqEJPtfE12Zq2iZMLtCN3wLFdSO0pgOQTj5RT8 qxnYG59FNsQBkhCep6PcJVnoQVnHMlDtDJyhxQi5RdZ1oore+76FNFCm1X+shdYKmnHb xcFBlOJEqWo27mfG/X6ZXYslY5NEMv0y0452eIxwAzuMfEGlXbb5cV+ZrsZIPv1wCwVh Zhag==
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=JvIB9HV2kUDeB6axUI62hikM2F+eLVdI06XOIlVc84c=; b=HqEl6F1VJ6qvYkLP5WgWB1+guw06fGmOB1QZpOhIA39n/3nYXGUbqxsve7LRIUZtix +5zvtx3ScxYeLSELUgL9TMpSUZRa0vaaAH6T0X4U08+40zi3k53lG/Oqve0L3s8llCQH NreNkQ32KsFNDx3WRWoGMT1eg66pyzEXgS1TUS1D4jaRORzvg+MuXG1pm19s1OPyg0iW juqcDO6itJAtEykaxYK9xx5i0M+f41xk2IMspjv5MdVcb0/kjskCtT5RdprXpvxgUSGz sHJNJT9crnbU3oLMaeZ4SK2HS1Dxll/N7ZwAQFaCN9hTZ2HJrn5kCQWAeMwy26Wq9yQa pa1A==
X-Gm-Message-State: AOAM533tqR9K8ZWC4cNmrMXe683SaccHz2G9mzaWJLbrLFcTf3doBZgP zLFbrXSuTFzvtKeCW6ueuBuFZkdVSBd3PDIy9Z8=
X-Google-Smtp-Source: ABdhPJxW2QFG/Ujy0dkrXLBwrNpxUVwNLxUfKxSEKBU7vkvHTgfzUjG7tw1NPwOn4z+2WT4iX9sVnN2n/+R1wqJS0nU=
X-Received: by 2002:adf:e588:: with SMTP id l8mr22771932wrm.255.1591006968541; Mon, 01 Jun 2020 03:22:48 -0700 (PDT)
MIME-Version: 1.0
References: <159064546659.30784.12927519685709906985@ietfa.amsl.com> <CAFpG3gfwsyxf7UAd61LLfsF-4Rd+sDEqjc3o86iy_UOveQbY-g@mail.gmail.com> <86151027.6608.1590676320799@appsuite-gw2.open-xchange.com>
In-Reply-To: <86151027.6608.1590676320799@appsuite-gw2.open-xchange.com>
From: tirumal reddy <kondtir@gmail.com>
Date: Mon, 1 Jun 2020 15:52:36 +0530
Message-ID: <CAFpG3gcX0rqVMWaJ6F-gayGhu7kia0RFrHfXJvrp3st9XDS4Nw@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000031f4fb05a7032d04"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/URiHHz_arIzH5cyBu9JHkLy6LGM>
Subject: Re: [Add] Fwd: New Version Notification for draft-reddy-add-server-policy-selection-02.txt
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 10:22:52 -0000

Please see inline

On Thu, 28 May 2020 at 20:02, Vittorio Bertola <
vittorio.bertola@open-xchange.com> wrote:

>
> Il 28/05/2020 12:19 tirumal reddy <kondtir@gmail.com> ha scritto:
>
>
> Hi all,
>
> We prepared an updated version of
> https://tools.ietf.org/html/draft-reddy-add-server-policy-selection-02 to
> address comments from Neil. It discusses how a DNS client can authenticate
> it is connecting to a DoH/DoT server hosted by a specific organization
> (e.g., ISP). We now rely on I-D.pp-add-resinfo to retrieve the Policy
> Assertion Token (PAT).
>
> Comments are welcome.
>
> Thanks for this work. I think we need feedback by client developers that
> would consume this information. You might need something more detailed or
> specific to express the server's policies; for example, machine-readable
> indication of authentication support, logging policies, or fine-grained
> description of filtering policies could be used by clients that want to
> standardize their analysis and presentation of server features. It's good
> to have an extension mechanism, but there would still be the need for
> agreement on what the new claims mean.
>

The attributes defined in the draft do not convey any “privacy claims” like
logging policies. We don’t want to compete/replace the privacy statements
written by an attorney and create any ambiguity or under-represent the
legal statements. The attributes identify the capabilities of the DoH
server (e.g., malware filtering) and the attribute privacyurl provides a
URL that points to the human readable privacy policy statement.

The main purpose of this draft is to discuss how a DNS client can
cryptographically identify it is connecting to a DoT/DoH server hosted by a
specific organization (e.g., ISP).  It is particularly useful when the
DoH/DoT server is insecurely discovered and prevents the client from
connecting to a attackers server.

Can you please provide more details on what you mean by machine-readable
authentication support and what kind of fine-grained description of
filtering policies should be conveyed to the client ?

Cheers,
-Tiru

> --
>
> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> vittorio.bertola@open-xchange.com
> Office @ Via Treviso 12, 10144 Torino, Italy
>
>