| | At Large Membership and Civil Society Participation in ICANN |
|
| |
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
|
Anonymous ICANNwatch Messages Considered Harmful?
|
Log in/Create an Account
| Top
| 65 comments
|
Search Discussion
|
|
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
|
 |
It's pretty much standard language out of ARIN, RIPE, APNIC, LACNIC and ICANN that IP addresses (and the blocks that hold them) are not owned. Of course that's merely an assertion.
But I have rarely heard anyone claim that an IP address is required to be unique and that folks are legally prevented from creating local instances of an address. It is an axiom of faith that the acceptance of routing information is purely voluntary, the fact that packets reach your block is merely an aspect of that voluntary acceptance of routing information by most, if not all, ISPs and not a necessary result of the allocation of a netblock to you.
What I hear you claiming is that anyone who sets up a DNS server at the f-root address is somehow engaged in a legally actionable misrepresentation. If so, who is being harmed, the user or the f-root "owner"? And what is that nature of that harm?
You claim it is an "unlawful communications intercept" to have a local instance of the f-root server address? That is a rather bold assertion that makes many assumptions. The first is that somehow the packet was intended for the f-root server as opposed to simply one of a class of fungible servers that offer authoritative answers to root zone queries. The second is that it is an "intercept", much less that it is "unlawful" (which of course raises the question of "under the laws of what jurisdiction?")
The root servers are a wonderful service - and I thank you for your contribution. But your claim of ownership is quite a reach. And as a member of the internet community, the apparent lack of information regarding the financial condition underlying the continued operation of the f-root group is troublesome (it would be useful for you to post the IRS 990s, which are, public documents.)
Your claim that there shall be no DNS service on 192.5.5.241 except yours strikes me as a landgrab not much different than Versign's Sitefinder - it is an assertion of private power over a privileged spot in the internet infrastructure.
What you are claiming is that internet users are not to be allowed to route around your service. You are the beneficiary of a conjunction of voluntary routing decisions. You seem to now be demanding that such decisions are no longer voluntary but must be coerced in your favor. That is something that I do not accept as a good thing for the internet nor do I see any legal throries that would support such a claim.
|
|
|
|
[ Reply to This | Parent
]
|
| |
|
|
|
Here are the 13 public-domain root server addresses.
128.63.2.53
128.8.10.90
192.112.36.4
192.203.230.10
192.228.79.201
192.33.4.12
192.36.148.17
192.5.5.241
192.58.128.30
193.0.14.129
198.32.64.12
198.41.0.4
202.12.27.33
Here are the /24 sub-nets from the above.
Note: You just place a zero at the far right.
128.63.2.0
128.8.10.0
192.112.36.0
192.203.230.0
192.228.79.0
192.33.4.0
192.36.148.0
192.5.5.0
192.58.128.0
193.0.14.0
198.32.64.0
198.41.0.0
202.12.27.0
The 13 sub-nets above then supply a large number
of resources to the DHCP server to hand out
individual addresses. The single addresses for
the root servers are not part of the DHCP
allocations. They get aliased on to one (or
more) local server that knows about all of the
TLD servers. All of the root server traffic
then becomes routed locally. It never leaves
the physical location or country. For third-world
countries where band-width is expensive, serving
the root server traffic locally saves a lot of
money and frees up band-width.
Rather than use 10.*.*.* or 192.168.*.* for
fire-walled networks, it is better to use real
IP addresses. The major carriers are starting
to use addresses like 10.*.*.* for internal
network fabric addressing. In many respects,
this is a reversal, the 10.*.*.* addresses,
once used at the edge are now moved to the
core and the public-domain root server sub-nets,
once viewed as being at the center, are now
any-casted in millions of locations around the
edge.
|
|
|
|
[ Reply to This | Parent
]
|
| |
Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their
respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com
|
