"Jeroen" == Jeroen Massar <jeroen@unfix.org> writes:
Jeroen> RFC's are still Request For Comments, not Standards, Some RFCs *are* standards and get labelled as such. Sadly 2826 isn't one of them. :-( Jeroen> nevertheless anyone can choose to use any infrastructure, Jeroen> rootserver, firewalling policies, routing policies and a Jeroen> whole lot of other politics that that person/organisation Jeroen> whishes to follow. For that matter if someone would setup Jeroen> his/her/it's own RIR and started giving out IPv4 or IPv6 Jeroen> addresses, who is going to stop you? That it won't Jeroen> interoperate with what most of the people on this globe Jeroen> call 'the internet' is another question, but isn't that Jeroen> their problem? Not really. Granted, they have the lion's share of the problems. But those problems won't stop at the boundary of their net. For example, a bogus TLD will leak out to people on the real internet, links on web pages can't be resolved (or point elsewhere), users get confused, mail gets bounced or treated as spam, etc, etc. Once that happens, bogus root servers and suchlike become a serious problem for the helpdesks and support people at ISPs on the real internet. If only there was a Protocol Police to deal with these impostors.
On Wed, Oct 13, 2004 at 09:55:18AM +0100, Jim Reid <jim@rfc1035.com> wrote a message of 26 lines which said:
links on web pages can't be resolved (or point elsewhere), users get confused, mail gets bounced or treated as spam, etc, etc.
Keep cool. With firewalls, intranets and split DNS, all these things already happen daily (and create problems for the poor guys at the support).
If only there was a Protocol Police to deal with these impostors.
A Police dealing with every broken implementation spotted in the wild? How long will they work, 48 hours a day?
participants (2)
-
Jim Reid -
Stephane Bortzmeyer