Re: [core] HTTP over UDP

Robert Cragie <robert.cragie@gridmerge.com> Fri, 26 March 2010 16:17 UTC

Return-Path: <robert.cragie@gridmerge.com>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 271643A6BB4 for <core@core3.amsl.com>; Fri, 26 Mar 2010 09:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.168
X-Spam-Level:
X-Spam-Status: No, score=-1.168 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, 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 MRIu7O47BfJH for <core@core3.amsl.com>; Fri, 26 Mar 2010 09:17:03 -0700 (PDT)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by core3.amsl.com (Postfix) with ESMTP id 702BD3A6B53 for <core@ietf.org>; Fri, 26 Mar 2010 09:15:21 -0700 (PDT)
Received: from 72-254-61-93.client.stsn.net ([72.254.61.93] helo=[10.7.39.29]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.70) id 1NvCCF-0006lo-NX for core@ietf.org; Fri, 26 Mar 2010 16:15:44 +0000
Message-ID: <4BACDDAB.9090506@gridmerge.com>
Date: Fri, 26 Mar 2010 09:15:39 -0700
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: core@ietf.org
References: <e9dffd641003260907n68333188ua6d2ff605c577897@mail.gmail.com>
In-Reply-To: <e9dffd641003260907n68333188ua6d2ff605c577897@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms060605030202020207080003"
Subject: Re: [core] HTTP over UDP
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: robert.cragie@gridmerge.com
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 16:17:05 -0000

It would seem reasonable to do this but HTTP is quite verbose so the aim 
is to compress the verbose text-based HTTP along with the content, which 
means that a request/response is more likely to fit into a UDP datagram, 
which is the aim for constrained environments.

Robert

Robert Cragie (Pacific Gas & Electric)

Gridmerge Ltd.
89 Greenfield Crescent,
Wakefield, WF4 4WA, UK
+44 (0) 1924 910888
http://www.gridmerge.com <http://www.gridmerge.com/>


On 26/03/2010 9:07 AM, Mark Baker wrote:
> Hello.  I've seen a handful of HTTP-like protocols over UDP proposed,
> but I'm curious why I haven't seen any mention of doing plain old HTTP
> over UDP, like this;
>
> http://tools.ietf.org/html/draft-goland-http-udp-00
>
> Has such an approach been considered and rejected?
>
> Mark.
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>
>