RFC 5867 on Building Automation Routing Requirements in Low-Power and Lossy Networks

rfc-editor@rfc-editor.org Fri, 11 June 2010 23:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3115828C189; Fri, 11 Jun 2010 16:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.186
X-Spam-Level:
X-Spam-Status: No, score=-1.186 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d7ucVgPGcaNt; Fri, 11 Jun 2010 16:24:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 6416C28C180; Fri, 11 Jun 2010 16:24:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6B5E0E06B1; Fri, 11 Jun 2010 16:24:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5867 on Building Automation Routing Requirements in Low-Power and Lossy Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20100611232415.6B5E0E06B1@rfc-editor.org>
Date: Fri, 11 Jun 2010 16:24:15 -0700
Cc: roll@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Jun 2010 23:24:13 -0000

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

        
        RFC 5867

        Title:      Building Automation Routing Requirements in 
                    Low-Power and Lossy Networks 
        Author:     J. Martocci, Ed.,
                    P. De Mil, N. Riou,
                    W. Vermeylen
        Status:     Informational
        Stream:     IETF
        Date:       June 2010
        Mailbox:    jerald.p.martocci@jci.com, 
                    pieter.demil@intec.ugent.be, 
                    nicolas.riou@fr.schneider-electric.com,  
                    wouter@vooruit.be
        Pages:      26
        Characters: 57123
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-roll-building-routing-reqs-09.txt

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

The Routing Over Low-Power and Lossy (ROLL) networks Working Group has
been chartered to work on routing solutions for Low-Power and Lossy
Networks (LLNs) in various markets: industrial, commercial (building),
home, and urban networks.  Pursuant to this effort, this document
defines the IPv6 routing requirements for building automation.  This 
document is not an Internet Standards Track specification; it is
published for informational purposes.

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/rfcsearch.html.
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