Browse Prior Art Database

The IETF in the Large: Administration and Execution (RFC3716)

IP.com Disclosure Number: IPCOM000022703D
Original Publication Date: 2004-Mar-01
Included in the Prior Art Database: 2004-Mar-26
Document File: 41 page(s) / 91K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

IAB Advisory Committee: AUTHOR

Abstract

In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB Advisory Committee (AdvComm), with a mandate to review the existing IETF administrative structure and relationships (RFC Editor, IETF Secretariat, IANA) and to propose changes to the IETF management process or structure to improve the overall functioning of the IETF. The AdvComm mandate did not include the standards process itself.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group IAB Advisory Committee

Request for Comments: 3716 IETF

Category: Informational March 2004

The IETF in the Large: Administration and Execution

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

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

Abstract

In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB

Advisory Committee (AdvComm), with a mandate to review the existing

IETF administrative structure and relationships (RFC Editor, IETF

Secretariat, IANA) and to propose changes to the IETF management

process or structure to improve the overall functioning of the IETF.

The AdvComm mandate did not include the standards process itself.

This memo documents the AdvComm's findings and proposals.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1. Overview of the AdvComm Work Process and Output. . . . 3

1.2. Scope. . . . . . . . . . . . . . . . . . . . . . . . . 3

1.3. Next Steps . . . . . . . . . . . . . . . . . . . . . . 4

2. Observations . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1. Current IETF Support Structure . . . . . . . . . . . . 4

2.1.1. What the Term IETF Includes in this Document . 4

2.1.2. Functions. . . . . . . . . . . . . . . . . . . 4

2.1.3. Support. . . . . . . . . . . . . . . . . . . . 6

2.2. Observed Stress Points . . . . . . . . . . . . . . . . 8

2.2.1. Stress Points Observed by IETF Leadership. . . 8

2.2.2. Stress Points Observed by Organizations

Supporting the IETF. . . . . . . . . . . . . . 10

2.3. A final Observation. . . . . . . . . . . . . . . . . . 10

3. Stand Facing the Future: Requirements for a Successful

IETF Administration. . . . . . . . . . . . . . . . . . . . . 10

3.1. Resource Management. . . . . . . . . . . . . . . . . . 10

3.1.1. Uniform Budgetary Responsibility . . . . . . . 10

IAB Advisory Committee Informational [Page 1]

RFC 3716 The IETF: Administration and Execution March 2004

3.1.2. Revenue Source Equivalence . . . . . . . . . . 11

3.1.3. Clarity in Relationship with Supporting

Organizations. . . . . . . . . . . . . . . . . 11

3.1.4. Flexibility in Service Provisioning. . . . . . 11

3.1.5. Administrative Efficiency. . . . . . . . . . . 11

3.2. Stewardship. . . . . . . . . . . . . . . . . . . . . . 12

3.2.1. Accountability for Change. . . . . . . . . . . 12

3.2.2. Persistence and Accessibility of Records . . . 12

3.3. Working Environment. . . . . . . . . . . . . . . . . . 12

3.3.1. Service Automation . . . . . . . . . . . . . . 12

3.3.2. Tools. . . . . . . . . . . . . . . . . . . . . 13

4. Advisory Committee Advice . . . . . . . . . . . . . . . . . 13

4.1. Proposed: (Single) Formalized IETF Organizational

Entity . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.1. Comments on the Necessity of this

Formalization. . . . . . . . . . . . . . . . . 14

4.2. Possible Structures....