IETF Logo Mail Archive

Re: [Doh] operational issues with doh

Patrick McManus <pmcmanus@mozilla.com> Tue, 31 October 2017 19:48 UTC

Return-Path: <pmcmanus@mozilla.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 9164713F612 for <doh@ietfa.amsl.com>; Tue, 31 Oct 2017 12:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.601
X-Spam-Level: **
X-Spam-Status: No, score=2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SBL_CSS=3.335, RCVD_IN_SORBS_SPAM=0.5, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 ViwpBizi-Hfd for <doh@ietfa.amsl.com>; Tue, 31 Oct 2017 12:48:01 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 23FFD13A302 for <doh@ietf.org>; Tue, 31 Oct 2017 12:48:01 -0700 (PDT)
Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) by linode64.ducksong.com (Postfix) with ESMTPSA id 415A03A0AA for <doh@ietf.org>; Tue, 31 Oct 2017 15:47:57 -0400 (EDT)
Received: by mail-lf0-f43.google.com with SMTP id e143so125248lfg.12 for <doh@ietf.org>; Tue, 31 Oct 2017 12:47:57 -0700 (PDT)
X-Gm-Message-State: AMCzsaWbGa+ea86gzlhERKYe3jQV+DUTO2I/Rv3OtMoj8hMYV2CdJ6WY fqlqZWa1EHC11JPfGGssJMfMR+nzy2iwx4eF7P8=
X-Google-Smtp-Source: ABhQp+QBCwGEKEE89BBsq6sHWiDP0WYgiOLi8KLZzs5zvRhdsdz4pj5dLQCQj9Sj+6EISLUv8G8jy9WQZu9hyZOrWEY=
X-Received: by 10.25.223.83 with SMTP id q19mr1198988lfj.104.1509479275945; Tue, 31 Oct 2017 12:47:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.21.22 with HTTP; Tue, 31 Oct 2017 12:47:55 -0700 (PDT)
In-Reply-To: <abe6593a-0bc9-9ed4-4ad4-c03093bcb490@cisco.com>
References: <abe6593a-0bc9-9ed4-4ad4-c03093bcb490@cisco.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Tue, 31 Oct 2017 15:47:55 -0400
X-Gmail-Original-Message-ID: <CAOdDvNoSONY2NkdzPYpSq=6sUWMo3Y3HJigWBWZpx9MDRcrr4Q@mail.gmail.com>
Message-ID: <CAOdDvNoSONY2NkdzPYpSq=6sUWMo3Y3HJigWBWZpx9MDRcrr4Q@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: doh@ietf.org
Content-Type: multipart/alternative; boundary="f403045e381609e9b4055cdd08a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/nioz-ZaGMXIJTKuTnGhhSSuFSYU>
Subject: Re: [Doh] operational issues with doh
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: Tue, 31 Oct 2017 19:48:02 -0000

I think I would prefer a separate document if people were interested in
working on that.

On Tue, Oct 31, 2017 at 2:57 PM, Eliot Lear <lear@cisco.com> wrote:

> Hi everyone,
>
> Just to follow up on the lengthy discussion that took place during
> chartering, there are some operational issues that use of doh can
> create, particularly with regard to load balancers and split DNS.  Do
> those go into the draft or do they go into a separate doc?  It's quite
> possible they can be mitigated against, and if they can be, and if the
> text isn't too long, can I suggest that we start out by having some text
> in the draft, and if it starts to get lengthy we split it off?
>
> Eliot
>
>
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>
>

v2.23.0 | Report a Bug | By Email