Q: - what do you think of this proposal?
How about if we sidestep the "mechanical Derivative
Rights process" entirely
and make those individuals inside the Standards Process
address this and
file releases when they are ready for the IETF WG Chairs and
AD's to review
the work for advancement???
Lets say that if it's a Standards Practice submission,
then it will need to
have this Mechanical Implementation Release issue addressed
prior to the
first consideration of the first port. All this requires is
that the
copyright notice constrain that it pertains to publication
rights only and
nothing else, and "that all mechanical rights beyond
'republication for use
in the advancement of IETF Standards process' are
controlled under other
'release instruments'".
That makes this a non-issue I guess, but also means that the
Standards
Process document has to be revised to map to this as well
and some prototype
document for releasing the instances of "derivative
rights for the Standards
Use Only" and possibly a under "derivative
rights for the Standards Use or
Commercial Use" as well...
Its a real simple process tweak and makes there no more real
overhead for
the IETF except that the WG Chair is then culpable to make
sure that the
paperwork is in order on any and all initiatives they
Shepard through the
Standards Process.
Todd
----- Original Message -----
From: "Simon Josefsson" <jas extundo.com>
To: "Harald Tveit Alvestrand" <haraldalvestrand.no>
Cc: <ipr-wgietf.org>
Sent: Wednesday, February 22, 2006 7:13 AM
Subject: Re: #1198 Proposed resolution - Implementation and
derivative work
> Harald Tveit Alvestrand <haraldalvestrand.no> writes:
>
> > --On onsdag, februar 22, 2006 15:57:07 +0100 Simon
Josefsson
> > <jasextundo.com> wrote:
> >
> >> arald Tveit Alvestrand <haraldalvestrand.no> writes:
> >>
> >>> I think this has gone on long enough.
> >>>
> >>> This is a WG Last Call on issue #1198,
with a timeout of one week, and
> >>> I'll close it on February 28.
> >>>
> >>> SUGGESTED RESOLUTION:
> >>>
------------------------------------------------------------
----
> >>> Implementations of IETF standards that
incorporate pieces of IETF
> >>> documents (such as MIBs or data tables)
need to have the right to
> >>> produce derivative works based on those
pieces.
> >>
> >> FWIW, I agree with this solution.
> >>
> >> I note that some may consider 'text' to be
something that you would
> >> have to incorporate in an implementation in
order to implement it. My
> >> point is that in the above, it may have been
implied that only 'code'
> >> is applicable for this rule. I'm not sure if
this was intentional.
> >
> > It was very much intentional that I wrote
"pieces" and not "code" -
> > that allows us to close this issue without having
to solve the "what
> > is code" issue first....
>
> Ok.
>
> I suggest to add that the derivative works should be
possible to
> release under licenses which are frequently used for
IETF standards.
> For example:
>
> Implementations of IETF standards that incorporate
pieces of IETF
> documents (such as MIBs or data tables) need to have
the right to
> produce derivative works based on those pieces, and
those rights
> need to be compatible with a wide range of licenses
commonly
> used by implementers.
>
> Without this modification, it is possible design a IETF
policy that
> satisfy the above resolution text but still fail my
intended point
> here: that free implementations may need to incorporate
parts of a
> standard, and to release the work under a license that
permits
> modifications.
>
> Thanks,
> Simon
>
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wgietf.org
> https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
|