Re: V5UA RFC 3807: Stream Mapping: Possibly Unhandled Scenario

Hi Brian,

I understand your point, that "SHOULD" is only a recommendation, and hence an implementation using 2 streams would still be compliant to specs.

reg an implementation refusing to establish an SCTP association, do you mean that UA should send SCTP disconnect, if it finds out that number of streams in the established association is unsufficient?

What i understand from this is, that an implementation can only try using the recommended stream philosophy, however, if the peer node does not follow it, implementation will have 2 options:

1. Bring down the SCTP association

2. Else, it will have to start reusing the same stream for carrying data for more than one C channel.

thanks & rgds

Saurabh

-----"Brian F. G. Bidulock" <[email protected]> wrote: -----

To: Saurabh Jain/HSS@HSS
From: "Brian F. G. Bidulock" <[email protected]>
Date: 10/25/2006 05:58AM
cc: [email protected]
Subject: Re: [Sigtran] V5UA RFC 3807: Stream Mapping: Possibly Unhandled Scenario

Saurabh,

SHOULD not MUST. 2 streams are sufficient. It is not an error to
place C-channels on the same stream. If an implementation is worried
it should refuse to establish an SCTP association that does not have
sufficient streams to meet its operational objectives.

--brian

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/

" DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran