IETF Logo Mail Archive

[core] CoAP over TCP

Carsten Bormann <cabo@tzi.org> Tue, 30 July 2013 12:34 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC22E21F8FD8 for <core@ietfa.amsl.com>; Tue, 30 Jul 2013 05:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.924
X-Spam-Level:
X-Spam-Status: No, score=-105.924 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZK8LBJMbzb5 for <core@ietfa.amsl.com>; Tue, 30 Jul 2013 05:34:40 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 28E4D21F9E3A for <core@ietf.org>; Tue, 30 Jul 2013 05:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r6UCYY3d023393 for <core@ietf.org>; Tue, 30 Jul 2013 14:34:34 +0200 (CEST)
Received: from dhcp-90f8.meeting.ietf.org (dhcp-90f8.meeting.ietf.org [130.129.8.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 79ABD2FC; Tue, 30 Jul 2013 14:34:34 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 30 Jul 2013 14:34:34 +0200
To: "core@ietf.org WG" <core@ietf.org>
Message-Id: <43DEBBFF-EF81-4B89-B911-46853BE7308B@tzi.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [core] CoAP over TCP
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 30 Jul 2013 12:34:50 -0000

It may seem obvious how to transport CoAP over TCP for the specific use cases that might benefit from that.  I have written up a small draft that discusses a couple more options than may come to mind immediately.  I wrote this up some time ago, but it might be useful as additional background material for Thursday's "Alternate Transports" segment.

Grüße, Carsten

Htmlized:        http://tools.ietf.org/html/draft-bormann-core-coap-tcp-00

Abstract:
  CoAP is defined to be transported over datagram transports such as
  UDP or DTLS.  For a number of applications, it may be useful to
  channel CoAP messages in a TCP connection.  This draft discusses
  different ways to do that.

v2.23.0 | Report a Bug | By Email