[BXXPwg] Channel Number Range

Marshall T. Rose mrose+mtr.netnews@dbc.mtview.ca.us
Wed, 6 Jun 2001 18:09:34 -0700


> (1) Is it reasonable for a BEEP implementation to reject a channel open
request because the channel number request is out of some implementation
dependent supported range?  If so, what error message would the BEEP
implementation issue?

yes, it's reasonable.

as far as the error message, that's an api issue, which is out of scope for
the protocol spec.


> (2)  If the answer to (1) is "yes", is it reasonable to have the channel
number range be limited differently for different transport mappings? (e.g.
the full range 1..2147483647 for BEEP over TCP, but only 1..65535 for BEEP
over SCTP?)

yes.


> (3) While it would increase complexity of implementation somewhat, is
there any other reason that a dynamic mapping (handled by the mapping layer)
between BEEP channel and SCTP stream number would create problems?

complexity is a problem.


> (4) In practice, a number of the initial SCTP implementation don't provide
the entire 0..65536 channel range... is this true of the initial BEEP
implementations also?

it depends on the implementation. i suspect that someone writing beep for
the pocketpc, may decide to use some simple datastructures that require some
limitations...


> (5) Can anyone developing profiles for BEEP Application Layer Protocols
comment on how they see channel numbers being used in their protocols?
More specifically, are there real situations where one might forsee a need
to use channel numbers that exceed 65535?

with freedom comes responsibility.

/mtr