Embed Size (px)
Citation preview
71th IETF, Philadelphia, March 2008
ROLL Working Group MeetingIETF-71, March 2008, Philadelphia
Online Agenda and Slides at:
https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi
Co-chairs: JP Vasseur/David CullerADs: Dave Ward/ Ross Callon
71th IETF, Philadelphia, March 2008
Note Well•Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:
•-the IETF plenary session,•-any IETF working group or portion thereof,•-the IESG or any member thereof on behalf of the IESG,•-the IAB or any member thereof on behalf of the IAB,•-any IETF mailing list, including the IETF list itself,•any working group or design team list, or any other list•functioning under IETF auspices,•-the RFC Editor or the Internet-Drafts function•All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979(updated by RFC 4879).
•Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.•Please consult RFC 3978 (and RFC 4748) for details.
•A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.
•A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.
71th IETF, Philadelphia, March 2008
Welcome to this first WG meeting !
http://www.ietf.org/html.charters/roll-charter.html Routing Over Low power and Lossy networks (roll) Last Modified: 2008-02-15 Additional information is available at tools.ietf.org/wg/roll
Chair(s):JP Vasseur <[email protected]> David Culler <[email protected]>
Routing Area Director(s):Ross Callon <[email protected]> David Ward <[email protected]> Routing Area Advisor:David Ward <[email protected]>
Mailing Lists:General Discussion: [email protected] To Subscribe: http://www.ietf.org/mailman/listinfo/roll Archive: http://www.ietf.org/mail-archive/web/roll/
71th IETF, Philadelphia, March 2008
Agenda - ROLL Working Group Meeting - IETF-71 - Philadelphia - March 2008
1) Agenda/admin (Chairs - 5mn) [5]
2) Charter Review and Milestones (Chairs - 10mn) [15]
3) Home Automation Routing Requirement in Low Power and Lossy Networksdraft-brandt-roll-home-routing-reqs-00 (Anders - 20mn) [35]
4) Industrial Routing Requirements in Low Power and Lossy Networksdraft-pister-rl2n-indus-routing-reqs-00 (Kris replaced by Geoff - 20mn) [55]
5) Urban WSNs Routing Requirements in Low Power and Lossy Networksdraft-dohler-rl2n-urban-routing-reqs-00 (Christian - 20mn) [75]
6) Overview of Existing Routing Protocols for Low Power and Lossy Networksdraft-levis-roll-overview-protocols-00 (David - 25mn) [100]
71th IETF, Philadelphia, March 2008
Charter Review and MilestonesWork Items:
• Produce routing requirements documents for Industrial, Connected Home, Building and urban sensor networks. Each document will describethe use case and the associated routing protocol requirements. Thedocuments will progress in collaboration with the 6lowpan Working Group(INT area).
• Survey the applicability of existing protocols to LLNs. The aim ofthis document will be to analyze the scaling and characteristics ofexisting protocols and identify whether or not they meet the routingrequirements of the applications identified above. Existing IGPs, MANET,NEMO, DTN routing protocols will be part of evaluation.
• Specification of routing metrics used in path calculation. Thisincludes static and dynamic link/node attributes required for routing inLLNs.
• Provide an architectural framework for routing and path selection atLayer 3 (Routing for LLN Architecture) that addresses such issues aswhether LLN routing protocols require a distributed and/or centralizedpath computation models, whether additional hierarchy is necessary andhow it is applied. Manageability will be considered with each approach,along with various trade-offs for maintaining low power operation,including the presence of non-trivial loss and networks with a verylarge number of nodes.
• Produce a routing security framework for routing in LLNs.
71th IETF, Philadelphia, March 2008
Milestones
Work Items:• Jul 2008 Submit Routing requirements for Industrial applications to the IESG
to be considered as an Informational RFC.• Jul 2008 Submit Routing requirements for Connected Home networks
applications to the IESG to be considered as an Informational RFC.• Jul 2008 Submit Routing requirements for Building applications to the IESG to
be considered as an Informational RFC.• Jul 2008 Submit Routing requirements for Urban networks applications to the
IESG to be considered as an Informational RFC.• Nov 2008 Submit Routing metrics for LLNs document to the IESG to be
considered as a Proposed Standard.• Feb 2009 Submit Protocol Survey to the IESG to be considered as an
Informational RFC.• Apr 2009 Submit Security Framework to the IESG to be considered as an
Informational RFC• May 2009 Submit the Routing for LLNs Architecture document to the IESG as
an Informational RFC.• Jun 2009 Recharter or close.
71th IETF, Philadelphia, March 2008
Few comments
• General: so far there has been lots of off-list discussion: please use the Mailing list,
• We first need to focus on the requirements documents: reviews, comments, … are real MUST
