RE: [Tsvwg] SHUTDOWN COMPLETE chunk bundled with DATA chunk

"Ravindra Kumar SR" <ravindrakumar.sr@ccpu.com> Fri, 25 May 2007 12:05 UTC

Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrYYC-00046D-8B; Fri, 25 May 2007 08:05:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1HrVXA-0000gF-5E for tsvwg-confirm+ok@megatron.ietf.org; Fri, 25 May 2007 04:52:28 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1HrVX9-0000g6-RR for tsvwg@ietf.org; Fri, 25 May 2007 04:52:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HrVKO-0003d2-DR for tsvwg@ietf.org; Fri, 25 May 2007 04:39:16 -0400
Received: from defender.ccpu.com ([216.54.134.34] helo=smtp.ccpu.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HrVKN-0003UE-1o for tsvwg@ietf.org; Fri, 25 May 2007 04:39:16 -0400
Received: from smtp.ccpu.com (localhost.localdomain [127.0.0.1]) by localhost.ccpu.com (Postfix) with ESMTP id 783F33467CC; Fri, 25 May 2007 01:39:14 -0700 (PDT)
Received: from sd-exchange.ccsd.ccpu.com (sd-exchange.ccpu.com [172.16.0.203]) by smtp.ccpu.com (Postfix) with ESMTP id 6DC863467CB; Fri, 25 May 2007 01:39:13 -0700 (PDT)
Received: from IN-EXCHANGE.ccin.ccpu.com ([172.25.0.16]) by sd-exchange.ccsd.ccpu.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 May 2007 01:39:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] SHUTDOWN COMPLETE chunk bundled with DATA chunk
Date: Fri, 25 May 2007 14:09:04 +0530
Message-ID: <22F058C3ED9D784E90CE473F2A9847F00158A609@in-exchange>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Tsvwg] SHUTDOWN COMPLETE chunk bundled with DATA chunk
Thread-Index: AceepCkUsHqkZ/paQkCYtlCPeqL4kwAAOpbw
From: Ravindra Kumar SR <ravindrakumar.sr@ccpu.com>
To: devayya <devayya.bopaiah@alcatel-lucent.com>, Andrey Konstantinov <avkonst@gmail.com>
X-OriginalArrivalTime: 25 May 2007 08:39:12.0342 (UTC) FILETIME=[2B6A2760:01C79EA8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
X-TMDA-Confirmed: Fri, 25 May 2007 04:52:27 -0400
X-Mailman-Approved-At: Fri, 25 May 2007 08:05:42 -0400
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

There are 2 condition of receiving SHUTDOWN_COMPLETE+DATA packet

1> on the existing association
2> OOTB

In the first condition, after processing SHUTDOWN_COMPLETE chunk you
just have to discard the DATA chunk. The IP guru Jon Postel says "Be
liberal in what you accept and be conservative in what you send".  

In the second condition, silently discard the packet.

Regards,
Ravindra Kumar S R

-----Original Message-----
From: devayya [mailto:devayya.bopaiah@alcatel-lucent.com] 
Sent: Friday, May 25, 2007 1:38 PM
To: Andrey Konstantinov
Cc: tsvwg@ietf.org
Subject: Re: [Tsvwg] SHUTDOWN COMPLETE chunk bundled with DATA chunk

Andrey,

Since the SHUTDOWN COMPLETE is first chunk in the packet then the 
association state will reach CLOSED state. and so

The RFC 2960 says,

"A DATA chunk received in CLOSED is out of the blue and SHOULD be 
handled per 8.4."



Regards,
devayya


Andrey Konstantinov wrote:

> Hi,
>  
> I have a question, because I can not find the answer in RFC 2960.
>  
> There is a situation when SCTP receives packet with two chunks. First 
> chunk is SHUTDOWN COMPLETE, second chunk is DATA.
> I know that packet is formed wrongly by remote side, but what is exact

> behaviour on this packet?
>  
> I expect two variants:
> 1. SCTP stops processing of the message after SHUTDOWN COMPLETE chunk.
> 2. SCTP sends ABORT chunk on DATA chunk since the SHUTDOWN COMPLETE 
> chunk has been processed and there is no association for the DATA
chunk.
>  
> Could you say me what solution is correct?
>  
> Best regards,
> Andrey Konstantinov