Re: [core] draft-bormann-core-coap-tcp
Carsten Bormann <cabo@tzi.org> Thu, 01 August 2013 07:52 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 283CA21F9DD5 for <core@ietfa.amsl.com>; Thu, 1 Aug 2013 00:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.063
X-Spam-Level:
X-Spam-Status: No, score=-106.063 tagged_above=-999 required=5 tests=[AWL=0.186, 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 MyyX64toTrJW for <core@ietfa.amsl.com>; Thu, 1 Aug 2013 00:52:24 -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 1D3BF21F9E0B for <core@ietf.org>; Thu, 1 Aug 2013 00:52:11 -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 r717q7sX029993; Thu, 1 Aug 2013 09:52:07 +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 C79B2B85; Thu, 1 Aug 2013 09:52:06 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <474bfcc6bc03b2cef5eab95f883c7830@xs4all.nl>
Date: Thu, 01 Aug 2013 09:52:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACB07377-D66F-4B44-8BB1-0CCD42A9A98F@tzi.org>
References: <474bfcc6bc03b2cef5eab95f883c7830@xs4all.nl>
To: consultancy@vanderstok.org
X-Mailer: Apple Mail (2.1508)
Cc: Core <core@ietf.org>
Subject: Re: [core] draft-bormann-core-coap-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: Thu, 01 Aug 2013 07:52:30 -0000
> I read your coap-tcp draft but I missed any text on TCP header size reduction. (If you mean as in RFC 6846 header compression, this should be orthogonal.) A reduced CoAP header is defined in the coap-over-websockets draft and I didn't see a need to invent another one, even though I'm not sure I like the version used in coap-over-websockets. Clearly, we would like to have a common way of compactifying the CoAP header for the reliable, connection-oriented transports, if we don't decide to stick with the 4-byte header (which is a bit awkward as it's not clear what to put into the message-ID field). This very moment I'm listening to the MINION talk by Janardhan Iyengar. I reference MINION as one possible approach for framing in the coap-over-tcp draft. Grüße, Carsten
- [core] draft-bormann-core-coap-tcp peter van der Stok
- Re: [core] draft-bormann-core-coap-tcp Carsten Bormann
- Re: [core] draft-bormann-core-coap-tcp Andrew Mcgregor