IETF Logo Mail Archive

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

Michael Richardson <mcr@sandelman.ca> Mon, 24 January 2022 17:36 UTC

Return-Path: <mcr@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 974EE3A0D2C for <add@ietfa.amsl.com>; Mon, 24 Jan 2022 09:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 p47RxVMwncfn for <add@ietfa.amsl.com>; Mon, 24 Jan 2022 09:36:09 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73DC63A0D2B for <add@ietf.org>; Mon, 24 Jan 2022 09:36:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D899D389FF; Mon, 24 Jan 2022 12:42:47 -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 68Vl4bLuLsYS; Mon, 24 Jan 2022 12:42:47 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 28880389FE; Mon, 24 Jan 2022 12:42:47 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1643046167; bh=D3WJuUCaB3LyUzq3VnTeIn7yq8aEy3aq7Pmdgq5ck5k=; h=From:To:Subject:In-Reply-To:References:Date:From; b=GM9FdD2VL77UJHG0xlXZxnsojVgdh2jbQ8qgqHNHUE2/Wstp4jzF1blfh2HizUKAu kjBWmco8aAsjfW6brqkO18mvBmRhhoaxjAZ5ICHe9C/IsS3rY4MuFJrHKycLqOv2dk 6HiQN0kVJZzdZ4ih0L7aVVLuzsM4GBREu532OUE6kHeO4FsB/gdH88IpRSIPes8loi 7GEbIK6obCrJsaMrgMzt7TgYkWFRj+PqwW5Od4D22Yl7z69wX8SMW+ij71y7rU19Q3 E2fP0VyTi30HUkSG5PdkUAozqTVyjFrQml0IbsJkRgjvyU3bB9inf0v/zDQYFAnFYR Jajp4CmtLeCLA==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8E8206B9; Mon, 24 Jan 2022 12:36:05 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>, ADD Mailing list <add@ietf.org>, tirumal reddy <kondtir@gmail.com>
In-Reply-To: <532c969a-8793-81a1-17c0-55ae5b21fad3@nohats.ca>
References: <164273967921.28045.13105308218406662743@ietfa.amsl.com> <CAFpG3geerJH+jWEZpZnHJpEFcOr+81WyOFvWoAaHmR6N4jBZyg@mail.gmail.com> <4182fe-1e8-ef1-d3e5-75b17da23b9e@nohats.ca> <CAHbrMsBvy6F05y+rXzS+KtpOCn4+RCcJnjLdduHfdz8ENCOQzw@mail.gmail.com> <54f568df-79ba-cc41-6337-a0f45c44344e@nohats.ca> <CAHbrMsAKAQjCZQrwTKp3_NiFh194ST54n1dOOM7WQ4ydi=yOFA@mail.gmail.com> <532c969a-8793-81a1-17c0-55ae5b21fad3@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: text/plain; charset="us-ascii"
Content-ID: <2294.1643045765.1@localhost>
Date: Mon, 24 Jan 2022 12:36:05 -0500
Message-ID: <2296.1643045765@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/Fx5fkr0KiB4v7h1MdLAglQmQQ2Q>
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: Mon, 24 Jan 2022 17:36:14 -0000

Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org> wrote:
    > On Mon, 24 Jan 2022, Ben Schwartz wrote:

    >> That is not clear from the text at all. In that case, yes you cover
    >> all the cases of split-dns but then I wonder how the external server
    >> will somehow "confirm authorization" of "corp.example.com" on the
    >> internal server if the externl server returns NXDOMAIN or REFUSED
    >> because the domain is internal only ? Especially because the
    >> connecting client is supposedly sending this query over its own
    >> trusted (encrypted) resolver to the public nameserver, reachin the
    >> public nameserver's external "view".
    >>
    >> In this case, "corp.example.com" would be publicly visible

    > You have now redefined split-dns again to be only the cases where the

No, because split-dns was never properly defined :-)

That's the IETF's fault.
We should fix this through some set of adjectives in a BCP.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email