Re: [core] I-D Action: draft-ietf-core-coap-tcp-tls-01.txt

Carsten Bormann <cabo@tzi.org> Thu, 19 November 2015 17:12 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 81DAB1B2CFF for <core@ietfa.amsl.com>; Thu, 19 Nov 2015 09:12:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 yHMS1eYTQdOu for <core@ietfa.amsl.com>; Thu, 19 Nov 2015 09:12:18 -0800 (PST)
Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D22B21B2CFA for <core@ietf.org>; Thu, 19 Nov 2015 09:12:16 -0800 (PST)
Received: from mfilter15-d.gandi.net (mfilter15-d.gandi.net [217.70.178.143]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 5E565FB8D2; Thu, 19 Nov 2015 18:12:15 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter15-d.gandi.net
Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter15-d.gandi.net (mfilter15-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id PpsfcdHaHgMt; Thu, 19 Nov 2015 18:12:13 +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 7DCD6FB88B; Thu, 19 Nov 2015 18:12:13 +0100 (CET)
Message-ID: <564E02EB.7060002@tzi.org>
Date: Thu, 19 Nov 2015 18:12:11 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: core@ietf.org
References: <20151119170916.4931.10171.idtracker@ietfa.amsl.com>
In-Reply-To: <20151119170916.4931.10171.idtracker@ietfa.amsl.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/q5xjirpCoQYhR07HTQp6TQRH2T8>
Subject: Re: [core] I-D Action: draft-ietf-core-coap-tcp-tls-01.txt
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, 19 Nov 2015 17:12:28 -0000

Sorry for the quick re-spin:
We have been alerted to a remnant of the length-field discussion, which
seems to be quite confusing to those who now want to implement the
decision.  So -01 just has the removal of that remnant:

https://www.ietf.org/rfcdiff?url2=draft-ietf-core-coap-tcp-tls-01

Grüße, Carsten


internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Constrained RESTful Environments Working Group of the IETF.
> 
>         Title           : A TCP and TLS Transport for the Constrained Application Protocol (CoAP)
>         Authors         : Carsten Bormann
>                           Simon Lemay
>                           Valik Solorzano Barboza
>                           Hannes Tschofenig
> 	Filename        : draft-ietf-core-coap-tcp-tls-01.txt
> 	Pages           : 12
> 	Date            : 2015-11-19
> 
> Abstract:
>    The Hypertext Transfer Protocol (HTTP) was designed with TCP as the
>    underlying transport protocol.  The Constrained Application Protocol
>    (CoAP), while inspired by HTTP, has been defined to make use of UDP
>    instead of TCP.  Therefore, reliable delivery and a simple congestion
>    control and flow control mechanism are provided by the message layer
>    of the CoAP protocol.
> 
>    A number of environments benefit from the use of CoAP directly over a
>    reliable byte stream such as TCP, which already provides these
>    services.  This document defines the use of CoAP over TCP as well as
>    CoAP over TLS.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-core-coap-tcp-tls/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-core-coap-tcp-tls-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-core-coap-tcp-tls-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>