[GSMP] IETF58 and other issues

Avri Doria <avri@acm.org> Sat, 18 October 2003 00:58 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02130 for <gsmp-archive@odin.ietf.org>; Fri, 17 Oct 2003 20:58:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfPv-0004JV-UN for gsmp-archive@odin.ietf.org; Fri, 17 Oct 2003 20:58:04 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9I0w3Ea016575 for gsmp-archive@odin.ietf.org; Fri, 17 Oct 2003 20:58:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfPv-0004JG-PC for gsmp-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 20:58:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02108 for <gsmp-web-archive@ietf.org>; Fri, 17 Oct 2003 20:57:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAfPt-0003mC-00 for gsmp-web-archive@ietf.org; Fri, 17 Oct 2003 20:58:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAfPs-0003m8-00 for gsmp-web-archive@ietf.org; Fri, 17 Oct 2003 20:58:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfPt-0004It-92; Fri, 17 Oct 2003 20:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfPc-0004HQ-C4 for gsmp@optimus.ietf.org; Fri, 17 Oct 2003 20:57:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02091 for <gsmp@ietf.org>; Fri, 17 Oct 2003 20:57:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAfPV-0003lj-00 for gsmp@ietf.org; Fri, 17 Oct 2003 20:57:37 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1AAfPU-0003lf-00 for gsmp@ietf.org; Fri, 17 Oct 2003 20:57:36 -0400
Received: from [147.28.0.62] (helo=acm.org) by psg.com with esmtp (Exim 4.24; FreeBSD 4.9) id 1AAfPT-000J2I-8F for gsmp@ietf.org; Sat, 18 Oct 2003 00:57:36 +0000
Date: Sat, 18 Oct 2003 09:57:47 +0900
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
From: Avri Doria <avri@acm.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1700C291-0106-11D8-94DA-000393CC2112@acm.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: quoted-printable
Subject: [GSMP] IETF58 and other issues
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
X-BeenThere: gsmp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>, <mailto:gsmp-request@ietf.org?subject=unsubscribe>
List-Id: General Switch Management Protocol WG <gsmp.ietf.org>
List-Post: <mailto:gsmp@ietf.org>
List-Help: <mailto:gsmp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gsmp>, <mailto:gsmp-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

While there has been a bit more traffic on the list and the work seems 
to be moving forward, I am still not sure whether there is enough 
activity at the moment to warrant a WG meeting in Minneapolis.

I would like to hear, on the list,  from anyone who has an issue that 
they feel should be discussed at the meeting.  I would also like to 
hear from anyone who is submitting a draft and feels the need to 
discuss it in the face to face forum.

I will be submitting an update to the base draft later today or 
tomorrow that includes fixes to the issues that Jay brought up in his 
message.  Basically I fixed the typos and added the extension block to 
the configuration message.   I also made some changes to the capability 
set block. QAs the addition of the general extension block there did 
not seem to work as well as it should i made the extension more 
specific to the capability set functionality.   I don't expect anyone 
had tried to use it yet since they would have screamed, figuratively, 
at me if they had.  As usual, i will be looking for comments and issues 
once it comes out.

Finally, Kenneth and I are working on a rework of our schedule.  We 
have, obviously missed our remaining milestones by a long way.  One of 
the ideas we have had is to break the major milestone:

> Dec 02
>   
> Submit GSMPv3 extensions to include control of switches  supporting 
> optical, TDM and other CCAMP features and any  updates of the base 
> spec for Proposed Standard

Into 3 milestones:

- submit rewritten base and packet specification  to the IESG for PS 
consideration
- submit optical spec   to the IESG for PS consideration
- submit tdm spec   to the IESG for PS consideration

the reason for subdividing them are:

-the work of dividing up the spec as we have done was not planned when 
the milestone where first written, it was the result of looking at the 
effect of adding all of the TDM and Optical content to RFC 3292 and 
realizing that it would be too cumbersome and insufficiently versatile. 
  It has also taken more effort then was originally thought as the 
packet and base were so intimately intertwined in the original.
-the base and packet specs together essentially reproduce the 
functionality of current RFC 3292 and are, in my estimation, the 
closest to being done.  With a little bit of focus, they could be ready 
for WG last call before IETF59.   Additionally the current MIB, 
RFC3295, covers this functionality and should need little or no 
revision.
-the optical spec and the tdm spec are individual documents and each 
requires a supporting MIB.  While the optical spec is in progress, 
neither the TDM spec nor the MIBS are as of yet.  So reasonable 
schedules for these need to be worked out.

Opinions?  discussion?

thanks

a.

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