[ih] CORRECTION: Not IEN's, but Packet Radio Notes

[Greg Skinner]

Also see https://www.saildart.org/[IP,SYS]/ <https://www.saildart.org/%5BIP,SYS%5D/> in the saildart (Stanford AI Lab) archives.  It contains TCP code originally written by Bill Plummer and edited by Charlie Lynn.

--gregbo 

[1] https://www.rfc-editor.org/in-notes/museum/tcp-jsys.txt
[2] https://www.rfc-editor.org/in-notes/museum/tcp-ip.txt

> On Apr 16, 2025, at 5:33 PM, Barbara Denny via Internet-history <internet-history at elists.isoc.org> wrote:
> 
> I also think Charlie Lynn (BBN) was working on one of the tcp implementations in the early 80s, if not before then.  He attended the BBN weekly packet radio meetings so he was aware of packet radio.
> barbara
>    On Wednesday, April 16, 2025 at 05:08:10 PM PDT, Vint Cerf via Internet-history <internet-history at elists.isoc.org> wrote:  
> 
> some key TCP players were part of the packet radio program (jim mathis,
> vint cerf, ....)
> v
> 
> 
> On Wed, Apr 16, 2025 at 7:49 PM Greg Skinner via Internet-history <
> internet-history at elists.isoc.org> wrote:
> 
>> On Apr 16, 2025, at 9:33 AM, Alexander McKenzie via Internet-history <
>> internet-history at elists.isoc.org> wrote:
>>> 
>>> Friends,
>>> 
>>> I must apologize for a serious misstatement.  I now realize it was not
>>> IEN's which were strictly controlled, it was Packet Radio Notes.  I
>> myself
>>> was on the public distribution list for IENs and I should have remembered
>>> this.
>>> 
>>> My sincere apologies,
>>> Alex McKenzie
>>> --
>>> Internet-history mailing list
>>> Internet-history at elists.isoc.org
>>> https://elists.isoc.org/mailman/listinfo/internet-history
>> 
>> OK, I understand (although some of those Packet Radio Notes are also
>> IENs).  But IMO some of the Packet Radio Notes (such as those that are in
>> https://apps.dtic.mil/sti/tr/pdf/ADA157696.pdf) that are not IENs could
>> have been valuable to TCP implementors who were not part of the initial
>> group of TCP implementors from the late 1970s and early 1980s.  At the very
>> least, they give an idea of how one might go about designing or tuning a
>> TCP implementation, or testing for interoperability (including performance).
>> 
>> --gregbo
> 
> Google, LLC
> 1900 Reston Metro Plaza, 16th Floor
> Reston, VA 20190
> +1 (571) 213 1346
> 
> 
> until further notice
> -- 
> Internet-history mailing list
> Internet-history at elists.isoc.org
> https://elists.isoc.org/mailman/listinfo/internet-history
> 
> -- 
> Internet-history mailing list
> Internet-history at elists.isoc.org
> https://elists.isoc.org/mailman/listinfo/internet-history