[GSMP] upcoming changes to specs

avri <avri@apocalypse.org> Mon, 16 June 2003 06:08 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29291 for <gsmp-archive@odin.ietf.org>; Mon, 16 Jun 2003 02:08:15 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5G67kn30278 for gsmp-archive@odin.ietf.org; Mon, 16 Jun 2003 02:07:46 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G67km30275 for <gsmp-web-archive@optimus.ietf.org>; Mon, 16 Jun 2003 02:07:46 -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 CAA28777 for <gsmp-web-archive@ietf.org>; Mon, 16 Jun 2003 02:07:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rn7S-0007Z8-00 for gsmp-web-archive@ietf.org; Mon, 16 Jun 2003 02:05:30 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Rn7R-0007Z5-00 for gsmp-web-archive@ietf.org; Mon, 16 Jun 2003 02:05:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G3HJa16282; Sun, 15 Jun 2003 23:17:19 -0400
Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G3GDm16263 for <gsmp@optimus.ietf.org>; Sun, 15 Jun 2003 23:16:13 -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 XAA17848 for <gsmp@ietf.org>; Sun, 15 Jun 2003 23:16:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RkRR-0006ld-00 for gsmp@ietf.org; Sun, 15 Jun 2003 23:13:57 -0400
Received: from cms1.etri.re.kr ([129.254.16.11]) by ietf-mx with esmtp (Exim 4.12) id 19RkRQ-0006lZ-00 for gsmp@ietf.org; Sun, 15 Jun 2003 23:13:56 -0400
Received: from apocalypse.org (129.254.191.55 [129.254.191.55]) by cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NAHCFNLM; Mon, 16 Jun 2003 12:16:12 +0900
Date: Mon, 16 Jun 2003 12:15:59 +0900
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
From: avri <avri@apocalypse.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <DA69F864-9FA8-11D7-8727-000393CC2112@apocalypse.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [GSMP] upcoming changes to specs
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 <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: 7bit
Content-Transfer-Encoding: 7bit

I recommend that anyone who is planning to submit a draft by the
deadline, submit a note discussing the changes they are making
in the document this week.  Of course if it is a new document (e.g.
a mib or pib on partitioning - anyone?  or maybe the tdm spec?)
then an abstract would help.  We are scheduling for an hour so we
want to plan.

And as an author who is planing to submit an update before the
deadline (barely) i will go first.

---- changes to draft-ietf-gsmp-v3-base-spec

After some discussions withe the team working on the Optical
draft, it was determined that I had not yet generalized enough
of the messages; i.e. that a lot of message content was still
very packet switch oriented.  I am therefore in the process of
doing more generalization.  Specifically:

- event flags - a notation that 8 event flags (8-15)
are reserved for technology specific definition

- addition of a technology specific block to msg 64
(switch configuration message)

-msg 65 - the porttype specific data needs generalization.

-msf 67  capability set definition needs generalization

- i am not sure if i will have a chance to do some of the
required changes in the optical reqs spec which has just
been submitted to the iesg.

- there has been an issue concerning the size of the gsmp
message header brought up by the folks working on
optical burst switching - i will send a specific message to the
list on this issue.

-I have had some discussions with Jonathan Sadler on the best
way to designate  the port specific adaptations.
We have tentatively decided to add a block to the port configuration
message.  Jonathan is, hopefully, going to be putting out a
doc on this issue.  I don't know if I will get this in on this pass.

So, for all the folks who spoken to me in the privately, I have two
requests;

- correct me if i left out one of the changes i agreed to make
- please discuss issues on the list so more people can voice
their opinions.

thanks
a.

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