IETF Logo Mail Archive

Re: [6lowapp] Charter and transports

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 03 November 2009 17:09 UTC

Return-Path: <pthubert@cisco.com>
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 4AC313A691D for <6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 09:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.69
X-Spam-Level:
X-Spam-Status: No, score=-9.69 tagged_above=-999 required=5 tests=[AWL=0.909, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 P3iLwivgglRc for <6lowapp@core3.amsl.com>; Tue, 3 Nov 2009 09:09:47 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id B974228C11F for <6lowapp@ietf.org>; Tue, 3 Nov 2009 09:09:43 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjcAAELy70qQ/uCWe2dsb2JhbACbVQEBFiQGqwaYFYQ9BItm
X-IronPort-AV: E=Sophos;i="4.44,675,1249257600"; d="scan'208";a="53525573"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 03 Nov 2009 17:10:03 +0000
Received: from xbh-ams-102.cisco.com (xbh-ams-102.cisco.com [144.254.73.132]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id nA3HA3a8009764; Tue, 3 Nov 2009 17:10:03 GMT
Received: from xmb-ams-107.cisco.com ([144.254.74.82]) by xbh-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Nov 2009 18:10:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 3 Nov 2009 18:09:59 +0100
Message-ID: <6A2A459175DABE4BB11DE2026AA50A5D8E01DD@XMB-AMS-107.cisco.com>
In-Reply-To: <261EF2B6-82AF-4FBD-AC71-609617E7A7CE@surrey.ac.uk>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [6lowapp] Charter and transports
Thread-Index: AcpcprrK21Aa5NvtRRCrTml7lyZuHgAAVt/g
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> <261EF2B6-82AF-4FBD-AC71-609617E7A7CE@surrey.ac.uk>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Lloyd Wood" <L.Wood@surrey.ac.uk>, <6lowapp@ietf.org>
X-OriginalArrivalTime: 03 Nov 2009 17:10:03.0365 (UTC) FILETIME=[7BBBD950:01CA5CA8]
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 17:09:48 -0000

Hi Lloyd,

Glad you mention it.

Is there a way to see Saratoga without the 'DTN' piece? 
Could you elaborate a bit on how flow control is done in Saratoga?

Cheers,

Pascal

>-----Original Message-----
>From: 6lowapp-bounces@ietf.org [mailto:6lowapp-bounces@ietf.org] On
Behalf Of Lloyd Wood
>Sent: mardi 3 novembre 2009 17:57
>To: 6lowapp@ietf.org
>Subject: Re: [6lowapp] Charter and transports
>
>> 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 mailing list
>6lowapp@ietf.org
>https://www.ietf.org/mailman/listinfo/6lowapp

v2.8.7 | Report a Bug | By Email