RE: [mpowr] Rough Strawman of MPOWR Charter

"Robert Snively" <rsnively@Brocade.COM> Fri, 23 January 2004 20:57 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21732 for <mpowr-archive@odin.ietf.org>; Fri, 23 Jan 2004 15:57:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8MI-0002Dd-PG for mpowr-archive@odin.ietf.org; Fri, 23 Jan 2004 15:56:55 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NKusBB008528 for mpowr-archive@odin.ietf.org; Fri, 23 Jan 2004 15:56:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8MI-0002DR-J1 for mpowr-web-archive@optimus.ietf.org; Fri, 23 Jan 2004 15:56:54 -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 PAA21710 for <mpowr-web-archive@ietf.org>; Fri, 23 Jan 2004 15:56:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ak8MH-0003Xb-00 for mpowr-web-archive@ietf.org; Fri, 23 Jan 2004 15:56:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ak8LL-0003Vn-00 for mpowr-web-archive@ietf.org; Fri, 23 Jan 2004 15:55:56 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Ak8KX-0003UP-00 for mpowr-web-archive@ietf.org; Fri, 23 Jan 2004 15:55:05 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1Ak8KY-0002Vq-0U for mpowr-web-archive@ietf.org; Fri, 23 Jan 2004 15:55:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8KV-000295-DT; Fri, 23 Jan 2004 15:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8KO-00027V-So for mpowr@optimus.ietf.org; Fri, 23 Jan 2004 15:54:56 -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 PAA21653 for <mpowr@ietf.org>; Fri, 23 Jan 2004 15:54:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ak8KN-0003TS-00 for mpowr@ietf.org; Fri, 23 Jan 2004 15:54:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ak8Jc-0003Rw-00 for mpowr@ietf.org; Fri, 23 Jan 2004 15:54:08 -0500
Received: from f070.brocade.com ([66.243.153.70] helo=blasphemy.brocade.com) by ietf-mx with esmtp (Exim 4.12) id 1Ak8Im-0003L3-00 for mpowr@ietf.org; Fri, 23 Jan 2004 15:53:16 -0500
Received: from hq-ex-3.corp.brocade.com (hq-ex-3 [192.168.38.35]) by blasphemy.brocade.com (Postfix) with ESMTP id 551AE143D3; Fri, 23 Jan 2004 12:52:45 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpowr] Rough Strawman of MPOWR Charter
Date: Fri, 23 Jan 2004 12:52:45 -0800
Message-ID: <BA03B41AFFEA154B80DEB5BC9E4B65D005917A34@hq-ex-3.corp.brocade.com>
Thread-Topic: [mpowr] Rough Strawman of MPOWR Charter
Thread-Index: AcPh7sMHx+i9bpatTeWQr5Vz3lEtZwAAIr6w
From: Robert Snively <rsnively@Brocade.COM>
To: Margaret Wasserman <margaret@thingmagic.com>
Cc: mpowr@ietf.org
Content-Transfer-Encoding: quoted-printable
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: quoted-printable
Content-Transfer-Encoding: quoted-printable

> 
> > > [Question:  Should we including any wording about how this
> > > WG relates to the ICAR and NEWTRK efforts?]
> > >
> >
> >There should be explicit liaison activities among these
> >different activities, since a good idea in one may
> >solve a problem in another.
> 
> Can you suggest wording for the charter regarding what type
> of liaison activities these groups should have?

Try this.  Though it may be a bit more explicit than you
want in the text, we should certainly do most of it anyway.

"The working group will determine and periodically review
the requirements for liaison with other working groups
addressing related administrative and procedural issues.
At present the icar and newtrk efforts have been identified
as required contacts.  The liaison groups' 
mailing lists will be explicitly
notified of the posting of each new revision of the 
working group's drafts.  The liaison groups' mailing lists will be
explicitly informed of each of the working group's
consensus calls.  The liaison groups will be requested and
expected to express their consensus review of this
working group's drafts at working
group last call.  The liaison groups' mailing lists will
be provided the final list of last call comments and the resolution
of those comments."


> 
> >I would suggest that you explicitly reference the draft
> >"draft-ietf-problem-issue-statement-xx" and the related
> >draft "draft-ietf-problem-process-xx" as source documents
> >for this work.
> 
> Okay.  Do you think that we should explicitly state that this
> group is charged with addressing particular parts of the
> problem statement, or just provide a general reference?

I believe a general reference, similar to that made in
the proposed draft for icar, would be appropriate.  As
we review those documents, those parts where mpowr will 
address a particular issue should almost jump right out at us.
And mpowr's work should be dedicated to not making any of
the issues worse.  Text like the following might be
appropriate.

	"The work of the working group will consider relevant
	parts of the following reference drafts in its work.
	The draft "draft-ietf-problem-issue-statement-xx"
	provides a clear indication of many
	of the problems that the mpowr drafts need to address
	and avoid.  Mpowr's efforts should be consistent
	with the proposed resolution process in the draft 
	"draft "draft-ietf-problem-process-xx"."
	

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