Query regarding SCTP DATA packets with invalid SSN value
Padmalochan Moharana <padman.m@gmail.com> Tue, 21 December 2010 07:56 UTC
Return-Path: <padman.m@gmail.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 892F33A68E2 for <tsvwg@core3.amsl.com>; Mon, 20 Dec 2010 23:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHcNjl1MLLsJ for <tsvwg@core3.amsl.com>; Mon, 20 Dec 2010 23:56:54 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id A7C3E3A67B6 for <tsvwg@ietf.org>; Mon, 20 Dec 2010 23:56:54 -0800 (PST)
Received: by qwg5 with SMTP id 5so3723906qwg.31 for <tsvwg@ietf.org>; Mon, 20 Dec 2010 23:58:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=IBbOU56F1eDjTwvVMUsj5ZNO9D51e8PzzWBa2Bbid/M=; b=MXYJJRfHh38YLMxmzamwiDPFsKu7ADLN4MmAPUUz7WMcFBr3bqhrNl25mRSlp0aCzJ 3YW6467tpwLhy4j5mEzDNYDs1GB6YA3KsVrAwcNgvpQYi8BKxxJP7dL/rxZ/CICzBk5l sAPS1vnHrPsTQxzDz6Vb+J9z5P/gvrt4qaq24=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CKJ6Kt7s/LbRobMeGPeh5O2N2gfeFWIs2edTLJyKvqvQ4RihmfP3eZ112/K+JWlGmX Najjcf5LsZ1y6LuW0EJooyNDIM9uP1+9XCLnQSgVhUnCbRfdORE8Uch0yKyCibfymSyJ ciZyUx5Rl+Ksvbd6OPve5Og8Km/8x0R94DPSk=
MIME-Version: 1.0
Received: by 10.229.216.143 with SMTP id hi15mr4731274qcb.27.1292918329726; Mon, 20 Dec 2010 23:58:49 -0800 (PST)
Received: by 10.229.75.71 with HTTP; Mon, 20 Dec 2010 23:58:49 -0800 (PST)
Date: Tue, 21 Dec 2010 13:28:49 +0530
Message-ID: <AANLkTimifM7Fv==sTE6447_W4av94+bHqxQPs8E2Yv=f@mail.gmail.com>
Subject: Query regarding SCTP DATA packets with invalid SSN value
From: Padmalochan Moharana <padman.m@gmail.com>
To: tsvwg <tsvwg@ietf.org>, Vlad Yasevich <vladislav.yasevich@hp.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Dec 2010 07:56:55 -0000
Hi, What will be the behavior of an SCTP end point on receive SCTP packets with valid TSN but invalid SSN in case of order delivery ? Suppose the ssn value of a sctp packet is corrupted by a hacker then in case of order delivery request should data packet hold by the end point and block that stream until it receive packets with proper order? Br, Padmalochan
- Query regarding SCTP DATA packets with invalid SS… Padmalochan Moharana
- Re: Query regarding SCTP DATA packets with invali… Randy Stewart