A Concise Guide to the Major Internet Bodies
alex simonelis submitted a good summary of the major internet bodies. If you hunger to know the difference between ICANN, IETF, ISOC and the rest of the alphabet soup of the governing bodies that make our beloved internet possible, this is a great place to look. It covers 10 major organizations.
Or goatse.cx for that matter.
Who is this guy kidding? The major Internet bodies my eye!
Infuriate left and right
Favorite internet bodies? Oh, so many jokes coming...
I don't think they can call this guide "concise" until they address these gaping holes...
Obliteracy: Words with explosions
It's nice to know what each organistion does, but is there an article about how they actually do it?
For instance, how (pardon my ignorance) ICANN actually controls numbers and names, technically. Is there a mainframe of some sort that stores them? How does ICANN make changes?
Rock that crushes, Paper & Scissors that don't matter.
He's a major body if ever I saw one ;)
liqbase
I wonder if the lawyers for the IANA ever abbreviate their titles to IANAL. And I wonder if that ever confuses the heck out of people.
"Hardly used" will not fetch you a better price for your brain.
The article only discussed the major bodies for just the one internet. What about the other internets? Is there an ICANN2, IETF2, and ISOC2?
Yes! I listen to NYC Speedcore and do math at 3AM. I suggest you try it too.
Ah, finally a story where a post about Natalie Portman will actually be on topic...
Wait, they don't mean that kind of internet body?
Drat.
<shameless plug>
You probably shouldn't click this.
We all know Google is the whole internet. It's like the libary index and filing system all in one, without it we're lost in a sea of knowledge without anything to sort it so we can find it.
I like muppets.
I'm a regular contributor to WTF, the most ubiquitous internet body.
A feeling of having made the same mistake before: Deja Foobar
ISOC Official Page IETF Official Page IESG Official Page IRTF Official Page IAB Official Page RFC Editor Official Page ICANN Official Page IANA Official Page W3C Official Page W3C encyclopedia article ICANN encyclopedia article IANA encyclopedia article
Creative Demolition
No one (and this article itself) has ever really objectively described the compromises/disputes between the old internet governance infrastructure and the increasingly corporate-dominated and somewhat authoritarian ICANN.
ICANN is supposed to have a standards pillar. However all internet standards are really developed by the IETF, published by the RFC Editor and adopted by the community the way that they have always been. (The exception being HTML/HTTP and its derivatives - the W3C is entirely corporate)
There's some mention here of the dispute over IANA. Back in the day, it was just Postel, and he demonstrated entire control over the root servers. But now it's really not clear who controls the root servers, allocates IP address ranges to the regional registries, and assigns other numbers. This stuff should be transparent!
My favorite guides to internet bodies are www.worldsex.com and www.thehun.net
I wonder if the lawyers for the IANA ever abbreviate their titles to IANAL.
;-)
The first few times I saw that abbreviation, I thought it was like the "I [heart] Hucklebees" thing and my browser was dropping the heart character.
Didn't know why people were so proud of it... figured it was something to do with goats
You can't take the sky from me...
Note that none of the entities discussed in the article is a major network operator - while they certainly may have their own organizational network just like any other company or organization, they dont directly operate the backbone networks. Their roles are advisory and (sort of) regulatory. To avoid any sort of appearance of favoritisim, I doubt they even get any special deals from whatever ISP they use to host their sites or connect their offices.
There is no 'center' or 'trunk' of the Internet. Every bandwidth flow is between two endpoints. Large backbone network operators generally have peering agreements (eg I'll send traffic to you that wants to go to your addresses if you agree to do the same for me, and we'll do it over the same set of wires) and either in most cases any two organizations that consider themselves to be 'peers' figure that average traffic in both directions will be the same, so they do it on a basis of each network paying for its own costs to interconnect to the other. Sometimes if the traffic is expected to be unbalanced, there will be a cost recovery clause in the peering agreement.
There are facilities known as 'peering points' that manage and operate various sorts of switched networks (FDDI, ATM, etc) that an organization can colocate routing equipment, and then have a shared 'connection' that they are able to use to peer with any other network operators that are located there. These are known as 'NAPs' - some were established back in the days of the NSF, some came later. These are about as close to the 'center' of the Internet as you can get, but they are not the center (nor is there a free ride to anywhere else from them)
Note you have to have your *own* IP addresses to peer, you announce your networks via BGP and accept announcements from your peers - you are specifically NOT allowed to use any other peer's router as your 'default route' - you can only send traffic to them that has a destination of one of the networks they announce to you as theirs, and you generally can only become party to a peering agreement if the other parties think you really are their 'peer' eg that it is desirable for them to connect to you as it is to you to connect to them. This would generally be met by being a large backbone yourself, with your own connectivity it multiple (more than 3) peering points, and your own customers (such as ISP's, webhosts, businesses, etc)
It is also possible to connect and a peering point and obtain what you think of as 'Internet service' - its called 'transit' - and its another type of agreement you can enter, that specifically *does* allow you to 'default' to the router of the org that you pay for transit. You can expect to pay market rates for transit bandwidth, although its a pretty competitive market. You would still be responsible for locating your own router onsite, interconnections with the shared fabric, and then the backhaul to your location.
For an interesting read, see http://worldofends.com/