Shorter msg for add reservations

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