[rfc-dist] RFC 5673 on Industrial Routing Requirements in Low-Power and Lossy Networks

[rfc-editor@rfc-editor.org]

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

        
        RFC 5673

        Title:      Industrial Routing Requirements in Low-Power 
                    and Lossy Networks 
        Author:     K. Pister, Ed.,
                    P. Thubert, Ed.,
                    S. Dwars, T. Phinney
        Status:     Informational
        Date:       October 2009
        Mailbox:    kpister at dustnetworks.com, 
                    pthubert at cisco.com, 
                    sicco.dwars at shell.com,
                    tom.phinney at cox.net
        Pages:      27
        Characters: 67934
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-roll-indus-routing-reqs-06.txt

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

The wide deployment of lower-cost wireless devices will significantly
improve the productivity and safety of industrial plants while
increasing the efficiency of plant workers by extending the
information set available about the plant operations.  The aim of
this document is to analyze the functional requirements for a routing
protocol used in industrial Low-power and Lossy Networks (LLNs) of
field devices.  This memo provides information for the Internet community.

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 at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute