From problem-statement-bounces@alvestrand.no Tue Aug 10 08:47:41 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 IAA22213 for ; Tue, 10 Aug 2004 08:47:40 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6D52361B91; Tue, 10 Aug 2004 14:47:10 +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 17378-07; Tue, 10 Aug 2004 14:47:04 +0200 (CEST) Received: from eikenes.alvestrand.no (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 01D9361BFE; Tue, 10 Aug 2004 14:47:01 +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 B2E7561B8D for ; Tue, 10 Aug 2004 14:46:59 +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 17324-09 for ; Tue, 10 Aug 2004 14:46:58 +0200 (CEST) Received: from tiere.net.avaya.com (tiere.net.avaya.com [198.152.12.100]) by eikenes.alvestrand.no (Postfix) with ESMTP id 28E5961B95 for ; Tue, 10 Aug 2004 14:46:58 +0200 (CEST) Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i7ACjPne017210 for ; Tue, 10 Aug 2004 08:45:25 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i7ACjMne017172 for ; Tue, 10 Aug 2004 08:45:24 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 10 Aug 2004 15:46:52 +0300 Message-ID: Thread-Topic: Hello Thread-Index: AcR+2Bxh5zls6MD4TH21LzXADt8XbgAAAANS From: "Romascanu, Dan (Dan)" To: X-Virus-Scanned: by amavisd-new at alvestrand.no Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Out of Office AutoReply: Hello X-BeenThere: problem-statement@alvestrand.no X-Mailman-Version: 2.1.5 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 Content-Transfer-Encoding: quoted-printable I will be traveling for business purposes between August 1 and 12, and = then will be on vacation until August 30. My e-mail connectivity will be = scarce during this period, especially after August 14. I will however = check voice mail daily, and can be reached for urgent matters at the = mobile phone number +1-917-622-7831. Regards, Dan From problem-statement-bounces@alvestrand.no Fri Aug 27 19:59:25 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 TAA21860 for ; Fri, 27 Aug 2004 19:59:24 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 48A6E61C22; Sat, 28 Aug 2004 01:58:54 +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 09198-08; Sat, 28 Aug 2004 01:58:51 +0200 (CEST) Received: from eikenes.alvestrand.no (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C64AC61C18; Sat, 28 Aug 2004 01:58:50 +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 F27E261C18 for ; Sat, 28 Aug 2004 01:58:49 +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 09198-07 for ; Sat, 28 Aug 2004 01:58:48 +0200 (CEST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by eikenes.alvestrand.no (Postfix) with ESMTP id BA10561B98 for ; Sat, 28 Aug 2004 01:58:47 +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 i7RNvKJ05451; Fri, 27 Aug 2004 16:57:20 -0700 (PDT) Message-Id: <200408272357.i7RNvKJ05451@boreas.isi.edu> To: ietf-announce@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 27 Aug 2004 16:57:20 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Virus-Scanned: by amavisd-new at alvestrand.no X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: problem-statement@alvestrand.no, rfc-editor@rfc-editor.org Subject: RFC 3844 on IETF Problem Resolution Process X-BeenThere: problem-statement@alvestrand.no X-Mailman-Version: 2.1.5 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 3844 Title: IETF Problem Resolution Process Author(s): E. Davies, J. Hofmann, Eds. Status: Informational Date: August 2004 Mailbox: elwynd@nortelnetworks.com, jeanette@wz-berlin.de Pages: 20 Characters: 44841 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-problem-process-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3844.txt This Informational document records the history of discussions in the Problem WG during 2003 of how to resolve the problems described in the IETF Problem Statement. It decomposes each of the problems described into a few areas for improvement and categorizes them as either problems affecting the routine processes used to create standards or problems affecting the fundamental structure and practices of the IETF. Expeditious and non-disruptive solutions are proposed for the problems affecting routine processes. The document also lists suggested ways to handle the development of solutions for the structure and practices problems proposed in IETF discussions. Neither the working group nor the wider IETF has reached consensus on a recommendation for any of the proposals. This document therefore has no alternative but to suggest that the search for structure and practices solutions be handed back to the control of the IESG. While there was working group consensus on the processes for short-term and medium term improvements, there was no working group consensus on the proposals for longer-term improvements. This document therefore includes longer-term improvement proposals only as a matter of record; they must not be regarded as recommendations from the working group. 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. 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--