I-D Action: draft-bormann-core-coap-sig-01.txt

internet-drafts@ietf.org Sat, 11 June 2016 13:15 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5181512D51B for <i-d-announce@ietf.org>; Sat, 11 Jun 2016 06:15:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-bormann-core-coap-sig-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160611131515.28960.76542.idtracker@ietfa.amsl.com>
Date: Sat, 11 Jun 2016 06:15:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/PXxg4Ac0w-2O8WvSqYhKDBdR50U>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jun 2016 13:15:15 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : CoAP Signaling Messages
        Authors         : Carsten Bormann
                          Klaus Hartke
	Filename        : draft-bormann-core-coap-sig-01.txt
	Pages           : 11
	Date            : 2016-06-11

Abstract:
   draft-ietf-core-coap-tcp-tls defines how to transport CoAP messages
   on reliable transports such as TCP, TLS, or WebSockets.

   All these underlying protocols have ways to set up connection
   properties and manage the connection.  In many cases, these ways
   cannot be used very well for managing CoAP's use of the connection.

   Signaling messages are a way to signal information that is about the
   connection.  They form a third basic kind of messages in CoAP, beyond
   requests and responses.  Message class 7 is used for signaling
   messages.

   Signaling messages are only relevant for the connection they appear
   in.  The present draft assumes reliable, sequence-preserving
   connections.  It is for further study whether signaling messages are
   needed or useful for DTLS connections.

   The present draft, when adopted, would resolve CoRE tickets #400
   (message sizes), #388 (by providing a foundation for a mechanism for
   version negotiation, once that is needed), #390 (connection close
   reason), #391 (server name indication), #394 (ping/pong).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bormann-core-coap-sig/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-bormann-core-coap-sig-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-bormann-core-coap-sig-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/