rfc2850.txt

RFC 的详细文档！


RFC 2850                      IAB Charter                       May 2000


   The IAB may organize ad hoc bodies of independent technical experts
   to adjudicate technical disputes.

3. IAB Organization

3.1 IAB chair

   The members of the IAB shall select one of its full members to serve
   as the chair of the IAB, with all of the duties and responsibilities
   normally associated with such a position.  The term of the IAB chair
   shall be one year, with no restriction on renewal.  The chair of the
   IAB may be removed at any time by the affirmative vote of two-thirds
   of the members of the IAB, or as a result of his or her departure
   from the IAB.

   The chair of the IAB shall have the authority to manage the
   activities and meetings of the IAB.

3.2 Executive Director

   The chair of the IAB shall have the authority to appoint an honorary
   Executive Director (ExecD) for a one-year renewable term, and to
   remove him or her. The ExecD shall administer the internal operation
   of the IAB, e.g., organization of meetings and reporting of their
   results.

   The ExecD is an ex-officio member as defined in Section 1.2.

3.3 Selection of the IRTF chair

   The IAB shall have the authority to appoint the chair of the Internet
   Research Task Force (IRTF) for a two-year renewable term, and to
   remove him or her. The IRTF chair shall be responsible for the
   management and organization of the IRTF according to [BCP 8].

   The IRTF chair is an ex-officio member as defined in Section 1.2.

3.4 Liaisons within the IETF

   The chair of the IAB and another full IAB member (other than the IETF
   chair), to be selected by the IAB, shall serve as liaisons to the
   IESG. In addition, the IESG will appoint one of its members (other
   than the IETF chair) to serve as a liaison to the IAB.  The IESG
   liaison may attend IAB meetings.

   Vacancies in these liaison seats have no effect on the IAB's or the
   IESG's powers to make decisions.




IAB                      Best Current Practice                  [Page 5]

RFC 2850                      IAB Charter                       May 2000


3.5 Decision taking

   The IAB attempts to reach all decisions unanimously.  If unanimity
   cannot be achieved, the chair may conduct informal polls to determine
   consensus.  The IAB may make decisions and take action if at least
   seven full members concur and there are no more than two dissents.

   The IAB may reach decisions by face to face meeting, teleconference,
   Internet communication, or any combination of the above.

3.6 Openness and confidentiality

   The IAB publishes minutes of all its meetings on the Internet, and
   conducts an open meeting at every IETF meeting. It publishes all its
   findings as RFCs, Internet Drafts or messages to the IETF mailing
   list. However, discussion of personnel matters and possibly legal and
   financial matters may sometimes be required to be kept confidential,
   and the chair may, with the consent of the full members, exclude
   liaison and ex officio members from such discussions.

   Specifically, the IAB makes use of the second level domain iab.org
   and the URL http://www.iab.org to publish information.

Security Considerations

   This memo does not raise any known security threats.

Summary of Changes from RFC 1601

   This document replaces [RFC 1601]. The principal change is the
   removal of material now covered in [BCP 8], [BCP 9] and [BCP 10],
   with many consequent editorial changes.  Additional changes are:

      - description of decision making when unanimity cannot be achieved
      - note on openness and confidentiality
      - addition of liaison seats for the Internet Society and the IANA
      - revised text concerning the IANA and the RFC Editor
      - clarifications following legal review













IAB                      Best Current Practice                  [Page 6]

RFC 2850                      IAB Charter                       May 2000


References

   [RFC 1601]  Huitema, C., "Charter of the Internet Architecture Board
               (IAB)", RFC 1601, March 1994.

   [BCP 8]     Weinrib, A., and J. Postel, "IRTF Research Group
               Guidelines and Procedures", BCP 8, RFC 2014, October
               1996.

   [BCP 9]     Bradner, S., "The Internet Standards Process -- Revision
               3", BCP 9, RFC 2026, October 1996.

   [BCP 10]    Galvin, J., "IAB and IESG Selection, Confirmation, and
               Recall Process: Operation of the Nominating and Recall
               Committees", BCP 10, RFC 2282, February 1998.

Author's Address

   Brian E. Carpenter
   IBM
   c/o iCAIR
   Suite 150
   1890 Maple Avenue
   Evanston IL 60201
   USA

   EMail: [e-mail]
























IAB                      Best Current Practice                  [Page 7]

RFC 2850                      IAB Charter                       May 2000


Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS 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.

Acknowledgement

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



















IAB                      Best Current Practice                  [Page 8]