Routing for Low power and Lossy Networks (RL2N) BOF

Description:

L2Ns (e.g Sensor Networks) have very specific routing requirements
that are not met by existing routing protocols that have been designed
for networks with different properties and constraints. As a matter of
fact, a plethora of proprietary routing protocols have been developed
by various companies or ad-hoc SDOs during the past few years. L2Ns
undoubtedly require an end-to-end IP-based solution thus making
"Internet of Things" a reality to avoid expensive and non manageable
networks. The aim of this BOF is to discuss the need to form a new WG
devoted to the routing issues for L2Ns. Specific protocol proposals
are out of scope for BOF discussion.

BOF organization:

More than 200 people have registered to the rsn@ietf.org mailing list
so far; we expect about 100 attendees with a good mix of vendors (Arch
Rock, Sensinode, Cisco, Samsumg, Intel (to be confirmed), Microsoft,
Dust, Zensys, Service Providers (To be confirmed: FT, TI, NTT, ...),
end users (USN: Ubiquitous Sensor Networks in Korea).

BOF Chairs:
JP Vasseur - jpv@cisco.com
David Culler - dculler@archrock.com

Routing Area Directors:
Ross Callon - rcallon@juniper.net
David Ward - dward@cisco.com

Technical Advisor: David Ward - dward@cisco.com

Mailing Lists:
rsn@ietf.org (active)

Related IDs:
draft-culler-rsn-routing-reqs
draft-vasseur-culler-rl2n-problem-statement => To be posted soon
draft-brandt-rl2n-home-routing-reqs => Routing Requirements for
Connected Home
draft-pister-rl2n-industrial-routing-reqs => Routing Requirements for=

Industrial Automation (to be posted soon)
draft-levis-rl2n-overview-protocols => Protocol Survey

A summary of the RL2N work can be found: http://www.employees.org/~jvasseur/

Tentative BOF Agenda

1. Administrativia (Chairs, 5 min)
    - Notes takers
    - Agenda bashing

2. Scoping the BOF (Chairs/ADs, 10 min)
    - Motivation and problem statement presentation
    - Interaction with other WG (6lowpan)
    - What's in scope?
    - What's out of scope?

3. Routing requirements for Sensor Networks (several & chairs, 30mn)
    - Summary of the discussions on rsn@ietf.org
    - Routing requirements for L2Ns and Protocol survey
    - Security
    - Manageability

4. RL2N WG Charter discussion (15 mn)

5. Conclusion and next steps (10mn, chairs and ADs).

Why do we need a new routing WG ?

The 6Lowpan Working Group (INT area) has been focussing on IP over
IEEE 802.15.4 WPAN. Furthermore 6lowpan has specifically decided not
to work on routing solutions (IETF-69). RL2Ns would focus on routing
solution at layer 3 thus independently of the layer 2 (L2Ns are made
of a variety of layer1/2 protocols (Low Power Wifi, IEEE 802.15.4,
Wibree, wired, ...)) and would closely collaborate with the 6lowpan
WG. There is currently no other Working Group working on routing
protocols for L2Ns. Because L2Ns brings quite specific routing
requirements, existing routing protocols (MANET protocols, IGPs) do
not meet the requirements exposed in the application-specific
documents and a related protocol survey can be found in
draft-levis-rl2n-protocol-overview. That said, the new WG may decide
to adapt an existing routing protocol, in which case it will interact
with the relevant WG.

Pontential WG charter/Milestones: will be provided before end of
October, 2007.