IETF Logo Mail Archive

Re: [DNSOP] Bailiwick discussion for draft-ietf-dnsop-rfc8499bis

John Levine <johnl@taugh.com> Thu, 07 October 2021 02:00 UTC

Return-Path: <johnl@iecc.com>
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 D5B3E3A082F for <dnsop@ietfa.amsl.com>; Wed, 6 Oct 2021 19:00:55 -0700 (PDT)
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, HEADER_FROM_DIFFERENT_DOMAINS=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=iecc.com header.b=eZXauzKP; dkim=pass (2048-bit key) header.d=taugh.com header.b=XNvnlwpY
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 j0AbdXMStVn1 for <dnsop@ietfa.amsl.com>; Wed, 6 Oct 2021 19:00:50 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46AB83A082C for <dnsop@ietf.org>; Wed, 6 Oct 2021 19:00:49 -0700 (PDT)
Received: (qmail 54387 invoked from network); 7 Oct 2021 02:00:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=d471.615e54d0.k2110; bh=+LNCouvWfC9KKEb5bbfyjYt0qh9MXf08ALhQESl3OTo=; b=eZXauzKP3jvW09gGJdw+zWA5OkcOOL41rvYUFl5xudggptr5oTKOGPZWOycyH7i3WDElrwGaau3kbMN/F8jUAc49cGEDa3uranC2aAeXNEarHxz9okAQAH776gXTatRXPoDRKjZ/pDQoSf/wfYTuE+Mm81N4bDuYtXnW0j4hdH86/isgHU47TfbKKqGOUDI/fci2JaM7CQrpPk5dp39UhwIkeJdYjjJ6ixzSIZ0ei4PuzCUKwlblSDUOpRITL9sRh9s+iIfnCPN7O9EkDQkVPCumQcMA1fxAKPPZ/+aa07/X2Qfx19M3+t026dB86c/xtEe8RjdDKXJLgXKqfs+gBA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=d471.615e54d0.k2110; bh=+LNCouvWfC9KKEb5bbfyjYt0qh9MXf08ALhQESl3OTo=; b=XNvnlwpYTfP0YZQuUQuf2FR6La1lTGABRluruxKdjO88QEldSn6rbMDd81rwJ/7VOfnFMQR75FDnoXR/EeJeta/raRzG7zFHBngq15FNYMcNxODztg3QQ1vgMkCanICh5uFm2MmyPP8KL8uBqE0JRWvMUxoJeHrtMPz6V/NFy6f4d5LUDB1oxNNHFkQdk+NJNNWJRd3r6Hz2kH5Z2hpDKXKshTm3/vs8WC6f7JA5Il9CTmv2ENn8QqXhfse0UX4vIbzHrL6eC05Slzp+uJEE61w/xeo0iaWN5R0+zsGQZu2ZkFr5JjdXpC4X2c4Y8mangAmTe3i3BomHhRpzGDZFog==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 07 Oct 2021 02:00:47 -0000
Received: by ary.qy (Postfix, from userid 501) id 8F7EB29DE2F1; Wed, 6 Oct 2021 22:00:47 -0400 (EDT)
Date: Wed, 06 Oct 2021 22:00:47 -0400
Message-Id: <20211007020047.8F7EB29DE2F1@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
Cc: paul@nohats.ca
In-Reply-To: <bb61304c-6ef9-7850-3dbb-19b624bc07b@nohats.ca>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/djYOSUdcR40d_-FFg8QpiA2sna0>
Subject: Re: [DNSOP] Bailiwick discussion for draft-ietf-dnsop-rfc8499bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Oct 2021 02:00:56 -0000

It appears that Paul Wouters  <paul@nohats.ca> said:
>The suggestion by Tony Finch:
>
>   * Sibling zones: two zones whose delegations are in the same
>     parent zone.
>
>   * Sibling glue: addresses of nameservers that are in a sibling zone.

So far we agree (which when it's Paul and me, is really saying something.)

>     Sibling glue is usually the glue that the DNS would require for that
>     sibling zone, but in some cases the requirement lies elsewhere, ...

This is where we always go off the rails.  There seem to be two mutually
exclusive interpretations of sibling glue:

1 - it's a small and entirely optional twiddle to speed up or skip
recursing into the sibling zone

b - it's an essential part of the response because it's the only way to
resolve a reference loop.

I've already said my piece about which of these makes sense and which is a cruel
joke, but if we're going to talk about sibling glue at all, we need to decide
which one we mean.

R's,
John

v2.23.0 | Report a Bug | By Email