RFC 7397: Report from the Smart Object Security Workshop
In plain English — editorial summary, not part of the RFC
This document provides a summary of a workshop on 'Smart Object Security' that took place in Paris on March 23, 2012. The main goal of the workshop was to allow participants to share their thoughts about the ability to utilize existing and widely deployed security mechanisms for smart objects. This report summarizes the discussions and lists the conclusions and recommendations to the Internet Engineering Task Force (IETF) community.
Document record
- Document ID
- RFC7397
- Published
- December 2014
- Authors
- J. Gilger; H. Tschofenig
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8628OAuth 2.0 Device Authorization GrantCurrent
August 2019
- RFC 7641Observing Resources in the Constrained Application Protocol (CoAP)Updated
September 2015
- RFC 7744Use Cases for Authentication and Authorization in Constrained EnvironmentsCurrent
January 2016
- RFC 6574Report from the Smart Object WorkshopCurrent
April 2012
- RFC 8240Report from the Internet of Things Software Update (IoTSU) Workshop 2016Current
September 2017
- RFC 8576Internet of Things (IoT) Security: State of the Art and ChallengesCurrent
April 2019
- RFC 7489Domain-based Message Authentication, Reporting, and Conformance (DMARC)Obsoleted
March 2015
- RFC 7076P6R's Secure Shell Public Key SubsystemCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?