Re: [core] CoAP implementation for TCP?

Carsten Bormann <cabo@tzi.org> Thu, 21 January 2016 12:09 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595F21ACD15 for <core@ietfa.amsl.com>; Thu, 21 Jan 2016 04:09:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDIa4hvu7M3v for <core@ietfa.amsl.com>; Thu, 21 Jan 2016 04:09:06 -0800 (PST)
Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [IPv6:2001:4b98:c:538::198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 414B91ACD02 for <core@ietf.org>; Thu, 21 Jan 2016 04:09:06 -0800 (PST)
Received: from mfilter25-d.gandi.net (mfilter25-d.gandi.net [217.70.178.153]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 91641FB8C4; Thu, 21 Jan 2016 13:09:04 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter25-d.gandi.net
Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter25-d.gandi.net (mfilter25-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id km-ke7kUnvwp; Thu, 21 Jan 2016 13:08:53 +0100 (CET)
X-Originating-IP: 93.199.254.229
Received: from nar.local (p5DC7FEE5.dip0.t-ipconnect.de [93.199.254.229]) (Authenticated sender: cabo@cabo.im) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id A90EBFB883; Thu, 21 Jan 2016 13:08:52 +0100 (CET)
Message-ID: <56A0CA52.8010101@tzi.org>
Date: Thu, 21 Jan 2016 13:08:50 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com>
References: <OF70FDA61F.29FDBC67-ON65257F41.003C9944-65257F41.003CF952@tcs.com>
In-Reply-To: <OF70FDA61F.29FDBC67-ON65257F41.003C9944-65257F41.003CF952@tcs.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/koP24xY77GFVJk2Ba-ImKnwmRoU>
Cc: core@ietf.org
Subject: Re: [core] CoAP implementation for TCP?
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 21 Jan 2016 12:09:08 -0000

Last time I looked at the libcoap variant employed by IoTivity, their
CoAP over TCP implementation was based on the L3 proposal -- the CoRE WG
chose L1 instead.
But changing that detail that is probably just a very small matter of
coding (and might have been done already, you may want to check).

Grüße, Carsten


Abhijan Bhattacharyya wrote:
> Dear List,
> Is there any available CoAP implementation that supports CoAP over TCP
> as suggested in "draft-ietf-core-coap-tcp-tls-01"?
> 
> Regards
> Abhijan Bhattacharyya
> Associate Consultant
> Scientist, Innovation Lab, Kolkata, India
> Tata Consultancy Services
> Mailto: abhijan.bhattacharyya@tcs.com
> Website: http://www.tcs.com <http://www.tcs.com/>
> ____________________________________________
> Experience certainty.        IT Services
>                        Business Solutions
>                        Consulting
> ____________________________________________
> 
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core