Aseem,

Good point. Looks like an oversight. Using the other signaling entities, or SEs, as a guide, it appears that when there is a single SE per call, as is the case with CESE, no other information is required; however, when there can be multiple SEs per call, as is the case with CLCSE, RMSE, _and our "LCRSE"_, one must identify which instance of the incoming SE in the remote EP is being released.

As a practical matter, I would say that upon receipt of LogicalChannelRateRelease as it is currently defined in H.245v5, an EP should release _all_ incoming SEs. At the earliest opportunity, we should add a logical-channel-number extension addition to this message, i.e.,

LogicalChannelRateRelease ::=SEQUENCE { ..., logicalChannelNumber LogicalChannelNumber }

BTW, If we had gone to the trouble of defining an SE for these messages, I bet this oversight would have been caught in time.

Paul Long Smith Micro Software, Inc.

-----Original Message----- From: Aseem Agarwal [mailto:aseem@trillium.com] Sent: Wednesday, November 10, 1999 12:40 PM To: plong@SMITHMICRO.COM Cc: h323implementors@imtc.org Subject: Re: LogicalChannelRate Messages

hi Paul

A related question. There are no "sequence number and logical channel number" information elements in LogicalChannelRateRelease message. How will a receiving entity correctly associate this message to the request message received earlier in case multiple such requests are pending ?

regards, aseem