RFC 7452 on Architectural Considerations in Smart Object Networking
rfc-editor@rfc-editor.org Thu, 19 March 2015 23:30 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 CABE41A000D for <ietf-announce@ietfa.amsl.com>; Thu, 19 Mar 2015 16:30:19 -0700 (PDT)
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 8kBSOGF0z4jc for <ietf-announce@ietfa.amsl.com>; Thu, 19 Mar 2015 16:30:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 30DCB1A0015 for <ietf-announce@ietf.org>; Thu, 19 Mar 2015 16:30:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 783DB18045E; Thu, 19 Mar 2015 16:29:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7452 on Architectural Considerations in Smart Object Networking
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150319232904.783DB18045E@rfc-editor.org>
Date: Thu, 19 Mar 2015 16:29:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/3q9cwFhpFzSuZMayoIIVQxpvxVE>
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: Thu, 19 Mar 2015 23:30:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7452
Title: Architectural Considerations in Smart Object
Networking
Author: H. Tschofenig, J. Arkko,
D. Thaler, D. McPherson
Status: Informational
Stream: IAB
Date: March 2015
Mailbox: Hannes.Tschofenig@gmx.net,
jari.arkko@piuha.net,
dthaler@microsoft.com,
dmcpherson@verisign.com
Pages: 24
Characters: 53504
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-iab-smart-object-architecture-06.txt
URL: https://www.rfc-editor.org/info/rfc7452
The term "Internet of Things" (IoT) denotes a trend where a large
number of embedded devices employ communication services offered by
Internet protocols. Many of these devices, often called "smart
objects", are not directly operated by humans but exist as components
in buildings or vehicles, or are spread out in the environment.
Following the theme "Everything that can be connected will be
connected", engineers and researchers designing smart object networks
need to decide how to achieve this in practice.
This document offers guidance to engineers designing Internet-
connected smart objects.
This document is a product of the Internet Architecture Board.
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