Re: [Doh] operational issues with doh

tjw ietf <tjw.ietf@gmail.com> Fri, 03 November 2017 20:16 UTC

Return-Path: <tjw.ietf@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 6003D13FF7D for <doh@ietfa.amsl.com>; Fri, 3 Nov 2017 13:16:05 -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_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 b3kRy-taZ9uy for <doh@ietfa.amsl.com>; Fri, 3 Nov 2017 13:16:03 -0700 (PDT)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (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 86F2E13FF48 for <doh@ietf.org>; Fri, 3 Nov 2017 13:16:03 -0700 (PDT)
Received: by mail-wr0-x22d.google.com with SMTP id l8so3479903wre.12 for <doh@ietf.org>; Fri, 03 Nov 2017 13:16:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7Mjo1bacR0hkJimM1IGlxulJf+ps9RCClQT6DDXqQ98=; b=h4jK8494dtVk7uotdBkIx9G4Thq/yh9W64o0uqmw9J9Y8uAcK9LZImbbn9ZdVBh6Wh b0YYkVfuYE977h26p+8Hb8EZO/ATYS+qbjJ+0qVsl1O8JO3ZwgPuK9OS8WnLMGZPGRux FXYgNJ+V1M8wdssoo3cLE62QDJI3SZU7nYFQXBPIZ+/HXGmCKyKdD84Jk9C+Lo3zshuD cEqg7V0X/5ko8Fqb9eCmQiT4ur6plSlBlVpY670t2y18qBumS3b4eBJaV4A302+h3S7N YUT9sSOkPDrgrGzLKJYQHWmhRLls9SyUG5DoSoRUSMo+P1DDRtOejIUghWOEi7r5a/Lj t3FQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7Mjo1bacR0hkJimM1IGlxulJf+ps9RCClQT6DDXqQ98=; b=jFfOkFZlVOI3q7b0xov1H8PwnVbWE3Ug3gv4fsOqkZzfHd6V2LjwK/WVaUyhcrl/ow CBz3gMmrg8rTzHHThMIaPlj6IzKpu3O312DlCeTEVTfo4W19r9v5b0Bm8p96tzgJZLm/ Gb8yTLgkmUgO0ZFsztBUAM327Ew4Vdy+v2yTWKDx2KjyLyzXLZVIUSTfRUjzhUxXZ6RM f9ObOI5xSjryj+mHAaaqjX4x46f6hFFQ4CWkGbAcSzFjsJLn73zv1zUK6G0GFFVhXfvt tpRcz28E190A1qum0qGQPuXSTdH4c864giO7IEEwmhPOedSWY2SHvOKCfeeESO92xLHj PKVw==
X-Gm-Message-State: AMCzsaXKOD1mG6XxnIn/nGclEaQINRNm+OBOmdUxRYFFgDf+UB88aswY GqX+540ZtmIHEo+8t2k6en4QOq5VSXgl87w19NQ=
X-Google-Smtp-Source: ABhQp+QRVg6I11Eq0DHcxPtFbqHjSuI5M4gkvW+A9FqEIpsUyBRmB+yZYzSQaoaWOvEO5W56ozTJWJLz7ZC83n93/Ug=
X-Received: by 10.223.168.45 with SMTP id l42mr6706631wrc.15.1509740162138; Fri, 03 Nov 2017 13:16:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.184.60 with HTTP; Fri, 3 Nov 2017 13:16:01 -0700 (PDT)
In-Reply-To: <CAOdDvNoSONY2NkdzPYpSq=6sUWMo3Y3HJigWBWZpx9MDRcrr4Q@mail.gmail.com>
References: <abe6593a-0bc9-9ed4-4ad4-c03093bcb490@cisco.com> <CAOdDvNoSONY2NkdzPYpSq=6sUWMo3Y3HJigWBWZpx9MDRcrr4Q@mail.gmail.com>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Fri, 3 Nov 2017 16:16:01 -0400
Message-ID: <CADyWQ+H74a0ks3LTBgdYyCW2T98jDwGccKTEe6biOhA9SFrADg@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: Eliot Lear <lear@cisco.com>, doh@ietf.org
Content-Type: multipart/alternative; boundary="f403045f4c221145eb055d19c65f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/YGfAdbpobCqQS5PIO62iWyFk5Mo>
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: Fri, 03 Nov 2017 20:16:05 -0000

Agree with Patrick, this should be more of an operational considerations
document.

On Tue, Oct 31, 2017 at 3:47 PM, Patrick McManus <pmcmanus@mozilla.com>
wrote:

> 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
>>
>>
>
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>
>