RFC 8352 on Energy-Efficient Features of Internet of Things Protocols
rfc-editor@rfc-editor.org Wed, 04 April 2018 04:07 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCC7126CD8; Tue, 3 Apr 2018 21:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 ZoQjg37QROOC; Tue, 3 Apr 2018 21:07:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FDA5124207; Tue, 3 Apr 2018 21:07:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 30D2CB824D1; Tue, 3 Apr 2018 21:06:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8352 on Energy-Efficient Features of Internet of Things Protocols
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lwip@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180404040646.30D2CB824D1@rfc-editor.org>
Date: Tue, 03 Apr 2018 21:06:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/saLZhZFdIxyDql4bDXHGVFV9UaM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 04 Apr 2018 04:07:16 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8352
Title: Energy-Efficient Features of
Internet of Things Protocols
Author: C. Gomez,
M. Kovatsch,
H. Tian,
Z. Cao, Ed.
Status: Informational
Stream: IETF
Date: April 2018
Mailbox: carlesgo@entel.upc.edu,
ietf@kovatsch.net,
tianhui@ritt.cn,
zhencao.ietf@gmail.com
Pages: 24
Characters: 61936
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lwig-energy-efficient-08.txt
URL: https://www.rfc-editor.org/info/rfc8352
DOI: 10.17487/RFC8352
This document describes the challenges for energy-efficient protocol
operation on constrained devices and the current practices used to
overcome those challenges. It summarizes the main link-layer
techniques used for energy-efficient networking, and it highlights
the impact of such techniques on the upper-layer protocols so that
they can together achieve an energy-efficient behavior. The document
also provides an overview of energy-efficient mechanisms available at
each layer of the IETF protocol suite specified for constrained-node
networks.
This document is a product of the Light-Weight Implementation Guidance Working Group of the IETF.
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/retrieve/bulk
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