cvs commit: src Makefile.inc1 src/crypto/openssh sshd.c src/etc Makefile src/etc/gss Makefile mech qop src/etc/mtree BSD.include.dist BSD.root.dist src/gnu/usr.bin/cvs/cvs Makefile src/include Makefile gssapi.h src/include/gssapi Makefile gssapi.h ...

Doug Rabson dfr at
Mon Jan 2 05:11:43 PST 2006

On Monday 02 January 2006 12:51, Hiroki Sato wrote:
> Doug Rabson <dfr at> wrote
>   in <200601020928.10955.dfr at>:
> df> I take the 'in whole or in part' phrase as allowing the kind of
> copying df> that I performed while writing the manpages. The above
> copyright notice df> is preserved in each and every manpage. I will
> also note that the df> Solaris manpages for GSS-API have been derived
> from the same text as df> can be clearly seen by reading a
> representative selection. I don't have df> the Solaris manpage source
> so I can't tell what copyright they contain.
>  See discussion in the IETF IPR-WG mailing list:
>  People in this discussion think creating a derivative work of an RFC
>  is not permitted to third parties though some commercial UNIXes
>  certainly include RFC derived manual pages.
>  Although some are working on fixing this problem[*], I think the
>  legality is still in a gray area at the current moment, at least.
>  [*]

The copyright notice for RFC3667 is quite different from that for 
RFC2744 (which is what I copied from). The above discussion does not 
apply here. In particular the words from RFC2744:

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works

seem to allow (and even encourage) the particular use that I have made 
of the text.

More information about the cvs-src mailing list