IETF Logo Mail Archive

Re: [dbound] BoF request for IETF 115

Tim Wicinski <tjw.ietf@gmail.com> Thu, 22 December 2022 17:34 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0728CC14F720 for <dbound@ietfa.amsl.com>; Thu, 22 Dec 2022 09:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTw7JibIjLfx for <dbound@ietfa.amsl.com>; Thu, 22 Dec 2022 09:34:11 -0800 (PST)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9028C14F74B for <dbound@ietf.org>; Thu, 22 Dec 2022 09:34:11 -0800 (PST)
Received: by mail-ed1-x52b.google.com with SMTP id e13so3882339edj.7 for <dbound@ietf.org>; Thu, 22 Dec 2022 09:34:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=77phlcAT7fTkSSI86+VX9uBeisjhFr1+OP97/P81dcI=; b=TtROsQuxAzqS71kmCDEAr4iR102QxSzUVpXYJWZyYtddK/yrWn7l1zYCWx1t+wPUOy 0J8w8BsdS4to5FyPuWwrToykbNvLagQoYTcC9RKVhV9N829/wotWgbqsBudKzrg3h2fR PCuPL3pnnJY8m937I27HahJ5EmpPGXNpfzpzzN/YCbIvZDPPJ59MkV4yvWQpsFOGgh7G h2aFVmetI/ZYVI+vTiFKrJWAgbxhcWBnyerLXy+v14kY3A7YVVHDowZQNRGJ4NubjrEg VW3AdIy7/4pi6Atdc29t5pK1/crFimJn66A7gO6vHaF3tg7E4iwd4sWgdGZYK8H4Pui+ Xz2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=77phlcAT7fTkSSI86+VX9uBeisjhFr1+OP97/P81dcI=; b=OoTFPEwrzUNWvsHe/tdsqioh4LkWVofpFnhu5rVR58+5f939i8S2fq7VchSnael9f5 MMCMNQjS5liV8pr+6Fwh4vJTu71M7k7HbNAPcPoum0fLJQtl0+NnAfo0R14aVsPIKFpD nJcvUtfJy9GNGtr1YugBGREz+F1qDVusk3s5i7sriXqlQsTG3WV/Iz2rKovePXBQCjJr e6q55wahKqZHwIkkYxuY7647p1RwlQUEeRuj8+U8PSBOsu9sstfcS/WE64t+uMeKFeds 3VfR1qgL5TgxEye/vlEIiT1upD10fzsVI1nq0+kHA0F3JRpuJfj+dPYJffdIJFCgGyJD lk4A==
X-Gm-Message-State: AFqh2kpmBkuQhSbpv2M059YAnVg10c39yzTa9cVlWQvm+tyumD4pZecn K//uhRJGDx5Ef+eObWpTIxLG1oLtavvWSRTJmzITnrEq
X-Google-Smtp-Source: AMrXdXux6J8UrqmXAVcgalnBR5CrrBxlleC1UP30l99nYT0RNOl0xOgcquw9uLbeGBLb80p/t7OHoWYjXNt1Rhs63o0=
X-Received: by 2002:aa7:c249:0:b0:47d:71a6:da61 with SMTP id y9-20020aa7c249000000b0047d71a6da61mr537196edo.81.1671730449717; Thu, 22 Dec 2022 09:34:09 -0800 (PST)
MIME-Version: 1.0
References: <CAL0qLwaePPropS=uijZ5iu5xJN=4PabY-F_hCG-MQ68+dwX3Bw@mail.gmail.com> <20221221185656.AD56856D7051@ary.qy> <7B0AA07F-29DD-4834-A32C-C3E48E181CBA@amazon.com> <c52ade51-b30d-ff5c-2f6b-800227452978@taugh.com> <CADyWQ+FcbfNTEB0LpZEriwUw1JC6ropFVrFEomGi0Q-2vMtJsg@mail.gmail.com> <52da7db1-530e-fa42-a6f4-c6ec055adafb@taugh.com> <C147CF80-4753-48AB-8091-4120DA640F78@amazon.com>
In-Reply-To: <C147CF80-4753-48AB-8091-4120DA640F78@amazon.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 22 Dec 2022 12:33:58 -0500
Message-ID: <CADyWQ+EP_J7bgNdJ4KOPawJvOOrsgv0gH888XFRw0DwvQqaudA@mail.gmail.com>
To: "Vixie, Paul" <upavixie=40amazon.com@dmarc.ietf.org>
Cc: John R Levine <johnl@taugh.com>, "dbound@ietf.org" <dbound@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009d9d4805f06e130a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/voLkVY5Mzna8bwC7s-UsURJNnVk>
Subject: Re: [dbound] BoF request for IETF 115
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2022 17:34:16 -0000

On Thu, Dec 22, 2022 at 12:10 PM Vixie, Paul <upavixie=
40amazon.com@dmarc.ietf.org> wrote:

> See inline.
>
> --
> Paul Vixie
> VP & Distinguished Engineer
>
> -----Original Message-----
> From: John R Levine <johnl@taugh.com>
> Date: Wednesday, December 21, 2022 at 19:59
> To: Tim Wicinski <tjw.ietf@gmail.com>
> Cc: "dbound@ietf.org" <dbound@ietf.org>
> Subject: Re: [dbound] BoF request for IETF 115
>
>     There's a different much harder but potentially more interesting
> problem,
>     how can you tell that two sibling are under the same management, with
>     typical examples being google.com, gmail.com, and 1e100.com.  I don't
> know
>     any way to do that without needing vast numbers of new RRs all over
> the
>     DNS tree.
>
> I think similarity in the SOA RNAME, or the content of an apex RP RR (*),
> could be used by zone administrators who wanted that level of
> organizational transparency. Most zone administrators in today's Internet
> do not want that kind of transparency since it might increase their
> accountability.
>
> If some team wants to work on this I think that's great. I agree to review
> drafts if so. But that's a separate topic from the driving forces behind a
> WG restart for DBound.
>
> (*) https://www.rfc-editor.org/rfc/rfc1183#section-2.2
>
>
This is good to know. But I feel like I'm lacking very concrete examples.
Can y'all create some specific examples ?
I apologize, it would clarify in my mind.

tim

v2.23.0 | Report a Bug | By Email