[GSMP] Shorter msg for add reservations

avri <avri@apocalypse.org> Fri, 20 June 2003 03:04 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 XAA01147 for <gsmp-archive@odin.ietf.org>; Thu, 19 Jun 2003 23:04:29 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5K343F25098 for gsmp-archive@odin.ietf.org; Thu, 19 Jun 2003 23:04:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TCC3-0006Wj-KP for gsmp-web-archive@optimus.ietf.org; Thu, 19 Jun 2003 23:04: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 XAA01127 for <gsmp-web-archive@ietf.org>; Thu, 19 Jun 2003 23:03:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TC9j-000669-00 for gsmp-web-archive@ietf.org; Thu, 19 Jun 2003 23:01:39 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19TC9i-000665-00 for gsmp-web-archive@ietf.org; Thu, 19 Jun 2003 23:01:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TCC1-0006WK-Iq; Thu, 19 Jun 2003 23:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TCBm-0006Vx-KE for gsmp@optimus.ietf.org; Thu, 19 Jun 2003 23:03: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 XAA01084 for <gsmp@ietf.org>; Thu, 19 Jun 2003 23:03:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TC9S-00065I-00 for gsmp@ietf.org; Thu, 19 Jun 2003 23:01:22 -0400
Received: from apocalypse.org ([192.48.232.17] ident=[of83yUOknr8m7wEcHHhT1CMWBQlJx9ba]) by ietf-mx with esmtp (Exim 4.12) id 19TC9R-000658-00 for gsmp@ietf.org; Thu, 19 Jun 2003 23:01:21 -0400
Received: from apocalypse.org (IDENT:fG/LH7y0x9gLcYRTRSOrwmPxgrQeAYN1@apocalypse.org [192.48.232.17]) by apocalypse.org (8.11.6/8.11.6) with ESMTP id h5K33eG12566 for <gsmp@ietf.org>; Thu, 19 Jun 2003 23:03:40 -0400
Date: Fri, 20 Jun 2003 12:03:36 +0900
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
From: avri <avri@apocalypse.org>
To: gsmp@ietf.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <DA69F864-9FA8-11D7-8727-000393CC2112@apocalypse.org>
Message-Id: <C93F860A-A2CB-11D7-A220-000393CC2112@apocalypse.org>
X-Mailer: Apple Mail (2.552)
Content-Transfer-Encoding: 7bit
Subject: [GSMP] Shorter msg for add reservations
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

As promised a specific message on header compression.

On Monday, Jun 16, 2003, at 12:15 Asia/Seoul, avri wrote:

>
>
> - 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.
>

So, what do people think?

Should there be a general mechanism inserted similar to the
short headers we removed over 2 years ago?  Some new sort
of header compression?

Should there be a new mechanism related solely to reservations.
I.e. a new add-reservation message is created that includes only

[vers, sub, msg type, result, code]
[partition id, transaction id]
[reservation id]
[I, submsg, length]  or is this needed - though we may be able to
                                use a bulk mechanism for other add-resv 
uses

anything else?   and is this still too big?

And does the reservation message need to  changed
to allow for these complete reservations.  What, if anything needs
to be added to the reservation message?

Opinions?  suggestions?

Please, speak up. As an editor, I am am working on the
update for the upcoming meeting at the moment, and need
guidance.

As a co-chair, I would like to know if there is consensus on making
such a change.

I encourage the Optical draft team to discuss their rationale and needs
on the list in response to this message.


a.

note: since i am functioning as a co-chair and editor, any process
issues that may arise from this dual role will be handled by the other
co-chair



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