Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis

fujiwara@jprs.co.jp Tue, 10 July 2018 15:49 UTC

Return-Path: <fujiwara@jprs.co.jp>
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 B9C4B130FF6 for <dnsop@ietfa.amsl.com>; Tue, 10 Jul 2018 08:49:07 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IN5Nn0EiDzHx for <dnsop@ietfa.amsl.com>; Tue, 10 Jul 2018 08:49:05 -0700 (PDT)
Received: from off-send01.osa.jprs.co.jp (off-send01.osa.jprs.co.jp [IPv6:2001:218:3001:17::10]) (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 D478A130DC4 for <dnsop@ietf.org>; Tue, 10 Jul 2018 08:49:04 -0700 (PDT)
Received: from off-sendsmg01.osa.jprs.co.jp (off-sendsmg01.osa.jprs.co.jp [172.23.8.61]) by off-send01.osa.jprs.co.jp (8.14.4/8.14.4) with ESMTP id w6AFn2QI027484; Wed, 11 Jul 2018 00:49:02 +0900
Received: from off-sendsmg01.osa.jprs.co.jp (localhost [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 9A5BE180064; Wed, 11 Jul 2018 00:49:01 +0900 (JST)
Received: from localhost (off-cpu05.osa.jprs.co.jp [172.23.4.15]) by off-sendsmg01.osa.jprs.co.jp (Postfix) with ESMTP id 7A509180062; Wed, 11 Jul 2018 00:49:01 +0900 (JST)
Date: Wed, 11 Jul 2018 00:49:01 +0900
Message-Id: <20180711.004901.1375169129903536717.fujiwara@jprs.co.jp>
To: vladimir.cunat+ietf@nic.cz
Cc: dnsop@ietf.org
From: fujiwara@jprs.co.jp
In-Reply-To: <2d26c4bd-6934-82e2-93b1-973035722d8a@nic.cz>
References: <17A1E6A9-E43F-41AB-B24D-4B29F17FCC07@gmail.com> <2d26c4bd-6934-82e2-93b1-973035722d8a@nic.cz>
X-Mailer: Mew version 6.6 on Emacs 24.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1690-8.2.0.1013-23960.001
X-TM-AS-Result: No-1.553-5.0-31-10
X-imss-scan-details: No-1.553-5.0-31-10
X-TMASE-MatchedRID: vMI3egdXDQ1CXIGdsOwlUu5i6weAmSDKZggZX8gYmrWObf10apLcSV8l h/2sQnVw8a9FfTFXt2nrvjIPxtOCYY+uMz+W0xT5nVTWWiNp+v9/aDoolm3GXZUQzHWBKOFAxhH 6LU2YFCX7McbkUgLlCwusH4Ftr5wCO8zsHF1nRBjhuXUWQoMQtyH2Y0Xxk8nYLO3j+XDwlkOjO0 WeR2c+ukFHF7XbDVpJokd86YtA9DNrLhXNtOJWGM/8zK5WVP8LS0iSG6xyIZc+WVT1m0MMzyrJh LSjJRVmsw7S0uQkblmnkU22CofUcYkxY/Kb2e94p+KVeca3Bbw7gpVt9VLiApJ+PGcjTlovrd6u AU77y3sLZ/tt5KWFIu7p9z1QKNZsUARAPI1OA8tkfd/zPGWwsvvpR1kNBhYY7Y82MSiAt9nKKEk fNPvzwp6oP1a0mRIj
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/33LMqWNAXueHsobHQUCRlnStbJE>
Subject: Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 10 Jul 2018 15:49:08 -0000

Thanks to Vladimír,

> From: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
> "Bailiwick" definition: I have (also) seen use like "in-bailiwick
> records" in the sense being in a subdomain.  I can't really judge how
> common that usage is, but it has already been discussed wrt. this draft:
> https://mailarchive.ietf.org/arch/msg/dnsop/MyEdXXdUKKyTTfX3_4_7AnhE3Io 
> My understanding of that thread is that the meaning was planned to be extended
> in the draft, but the current text seems still restricted to name servers.

I missed updating the part. It's too late, but if possible, I would
like to update the part a follows.

-----------------------------------------------
"In-bailiwick" is an adjective indicating that a domain name is
a subdomain of or (rarely) the same as another domain name.
"Out-of-bailiwick" is the antonym of in-bailiwick.
(The term "bailiwick" means the district or territory where a bailiff or policeman has
jurisdiction.)

"In-bailiwick" and "out-of-bailiwick" are usually used for name servers' names.
"In-bailiwick" name server is a name server whose name
is either a subdomain of or (rarely) the same as the origin
of the zone that contains the delegation to the name server.
In-bailiwick name servers may have glue records in their parent
zone (using the first of the definitions of "glue records" in the definition above).

"In-bailiwick" names are divided into two type of name server names:
"in-domain" names and "sibling domain" names.

In-domain:
sibling domain:

examples
---------------------------------------------

--
Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>