|
This is a common perception... and one that I share to some extent. None
the less, it's not an easy problem. The network runs on consensus - and that is
nearly impossible to build and enforce. Ultimately, we hope, what works will win
out and become recognized as a standard. That is more likely than any body
creating a "standard" and then "enforcing" it into place.
Some, with the power and money to do so, are capable of pushing their
"standards" onto the 'net... and that is both good and bad.
I guess my point is this: Picking somebody other than IETF to do this
would most likely change the name but produce the same result. Giving any strong
enforcement power to any such body would be disastrous because that power would
quickly be abused either directly or through compromise. Imagine, for example,
if VeriSign were in charge (chaching!) of how everything worked on the Internet!
(I know from personal experience that they would love that... they may even feel
entitled to it from some of the conversations I've
overheard.)
It's not an easy problem.
The answer resides in real solutions - not in enforcement. You can't
pry a good working solution from the cold dead hands of a good systems admin -
or even most mediocre ones, but you can be pretty sure that almost every systems
admin (good, bad, and ugly) will avoid using a bad solution no matter what
enforcement might be at work - if they have any alternative at
all.
The Internet is an interesting training ground for real life problems
we've yet to deal with on this planet. It only works when it really works...
network effects create tremendous leverage... but opportunities
to compromise the system for local motives will be exploited if they
can be - even if that means killing off the whole thing. (sad but we treat each
other this way too more often than not...) Broader vision and altruism are often
missing from the decision making process - so any single point of authority with
significant power finds itself corrupted and manipulated - if not from the
inside then from the outside.
Often we forget that we're all connected. Often when folks say that the
solution is in some strong central authority that can enforce a proper standard,
they are really saying "everything would be fine if everyone would just do what
I say." These folks fail to consider what it would be like if they got their
wish, but the "authority" decided to do things that they couldn't live with. Be
careful what you wish for - you might get it.
The Internet is a great model for this kind of problem - a problem that
we face every day without recognizing it. Humans have not yet discovered how to
work and solve these problems (at least not en-mass) - but
perhaps they will now that we can face them from a different perspective.
It's easy to forget we all breath the same air, but not so easy to forget when
your email isn't working ;-)
The IETF, like any body attempting to do that job, is mostly stuck
battling a never ending storm of conflicting self interest on the part of the
participants. When we (all) figure out how to solve those problems more
efficiently then good standards will emerge and consensus will be easier to
develop.
In the mean time, it's a race to develop good working solutions and hope
they catch on before too much damage is done - for all I know this method might
even be the model solution in the end... It seems to work in nature - competing
diversity, with successful paradigms sweeping away the old... broad
communication and collaboration offering advantage to those who participate...
it makes me think...
Sorry for all the philosophy...
_M
PS: A Beautiful Mind was a great movie (IMO). There was a great moment
where some complex realities of economics were crystallized and made
transparent - I love when that happens. Let's not all "go for the
blonde".
|
Title: Message
- [Declude.JunkMail] AOL and Reverse DNS Andy Schmidt
- RE: [Declude.JunkMail] AOL and Reverse DNS Todd Holt
- Re: [Declude.JunkMail] AOL and Reverse ... Hosting Support
- RE: [Declude.JunkMail] AOL and Reve... Todd Holt
- Re: [Declude.JunkMail] AOL and ... Hosting Support
- RE: [Declude.JunkMail] AOL and ... Pete McNeil
- Re: [Declude.JunkMail] AOL... Hosting Support
- Re: [Declude.JunkMail]... Pete McNeil
- Re: [Declude.JunkM... Hosting Support
- RE: [Declude.JunkM... Kevin Bilbee
- Re: [Declude.JunkM... Hosting Support
- RE: [Declude.JunkMail] AOL... Burzin Sumariwalla
- RE: [Declude.JunkMail] AOL and Reverse ... Kevin Bilbee
- Re: [Declude.JunkMail] AOL and Reverse ... DLAnalyzer Support
- RE: [Declude.JunkMail] AOL and Reve... Todd Holt
- RE: [Declude.JunkMail] AOL and Reverse DNS John Tolmachoff \(Lists\)
- RE: [Declude.JunkMail] AOL and Reverse DNS Chuck Schick
- RE: [Declude.JunkMail] AOL and Reverse DNS Andy Schmidt
