Ray Pelletier <rpelletier at isoc.org> writes:
> Simon,
>
> As to the Code Components list. The Policy document points to
> http://trustee.ietf.org/policyandprocedures.html
> for the location of the List.
Ray,
The document you posted in this thread points to another URL:
4. License to Code Components.
a. Definition. IETF Contributions and IETF Documents often
include components intended to be directly processed by a
computer (“Code Components”). A list of common Code Components
can be found at
http://trustee.ietf.org/docs/Code_Components_List_8-12-08.txt .
Generally, the PDF the Trustees agreed to (according to your initial
post in this thread) is not the document that is currently available
from http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf
That PDF on the web site is attached below for archival. For reference
it has this SHA-1 checksFrom ipr-wg-bounces at ietf.org Fri Nov 14 05:56:54 2008
Return-Path: <ipr-wg-bounces at ietf.org>
X-Original-To: ipr-wg-archive at megatron.ietf.org
Delivered-To: ietfarch-ipr-wg-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 370253A68AC;
Fri, 14 Nov 2008 05:56:54 -0800 (PST)
X-Original-To: ipr-wg at core3.amsl.com
Delivered-To: ipr-wg at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 56ADC3A6996;
Fri, 14 Nov 2008 01:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id pqyQavHV13ds; Fri, 14 Nov 2008 01:26:28 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39])
by core3.amsl.com (Postfix) with ESMTP id 3C5F23A67E2;
Fri, 14 Nov 2008 01:26:26 -0800 (PST)
Received: from c80-216-27-189.bredband.comhem.se ([80.216.27.189]
helo=mocca.josefsson.org)
by yxa-v.extundo.com with esmtpsa (TLS-1.0:DHE_RSA_AES_128_CBC_SHA1:16)
(Exim 4.63) (envelope-from <simon at josefsson.org>)
id 1L0uwU-0005W9-Ch; Fri, 14 Nov 2008 10:26:23 +0100
From: Simon Josefsson <simon at josefsson.org>
To: Ray Pelletier <rpelletier at isoc.org>
Subject: Re: [Trustees] IETF Trust Decision on "Legal Provisions for IETF
Documents" (dated October 16, 2008)
References: <0BDFFF51DC89434FA33F8B37FCE363D511F9576A at zcarhxm2.corp.nortel.com>
<87zlk5tly2.fsf at mocca.josefsson.org>
<5FB4C0FE-5184-4F3B-8B23-BE86099150A0 at isoc.org>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:081114:rpelletier at isoc.org::vuCXorZ3wsJJozJw:22Kv
X-Hashcash: 1:22:081114:edj at nortel.com::Uu6WBl291TfXjN/f:8K3E
X-Hashcash: 1:22:081114:trustees at ietf.org::Pu+A0+yRJrCqd2aJ:q2bt
X-Hashcash: 1:22:081114:ipr-wg at ietf.org::1XlDvn93Q+iGjAJI:w3Md
Date: Fri, 14 Nov 2008 10:26:13 +0100
In-Reply-To: <5FB4C0FE-5184-4F3B-8B23-BE86099150A0 at isoc.org> (Ray Pelletier's
message of "Wed, 12 Nov 2008 11:29:12 -0500")
Message-ID: <87ljvm4q16.fsf at mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
X-Mailman-Approved-At: Fri, 14 Nov 2008 05:56:52 -0800
Cc: Trustees <trustees at ietf.org>, ipr-wg at ietf.org,
Ed Juskevicius <edj at nortel.com>
X-BeenThere: ipr-wg at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>,
<mailto:ipr-wg-request at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipr-wg>
List-Post: <mailto:ipr-wg at ietf.org>
List-Help: <mailto:ipr-wg-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>,
<mailto:ipr-wg-request at ietf.org?subject=subscribe>
Sender: ipr-wg-bounces at ietf.org
Errors-To: ipr-wg-bounces at ietf.org
Ray Pelletier <rpelletier at isoc.org> writes:
> Simon,
>
> As to the Code Components list. The Policy document points to
> http://trustee.ietf.org/policyandprocedures.html
> for the location of the List.
Ray,
The document you posted in this thread points to another URL:
4. License to Code Components.
a. Definition. IETF Contributions and IETF Documents often
include components intended to be directly processed by a
computer (“Code Components”). A list of common Code Components
can be found at
http://trustee.ietf.org/docs/Code_Components_List_8-12-08.txt .
Generally, the PDF the Trustees agreed to (according to your initial
post in this thread) is not the document that is currently available
from http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf
That PDF on the web site is attached below for archival. For reference
it has this SHA-1 checksum:
2e2um:
2e2b1b5cf1a5b342c46be9b313ee6d054063a827 IETF-Trust-License-Policy.pdf
The changes between the two documents include:
* Effective Date added
* URL for code components changed
* Copyright notices changed from:
Copyright (c) <YEAR>, IETF Trust and the persons identified as its
authors. All rights reserved.
into
Copyright (c) [insert year] IETF Trust and the persons identified as
the document authors. All rights reserved.
There may be other changes too, it is difficult to review changes
between PDF documents.
The copyright notice change appears unfortunate: not all IETF
Contributions are documents. This seems like a potentially significant
change.
Did all Trustees agree to make this change? In other words: which
document did the Trustees actually approve?
> There is a link there labelled IETF Legal Provisions for IETF
> Documents & Code Components List pointing to:
> http://trustee.ietf.org/license-info/
>
> That has a link there labelled Examples of common Code Components
> which may be found in IETF Documents with a link to:
> http://trustee.ietf.org/docs/Code-Components-List.txt
Using the term 'Examples' here is inappropriate.
RFC 5377 has requested that the Trust maintain a list of RFC components
that will be considered code. As far as I read RFC 5377, the list
maintained by the Trust is normative at any single point of time, and
the content of the list has legal implications. It is not an "example
list".
> I think you are suggesting that there should be an archive maintained
> of old Code Component lists. If so, I agree.
My point was to publicly archive the code component list at the date of
publication.
However, I agree that publicly archiving old code component lists too is
useful.
> I expect they would be accessible from Archive of Obsolete Policies
> and Procedures at http://trustee.ietf.org/license-info/
>
> I think you are also suggesting we should post
> Code_Components_List_8-12-08.txt and have it accessible from there.
>
> Do I have this correct?
No, here is what I suggest:
1) Make the content of
http://trustee.ietf.org/docs/Code-Components-List.txt be the content
of http://trustee.ietf.org/docs/Code_Components_List_8-12-08.txt.
This avoids the unfortunate use of the term 'Example' in the list
itself.
The latter list is more appropriate for another reason: it was the
latter list that was approved by the Trustees according to your
initial post in this thread.
2) Change text 'Examples of common' into 'Common' on
http://trustee.ietf.org/license-info/
3) Decide which version of the document is the official one, and please
also post the final document to this list. The decision seems to be
which copyright notice to use: the one the trustees approved
(according to your post) or the one currently available from the
trustee.ietf.org site.
/Simon
>
> Ray
>
> On Nov 12, 2008, at 2:58 AM, Simon Josefsson wrote:
>
>> "Ed Juskevicius" <edj at nortel.com> writes:
>>
>>> This message is an announce the IETF Trustees have reached
>>> consensus on
>>> a policy entitled "Legal Provisions Relating to IETF Documents".
>>
>> Congratulations! And thanks for posting the final documents.
>>
>> To make sure we also archive the Code Components List, which is linked
>> from by the Legal Provisions, and make that available for easy
>> reference
>> (via the mailing list archive) I retrieved the file today. I used the
>> URL from the PDF you posted. SHA-1 hash as below.
>>
>> mocca:~$ wget -q http://trustee.ietf.org/docs/Code_Components_List_8-12-08.txt
>> jas at mocca:~$ sha1sum Code_Components_List_8-12-08.txt
>> 9dbc3bc95964c4f506630d2ff7e20ae02ccced2a
>> Code_Components_List_8-12-08.txt
>> jas at mocca:~$
>>
>> The Trustee's web pages links to another Code Components list from
>> <http://trustee.ietf.org/license-info/>. I'm including SHA-1 hash of
>> that file and attaches it as well. The content appears to be the
>> same,
>> but it uses different formatting. It is not clear to me which is the
>> canonical source.
>>
>> jas at mocca:~$ wget -q http://trustb1b5cf1a5b342c46be9b313ee6d054063a827 IETF-Trust-License-Policy.pdf
The changes between the two documents include:
* Effective Date added
* URL for code components changed
* Copyright notices changed from:
Copyright (c) <YEAR>, IETF Trust and the persons identified as its
authors. All rights reserved.
into
Copyright (c) [insert year] IETF Trust and the persons identified as
the document authors. All rights reserved.
There may be other changes too, it is difficult to review changes
between PDF documents.
The copyright notice change appears unfortunate: not all IETF
Contributions are documents. This seems like a potentially significant
change.
Did all Trustees agree to make this change? In other words: which
document did the Trustees actually approve?
> There is a link there labelled IETF Legal Provisions for IETF
> Documents & Code Components List pointing to:
> http://trustee.ietf.org/license-info/
>
> That has a link there labelled Examples of common Code Components
> which may be found in IETF Documents with a link to:
> http://trustee.ietf.org/docs/Code-Components-List.txt
Using the term 'Examples' here is inappropriate.
RFC 5377 has requested that the Trust maintain a list of RFC components
that will be considered code. As far as I read RFC 5377, the list
maintained by the Trust is normative at any single point of time, and
the content of the list has legal implications. It is not an "example
list".
> I think you are suggesting that there should be an archive maintained
> of old Code Component lists. If so, I agree.
My point was to publicly archive the code component list at the date of
publication.
However, I agree that publicly archiving old code component lists too is
useful.
> I expect they would be accessible from Archive of Obsolete Policies
> and Procedures at http://trustee.ietf.org/license-info/
>
> I think you are also suggesting we should post
> Code_Components_List_8-12-08.txt and have it accessible from there.
>
> Do I have this correct?
No, here is what I suggest:
1) Make the content of
http://trustee.ietf.org/docs/Code-Components-List.txt be the content
of http://trustee.ietf.org/docs/Code_Components_List_8-12-08.txt.
This avoids the unfortunate use of the term 'Example' in the list
itself.
The latter list is more appropriate for another reason: it was the
latter list that was approved by the Trustees according to your
initial post in this thread.
2) Change text 'Examples of common' into 'Common' on
http://trustee.ietf.org/license-info/
3) Decide which version of the document is the official one, and please
also post the final document to this list. The decision seems to be
which copyright notice to use: the one the trustees approved
(according to your post) or the one currently available from the
trustee.ietf.org site.
/Simon
>
> Ray
>
> On Nov 12, 2008, at 2:58 AM, Simon Josefsson wrote:
>
>> "Ed Juskevicius" <edj at nortel.com> writes:
>>
>>> This message is an announce the IETF Trustees have reached
>>> consensus on
>>> a policy entitled "Legal Provisions Relating to IETF Documents".
>>
>> Congratulations! And thanks for posting the final documents.
>>
>> To make sure we also archive the Code Components List, which is linked
>> from by the Legal Provisions, and make that available for easy
>> reference
>> (via the mailing list archive) I retrieved the file today. I used the
>> URL from the PDF you posted. SHA-1 hash as below.
>>
>> mocca:~$ wget -q http://trustee.ietf.org/docs/Code_Components_List_8-12-08.txt
>> jas at mocca:~$ sha1sum Code_Components_List_8-12-08.txt
>> 9dbc3bc95964c4f506630d2ff7e20ae02ccced2a
>> Code_Components_List_8-12-08.txt
>> jas at mocca:~$
>>
>> The Trustee's web pages links to another Code Components list from
>> <http://trustee.ietf.org/license-info/>. I'm including SHA-1 hash of
>> that file and attaches it as well. The content appears to be the
>> same,
>> but it uses different formatting. It is not clear to me which is the
>> canonical source.
>>
>> jas at mocca:~$ wget -q http://trustee.ietf.ee.ietf.org/docs/Code-Components-List.txt
>> jas at mocca:~$ sha1sum Code-Components-List.txt
>> d48d740ce99a322c00e28865f4a76213b377caed Code-Components-List.txt
>> jas at mocca:~$
>>
>> /Simon
>> o ABNF definitions
>> o ASN.1 modules
>> o ASN.1 structures
>> o Management Information Base (MIB) modules
>> o TLS presentation syntax
>> o eXternal Data Representation (XDR)
>> o Extensible Markup Language (XML) Schemas
>> o XML DTDs
>> o XML RelaxNG definitions
>> o tables of values
>> o classical programming codeExamples of common Code Components which
>> may be found in IETF Contributions and IETF Documents:
>>
>>
>> o ABNF definitions
>>
>> o ASN.1 modules
>>
>> o ASN.1 structures
>>
>> o Management Information Base (MIB) modules
>>
>> o TLS presentation syntax
>>
>> o eXternal Data Representation (XDR)
>>
>> o Extensible Markup Language (XML) Schemas
>>
>> o XML DTDs
>>
>> o XML RelaxNG definitions
>>
>> o tables of values
>>
>> o classical programming code
>>
>>
>> _______________________________________________
>> Trustees mailing list
>> Trustees at ietf.org
>> https://www.ietf.org/mailman/listinfo/trustees
Attachment:
IETF-Trust-License-Policy.pdf
Description: Adobe PDF document
Attachment:
IETF-Trust-License-Policy.pdf
Description: Adobe PDF document
aWxlcg08PC9TaXplIDQ4Pj4Nc3RhcnR4cmVmDTExNg0lJUVPRg0=
_______________________________________________ Ipr-wg mailing list Ipr-wg at ietf.org https://www.ietf.org/mailman/listinfo/ipr-wg