- From: Tuexen Michael <michael.tuexen AT siemens.com>
- To: "'Sumathi.Elangovan'" <Sumathi.Elangovan AT uk.thalesgroup.com>, discussion AT sctp.de, "'Thomas Dreibholz'" <dreibh AT exp-math.uni-essen.de>
- Subject: RE: [SCTP-Discussion] assoc_change!!
- Date: Mon Dec 9 17:32:00 2002
- List-id: SCTP Discussions <discussion.sctp.de>
Hi,
there are constants defined in section 5.3.1.1
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctpsocket-05.txt
Unfortunately, we do not use the exact names of the constants but
you can find the ones we are using in ext_socket.h.
We will update the socketapi so the latest version of the ID
when a new release of the sctplib is available.
Best regards
Michael
Michael Tuexen Tel.: +49 89 722 47210
Siemens AG Fax: +49 89 722 48212
ICN CP SE C 7 e-mail:
Michael.Tuexen AT siemens.com
>
-----Original Message-----
>
From: Sumathi.Elangovan
>
[mailto:Sumathi.Elangovan AT uk.thalesgroup.com]
>
Sent: Monday, December 09, 2002 5:09 PM
>
To:
>
discussion AT sctp.de;
>
'Thomas Dreibholz'
>
Subject: [SCTP-Discussion] assoc_change!!
>
>
>
Hi!
>
>
I am testing the UDP-style interface for my
>
application...when I test it between two nodes....at the
>
server side.. I get assoc_change : state:11:error = 0, instr
>
=1, outstr = 1" which is defined within the handle event(). I
>
also get state as 12 and 14....I want to know what these
>
numbers represent,? Is it defined in your implementation
>
somewhere? When I observe the SCTP packets on the
>
ethereal...I can relate 11 as Association up....12 as
>
shutdown and 14 as Abort...but I am not absolutely
>
certain.Your help is much appreciated. Thank you!!!
>
>
Regards
>
Sumathi Elangovan
>
>
Sumathi Elangovan
>
Design Engineer
>
Thales Research Limited
>
Reading
>
Tel: 0118 923 8272
>
Email :
>
Sumathi.Elangovan AT uk.thalesgroup.com
>
>
>
>
>
**********************************************************************
>
This email and any files transmitted with it are intended solely for
>
the use of the individual or entity to whom they are addressed and may
>
not be divulged to any third party without the express permission of
>
the originator. Any views expressed in this message are those of the
>
individual sender, except where the sender specifically states them to
>
be the views of Thales Research & Technology (UK) Ltd.
>
**********************************************************************
>
_______________________________________________
>
discussion mailing list
>
discussion AT sctp.de
>
http://www.sctp.de/mailman/listinfo/discussion
>
Archive powered by MHonArc 2.6.19+.