From dev-return-21649-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Tue Mar 31 23:35:30 2009 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 11781 invoked from network); 31 Mar 2009 23:35:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Mar 2009 23:35:30 -0000 Received: (qmail 37627 invoked by uid 500); 31 Mar 2009 23:35:30 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 37557 invoked by uid 500); 31 Mar 2009 23:35:30 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 37531 invoked by uid 99); 31 Mar 2009 23:35:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2009 23:35:30 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of preethi.cis@gmail.com designates 209.85.198.225 as permitted sender) Received: from [209.85.198.225] (HELO rv-out-0506.google.com) (209.85.198.225) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2009 23:35:18 +0000 Received: by rv-out-0506.google.com with SMTP id l9so3546254rvb.43 for ; Tue, 31 Mar 2009 16:34:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :x-mimeole; bh=8q81GAyqUon9bdCQUUWjZPVQvfcyk0hvPTc+CWBKg4M=; b=tyIIPdrjPX9Sf76cZRF919cZR+SXzJS+NEcrCRid66FA8kRp8aLYTBtyyxrcCMd30k sVWzXHcke/F//Pe5tuACtTAgafFFg6Dnk3Ar/14kr/zmvOL2IYrQ7qakd1sROYOyikcx gCwbrtmIF3N2/QouVHH4OlGy0pK5wFaVMbZ+M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:x-mimeole; b=lyLKs3NbQDyiQ/NNVCcduNiMR7fOBrSN9yv46GVLeT3AqWiX9LGyvg2J3qvQI/fxlL ljOl17Q97Z8Jp+zODemD0ZMYNDC/UXJ/F1J+NCQ6NrFhcJ9f9B+eFFxLdufiCFYmO9qb sYazVTP7OEgr1e2hJU/rnGOKYm/ZshnKSV2S8= Received: by 10.140.141.16 with SMTP id o16mr899907rvd.241.1238542497471; Tue, 31 Mar 2009 16:34:57 -0700 (PDT) Received: from prenatarwxp01 (dhcp-171-71-57-16.cisco.com [171.71.57.16]) by mx.google.com with ESMTPS id k2sm491002rvb.34.2009.03.31.16.34.55 (version=SSLv3 cipher=RC4-MD5); Tue, 31 Mar 2009 16:34:56 -0700 (PDT) From: "Preethi Natarajan" To: , Cc: "Jonathan Leighton" , "Preethi Natarajan \(prenatar\)" Subject: HTTP over SCTP Date: Tue, 31 Mar 2009 16:34:53 -0700 Message-ID: <001701c9b259$4caa6a40$103947ab@cisco.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C9B21E.A04B9240" X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcmyWUqkglB439nVTWGOiBqgdnifPg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C9B21E.A04B9240 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello folks, We are trying to adapt HTTP to work over SCTP streams (http://tools.ietf.org/html/draft-natarajan-http-over-sctp-01). Since this proposal was received warmly at the httpbis WG, we are contemplating on a more formal specification of HTTP over SCTP. The current HTTP over SCTP design exploits SCTP streams to avoid head-of-line blocking. SCTP also offers other services unavailable in TCP such as unordered delivery, partially reliable transmission, message based transfer, multihoming support, more secure connection establishment with a cookie mechanism and so on. We plan on adapting our design proposal to leverage some/all of these SCTP services in the future. We implemented HTTP over SCTP streams in Apache and Firefox. Experiments show significant improvements to end user performance in networks with high latency and/or lossy paths. (I can point you to relevant material if you are interested in knowing more.) We are interested in submitting our code changes to APR and httpd. We'd very much appreciate guidance from httpd and APR developers on our mods and the submission process. Thanks! Preethi ------=_NextPart_000_0018_01C9B21E.A04B9240 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hello=20 folks,
 
We are = trying to=20 adapt HTTP to work over SCTP streams (htt= p://tools.ietf.org/html/draft-natarajan-http-over-sctp-01).=20 Since this proposal was received warmly at the httpbis WG, we are=20 contemplating on a more formal specification of HTTP over=20 SCTP.
 
The current HTTP over SCTP design=20 exploits SCTP streams to avoid = head-of-line blocking. SCTP also offers other services unavailable in = TCP such=20 as unordered delivery, partially reliable transmission, message based = transfer,=20 multihoming support, more secure connection establishment with a cookie=20 mechanism and so on. We plan on adapting our design proposal to leverage = some/all of these SCTP services in the future. 
 
We implemented HTTP over SCTP = streams in Apache and=20 Firefox. Experiments show significant improvements to end user=20 performance in networks = with high=20 latency and/or lossy paths. (I can point you to relevant material = if you=20 are interested in knowing more.)
 
We are=20 interested in submitting our code changes to APR and httpd. We'd = very=20 much appreciate guidance from httpd and APR developers on our mods=20 and the submission process. =
 
Thanks!
Preethi
------=_NextPart_000_0018_01C9B21E.A04B9240--