Re: An IETF repository for working code in our protocols?

["Joel M. Halpern" <[e-mail]>]

One of the advantages of pointers to implementations is that it can 
include equally pointers to open source and pointers to closed source of 
various forms.  The IETF doesn't take a stance among implementations.

Yours,
Joel

On 8/19/2020 2:46 PM, Vijay Gurbani wrote:
> Dear Glenn: Thank you very much for your note.  More inline.
> 
> On Wed, Aug 19, 2020 at 1:19 PM Deen, Glenn (NBCUniversal) 
> <[e-mail] <mailto:[e-mail]>> wrote:
> 
>     Hi Vijay,
> 
>       In additional to the points others have made, I’ll add that an
>     IETF code repository would need to carefully work out license issues
>     and also how it fits into the IETF’s Intellectual Property set up
>     that is managed by the IETF  Trust.
> 
>     [...]
> 
>     There may be more that pop up once the topic was looked at deeper.
> 
>     I’m not saying that any of these are show stoppers, but there’s a
>     lot of legal elements that would be need to worked out before any
>     bits got checked into a repository.
> 
> 
> Yes, absolutely.  All of what you listed are important and weighty 
> concerns.  But none of them appear to be insurmountable if we decided to 
> do this.  Clearly, the precedent set by IEEE and ACM in similar areas 
> seems to point to the possible existence of a happy medium, should we go 
> this route.
> 
> Cheers,
> 
> - vijay
>