The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process
RFC 4333
Document | Type |
RFC
- Best Current Practice
(December 2005)
Obsoleted by RFC 8711
|
|
---|---|---|---|
Authors | Geoff Huston , Bert Wijnen | ||
Last updated | 2015-10-14 | ||
RFC stream | Internet Architecture Board (IAB) | ||
Formats |
RFC 4333
Appendix A. IAB Members Internet Architecture Board members at the time this document was written were the following: Bernard Aboba Loa Andersson Brian Carpenter Leslie Daigle Patrik Faltstrom Bob Hinden Kurtis Lindqvist David Meyer Pekka Nikander Eric Rescorla Pete Resnick Janathan Rosenberg Lixia Zhang Appendix B. IESG Members Internet Engineering Steering Group members at the time this document was written were the following: Brian Carpenter Bill Fenner Ted Hardie Sam Hartman Scott Hollenbeck Russell Housley David Kessens Allison Mankin Mark Townsley Jon Peterson Margaret Wasserman Bert Wijnen Alex Zinin Huston & Wijnen Best Current Practice [Page 7] RFC 4333 IAOC Member Selection December 2005 Authors' Addresses Geoff Huston (editor) APNIC EMail: gih@apnic.net Bert Wijnen (editor) Lucent Technologies EMail: bwijnen@lucent.com Huston & Wijnen Best Current Practice [Page 8] RFC 4333 IAOC Member Selection December 2005 Full 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. 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. Intellectual Property 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. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Huston & Wijnen Best Current Practice [Page 9]