← Back to context

Comment by throw0101a

4 days ago

> Exactly. IPv6 was developed in the ivory towers where it was still assumed that everyone wanted to be a full participant of the internet.

IPv6 was developed in the open on mailing lists that anyone could subscribe to:

    The criteria presented here were culled from several sources,
    including "IP Version 7" [1], "IESG Deliberations on Routing and
    Addressing" [2], "Towards the Future Internet Architecture" [3], the
    IPng Requirements BOF held at the Washington D.C. IETF Meeting in
    December of 1992, the IPng Working Group meeting at the Seattle IETF
    meeting in March 1994, the discussions held on the Big-Internet
    mailing list (big-internet-at-munnari.oz.au, send requests to join to
    big-internet-request-at-munnari.oz.au), discussions with the IPng Area
    Directors and Directorate, and the mailing lists devoted to the
    individual IPng efforts.

* https://datatracker.ietf.org/doc/html/rfc1726

Just like all current IETF discussions are in the open and free for all to participate. If you don't like the direction things are going in participate: as Gandhi did (not) say, “Be the change you want to see in the world.”

One of the co-authors on that RFC worked at BBN: you know, the folks that actually built the first the routers (IMPs) that created the ARPA/Internet in the first place. I would hazard to guess they have know something about network operations.

* https://www.goodreads.com/book/show/281818.Where_Wizards_Sta...

> But the social/political environment was that everyone just wants to be a passive consumer, paying monthly fees to centralized hosts to spoon-feed them content through an algorithm.

Disagree, especially with the hoops that users and developers have to jump through to deal with (CG-)NAT:

> [Residential customers] don't care about engineering, but they sure do create support tickets about broken P2P applications, such as Xbox/PS gaming applications, broken VoIP in gaming lobbies, failure of SIP client to punch through etc. All these problems don't exist on native routed (and static) IPv6.

* https://blog.ipspace.net/2025/03/response-end-to-end-connect...