IETF Logo Mail Archive

Re: [Add] I-D Action: draft-reddy-add-enterprise-split-dns-08.txt

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 23 January 2022 18:09 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 7CB233A2418 for <add@ietfa.amsl.com>; Sun, 23 Jan 2022 10:09:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=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=sandelman.ca
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 yRuN6zV84OD3 for <add@ietfa.amsl.com>; Sun, 23 Jan 2022 10:09:34 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5384C3A2416 for <add@ietf.org>; Sun, 23 Jan 2022 10:09:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 717F438A17; Sun, 23 Jan 2022 13:16:09 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vqCx7kDiJm6J; Sun, 23 Jan 2022 13:16:07 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F282C38A16; Sun, 23 Jan 2022 13:16:06 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1642961766; bh=t3onV+rxBSPQ8vbT19lsIlpnVN7PioLwNUbDwpbuyn0=; h=From:To:Subject:In-Reply-To:References:Date:From; b=ku88CWMb2KmtAWsoBw3t3vn2IQr3HXvL4YUbHGd4xPUBfcGrESnKzyIjubiR4s6g1 GVqQCuY62XeT6HBJC+pE3kWVB+k3YxdHQPK8ABMlOFKyYnYpNFwJf0DaYkXYRbhoUG h+7oNRgQh//XdtCTw7jimn7BbE1DChfk98WuFoNez6+XNCtI9pUBegYXIe/YiQ76gm vR9U7LAM4iyqVjyWOI8XkMhwezm+P2RD0XdvDK1og1lzXpr/Y70XGVQTdHa+0NMsuz UW1el9YIXf226i4r2SqS68oacTtWbkESZ8Ivi1TKu6bfqJox7jRLvwK09Awb1k0GnF mFPTuaeZZd/YQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 18DB64EE; Sun, 23 Jan 2022 13:09:29 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Paul Wouters <paul@nohats.ca>, tirumal reddy <kondtir@gmail.com>, ADD Mailing list <add@ietf.org>
In-Reply-To: <4182fe-1e8-ef1-d3e5-75b17da23b9e@nohats.ca>
References: <164273967921.28045.13105308218406662743@ietfa.amsl.com> <CAFpG3geerJH+jWEZpZnHJpEFcOr+81WyOFvWoAaHmR6N4jBZyg@mail.gmail.com> <4182fe-1e8-ef1-d3e5-75b17da23b9e@nohats.ca>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 23 Jan 2022 13:09:29 -0500
Message-ID: <32384.1642961369@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/WjXgKDjl_cJOwanjNTFUWVKIZxg>
Subject: Re: [Add] I-D Action: draft-reddy-add-enterprise-split-dns-08.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: Sun, 23 Jan 2022 18:09:40 -0000

Paul Wouters <paul@nohats.ca> wrote:
    >>    *  Restricted the scope of the document to split-horizon DNS names

...

    > I am not sure if reducing the scope of split-dns is the way forward. A
    > lot of split DNS is specifically for internal only domains, so I feel
    > this document is now going to be very confusing for offering a
    > split-dns solution without actually offering a split-dns solution.

I agree with you strongly.
Since ADD has determined that explaining split-dns in a normative fashion is
out of scope, would it be reasonable to ask DNSOP to do that?

I don't see how we can proceed without a clear consensus on what the various
split-dns methods are.  We at least, need some names.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email