On Thu, Nov 30, 2017 at 01:36:00PM +0100,
Martin Hoffmann <mar...@opennetlabs.com> wrote
a message of 297 lines which said:
> GLOBAL DNS -- FORMAT OF NAMES
>
> | Names in the common display format are normally written such that the
> | directionality of the writing system presents labels by decreasing
> | distance from the root (so, in both English and C the first label in
> the | ordered list is right-most; but in Arabic it may be left-most,
> depending | on local conventions).
>
> The first sentence makes it sound as if right-to-left languages would
> normally write ‘com.example’ which is not the case.
BiDI is complicated enough so I suggest we keep only examples where
the script of the domain name is the same as the parent script. This
way, sentences like "The TLD is at the end" are always true. Writing a
latin domain name in arabic is left as an exercice for the reader :-)
> under these circumstances the name will always be in the ‘usual’
> order.
I challenge this assumption. After all, numbers in arabic are
sometimes big-endian and sometimes little-endian (depending on wether
you are in the Middle-East or in North Africa).
> PRIMING
>
> This comes a bit suddenly. Maybe it should start with a short
> introduction a la ‘In order to operate in recursive mode, a resolver
> needs to know the address of at least one root server.’
IMHO, the reference to the excellent RFC 8109 is sufficient.
> PASSIVE DNS
>
> | A mechanism to collect DNS data by storing DNS transactions from name
> | servers. Some of these systems also collect the DNS queries
> associated | with the responses.
>
> I don’t think it has been defined yet, but the term ‘transaction’
> commonly refers to a pair of a query and its response (plus possibly
> any re-sent queries or responses due to packet loss). With this in
> mind, the second sentence doesn’t quite make sense.
I agree and I suggest this text:
Passive DNS: A mechanism to collect DNS data by storing DNS
responses from name servers. Some of these systems also
collect the DNS queries associated with the responses, although
it raises some privacy concerns. Passive
DNS databases can be used to answer historical questions about DNS
zones such as which values were present at a given time in the
past, or when a name was spotted first. Passive DNS databases allow
searching of the stored records
on keys other than just the name and type, such as "find all names
which have A records of a particular value".
> IN-BAILIWICK
...
> Also, on behalf on non-native speakers, a short explanation of the
> origin of the term would perhaps be nice.
I like the Wiktionary (and it can be copied freely into a RFC):
Etymology
>From bailie (“bailiff”) and wick (“dwelling”), from Old English wīc.
bailiwick (plural bailiwicks)
The district within which a bailie or bailiff has jurisdiction.
The Bailiwick of Jersey.
A person's concern or sphere of operations, their area of skill or
authority.
Synonyms
(area or subject of authority or involvement): domain, department,
jurisdiction, sphere, territory, turf.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
