Browse Prior Art Database

IETF Problem Statement (RFC3774)

IP.com Disclosure Number: IPCOM000028221D
Original Publication Date: 2004-May-01
Included in the Prior Art Database: 2004-May-05
Document File: 23 page(s) / 55K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Davies: AUTHOR [+2]

Abstract

This memo summarizes perceived problems in the structure, function, and processes of the Internet Engineering Task Force (IETF). We are attempting to identify these problems, so that they can be addressed and corrected by the IETF community.

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

Network Working Group                                     E. Davies, Ed.

Request for Comments: 3774                               Nortel Networks

Category: Informational                                         May 2004

                         IETF Problem Statement

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

   This memo summarizes perceived problems in the structure, function,

   and processes of the Internet Engineering Task Force (IETF).  We are

   attempting to identify these problems, so that they can be addressed

   and corrected by the IETF community.

   The problems have been digested and categorized from an extensive

   discussion which took place on the 'problem-statement' mailing list

   from November 2002 to September 2003.  The problem list has been

   further analyzed in an attempt to determine the root causes at the

   heart of the perceived problems: The result will be used to guide the

   next stage of the process in the Problem Statement working group

   which is to recommend the structures and processes that will carry

   out the corrections.

Davies                       Informational                      [Page 1]

RFC 3774                 IETF Problem Statement                 May 2004

Table of Contents

   1.  Introduction: Issues/Problems in the IETF Process  . . . . . .  2

       1.1.  Consequences of Past Growth  . . . . . . . . . . . . . .  3

       1.2.  The Aim is Improvement, not Finger-pointing  . . . . . .  4

       1.3.  Perceived Problems - Consensus on Solutions  . . . . . .  4

   2.  Root Cause Problems  . . . . . . . . . . . . . . . . . . . . .  5

       2.1.  Participants in the IETF do not have a Common

             Understanding of its Mission . . . . . . . . . . . . . .  5

       2.2.  The IETF does not Consistently use Effective

             Engineering Practices  . . . . . . . . . . . . . . . . .  7

       2.3.  The IETF has Difficulty Handling Large and/or Complex

             Problems . . . . . . . . . . . . . . . . . . . . . . . .  9

       2.4.  Three Stage Standards Hierarchy not properly Utilized  . 11

       2.5.  The IETF's Workload Exceeds the Number of Fully

             Engaged Participants . . . . . . . . . . . . . . . . . . 12

             2.5.1.  Lack of Formal Recognition . . . . . . . . . . . 13

       2.6.  The IETF Management Structure is not Matched to the

          ...