Hi Michael!But you are talking about an API. So you have to chose one.
Please! I need some more clarification.
My doubt is general. It is not based on using Socket API or SCTP API.
I have referred the TCP Listen socket and Connect socket only for explaining my doubt.This is the concept of the sctplib. Therefore it is not mentioned in the RFC...
As per your comment,
“The concept is that you first tear down all associations, delete them and then delete the instances.”
Please keep in mind that the API description in the RFC 2960 is for information
Is it mentioned in RFC? I need the reference to the statement.
SCENARIO 1:
Step 1:No problem. An end point can have multiple connections.
As per RFC2960 Section 10.1 A) Initialize:
Instance “X” is created.
Step 2:
As per RFC2960 10.2 D) COMMUNICATION UP notification:
Associations are accepted from the peer systems “A” and “B”.
So using a single instance, two associations are ACCEPTED.
Step 3:Well, it does not make sense to have an association but have no end-points.
As per RFC2960 10.1 P) Destroy SCTP instance:
Instance “X” is to be destroyed.
My doubt is on Step 3.
Before deleting an Instance “X”, associations “A” and “B” are to be deleted or not?
(Since the association “A” and “B” are created using the instance “X”.) It is not mentioned in RFC.
SCENARIO 2:
Step 1:
As per RFC2960 Section 10.1 A) Initialize:
Instance “Y” is created.
Step 2:
As per RFC2960 10.1 B) Associate:
Associations are created with from the peer systems “C” and “D”.
So using a single instance, two associations are CREATED.
Step 3:
As per RFC2960 10.1 P) Destroy SCTP instance:
Instance “Y” is to be destroyed.
My doubt is on Step 3.
Before deleting an Instance “Y”, associations “C” and “D” are to be deleted or not ?
(Since the association “C” and “D” are created using the instance “Y”). It is not mentioned in RFC.
Thanks in advance.
With best regards,
S.Gobinath.
Reply:
I was referring to the sctplib callback API. This is completely
different
from the socket API. Which one are you referring to?
See more comments in-line.
Best regards
Michael
Inline comments in reply:
------------------------
Correct, but this is socket API.
I do not know what an instance is? But if you use the socket API for
SCTP it is
in this case pretty similar to the TCP case.
Original Message:
Please! I need some more clarification.
In case of TCP:
When the Listen socket is deleted, already accepted sockets will work unaltered.
Like that in case of SCTP:
When an Instance is deleted, all the associations created under it should be deleted or should work unaltered?
Thanks in advance
With best regards,
S.Gobinath.
Reply:
The concept is that you
first tear down all associations, delete them
and then delete the instances.
Best regards
Michael
Original Message:
Hi!
I am having a doubt on deleting an Instance.
I want to know, when an Instance is deleted whether all the associations
belong that instance will be deleted or not.
SCENARIO 1:
As from Client side:
Created an Instance "X"
Created an Association "A"
Created an Association "B"
Created an Association "C"
Delete an Instance "X"
Whether all the associations "A", "B" and "C"
will be deleted or not?
SCENARIO 2:
As from Server side:
Created an Instance "Y"
Accepted an Association "D"
Accepted an Association "E"
Accepted an Association "F"
Delete an Instance "Y"
Whether all the associations "D", "E" and "F" will be deleted or not?
Thanks in advance.
With best regards,
S.Gobinath.
Archive powered by MHonArc 2.6.19+.