ietf-asrg
[Top] [All Lists]

Re: [Asrg] Assume perfect knowledge by domain registry provisioners, so what?

2003-05-12 10:15:58
Each registry is disjoint, any exchange of data between two are either via
a policy body, e.g., registries constituency (cc or g) within ICANN, via a
community of interests, e.g., registries within the CDNC, or "accidentally"
via overlapping registrars (some registrars are registries, and vica versa).

It is an exercise left to the reader to determin the upper bounds for delay
for data nominally concerning "spam" to go from the .kr registry operator to
the joker.com .com registrar, or reverse, to take to examples simply for the
purpose of using well-known practitioners of domain name registry.

In the above para, "registry" refers to domain name registries.

To get even more disjoint, estimate the upper bound on a human-assisted
forward and/or reverse mapping, involving a domain name in a VGRS registry
with joker.com registrar, and an APNIC RIR address assignement.

To restate: in just the com/net/org/biz/info/name (cnobin) playpen, 21 of
the 100+ registrars have 92% of all registrations -- that's 24 players to
my count. Another 25 ccTLDs, with fewer than 25 distinct operators, defines
the major non-cnobin space down to the 125K threashold -- that's an additional
20 operators and their registrars, many of which are in the first cohort.
So, mild handwave, 100 actors, 100 endpoints, defines 90% or more of authors
of entries into the public DNS.

Presently these are organized into ~30 (6+25) stars, with a significant amount
of "multihoming" by registrars that act upon two or more of the ~30 registries.
There is arbitrary latency for any communication between stars, and even for
communication from a registry to a registrar (polling artifact). If this is
changed, presumably for the better, does it matter?

All data from SOTD, Q302.

Eric
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg



<Prev in Thread] Current Thread [Next in Thread>