[Dtls-iot] RFC 7925 on Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things

rfc-editor@rfc-editor.org Tue, 19 July 2016 14:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40A7C12DFFB; Tue, 19 Jul 2016 07:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 R8ATrnm5Daig; Tue, 19 Jul 2016 07:33:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8BBB12DEDF; Tue, 19 Jul 2016 07:01:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BC2AFB80E13; Tue, 19 Jul 2016 07:01:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160719140117.BC2AFB80E13@rfc-editor.org>
Date: Tue, 19 Jul 2016 07:01:17 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtls-iot/2wPhWZNsQH6RFX5CUobQlpyD0i4>
Cc: dtls-iot@ietf.org, rfc-editor@rfc-editor.org
Subject: [Dtls-iot] RFC 7925 on Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2016 14:33:39 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7925

        Title:      Transport Layer Security (TLS) / 
                    Datagram Transport Layer Security (DTLS) Profiles 
                    for the Internet of Things 
        Author:     H. Tschofenig, Ed.,
                    T. Fossati
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2016
        Mailbox:    Hannes.Tschofenig@gmx.net, 
                    thomas.fossati@nokia.com
        Pages:      61
        Characters: 141911
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dice-profile-17.txt

        URL:        https://www.rfc-editor.org/info/rfc7925

        DOI:        http://dx.doi.org/10.17487/RFC7925

A common design pattern in Internet of Things (IoT) deployments is
the use of a constrained device that collects data via sensors or
controls actuators for use in home automation, industrial control
systems, smart cities, and other IoT deployments.

This document defines a Transport Layer Security (TLS) and Datagram
Transport Layer Security (DTLS) 1.2 profile that offers
communications security for this data exchange thereby preventing
eavesdropping, tampering, and message forgery.  The lack of
communication security is a common vulnerability in IoT products that
can easily be solved by using these well-researched and widely
deployed Internet security protocols.

This document is a product of the DTLS In Constrained Environments Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC