IETF Logo Mail Archive

Re: [Add] Proposed charter and BoF request for IETF 106

tirumal reddy <kondtir@gmail.com> Wed, 09 October 2019 18:04 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 8621A120AA1 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 11:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 3RINV2oxu82D for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 11:04:29 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 7761E120AA0 for <add@ietf.org>; Wed, 9 Oct 2019 11:04:29 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id n26so7055919ioj.8 for <add@ietf.org>; Wed, 09 Oct 2019 11:04:29 -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=U3l7K3atR4ozVeAb1g0mrMYJzpCAZcnVLSm53QYSPbY=; b=owGtv1ApxCOZcYVvJiQm4SEoTmcp4taVEPgpINftKPuYr/C9lVNTU2km7okBe9jWBQ Fxyja/VLdxl5twW1nXMZUKCmLh95jidBdHtj0adud6v+gHQoplcU+CHE+8nVrl/nQZBb TH3RmXkW80zw09r3JmsKjvzIlnMl4LTwRJOzDVmslkE+oRd333LBCLUjinAElI7z7wZC GdgRe/iTToxSHtBFL94LAFSDKQKNdULiyyoGnM3rwf3RpYR6OZUMdqGWjB/rhlkYWuJq x/Rn7WFZ/9Kg5HRbEFko08xW5K626UYr7VPWAOKBv3XyxAq8ZMq7wBgzIk98HSGhPg7p h2KQ==
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=U3l7K3atR4ozVeAb1g0mrMYJzpCAZcnVLSm53QYSPbY=; b=au+DkFmcf3t6AAN4xH95zPr36iOz85kJInYJvKKatZg3b+wpaUkqlHSy1XPfwTypug lYojDqBzzH08eD7FIh7TnHnk5XW7eBJM2xuKAfxy0sbEUYZxti5Yff37NzCdIDiNloxP GgoEbpeW+sKrJt813Sf3fOqmhLmkPkQuENFWlofbHSH12w4wycuTMBTGoivj/TAI0yxv SKjMjFnWgfWqbc5J84zWukIUUX6FgZmE6LL8cbQ1yAnIYmRbodP0gK9QucPiK8FjbBNP Grn8m+b8ZVhEQ5KhHBoNJbTfkhBMlZiQ5v3bmK/E61V4dQNt6kcN0vTX13ecOrb8bsVD kxnw==
X-Gm-Message-State: APjAAAWk7Sk0cW0tzX8gTre+74pQgD9X+BUh6hbHs+tmiQ2slxAIWCfi +rP+JaWOlQ0KPYLOd5hnDIsOhoMXRjUll0rMhaUg3/L0
X-Google-Smtp-Source: APXvYqzwn03YfLGId1/AMPc8EKKz8YFNowoQFcC493EuaYEUha/AMWkwgsNE8xX0gaNvYsP/on3ulSqTHqaGrTmcbwg=
X-Received: by 2002:a02:c919:: with SMTP id t25mr4577297jao.77.1570644268493; Wed, 09 Oct 2019 11:04:28 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <CABcZeBMkAFZW9mWjw92v+OR0Fa8ed+P80yc78eY07hCpsCNY6Q@mail.gmail.com> <1556423899.28427.1570640191209@appsuite-gw2.open-xchange.com> <CABcZeBNyRDqnVL68aXny=Ht69NjahmS4zRsnYizO53M--rhM5g@mail.gmail.com> <alpine.LRH.2.21.1910091313590.2297@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1910091313590.2297@bofh.nohats.ca>
From: tirumal reddy <kondtir@gmail.com>
Date: Wed, 09 Oct 2019 19:04:15 +0100
Message-ID: <CAFpG3gch-mgJJMO1rEg61PhYNKeKYiJwz4NTQ3QDbEb=WNkyQw@mail.gmail.com>
To: Paul Wouters <paul@nohats.ca>
Cc: ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b1322f05947e1d70"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/mpoSn8wTXgAPA-5ArsS3a8f819k>
Subject: Re: [Add] Proposed charter and BoF request for IETF 106
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: Wed, 09 Oct 2019 18:04:32 -0000

On Wed, 9 Oct 2019 at 18:15, Paul Wouters <paul@nohats.ca> wrote:

> On Wed, 9 Oct 2019, Eric Rescorla wrote:
>
> > You're misunderstanding me. I'm not saying that we should not enable
> network operators to shift to encrypted transport.
> > As I said in the section of my message that you cut, I'm more than happy
> to have the IETF standardize a mechanism for
> > the network to tell endpoints that it supports encrypted transport. I'm
> merely observing that this does not address the
> > issue that Mozilla is trying to address with our DoH/TRR deployment.
>
> And it seems doing this at the DHCP / Captive Portal level is enough. I
> don't see the need for a WG to be spun up for this.
>

DHCP is not a secure way to discover the local DoT/DoH server.

-Tiru


>
> Paul
>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>

v2.23.0 | Report a Bug | By Email