Ivo Emanuel Gonçalves
2009-Mar-30 11:44 UTC
[Speex-dev] ietf discussion about draft-ietf-avt-rtp-speex
On 3/30/09, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote:> It seems to be related to debian, that doesn't like the fact that not > everyone is allowed to modify these documents. If it's that much > problem, I'd say just remove it.Guys, both the Vorbis RTP and the Ogg media types RFCs have this clause. It did not raise any problem. If there are problems with the Speex draft, this is not it. -Ivo
Alfred E. Heggestad
2009-Apr-13 20:57 UTC
[Speex-dev] ietf discussion about draft-ietf-avt-rtp-speex
Ivo Emanuel Gon?alves wrote:> On 3/30/09, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: >> It seems to be related to debian, that doesn't like the fact that not >> everyone is allowed to modify these documents. If it's that much >> problem, I'd say just remove it. > > Guys, both the Vorbis RTP and the Ogg media types RFCs have this > clause. It did not raise any problem. If there are problems with the > Speex draft, this is not it. >I have just submitted version -06 of the speex-rtp draft.. the additional copying conditions is still there, we can keep them for now, unless some IETF person heavily protests.. Ivo, could you also review the updated memo-status/copyright notice, located on page 1-2 ? /alfred> -Ivo
Ivo Emanuel Gonçalves
2009-Apr-18 11:45 UTC
[Speex-dev] ietf discussion about draft-ietf-avt-rtp-speex
Sorry for the delay. On 4/13/09, Alfred E. Heggestad <aeh at db.org> wrote:> Ivo, could you also review the updated memo-status/copyright notice, > located on page 1-2 ?Is this a new standard for writing Internet drafts? I've never seen it in other documents. Specifically, this part: "This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English." Unless it is required now by the IETF I would advise to remove it. You are placing restrictions which do not usually appear(?) and may otherwise conflict with IETF guidelines. It actually differs from the standard Intellectual Property and Full Copyright Statement clauses that proposed Standard Tracks documents carry at the bottom. Finally, the "no derivative works" seems a no-no to me, but I'm no lawyer. I for one assume Debian and other Free Culture organizations won't be pleased. -Ivo