IETF Logo Mail Archive

Re: [DNSOP] Terminology question: split DNS

George Michaelson <ggm@algebras.org> Mon, 19 March 2018 18:10 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C14F12D95B for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 11:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=algebras-org.20150623.gappssmtp.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 KnhWb6bNwO6p for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 11:10:17 -0700 (PDT)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (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 41C4B127369 for <dnsop@ietf.org>; Mon, 19 Mar 2018 11:10:17 -0700 (PDT)
Received: by mail-qt0-x233.google.com with SMTP id q11so13235328qtl.9 for <dnsop@ietf.org>; Mon, 19 Mar 2018 11:10:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ivuCJs2IZfbzS1XqMQW98JC79ZG8szXu9+3ry1qQ1Lw=; b=WPNn2q1fSvnCMMu2UNo/B4jtQupz6wWsOm9BgJ2nDwEorNpOGUYsJkCIeuYaTOh4aO 5d5jBzjNoCwkd9IElCSf4zi6Tz6ctZGIUA3vy77rIUksGSAULqAxZ97ASJJ0440f4ILG 9iwYqiQFMBPc+ahtxr9zrWLwCK99U7sHFjybQHE0w0UdvLyYzkEf7jq+bc5idBdY2F1e R4oBbyBw4mZmZqtVKgImmHR15Lry33dldGE+wh8HTFyzwKpCEKs3auOlb+fwLgpoKScH gqeQ6XiW3shDYyEwWG0WvOqM4pYg+opRxHMOkYB3EJZBUVvqIlI2sekjyiqd0Kvyywb8 /FJQ==
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=ivuCJs2IZfbzS1XqMQW98JC79ZG8szXu9+3ry1qQ1Lw=; b=B00LyFfv6lRSIIK7BNXUjsvAHDUBhfTC4SQuqpysrpn56LrNB7ptOK9XmEcPWcInLx TF6U4/siKLssoi7O78JIrR25O7vqGGd2IigooY4rqpjACRNiIITA22l46J3NkkJxSdSI Rm3GA/CJ0KjKCfbA4RyokQL1GYBhHOkT0hvcxtybBGwmGyiTNTkBtrt9C61rIjCDHAY2 75IBGb6Pi0kVVs00nlj4L0tAb229k83eRd5RVXE5MSZNjf+HwFd4kHo9CN20cKdcAbrO SzidwkNdTMkl0xJqrsSEAfILx4ZGtwKjpEEsVVppJsG3y//Swz9WJBVKLeTxBWYU8C5V 4hwg==
X-Gm-Message-State: AElRT7HnaG3TLiAPLa1mz44zXOJlb4FbnApy6aPMxZo/fyaj/mg97oxd qn/Stc7h736qtJoTPmLxs7vQ/ver7DSPdTcdDnn2FtyTl8Y=
X-Google-Smtp-Source: AG47ELtx0A0lJsHwypu86JoU+Blj3aYZuCczfn0Ld0bnud+NA7boUTpxR6FGvBzKdCNQYLmXrW9TqvL5n/Pt5Rg5jvA=
X-Received: by 10.200.49.99 with SMTP id h32mr19429351qtb.299.1521483016365; Mon, 19 Mar 2018 11:10:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.55.57 with HTTP; Mon, 19 Mar 2018 11:10:15 -0700 (PDT)
X-Originating-IP: [2001:67c:370:128:7cdb:5bd4:43dc:d1f8]
In-Reply-To: <3D490CA8-0733-47AD-A088-113B1116B207@vpnc.org>
References: <3D490CA8-0733-47AD-A088-113B1116B207@vpnc.org>
From: George Michaelson <ggm@algebras.org>
Date: Mon, 19 Mar 2018 18:10:15 +0000
Message-ID: <CAKr6gn0RrJEzLCg-nzmwpY7R4XUtRXudQZWdgpz2Vt3X1+BL4Q@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/loKZ6GmLHFjXCdhIBMOV3n64jRE>
Subject: Re: [DNSOP] Terminology question: split DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 18:10:22 -0000

"A DNS resolver which looks at the client requesting address, and uses
this to serve different versions of information about a zone based on
which client address or prefix requests it."

the concept of "side" is rather limited. split DNS can encompass more
than two sides can't it?

-George

On Mon, Mar 19, 2018 at 5:47 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> Some folks had reservations about the current definition of "split DNS":
>    "Where a corporate network serves up partly or completely different DNS
> inside and outside
>    its firewall. There are many possible variants on this; the basic point
> is that the
>    correspondence between a given FQDN (fully qualified domain name) and a
> given IPv4 address
>    is no longer universal and stable over long periods."
>    (Quoted from <xref target="RFC2775"/>, Section 3.8)
>
> What would the WG like for this definition?
>
> --Paul Hoffman
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

v2.23.0 | Report a Bug | By Email