i always thought it was brought in place earlier but as geoff huston writes in the mythology of ip version 6 it was

In January 1983, the Advanced Research Projects Agency Network (ARPANET) experienced a "flag day," and the Network Control Protocol, NCP, was turned off, and TCP/IP was turned on.

and i learned from david h. crocker's page: "A common error about the "T" in TCP/IP is, that it stands for transport or transfer whereas the "T" stands for transmission." (out of crocker's review of: "ruling the root" by milton l. mueller). to get the tast of the discussion it's worth to read mueller's response and crocker's follow-up.

dave crocker outlined 1992 the road to a new ip and adds to his text:

If you've wondered about the beginnings of the new version of IP (IPv6) this articles gives some background. Back when IPv6's goals were clearer, so were the technical solutions.

"The first use of the DNS took place on June 23, 1983, 20 years ago, writes nominum"

As the world’s largest and busiest distributed database, the DNS handles billions of requests every day and was the first proof that database replication could be invisible and reliable on a global scale.

paul mockapetris works there on new applications for dns such as intentional domain names, ip telephony, ip sec development, ... ( web hosting news), as other companies and research inttitutes, i have to add.

Receipt of a TS Packet with a non-zero PUSI value indicates that the TS Packet contains the start of a new SNDU. It also indicates the presence of the Payload Pointer. The Payload Pointer value indicates that there are payload ((Payload Pointer) €1) bytes of the SNDU currently being reassembled at the start of the TS Packet payload. A Payload Pointer value equal to 0 or greater than 183 is illegal in ULE, and the SNDU reassembly MUST be aborted. This event may generate an error message.

out of a ietf draft on "ultra lightweight encapsulation (ule) for transmission of ip datagrams over mpeg-2/dvb networks"

well, it creates an error message in my brain, for sure. PUSI stands for:

Payload_Unit_Start_Indicator of MPEG-2 [ISO-MPEG]. A PUSI value of zero indicates that the TS Packet does not carry the start of a new payload. In this document, a PUSI value of one indicates that the TS Packet does carry the start of a new payload. When the PUSI bit is set to 1, in ULE this also indicates the presence of a one byte pointer directly following the TS packet header.

will take me a while to figure out the consequences and meaning of all of this. but that's how future/history sounds, they say ...

just out of curiousity, i guess i will join the talk on Trunk MIBs, imagening that they are talking about a drunk men in black ...