Re: [hackathon] Open Source Software and network protocol standards

Stuart,
           I would like to mention OpenWSN,
which is the reference for the 6tisch WG IoT stack. It was also used at the
Interop
sessions.
Regards,

                           Diego

On Tue, Mar 22, 2022 at 8:43 AM Robert Moskowitz <rgm@labs.htt-consult.com>
wrote:

> I would like to think we all had fun back then.  Really accomplishing
> something.
>
> On 3/22/22 06:34, Shoichi Sakane (ssakane) wrote:
>
> Yes, timezone was a big problem.  So, I and Itojun joined many times of
> the bakeoff events in person.  Our implementation supported both IPv6 and
> IPv4 so that any participants was able to check interoperability with us.
>
> Shoichi
> ------------------------------
> *From:* Robert Moskowitz <rgm@labs.htt-consult.com>
> <rgm@labs.htt-consult.com>
> *Sent:* Tuesday, March 22, 2022 18:51
> *To:* Shoichi Sakane (ssakane) <ssakane@cisco.com> <ssakane@cisco.com>;
> RA <ran.atkinson@gmail.com> <ran.atkinson@gmail.com>; hackathon@ietf.org
> <hackathon@ietf.org> <hackathon@ietf.org>
> *Cc:* Stuart Cheshire <cheshire@apple.com> <cheshire@apple.com>
> *Subject:* Re: [hackathon] Open Source Software and network protocol
> standards
>
> Thanks.  I was struggling to remember all the product participants and
> knew there was one from Japan...
>
> I don't recall if you made it to any of the in-person interops, but you
> were part of the remote ones I ran out of my basement office.  It was a
> challenge to coordinate everyone's testing time, with some of us doing the
> testing in the middle of local night to accommodate others.  I still have
> the world timezone map up on my wall down in that office that I used to
> figure out what time it was for each of you, and the chat server (I ran
> down there) logs I used for our progress reports.
>
> Challenge was you were already at IPv6 and it made connecting to other
> testers limited.
>
> On 3/22/22 02:12, Shoichi Sakane (ssakane) wrote:
>
> I would be happy if you all IPsec guys remembered the KAME IPv6/IPsec
> implemetation and racoon for IKEv1/v2 which is ported on MacOS and Linux.
>
> Shoichi
> ------------------------------
> *From:* hackathon <hackathon-bounces@ietf.org>
> <hackathon-bounces@ietf.org> on behalf of RA <ran.atkinson@gmail.com>
> <ran.atkinson@gmail.com>
> *Sent:* Tuesday, March 22, 2022 5:44
> *To:* hackathon@ietf.org <hackathon@ietf.org> <hackathon@ietf.org>
> *Cc:* Stuart Cheshire <cheshire@apple.com> <cheshire@apple.com>
> *Subject:* Re: [hackathon] Open Source Software and network protocol
> standards
>
> NRL’s open-source IPv6+IPsec for 4.4 BSD UNIX was the basis for many (most
> ?) 1st generation commercial IPsec implementations and also was used in
> some early IPv6 implementations.  It was developed/tested both on SPARC and
> x86.
>
> IPsec would have taken years longer without the NRL open-source
> implementation, both to standardize and to ship in products.
>
> Ran
>
>
> > On Mar 20, 2022, at 10:01, Paul Wouters <paul@nohats.ca>
> <paul@nohats.ca> wrote:
> >
> >
> >> Subject: Re: [hackathon] Open Source Software and network protocol
> standards
> >
> >> My intuition is that in recent years Open Source Software has had a
> significant impact on network protocol standards, both in the availability
> of easily accessible open implementations contributing to the success of
> network protocol standards, and, in contrast, the lack of easily accessible
> open implementations contributing to less success for those network
> protocol standards.
> >
> > For IKEv1 / IPsec there were a number of "bake off" [tm][r] events where
> > FreeSWAN was the main interop target for all commercial implementations
> > for a number of years in the late '90s.
> >
> > The software and protocol were evolving/implementing at the same time.
> >
> > Paul
> >
> > _______________________________________________
> > hackathon mailing list
> > hackathon@ietf.org
> > https://www.ietf.org/mailman/listinfo/hackathon
> > Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe
> <hackathon-request@ietf.org?subject=unsubscribe>
>
> _______________________________________________
> hackathon mailing list
> hackathon@ietf.org
> https://www.ietf.org/mailman/listinfo/hackathon
> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe
> <hackathon-request@ietf.org?subject=unsubscribe>
>
> _______________________________________________
> hackathon mailing listhackathon@ietf.orghttps://www.ietf.org/mailman/listinfo/hackathon
> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe <hackathon-request@ietf.org?subject=unsubscribe>
>
>
> --
> Robert Moskowitz
> Owner
> HTT Consulting
> C:      248-219-2059
> F:      248-968-2824
> E:      rgm@labs.htt-consult.com
>
> There's no limit to what can be accomplished if it doesn't matter who gets
> the credit
>
> _______________________________________________
> hackathon mailing listhackathon@ietf.orghttps://www.ietf.org/mailman/listinfo/hackathon
> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe <hackathon-request@ietf.org?subject=unsubscribe>
>
>
> --
> Robert Moskowitz
> Owner
> HTT Consulting
> C:      248-219-2059
> F:      248-968-2824
> E:      rgm@labs.htt-consult.com
>
> There's no limit to what can be accomplished if it doesn't matter who gets
> the credit
> _______________________________________________
> hackathon mailing list
> hackathon@ietf.org
> https://www.ietf.org/mailman/listinfo/hackathon
> Unsubscribe: mailto:hackathon-request@ietf.org?subject=unsubscribe
>