Re: [6lowapp] Charter and transports
Lloyd Wood <L.Wood@surrey.ac.uk> Tue, 03 November 2009 16:56 UTC
Return-Path: <L.Wood@surrey.ac.uk>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 45E1A3A691D for <6lowapp@core3.amsl.com>;
Tue, 3 Nov 2009 08:56:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Wic13gZB9os7 for
<6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 08:56:55 -0800 (PST)
Received: from mail82.messagelabs.com (mail82.messagelabs.com
[195.245.231.67]) by core3.amsl.com (Postfix) with SMTP id BD0C23A680C for
<6lowapp@ietf.org>; Tue, 3 Nov 2009 08:56:54 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: L.Wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-82.messagelabs.com!1257267434!71764385!1
X-StarScan-Version: 6.1.3; banners=-,-,-
X-Originating-IP: [131.227.102.140]
Received: (qmail 26254 invoked from network); 3 Nov 2009 16:57:14 -0000
Received: from ads40.surrey.ac.uk (HELO ads40.surrey.ac.uk) (131.227.102.140)
by server-2.tower-82.messagelabs.com with SMTP; 3 Nov 2009 16:57:14 -0000
Received: from ads31.surrey.ac.uk ([131.227.120.131]) by ads40.surrey.ac.uk
with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Nov 2009 16:57:14 +0000
Received: from [192.168.1.209] ([86.3.114.249]) by ads31.surrey.ac.uk over TLS
secured channel with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 3 Nov 2009 16:57:14 +0000
Message-Id: <261EF2B6-82AF-4FBD-AC71-609617E7A7CE@surrey.ac.uk>
From: Lloyd Wood <L.Wood@surrey.ac.uk>
To: 6lowapp@ietf.org
In-Reply-To: <ca722a9e0911030839s7d2f609bu2e4adaa02298c66e@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 3 Nov 2009 16:57:13 +0000
References: <5A85AE5A-4C5D-4A0F-8CDF-BEB4C69FF002@cisco.com>
<5572F86E-C14F-48E6-922D-EABBB957EE22@nokia.com>
<4AEF832C.9050603@eecs.berkeley.edu>
<3C5BAF7D-CD31-434B-9AE2-BB8ED6C4B0E0@nokia.com>
<66D8B4F0-8106-47C2-8CC1-936791195D22@archrock.com>
<72876869-927E-45B6-A9D9-1A7E5A22E196@nokia.com>
<EB72DA52-70E1-404B-A507-4871720A1FA8@archrock.com>
<0D347129-430F-4902-B7AA-05D7B3360C2F@sensinode.com>
<921972845143124766@unknownmsgid>
<ca722a9e0911030839s7d2f609bu2e4adaa02298c66e@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 03 Nov 2009 16:57:14.0142 (UTC)
FILETIME=[B13DBBE0:01CA5CA6]
Subject: Re: [6lowapp] Charter and transports
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks
<6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>,
<mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>,
<mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2009 16:56:56 -0000
> Obviously UDP is something we will need to support as a transport for > CoAP, and I argue that we also need to allow the use of CoAP over TCP > as this is useful for some applications. When using UDP, some simple > mechanism for reliability (e.g. stop-and-wait) would of course be > needed along with a transaction ID (see e.g. 6lowapp-frank-chopan). > When doing this we should of course cooperate with TSV people. http://tools.ietf.org/html/draft-wood-tsvwg-saratoga is such a protocol, providing reliability and IDs. L. DTN work: http://info.ee.surrey.ac.uk/Personal/L.Wood/saratoga/ <http://info.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood@surrey.ac.uk>
- [6lowapp] Where does TCP not work Cullen Jennings
- Re: [6lowapp] Where does TCP not work Don Sturek
- Re: [6lowapp] Where does TCP not work Lars Eggert
- Re: [6lowapp] Where does TCP not work Kris Pister
- Re: [6lowapp] Where does TCP not work Lars Eggert
- Re: [6lowapp] Where does TCP not work Jonathan Hui
- Re: [6lowapp] Where does TCP not work Lars Eggert
- Re: [6lowapp] Where does TCP not work Jonathan Hui
- Re: [6lowapp] Where does TCP not work Lars Eggert
- Re: [6lowapp] Where does TCP not work Jonathan Hui
- Re: [6lowapp] Where does TCP not work Cullen Jennings
- Re: [6lowapp] Charter and transports Zach Shelby
- Re: [6lowapp] Where does TCP not work Pascal Thubert (pthubert)
- Re: [6lowapp] Where does TCP not work Kris Pister
- Re: [6lowapp] Where does TCP not work Kris Pister
- Re: [6lowapp] Where does TCP not work Don Sturek
- Re: [6lowapp] Charter and transports Don Sturek
- Re: [6lowapp] Where does TCP not work Don Sturek
- Re: [6lowapp] Where does TCP not work Richard Kelsey
- Re: [6lowapp] Where does TCP not work Pascal Thubert (pthubert)
- Re: [6lowapp] Charter and transports Lisa Dusseault
- Re: [6lowapp] Charter and transports Don Sturek
- Re: [6lowapp] Charter and transports Lloyd Wood
- Re: [6lowapp] Where does TCP not work Pascal Thubert (pthubert)
- Re: [6lowapp] Charter and transports Pascal Thubert (pthubert)
- Re: [6lowapp] Charter and transports Lloyd Wood
- Re: [6lowapp] Charter and transports Zach Shelby
- Re: [6lowapp] Charter and transports Don Sturek
- Re: [6lowapp] Where does TCP not work Lars Eggert
- Re: [6lowapp] Where does TCP not work Don Sturek
- Re: [6lowapp] Where does TCP not work Kris Pister
- Re: [6lowapp] Where does TCP not work Kris Pister
- Re: [6lowapp] Where does TCP not work Pascal Thubert (pthubert)
- Re: [6lowapp] Where does TCP not work Pascal Thubert (pthubert)