-Original Message-
From: Simon Josefsson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 30, 2005 7:29 AM
To: Ted Mittelstaedt
Cc: freebsd-questions@freebsd.org
Subject: Re: Proposed license for IETF Contributions
Ted Mittelstaedt [EMAIL PROTECTED] writes:
Please provide me
Ted Mittelstaedt [EMAIL PROTECTED] writes:
Please provide me with a reference for this.
http://www.copyright.gov/circs/circ1.html#wnp
Under the subheading:
WHAT IS NOT PROTECTED BY COPYRIGHT?
Works consisting entirely of information that is common property and
containing no original
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Simon Josefsson
Sent: Monday, November 21, 2005 9:28 AM
To: Ted Mittelstaedt
Cc: freebsd-questions@freebsd.org
Subject: Re: Proposed license for IETF Contributions
Ted Mittelstaedt [EMAIL PROTECTED] writes
Josefsson
Sent: Friday, November 18, 2005 7:28 AM
To: freebsd-questions@freebsd.org
Subject: Proposed license for IETF Contributions
Hi all. I noticed the following in the release notes for 6.0:
The following manual pages, which were derived from RFCs and
possibly violate the IETF's
James Bailie [EMAIL PROTECTED] writes:
Simon's proposed license seems reasonable to me. It is
essentially a BSD-style license, allowing royalty-free
redistribution and modification, but with a difference when it
comes to attribution. Original unmodified text from a
specification must
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of James Bailie
Sent: Sunday, November 20, 2005 9:38 AM
To: freebsd-questions@freebsd.org
Subject: Re: Proposed license for IETF Contributions
Ted Mittelstaedt wrote:
You might check this but I believe
RFC is a specification,
and therefore uncopyrightable.
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Simon Josefsson
Sent: Friday, November 18, 2005 7:28 AM
To: freebsd-questions@freebsd.org
Subject: Proposed license for IETF Contributions
Hi all. I
Ted Mittelstaedt wrote:
You might check this but I believe that the Copyright convention
specifically
excepts specifications from copyright coverage. I think there's some
other
classes of original work that fall under this. How about simply
rewriting the
ITEF license to designate any
Hi all. I noticed the following in the release notes for 6.0:
The following manual pages, which were derived from RFCs and
possibly violate the IETF's copyrights, have been replaced:
gai_strerror(3), getaddrinfo(3), getnameinfo(3), inet6_opt_init(3),
inet6_option_space(3),
