Re: [mpowr] Why MPOWR?

Melinda Shore <mshore@cisco.com> Sat, 07 February 2004 14:18 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04576 for <mpowr-archive@odin.ietf.org>; Sat, 7 Feb 2004 09:18:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApTH3-00017L-BD for mpowr-archive@odin.ietf.org; Sat, 07 Feb 2004 09:17:33 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i17EHXQe004289 for mpowr-archive@odin.ietf.org; Sat, 7 Feb 2004 09:17:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApTH3-000176-7S for mpowr-web-archive@optimus.ietf.org; Sat, 07 Feb 2004 09:17:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04572 for <mpowr-web-archive@ietf.org>; Sat, 7 Feb 2004 09:17:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApTH1-00011y-00 for mpowr-web-archive@ietf.org; Sat, 07 Feb 2004 09:17:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApTG7-0000yk-00 for mpowr-web-archive@ietf.org; Sat, 07 Feb 2004 09:16:36 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1ApTFX-0000vS-00 for mpowr-web-archive@ietf.org; Sat, 07 Feb 2004 09:15:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApTFY-0000rg-E6; Sat, 07 Feb 2004 09:16:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ApTFF-0000pG-Bx for mpowr@optimus.ietf.org; Sat, 07 Feb 2004 09:15:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04550 for <mpowr@ietf.org>; Sat, 7 Feb 2004 09:15:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApTFD-0000vL-00 for mpowr@ietf.org; Sat, 07 Feb 2004 09:15:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApTEM-0000r3-00 for mpowr@ietf.org; Sat, 07 Feb 2004 09:14:46 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1ApTDm-0000k8-00 for mpowr@ietf.org; Sat, 07 Feb 2004 09:14:10 -0500
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i17EDbpp024077; Sat, 7 Feb 2004 06:13:37 -0800 (PST)
Received: from cisco.com ([10.25.65.182]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with SMTP id AQS42379; Sat, 7 Feb 2004 06:13:36 -0800 (PST)
Date: Sat, 07 Feb 2004 09:13:34 -0500
Subject: Re: [mpowr] Why MPOWR?
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v553)
Cc: mpowr@ietf.org
To: Bernard Aboba <aboba@internaut.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <Pine.LNX.4.56.0402040844140.19559@internaut.com>
Message-Id: <D091C8EF-5977-11D8-AC62-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
Content-Transfer-Encoding: 7bit
Sender: mpowr-admin@ietf.org
Errors-To: mpowr-admin@ietf.org
X-BeenThere: mpowr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>, <mailto:mpowr-request@ietf.org?subject=unsubscribe>
List-Id: Management Positions -- Oversight, Work and Results <mpowr.ietf.org>
List-Post: <mailto:mpowr@ietf.org>
List-Help: <mailto:mpowr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>, <mailto:mpowr-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wednesday, February 4, 2004, at 11:54 AM, Bernard Aboba wrote:
> There are even some drafts in the queue with no prospects for
> publication, since they have normative dependencies on drafts that were
> abandoned long ago and will never be completed (one of the MIDCOM
> documents is an example of this).

Note that the references in the midcom draft in question have been
corrected and the revised document is in the RFC editor's hands.  The
problem in this particular case is that because we don't have a way
of flagging documents as being dependencies there's no way to know
who to notify when work on a document is stopped or the document is
dropped completely.  This isn't an mpowr problem but rather a
tools problem.  It would be useful to tag unpublished documents that
are cited in somebody else's normative references so that when the
documents change status notifications can be propagated.  We're nowhere
near being able to put that kind of capability in the hands of
document editors, which is where it seems to me to belong.

Melinda


_______________________________________________
mpowr mailing list
mpowr@ietf.org
https://www1.ietf.org/mailman/listinfo/mpowr