[Lwip] RFC 8387 on Practical Considerations and Implementation Experiences in Securing Smart Object Networks
rfc-editor@rfc-editor.org Wed, 16 May 2018 00:15 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CDE12E8FA; Tue, 15 May 2018 17:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 dYJNlsqjtWMz; Tue, 15 May 2018 17:15:48 -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 96EEA12E8EB; Tue, 15 May 2018 17:15:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 00B06B8182E; Tue, 15 May 2018 17:15:45 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lwip@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180516001546.00B06B8182E@rfc-editor.org>
Date: Tue, 15 May 2018 17:15:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/UK-pC5MZzOIpZC6I6GVgXSOhBVk>
Subject: [Lwip] RFC 8387 on Practical Considerations and Implementation Experiences in Securing Smart Object Networks
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Lightweight IP stack <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2018 00:15:50 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8387
Title: Practical Considerations and Implementation Experiences
in Securing Smart Object Networks
Author: M. Sethi,
J. Arkko,
A. Keranen,
H. Back
Status: Informational
Stream: IETF
Date: May 2018
Mailbox: mohit@piuha.net,
jari.arkko@piuha.net,
ari.keranen@ericsson.com,
heidi.back@nokia.com
Pages: 33
Characters: 86278
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lwig-crypto-sensors-06.txt
URL: https://www.rfc-editor.org/info/rfc8387
DOI: 10.17487/RFC8387
This memo describes challenges associated with securing resource-
constrained smart object devices. The memo describes a possible
deployment model where resource-constrained devices sign message
objects, discusses the availability of cryptographic libraries for
resource-constrained devices, and presents some preliminary
experiences with those libraries for message signing on resource-
constrained devices. Lastly, the memo discusses trade-offs involving
different types of security approaches.
This document is a product of the Light-Weight Implementation Guidance Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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