datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Multicast requirements for control over LLN
draft-vanderstok-roll-mcreq-02

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-01-15 (latest revision 2012-07-14)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-vanderstok-roll-mcreq

Abstract

This is a working document intended to focus discussion on requirements for multicast in Low-power and Lossy Networks in the area of M2M communication for control applications. The Trickle algorithm, which uses random re-broadcasting to assure that messages arrive at all destinations, has been proposed in the Trickle Multicast Forwarding ROLL WG draft as the basis for a multicast routing protocol. In this draft additional requirements on multicast routing are presented, such as timeliness, motivated by building control. Random re-broadcasting and timeliness can be difficult to reconcile. This draft presents some simulation results in typical control settings which show that achieving latencies below 400 ms is feasible with Trickle. Recommendations are proposed for the current Trickle Multicast Forwarding draft to achieve optimal performance and meet the stated requirements.

Authors

Peter Van der Stok <consultancy@vanderstok.org>
Esko Dijk <esko.dijk@philips.com>
Armand Lelkens <armand.lelkens@philips.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)