Il 26/01/2014 18:30, Roland Perry ha scritto:
my intention was not to use the example.com "technical background"
such as the real NSs operated by IANA.
Except your diagrams quote "a.iana-servers.net" as the NS, which is
where the potential for great confusion kicks in.
That's right, the diagram on page 6 uses the real authoritative
nameservers for example.com, because there I show how really example.com
works.
In the rest of the document I used the example.com in other scenarios
too, many of them fictitious (blog.example.com, criminal.example.com),
just for the purpose of describing the specific situation.
I think a suitably-chosen example would be much less difficult for the
non-experts (they won't go away with the impression that IANA runs
everyone's NS).
Would not this just move the problem toward the new domain's registry
and NSs? If the impression that the document gives is this, maybe
something else should be changed too.
Choosing an example isn't easy (if it was, I'd have suggested one
already). In a perfect world we'd have Ripe-NCC set up a dedicated one
with the desired characteristics for us. (Something like
target-domain.org, with three NS in different parts of the world, none
of them on I* networks.)
A RIPE-NCC members feedback would be greatly appreciated on that! :)
P.S.: in the meanwhile I fixed two typos on diagrams of page 13 and 15:
blog.example.com instead of blog.www.example.com.
--
Pier Carlo Chiodi
http://pierky.com/aboutme
The opinions expressed here represent my own and not those of any
organization, entity or committee to which I may hold a position.
