Architectural Considerations in Smart Object Networking

Document Type Replaced Internet-Draft (individual)
Authors Hannes Tschofenig  , Jari Arkko  , Dave Thaler  , Danny McPherson 
Last updated 2013-02-11 (latest revision 2012-12-27)
Replaced by RFC 7452
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-iab-smart-object-architecture
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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. How can different forms of embedded and constrained devices be interconnected? How can they employ and interact with the currently deployed Internet? This memo discusses smart objects and some of the architectural choices involved in designing smart object networks and protocols that they use. The document is being discussed at


Hannes Tschofenig (
Jari Arkko (
Dave Thaler (
Danny McPherson (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)