Thanks.
Adding a example as a text is a little complicated.
Adding examples as a table is good ? or too large ?
Delegation | Parent | Name Server Name | Type
| Zone | |
------------+--------+--------------------+------------------------------
com | . | a.gtld-servers.net | in-bailiwick / sibling domain
net | . | a.gtld-servers.net | in-bailiwick / in-domain
example.org | org | ns.example.org | in-bailiwick / in-domain
example.org | org | ns.ietf.org | in-bailiwick / sibling domain
example.org | org | ns.example.com | out-of-bailiwick
example.jp | jp | ns.example.jp | in-bailiwick / in-domain
example.jp | jp | ns.example.ne.jp | in-bailiwick / sibling domain
example.jp | jp | ns.example.com | out-of-bailiwick
--
Kazunori Fujiwara, JPRS <fujiw...@jprs.co.jp>
> From: George Michaelson <g...@algebras.org>
> feels like a concrete example in a.b.c.example.com terms would help
> define both in-baliwick, and out-of-baliwick, for the cases.
>
> On Wed, Dec 13, 2017 at 9:42 PM, <fujiw...@jprs.co.jp> wrote:
>> Thanks.
>>
>> terminology-bis-08:
>> | In-bailiwick: An adjective to describe a name server whose name is
>> | either subordinate to or (rarely) the same as the zone origin.
>>
>> Ok, In-bailwick in terminology-bis-08 may be restrictive because "the
>> zone origin" is unclear. I intended that "the zone origin" is the zone
>> origin of parent zone. The sentence needs more words.
>>
>> NEW
>>
>> In-bailiwick: An adjective to describe a name server whose name is
>> either subordinate to or (rarely) the same as the origin
>> of the zone that contains the delegation to the name server.
>>
>> ... bad english text ... please fix.
>>
>> --
>> Kazunori Fujiwara, JPRS <fujiw...@jprs.co.jp>
>>
>>> From: Mark Andrews <ma...@isc.org>
>>> The text for "in-bailwick" is too restrictive, it doesn’t just cover NS
>>> records or
>>> glue records.
>>>
>>> In-bailwick refers to records that in the normal course of DNS resolution
>>> would have been requested of by the server the current response is from.
>>> e.g. if you are querying a .com server then all records in the response
>>> that end
>>> with .com are in-bailwick.
>>>
>>> Mark
>>>
>>>> On 5 Dec 2017, at 5:27 am, Paul Hoffman <paul.hoff...@vpnc.org> wrote:
>>>>
>>>> Greetings again.
>>>>
>>>> Some of the new terms added to the terminology-bis draft
>>>> (https://datatracker.ietf.org/doc/draft-ietf-dnsop-terminology-bis/)since
>>>> RFC 7719 can be a bit tricky. This week, we hope you will look at the
>>>> definitions in the draft for:
>>>> - In-bailiwick
>>>> - Out-of-bailiwick
>>>> - In-domain
>>>> - Sibling domain
>>>> Please review these terms and comment on the list if you think the
>>>> definitions should change.
>>>>
>>>> --Paul Hoffman
>>>>
>>>> [[ As a reminder, we asked the following last week, but got no reply: For
>>>> the past many versions of the terminology-bis draft
>>>> (https://datatracker.ietf.org/doc/draft-ietf-dnsop-terminology-bis/),
>>>> Section 2 has definitions of "Global DNS" and "Private DNS", based on the
>>>> facets listed in "Naming system". This was discussed heavily on the list
>>>> earlier, but it is also a pretty big change, so we want to be sure that it
>>>> is what the WG wants. Please review these terms and comment on the list if
>>>> you think the definitions should change. ]]
>>>>
>>>> _______________________________________________
>>>> DNSOP mailing list
>>>> DNSOP@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dnsop
>>>
>>> --
>>> Mark Andrews, ISC
>>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>>> PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
>>>
>>> _______________________________________________
>>> DNSOP mailing list
>>> DNSOP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dnsop
>>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
