RFC 7102 on Terms Used in Routing for Low-Power and Lossy Networks

rfc-editor@rfc-editor.org Sat, 25 January 2014 00:35 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 9E74B1A023B; Fri, 24 Jan 2014 16:35:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 3Tp4PpF_GeFZ; Fri, 24 Jan 2014 16:35:36 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 6038F1A022B; Fri, 24 Jan 2014 16:35:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0EAB57FC158; Fri, 24 Jan 2014 16:35:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7102 on Terms Used in Routing for Low-Power and Lossy Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20140125003534.0EAB57FC158@rfc-editor.org>
Date: Fri, 24 Jan 2014 16:35:34 -0800
Cc: drafts-update-ref@iana.org, roll@ietf.org, 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, 25 Jan 2014 00:35:37 -0000

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

        
        RFC 7102

        Title:      Terms Used in Routing for 
                    Low-Power and Lossy Networks 
        Author:     JP. Vasseur
        Status:     Informational
        Stream:     IETF
        Date:       January 2014
        Mailbox:    jpv@cisco.com
        Pages:      8
        Characters: 16444
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-roll-terminology-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7102.txt

This document provides a glossary of terminology used in routing
requirements and solutions for networks referred to as Low-Power and
Lossy Networks (LLNs).  An LLN is typically composed of many embedded
devices with limited power, memory, and processing resources
interconnected by a variety of links.  There is a wide scope of
application areas for LLNs, including industrial monitoring, building
automation (e.g., heating, ventilation, air conditioning, lighting,
access control, fire), connected home, health care, environmental
monitoring, urban sensor networks, energy management, assets
tracking, and refrigeration.

This document is a product of the Routing Over Low power and Lossy networks 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://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