IETF Logo Mail Archive

Query: OpenSSL compatibility with LK-SCTP Transport.

sandeep kandula <sandeep.emb@gmail.com> Mon, 01 August 2011 07:13 UTC

Return-Path: <sandeepkandula30@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4788521F8541 for <tsvwg@ietfa.amsl.com>; Mon, 1 Aug 2011 00:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cq8Rqs1Huxcv for <tsvwg@ietfa.amsl.com>; Mon, 1 Aug 2011 00:13:53 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3310621F853E for <tsvwg@ietf.org>; Mon, 1 Aug 2011 00:13:52 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1112856wyj.31 for <tsvwg@ietf.org>; Mon, 01 Aug 2011 00:13:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=DAZvSMz2aHEa83XnjS8uDv6Okf2c+m3lFgyDdoO8E9M=; b=kvzzeuUqs1U5EbyVXDka2POPGghMwY6W3MHFyZmfjUcx8vD9KULQZz1Q9NYt5Kjnl0 WMir0nEtTcn26g53XNWkvKM5QsNMuInSEUV8WueEm0YIHkDoe2mR3Qpypkl7800ELcps 9ylKo55poZF90MNS6jQivkZhAv4DSpUo2Jlyw=
Received: by 10.216.135.71 with SMTP id t49mr370571wei.43.1312182837059; Mon, 01 Aug 2011 00:13:57 -0700 (PDT)
MIME-Version: 1.0
Sender: sandeepkandula30@gmail.com
Received: by 10.216.133.94 with HTTP; Mon, 1 Aug 2011 00:13:37 -0700 (PDT)
In-Reply-To: <CALLaRWrW_Mzr5JpCXiyurWTSvsgWs2Wi_52pQKvX0NG7FZJN1Q@mail.gmail.com>
References: <CALLaRWrW_Mzr5JpCXiyurWTSvsgWs2Wi_52pQKvX0NG7FZJN1Q@mail.gmail.com>
From: sandeep kandula <sandeep.emb@gmail.com>
Date: Mon, 01 Aug 2011 12:43:37 +0530
X-Google-Sender-Auth: jT8iXJm9dKM2gTVOKhCQNgfx9OM
Message-ID: <CALLaRWoTCucP2U9A=ak==t7U_mfxHJczjv-PKJ1E5cVxLqVPkQ@mail.gmail.com>
Subject: Query: OpenSSL compatibility with LK-SCTP Transport.
To: lksctp-developers <lksctp-developers@lists.sourceforge.net>, tsvwg <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="0016e6de17d3e221ad04a96c5f2c"
Cc: Rashm! Agrawal <rashmi.k.agrawal@gmail.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 01 Aug 2011 07:13:54 -0000

Hi All,

I’m a new baby to open source world. Please forgive me, if I posted this
query to a wrong mailing list.

Here is my query. Currently I have a proprietary application which uses
LKSCTP (Open source SCTP implementation) stack. And I’m planning use the
“Transport Layer Security” for the SCTP transport provided by the LKSCTP
community, as suggested by RFC 3436. (http://www.ietf.org/rfc/rfc3436.txt)

Can somebody help me regarding this, by answering following quires?

1.    Can I use TLS (Transport Layer Security) with LKSCTP, without losing
any of my SCTP features? If “No” What are SCTP features I cannot use with
TLS.
2.    Is OPENSSL is correct choice for this? If “No” Why cannot I use
OpenSSL for this? Do you have any other suggestion please help me.
3.    What are the limitations if I use the TLS for my application through
SCTP transport?

Please let me know if you have any suggestion or more information regarding
the same.
Thanks in advance for your help.



-- 
Regards,
Sandeep.

v2.46.0 | Report a Bug | By Email | System Status