[rfc-dist] RFC 3669 on Guidelines for Working Groups on Intellectual Property Issues

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Wed, 18 Feb 2004 12:17:21 -0800


A new Request for Comments is now available in online RFC libraries.

        RFC 3669

        Title:      Guidelines for Working Groups on Intellectual
                    Property Issues
        Author(s):  S. Brim
        Status:     Informational
        Date:       February 2004
        Mailbox:    sbrim@cisco.com
        Pages:      17
        Characters: 40946
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipr-wg-guidelines-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3669.txt

This memo lays out a conceptual framework and rules of thumb useful
for working groups dealing with Intellectual Property Rights (IPR)
issues.  It documents specific examples of how IPR issues have been
dealt with in the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <040218121621.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3669

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <040218121621.RFC@RFC-EDITOR.ORG>