From problem-statement-bounces@alvestrand.no Thu May 20 19:46:13 2004 Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06546 for ; Thu, 20 May 2004 19:46:13 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id B2D9261BF4; Fri, 21 May 2004 01:45:42 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12068-10; Fri, 21 May 2004 01:45:40 +0200 (CEST) Received: from eikenes.alvestrand.no (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 8B210622BE; Fri, 21 May 2004 01:45:40 +0200 (CEST) X-Original-To: problem-statement@alvestrand.no Delivered-To: problem-statement@alvestrand.no Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D9B9961B91 for ; Thu, 6 May 2004 01:27:14 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09038-10 for ; Thu, 6 May 2004 01:27:14 +0200 (CEST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4A20A61AA5 for ; Thu, 6 May 2004 01:27:13 +0200 (CEST) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i45NPeU09699; Wed, 5 May 2004 16:25:40 -0700 (PDT) Message-Id: <200405052325.i45NPeU09699@boreas.isi.edu> To: IETF-Announce: ; From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 05 May 2004 16:25:40 -0700 X-ISI-4-28-6-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Virus-Scanned: by amavisd-new at alvestrand.no X-Mailman-Approved-At: Fri, 21 May 2004 01:45:39 +0200 X-Content-Filtered-By: Mailman/MimeDel 2.1.3 Cc: problem-statement@alvestrand.no, rfc-editor@rfc-editor.org Subject: RFC 3774 on IETF Problem Statement X-BeenThere: problem-statement@alvestrand.no X-Mailman-Version: 2.1.3 Precedence: list List-Id: Problem Statement List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: problem-statement-bounces@alvestrand.no Errors-To: problem-statement-bounces@alvestrand.no X-Virus-Scanned: by amavisd-new at alvestrand.no --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3774 Title: IETF Problem Statement Author(s): E. Davies, Ed. Status: Informational Date: May 2004 Mailbox: elwynd@nortelnetworks.com Pages: 22 Characters: 55172 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-problem-issue-statement-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3774.txt 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. This document is a product of the Problem Statement Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart--