|
The current shipping release of Flextronics Software Systems (formerly HSS)
SCTP is Rel 5.0 and is uniquely positioned to meet the
Functional and Performance needs of Next Generation
Networks.
Feature list includes
- Compliant to IETF RFC 2960 and Implementor’s Guide draft < draft-ietf-tsgwg-sctpimpguide-08.txt>
- Conformance to SCTP MIB draft <draft-ietf-sigtran-sctp-mib-09txt>
- Conformance to Socket Interface draft <draft-ietf-tsvwg-sctpsocket-07.txt>
- Conformance to Adler 32 as defined in RFC 2960 and CRC32C as per Checksum Algorithm RFC 3309. Selection can be done at Init-time
- Conformance to SCTP Dynamic Addition/Deletionof IP addresses draft <draft-ietf-tsvwg-addip-sctp-07.txt>
- Conformance to SCTP Applicability Statement draft <draft-ietf-sigtran-sctp-applicability-08.txt>
- Support for Path MTU discovery procedures as per RFC 1191
- Support for TCP Congestion Control (for Delayed Acknowledgement) as per RFC 2581
- Support for MD5 Message Digest Algorithm as per RFC 1321
- Support for Security for Cookie Message Generation with as per RFC 2104 - MD5 cryptographic hash function
- Support for Sequence Number (TSN/SSN) generation as per RFC 1982
- Support for RFC 1750 -Randomness Recommendations for Secutiry (For initial Tag, TSN and private key)
- Support for multihoming, multi-streaming as specified in the protocol
- MT-Safe Support on per association basis
- Support for Compile/Run time configuration of Statistics, Errors and Traces with different levels
- Support for IPV6. The same association can also have both Ipv4 and Ipv6 Addresses
Redundancy
SCTP Stack redundancy feature supports HOT STANDBY
redundancy Model. This model of redundancy is also called
Transparent Update Model in Flextronics Software Systems terminology of redundancy
implementation. SCTP redundancy features also support
mechanism to bring a new or recovered Node to be synchronized
with current Active Node.
Ports Available
All Flextronics Software Systems stacks including SCTP stacks are based on HSS
AAPE™ Architecture, according to which all platform
(both operating system and hardware) specific interactions
are wrapped to a single module. With this effort to
port core stack code to a different platform is significantly
reduced. On an average it takes less that a couple of
weeks to port and test stack code to a new platform.
SCTP stack code is available for following Operating
Systems.
- Linux ( Kernel version 2.4.5 )
- SunOs (Version 2.5 and over)
- VxWorks (Version 5.5.1)
- Windows NT and Windows 2000 ( SCTP and M3UA)
Conformance
SCTP protocol stack was tested against a detailed test
plan for validating the conformance to various mandatory
and optional SCTP features. This document was also submitted
to IETF as conformance specification document.
Interoperability
To test the interoperability of its software stack with
other vendors, Flextronics Software Systems (formerly HSS) has been participating
in various interoperability events.
- SCTP bakeoff event at Research Triangle Park,
Raleigh, USA
This interoperability event was organized by Nortel
Networks and was held on October 2000. This event
was based on version 13 of SCTP specification. About
20 companies participated in this event
- SCTP interoperability Event at ETSI, France
This interoperability event was held at ETSI (European
Telecommunications Standards Institute) facilities
in Sophia Antipolis, France. This event was held in
June 2001. Siemens supported the bakeoff by providing
technical support for the test-bed. SCTP RFC 2960
based implementations were tested in the Bakeoff.
Performance
Optimization of software stack for memory and processing
power requirement for various scenarios like varying
User message sizes, number of configured associations/streams,
different traffic patterns etc. is an ongoing activity
with HSS SIGTRAN stacks. Detailed performance report
on SCTP stack running in various load conditions can
be obtained by sending a mail to support@flextronicssoftware.com.
For detailed IETF drafts mail us at hssinfo@flextronicssoftware.com.
|
