Re: [Trustees] IETF Trust Decision on "Legal Provisions for IETF Documents" (dated October 16, 2008)

In the interest of (hopefully) persistently archiving the relevant legal
documents, at around the time they were published, I noticed that the
code component URL changed again.  The page
http://trustee.ietf.org/license-info/ now links to
http://trustee.ietf.org/docs/Code-Components-List-11-10-08.txt which has
the following SHA-1 hash:

fbb16427e7fcbb7a0e20d2811e03f17c59f50eee  Code-Components-List-11-10-08.txt

The content of the file is attached below for reference.

Btw, this is an area where publishing a CMS signature on the documents
would be useful...

/Simon

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)

not doing required disclosures

disclosure is not just a good idea ...

http://www.cafc.uscourts.gov/opinions/07-1545.pdf

Scott

Re: not doing required disclosures

Scott O. Bradner wrote:

How does this pertain to individuals requirements to disclose formally 
who they represent in their workings inside the IETF?

Todd Glassey
> disclosure is not just a good idea ...
>
> http://www.cafc.uscourts.gov/opinions/07-1545.pdf
>
> Scott
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wg <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ipr-wg
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com 
> Version: 8.0.176 / Virus Database: 270.9.11/1818 - Release Date: 11/28/2008 7:31 PM
>
>