This package was debianized by Kai Henningsen kai@khms.westfalen.de on
Sun, 26 Jan 1997 20:35:58 +0100.

It was downloaded from <http://www.iana.org> and various places (on
isi.edu) this pointed to.  (See source package, debian/genorig.*.)

Copyright:

q> From - Sun Jan 26 19:40:04 1997
q> X-Mozilla-Status: 0001
q> BCC: kai@khms.westfalen.de
q> Message-ID: <32EBA504.4362D2D5@khms.westfalen.de>
q> Date: Sun, 26 Jan 1997 19:40:04 +0100
q> From: Kai Henningsen <kai@khms.westfalen.de>
q> X-Mailer: Mozilla 3.0Gold (X11; I; Linux 2.0.27 i486)
q> MIME-Version: 1.0
q> To: iana@iana.org
q> Subject: IANA document copyright?
q> Content-Type: text/plain; charset=iso-8859-1
q> Content-Transfer-Encoding: 8bit
q> 
q> Ive found the "rfc-copyright-story" document, and I suspect that it
q> also applies to the IANA documents. However, I havent been able to
q> find any concrete statement on this.
q> 
q> Could you please clarify?
q> 
q> The reason for this is that Im considering making a package from the
q> IANA docs (and another from the more important RFCs) for the Debian
q> GNU/Linux distribution, and they insist (quite rightly, I think) on
q> including a statement as to the copyright status in every such package.
q> 
q> Thank you!
q> 
q> Kai Henningsen

a> From iana 28 Jan 1997 14:13:04 -0800 remote from ISI.EDU
a> Received: by ISI.EDU
a> 	  06 Feb 1997 22:28:00 -0800
a> Date: 28 Jan 1997 14:13:04 -0800
a> From: iana@ISI.EDU
a> To: kai@khms.westfalen.de
a> Message-ID: <199701282213.AA03327@nam.isi.edu>
a> Subject: Re: IANA document copyright?
a> Received: from zephyr.isi.edu(really [128.9.160.160]) by muenster.westfalen.de via smail with smtp id <m0vpLgZ-000GwhC@muenster.westfalen.de> for <kai@khms.westfalen.de>; Tue, 28 Jan 1997 23:07:23 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built 1996-Nov-13
a> Received: from nam.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA04102>; Tue, 28 Jan 1997 14:07:19 -0800
a> Posted-Date: Tue, 28 Jan 1997 14:13:04 -0800
a> Received: by nam.isi.edu (5.65c/4.0.3-6) id <AA03327>; Tue, 28 Jan 1997 14:13:04 -0800
a> 
a> 
a> 
a> Kai,
a> 
a> To clarify: IANA publishes its documents through RFCs (see RFC 1700),
a> therefore the rfc-copyright-story document applies.  Thanks.
a> 
a> Josh

And here is the rfc-copyright-story:

r> Hi.
r> 
r> The Request For Comments (RFC) documents are intended to have wide
r> distribution.
r> 
r> 1.  Copying and distributing the whole RFC without any changes:
r> 
r> 1a.  The copying and free redistribution are generally encouraged.
r> 
r> 1b.  The inclusion of RFCs in other documents and collections that are
r> distributed for a fee is also encouraged, though in this case it is a
r> courtesy (i) to ask the RFC author and (ii) provide the RFC author
r> with a copy of the final document or collection.  Anyone can takes
r> some RFCs, put them in a book, copyright the book, and sell it.  This
r> in no way inhibits anyone else from doing the same thing, or inhibits
r> any other distribution of the RFCs.
r> 
r> 2.  Copying and distributing the whole RFC with changes in format,
r> font, etcetera:
r> 
r> 2a.  The same as case 1 with the addition that a note should be made
r> of the reformatting.
r> 
r> 3.  Copying and distributing portions of an RFC:
r> 
r> 3a.  As with any material excerpted from another source, proper credit
r> and citations must be provided.
r> 
r> 4.  Translating RFCs into other languages:
r> 
r> 4a.  Since wide distribution of RFCs is very desirable, translation
r> into other languages is also desirable.  The same requirements and
r> courtesies should be followed in distributing RFCs in translation as
r> would be followed when distributing RFCs in the original language.
r> 
r> 
r> --jon.
