Browse Prior Art Database

Terminology for Constrained-Node Networks (RFC7228)

IP.com Disclosure Number: IPCOM000236778D
Publication Date: 2014-May-15
Document File: 34 page(s) / 38K

Publishing Venue

The IP.com Prior Art Database

Related People

C. Bormann: AUTHOR [+3]

Abstract

Small devices with limited CPU, memory, and power resources, so- called "constrained devices" (often used as sensors/actuators, smart objects, or smart devices) can form a network, becoming "constrained nodes" in that network. Such a network may itself exhibit constraints, e.g., with unreliable or lossy channels, limited and unpredictable bandwidth, and a highly dynamic topology.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Internet Engineering Task Force (IETF)                        C. Bormann Request for Comments: 7228                       Universitaet Bremen TZI Category: Informational                                         M. Ersue ISSN: 2070-1721                             Nokia Solutions and Networks                                                               A. Keranen                                                                 Ericsson                                                                 May 2014

                Terminology for Constrained-Node Networks

Abstract

   The Internet Protocol Suite is increasingly used on small devices    with severe constraints on power, memory, and processing resources,    creating constrained-node networks.  This document provides a number    of basic terms that have been useful in the standardization work for    constrained-node networks.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7228.

Bormann, et al.               Informational                     [Page 1]
 RFC 7228                     CNN Terminology                    May 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3

   2. Core...