Chronological Thread 

< Chronological >      < Thread >

---

Hello All,
If i am not wrong there is bug while processing of SCTP SACK chunk,
The function rtx_process_sack() doesn't handle Duplicates TSN's,
Once the Duplicate Packets are received i think they should be deleted from
the
Re-Transmission Queue which is not taking place.

If the Code is required for the same , i will attach it in my next mail.
Hari

-----Original Message-----
From:
discussion-admin AT sctp.de

[mailto:discussion-admin AT sctp.de]On
Behalf Of
discussion-request AT sctp.de
Sent: Sunday, December 16, 2001 4:32 PM
To:
discussion AT sctp.de
Subject: discussion digest, Vol 1 #200 - 1 msg


Send discussion mailing list submissions to

discussion AT sctp.de

To subscribe or unsubscribe via the World Wide Web, visit
http://www.sctp.de/mailman/listinfo/discussion
or, via email, send a message with subject or body 'help' to

discussion-request AT sctp.de

You can reach the person managing the list at

discussion-admin AT sctp.de

When replying, please edit your Subject line so it is more specific
than "Re: Contents of discussion digest..."


Today's Topics:

1. Error Simulation in M3UA (Sundaresan M)

--__--__--

Message: 1
From: "Sundaresan M"
<sundarem AT future.futsoft.com>
To:
<discussion AT sctp.de>
Date: Sat, 15 Dec 2001 17:43:07 +0530
charset="iso-8859-1"
Subject: [SCTP-Discussion] Error Simulation in M3UA
Reply-To:
discussion AT sctp.de

Hi,

Thanks for the replies on IUA. I got a good move into IUA.

But my M3UA related question is still not answered by the group.
Anyway I am sending the same query again to the group. I will be happy if
anyone could answer/guide me.

In M3UA, I was testing a Error condition - PROTOCOL ERROR.

According to draft-ietf-m3ua-06.txt --> Protocol error means the following,
The "Protocol Error" error is sent for any protocol anamoly i.e. , reception
of a parameter that is syntactically correct but unexpected in the current
situation.

When I was testing MGC from SG my scenario for the following looked like
this:
1) On receiving ASPUP from the ASP(MGC) send ASPUP ACK followed by the
Notify message with Routing context field populated.
--> Meaning that NOTIFY is expected at this moment, but without the ROuting
Context value. SO Notify is syntactically correct, but the parameter
"Routing Conext" is unexpected in current situation.
I think this is fine.

Now I am testing the SG side. But now I am unable to find a typical scenario
for PROTOCOL error situation. Can anyone help me out to figure a scenario
where this is possible.

If my question is unclear please inform me so that I can rephrase it.
But I am terribly expecting a reply from our energitic group.

Best Regards,
Sundar.


-----Original Message-----
From:
discussion-admin AT sctp.de

[mailto:discussion-admin AT sctp.de]On
Behalf Of
discussion-request AT sctp.de
Sent: Saturday, 15 December 2001 4:32 PM
To:
discussion AT sctp.de
Subject: discussion digest, Vol 1 #199 - 2 msgs


Send discussion mailing list submissions to

discussion AT sctp.de

To subscribe or unsubscribe via the World Wide Web, visit
http://www.sctp.de/mailman/listinfo/discussion
or, via email, send a message with subject or body 'help' to

discussion-request AT sctp.de

You can reach the person managing the list at

discussion-admin AT sctp.de

When replying, please edit your Subject line so it is more specific
than "Re: Contents of discussion digest..."


Today's Topics:

1. RE: discussion digest, Vol 1 #198 - 3 msgs
(hari AT cosystems.com)
2. Streams and D-Channels (Michael Mueller/bhu5nji)

-- __--__--

Message: 1
From:
hari AT cosystems.com
To:
<discussion AT sctp.de>
Date: Fri, 14 Dec 2001 19:07:15 +0530
Subject: [SCTP-Discussion] RE: discussion digest, Vol 1 #198 - 3 msgs
Reply-To:
discussion AT sctp.de

Hello sundar,
i think u r getting confused with the StreamId assignment to D-Channels.
It's only to remove the head-of-line blocking,
It's immaterial whether MGC and SG use same Stream ID for a D-Channel.
SG may assign for example interfaceId One ---> Stream ID 5 and MGC may
assign InterfaceID One-> Stream Id One.

So there need not be any transfer of information regarding the streamId
assignment between MGC and SG.
MGC will send the ASP_ACTIVE with a set of InterfaceID's on which MGC would
like to be ACTIVE that's it.

And, Yes u can send on a single StreamID mutiple D-Channel Signaling mesgs.

Hope i was able to clear the ideas on StreamID assignment.

Hari




discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion


End of discussion Digest_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion



--__--__--

_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion


End of discussion Digest_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion

---

• [SCTP-Discussion] Bug In Processing Of Sack, hari, 12/17/2001

---

Archive powered by MHonArc 2.6.19+.