[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 RFC 4371

Network Working Group                                  B. Carpenter (ed)
Internet-Draft                                                       IBM
Expires: March 31, 2006                                    L. Lynch (ed)
                                                                      UO
                                                      September 27, 2005


                      BCP101 Update for IPR Trust
                    draft-carpenter-bcp101-update-02

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 31, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document updates BCP 101 to take account of the new IETF
   Intellectual Property Trust.








Carpenter (ed) & Lynch (ed)  Expires March 31, 2006             [Page 1]

Internet-Draft                BCP101 Update               September 2005


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Updates to RFC 4071 . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5
   Intellectual Property and Copyright Statements  . . . . . . . . . . 6







































Carpenter (ed) & Lynch (ed)  Expires March 31, 2006             [Page 2]

Internet-Draft                BCP101 Update               September 2005


1.  Introduction

   The first version of BCP 101, i.e., RFC 4071 [1], assumed that the
   vehicle for certain IETF-related Intellectual Property Rights (IPR)
   would be the Internet Society (ISOC).  Since that time, an IETF Trust
   has been created to hold such IPR.  This document appropriately
   updates RFC 4071.

   This update comes into force as soon as it has been approved by the
   IESG and the IETF Trust Agreement has been formally signed by its
   Settlors and initial Trustees.

   Terms and abbreviations used in this document are defined in RFC
   4071.


2.  Updates to RFC 4071

   A Trust ("the IETF Trust") has been formed for the purpose of
   acquiring, holding, maintaining and licensing certain existing and
   future intellectual property and other property used in connection
   with the administration of the IETF.  The Trust was formed by the
   signatures of its Settlors and initial Trustees.  The Settlors, who
   contributed initial intellectual property to the Trust, were ISOC and
   the Corporation for National Research Initiatives.  The Trustees of
   the IETF Trust are the members of the IAOC, and the Beneficiary of
   the IETF Trust is the IETF as a whole.

   In its administration of IPR under the terms of BCP 101, the IASA,
   including the IAD and the IAOC, will treat the IETF Trust rather than
   ISOC as the proper entity for ownership and licensing of IETF IPR.
   Specifically, references to ISOC in sections 3.1, 5.3 and 7 of [1]
   shall be interpreted as referring to the IETF Trust wherever IPR
   issues are concerned.  The duty to serve as Trustees is added to
   section 3.2 of [1].


3.  Security Considerations

   This document has no security implications for the Internet.


4.  IANA Considerations

   This document requires no action by the IANA.






Carpenter (ed) & Lynch (ed)  Expires March 31, 2006             [Page 3]

Internet-Draft                BCP101 Update               September 2005


5.  Acknowledgements

   The members of the IAOC when this document was written were:
      Brian Carpenter
      Steve Crocker
      Leslie Daigle
      Ed Juskevicius
      Kurtis Lindqvist
      Lucy Lynch
      Ray Pelletier
      Lynn St Amour
      Jonne Soininen

   Useful comments were received from Harald Alvestrand.  Comments on
   RFC 4071 by Patrice Lyons assisted in preparing this document.

   This document was produced using the xml2rfc tool[2].


6.  References

6.1.  Normative References

   [1]  Austein, R. and B. Wijnen, "Structure of the IETF Administrative
        Support Activity (IASA)", BCP 101, RFC 4071, April 2005.

6.2.  Informative References

   [2]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
        June 1999.





















Carpenter (ed) & Lynch (ed)  Expires March 31, 2006             [Page 4]

Internet-Draft                BCP101 Update               September 2005


Authors' Addresses

   Brian Carpenter (ed)
   IBM
   48 Avenue Giuseppe Motta
   1211 Geneva 2,
   Switzerland

   Email: brc@zurich.ibm.com


   Lucy Lynch (ed)
   University of Oregon
   1225 Kincaid St
   Eugene, Oregon 97403
   USA

   Phone: +1 541 346 1774
   Email: llynch@darkwing.uoregon.edu
































Carpenter (ed) & Lynch (ed)  Expires March 31, 2006             [Page 5]

Internet-Draft                BCP101 Update               September 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Carpenter (ed) & Lynch (ed)  Expires March 31, 2006             [Page 6]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/