This package was first 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/>.

Copyright Holder: The Internet Corporation for Assigned Names and Numbers

License:

	------------------------------------------------------------------------
	Message-ID: <32EBA504.4362D2D5@khms.westfalen.de>
	Subject: IANA document copyright?
	From: Kai Henningsen <kai@khms.westfalen.de>
	Date: Sun, 26 Jan 1997 19:40:04 +0100
	To: iana@iana.org

	Ive found the "rfc-copyright-story" document, and I suspect that it
	also applies to the IANA documents. However, I havent been able to find
	any concrete statement on this.

	Could you please clarify?

	The reason for this is that Im considering making a package from the
	IANA docs (and another from the more important RFCs) for the Debian
	GNU/Linux distribution, and they insist (quite rightly, I think) on
	including a statement as to the copyright status in every such package.

	Thank you!

	Kai Henningsen
	------------------------------------------------------------------------

	------------------------------------------------------------------------
	Message-ID: <199701282213.AA03327@nam.isi.edu>
	Subject: Re: IANA document copyright?
	From: iana@ISI.EDU
	Date: 28 Jan 1997 14:13:04 -0800
	To: kai@khms.westfalen.de

	Kai,

	To clarify: IANA publishes its documents through RFCs (see RFC 1700),
	therefore the rfc-copyright-story document applies.  Thanks.

	Josh

	And here is the rfc-copyright-story:

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