RFC 7397 on Report from the Smart Object Security Workshop

rfc-editor@rfc-editor.org Sat, 13 December 2014 00:54 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 907621A1A5C for <ietf-announce@ietfa.amsl.com>; Fri, 12 Dec 2014 16:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 YEC3Etqg-7xE for <ietf-announce@ietfa.amsl.com>; Fri, 12 Dec 2014 16:54:12 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 664221A8842 for <ietf-announce@ietf.org>; Fri, 12 Dec 2014 16:54:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A139181CD3; Fri, 12 Dec 2014 16:54:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7397 on Report from the Smart Object Security Workshop
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141213005405.7A139181CD3@rfc-editor.org>
Date: Fri, 12 Dec 2014 16:54:05 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/6UuebznH4S3QJfCCW-Fx-DalU0g
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 00:54:14 -0000

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

        
        RFC 7397

        Title:      Report from the Smart Object 
                    Security Workshop 
        Author:     J. Gilger, H. Tschofenig
        Status:     Informational
        Stream:     Independent
        Date:       December 2014
        Mailbox:    Gilger@ITSec.RWTH-Aachen.de, 
                    Hannes.tschofenig@gmx.net
        Pages:      23
        Characters: 51259
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-gilger-smart-object-security-workshop-03.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7397.txt

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.


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/rfc.html

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