Forgot your password?
typodupeerror
The Internet Technology

Today, the IETF Turns 25 27

Posted by timothy
from the renting-out-the-room dept.
FranckMartin writes "Little known to the general public, the Internet Engineering Task Force celebrates its 25th birthday on the 16th of January. DNSSEC, IDN, SIP, IPv6, HTTP, MPLS ... all acronyms that were codified at the IETF. But little known, one can argue the IETF does not exist; it just happens that people meet 3 times a year in some hotel around the world and are on mailing lists in between. The openness of the IETF and its structure has inspired the way ICANN is run, as well as the way the Internet Governance Forum (IGF) has been open to the civil society."
This discussion has been archived. No new comments can be posted.

Today, the IETF Turns 25

Comments Filter:
  • That's news to me.
    • by dpilot (134227)

      Wouldn't things be much better and open if instead of ICANN or IETF we just had joint agreements between Comcast, ATT, Verizon, Time-Warner, and maybe Level3? I guess I should be international and include a few other "key players" in that list, too.

      • Wouldn't things be much better and open if instead of ICANN or IETF

        I'm OK with the IETF.

        It is ICANN that has messed things up with their awful processes and back-room dealings.

      • by Tacvek (948259)

        You should not have any problem with the IETF. They do virtually everything in the public. You may read the mailing lists, and contribute.

        The standards created by the IETF are generally completely open by every definition, in that any part may participate in development, there is no restrictions of any kind on access to the standards text[1], and most do not require any patent licensing[2].

        The IETF has also been generally fairly competent. They did screw up a bit with IPv6[3], but otherwise many of the stan

      • Wouldn't things be much better and open if instead of ICANN or IETF we just had joint agreements between Comcast, ATT, Verizon, Time-Warner, and maybe Level3? I guess I should be international and include a few other "key players" in that list, too.

        It is called the ITU!

  • My brain melted trying to comprehend that summary on a Sunday morning.

  • ZzzzZZzzz... KASNORK!!! ZZZZzzzzzZZZZZZzzzz...

    I'm sorry, what? Who? ...OK...

    Why did you wake me up?
  • ICANT (Score:5, Insightful)

    by girlintraining (1395911) on Sunday January 16, 2011 @01:41PM (#34898230)

    The openness of the IETF and its structure has inspired the way ICANN is run,

    Yes, I believe for the ICANN people, it served as a giant lighthouse warning petty tyrants of the dangers of open, collaborative design processes. Since ICANN took office, domain name registration has become horribly convoluted, the prices have gone up, lawsuits abound, and we're now in danger of running out of real estate (IPv4 addresses), while they sit on their arse and worry about copyright. They're like a HOA -- they're fining people left and right and ordering them to take down christmas decorations, flags, and people who dare to paint their house in an unapproved color, while they forget to spend money on things like garbage collection, road repair, and snow removal.

    No, actually, they ARE the internet's HOA, and about as bloody useful.

    • by dodobh (65811)

      What does ICANN have to do with IPv4 running out? IP is IETF territory, and the IETF has done it's job by putting IPv6 out there.

      IPv6 adoption is now a business problem, and you can see the lack of business innovation in that space.

  • This sentence in the article is no longer true. There was a time when people coded stuff, then wrote an I-D to document it. The problem is that the burden of having at least 2 implementations is only to promote an RFC to the Draft Standard level, which is less and less frequent.

    This is a real problem, because some of the bugs in an RFC can only be found by testing two implementations against each other. Unfortunately my last tentative to improve this was rejected:

    http://www.ietf.org/mail-archive/web/ietf [ietf.org]

<<<<< EVACUATION ROUTE <<<<<

Working...