Multicast Protocol for Low power and Lossy Networks (MPL)
draft-ietf-roll-trickle-mcast-11
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7731.
|
|
|---|---|---|---|
| Authors | Jonathan Hui , Richard Kelsey | ||
| Last updated | 2015-02-05 (Latest revision 2014-11-24) | ||
| Replaces | draft-hui-6man-trickle-mcast | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Ines Robles | ||
| Shepherd write-up | Show Last changed 2014-04-14 | ||
| IESG | IESG state | Became RFC 7731 (Proposed Standard) | |
| Consensus boilerplate | Yes | ||
| Telechat date |
(None)
Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Alvaro Retana | ||
| IESG note | ** No value found for 'doc.notedoc.note' ** | ||
| Send notices to | roll-chairs@ietf.org, draft-ietf-roll-trickle-mcast@ietf.org | ||
| IANA | IANA review state | IANA OK - Actions Needed |
draft-ietf-roll-trickle-mcast-11
algorithm [RFC6206]. MPL Forwarders use MPL Control Messages to
discover new MPL Data Messages that have not yet been received.
When discovering that a neighboring MPL Forwarder has not yet
received an MPL Data Message, the MPL Forwarder schedules those
MPL Data Messages for transmission using the Trickle algorithm.
Note that the use of proactive and reactive forwarding strategies
within the same MPL Domain are not mutually exclusive and may be used
simultaneously. For example, upon receiving a new MPL Data Message
when both proactive and reactive forwarding techniques are enabled,
an MPL Forwarder will proactively retransmit the MPL Data Message a
limited number of times and schedule further transmissions upon
receiving MPL Control Messages.
4.4. Signaling Overview
MPL generates and processes the following messages:
MPL Data Message - Generated by an MPL Seed to deliver a multicast
message across an MPL Domain. The MPL Data Message's source is an
address in the Local Interface Set of the MPL Seed that generated
the message and is valid within the MPL Domain. The MPL Data
Message's destination is the MPL Domain Address corresponding to
the MPL Domain. An MPL Data Message contains:
* The Seed Identifier of the MPL Seed that generated the MPL Data
Message.
* The sequence number of the MPL Seed that generated the MPL Data
Message.
* The original multicast message.
MPL Control Message - Generated by an MPL Forwarder to communicate
information contained in an MPL Domain's Seed Set and Buffered
Message Set to neighboring MPL Forwarders. An MPL Control Message
contains a list of tuples for each entry in the Seed Set. Each
tuple contains:
* The minimum sequence number maintained in the Seed Set for the
MPL Seed.
* A bit-vector indicating the sequence numbers of MPL Data
Messages resident in the Buffered Message Set for the MPL Seed,
where the first bit represents a sequence number equal to the
minimum threshold maintained in the Seed Set.
* The length of the bit-vector.
Hui & Kelsey Expires May 28, 2015 [Page 8]
Internet-Draft MPL November 2014
5. MPL Parameters and Constants
This section describes various program and networking parameters and
constants used by MPL.
5.1. MPL Multicast Addresses
MPL makes use of MPL Domain Addresses to identify MPL Interfaces of
an MPL Domain. By default, MPL Forwarders subscribe to the
ALL_MPL_FORWARDERS multicast address with a scope value of 3
[RFC7346].
For each MPL Domain Address that an MPL Interface subscribes to, the
MPL Interface MUST also subscribe to the MPL Domain Address with a
scope value of 2 (link-local) when reactive forwarding is in use.
MPL Forwarders use the link-scoped MPL Domain Address to communicate
MPL Control Messages to neighboring (i.e. on-link) MPL Forwarders.
5.2. MPL Message Types
MPL defines an IPv6 Option for carrying an MPL Seed Identifier and a
sequence number within an MPL Data Message. The IPv6 Option Type has
value 0x6D.
MPL defines an ICMPv6 Message (MPL Control Message) for communicating
information contained in an MPL Domain's Seed Set and Buffered
Message Set to neighboring MPL Forwarders. The MPL Control Message
has ICMPv6 Type MPL_ICMP_TYPE.
5.3. MPL Seed Identifiers
MPL uses MPL Seed Identifiers to uniquely identify MPL Seeds within
an MPL Domain. For each MPL Domain that the MPL Forwarder serves as
an MPL Seed, the MPL Forwarder MUST have an associated MPL Seed
Identifier. An MPL Forwarder MAY use the same MPL Seed Identifier
across multiple MPL Domains, but the MPL Seed Identifier MUST be
unique within each MPL Domain. The mechanism for assigning and
verifying uniqueness of MPL Seed Identifiers is not specified in this
document.
5.4. MPL Parameters
PROACTIVE_FORWARDING A boolean value that indicates whether the MPL
Forwarder schedules MPL Data Message transmissions after receiving
them for the first time. PROACTIVE_FORWARDING has a default value
of TRUE. The mechanism for setting PROACTIVE_FORWARDING is not
specified within this document.
Hui & Kelsey Expires May 28, 2015 [Page 9]
Internet-Draft MPL November 2014
SEED_SET_ENTRY_LIFETIME The minimum lifetime for an entry in the
Seed Set. SEED_SET_ENTRY_LIFETIME has a default value of 30
minutes. It is RECOMMENDED that all MPL Forwarders use the same
value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and use a
default value of 30 minutes. Using a value of
SEED_SET_ENTRY_LIFETIME that is too small can cause the duplicate
detection mechanism to fail, resulting in a MPL Forwarder to
receive a given MPL Data Message more than once. The mechanism
for setting SEED_SET_ENTRY_LIFETIME is not specified within this
document.
As specified in [RFC6206], a Trickle timer runs for a defined
interval and has three configuration parameters: the minimum interval
size Imin, the maximum interval size Imax, and a redundancy constant
k.
This specification defines a fourth Trickle configuration parameter,
TimerExpirations, which indicates the number of Trickle timer
expiration events that occur before terminating the Trickle algorithm
for a given MPL Data Message or MPL Control Message.
Each MPL Interface uses the following Trickle parameters for MPL Data
Message and MPL Control Message transmissions.
DATA_MESSAGE_IMIN The minimum Trickle timer interval, as defined in
[RFC6206], for MPL Data Message transmissions. DATA_MESSAGE_IMIN
has a default value of 10 times the expected link-layer latency.
DATA MESSAGE_IMAX The maximum Trickle timer interval, as defined in
[RFC6206], for MPL Data Message transmissions. DATA_MESSAGE_IMAX
has a default value equal to DATA_MESSAGE_IMIN.
DATA_MESSAGE_K The redundancy constant, as defined in [RFC6206], for
MPL Data Message transmissions. DATA_MESSAGE_K has a default
value of 1.
DATA_MESSAGE_TIMER_EXPIRATIONS The number of Trickle timer
expirations that occur before terminating the Trickle algorithm's
retransmission of a given MPL Data Message.
DATA_MESSAGE_TIMER_EXPIRATIONS has a default value of 3.
CONTROL_MESSAGE_IMIN The minimum Trickle timer interval, as defined
in [RFC6206], for MPL Control Message transmissions.
CONTROL_MESSAGE_IMIN has a default value of 10 times the worst-
case link-layer latency.
Hui & Kelsey Expires May 28, 2015 [Page 10]
Internet-Draft MPL November 2014
CONTROL_MESSAGE_IMAX The maximum Trickle timer interval, as defined
in [RFC6206], for MPL Control Message transmissions.
CONTROL_MESSAGE_IMAX has a default value of 5 minutes.
CONTROL_MESSAGE_K The redundancy constant, as defined in [RFC6206],
for MPL Control Message transmissions. CONTROL_MESSAGE_K has a
default value of 1.
CONTROL_MESSAGE_TIMER_EXPIRATIONS The number of Trickle timer
expirations that occur before terminating the Trickle algorithm
for MPL Control Message transmissions.
CONTROL_MESSAGE_TIMER_EXPIRATIONS has a default value of 10.
As described in [RFC6206], if different nodes have different
configuration parameters, Trickle may have unintended behaviors.
Therefore, it is RECOMMENDED that all MPL Interfaces attached to the
same link of a given MPL Domain use the same values for the Trickle
Parameters above for a given MPL Domain. The mechanism for setting
the Trickle Parameters is not specified within this document.
The default MPL parameters specify a forwarding strategy that
utilizes both proactive and reactive techniques. Using these default
values, an MPL Forwarder proactively transmits any new MPL Data
Messages it receives then uses MPL Control Messages to trigger
additional MPL Data Message retransmissions where message drops are
detected. Setting DATA_MESSAGE_IMAX to the same as DATA_MESSAGE_IMIN
in this case is acceptable since subsequent MPL Data Message
retransmissions are triggered by MPL Control Messages, where
CONTROL_MESSAGE_IMAX is greater than CONTROL_MESSAGE_IMIN.
6. Protocol Message Formats
The protocol messages generated and processed by an MPL Forwarder are
described in this section.
6.1. MPL Option
The MPL Option is carried in MPL Data Messages in an IPv6 Hop-by-Hop
Options header, immediately following the IPv6 header. The MPL
Option has the following format:
Hui & Kelsey Expires May 28, 2015 [Page 11]
Internet-Draft MPL November 2014
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Opt Data Len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S |M|V| rsv | sequence | seed-id (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type 0x6D.
Opt Data Len Length of the Option Data field in octets.
S 2-bit unsigned integer. Identifies the length of
seed-id. 0 indicates that the seed-id is the
IPv6 Source Address and not included in the MPL
Option. 1 indicates that the seed-id is a 16-bit
unsigned integer. 2 indicates that the seed-id
is a 64-bit unsigned integer. 3 indicates that
the seed-id is a 128-bit unsigned integer.
M 1-bit flag. 1 indicates that the value in
sequence is known to be the largest sequence
number that was received from the MPL Seed.
V 1-bit flag. 0 indicates that the MPL Option
conforms to this specification. MPL Data
Messages with an MPL Option in which this flag is
1 MUST be dropped.
rsv 4-bit reserved field. MUST be set to 0 on
transmission and ignored on reception.
sequence 8-bit unsigned integer. Identifies relative
ordering of MPL Data Messages from the MPL Seed
identified by seed-id.
seed-id Uniquely identifies the MPL Seed that initiated
dissemination of the MPL Data Message. The size
of seed-id is indicated by the S field.
The Option Data (in particular the M flag) of the MPL Option is
updated by MPL Forwarders as the MPL Data Message is forwarded.
Nodes that do not understand the MPL Option MUST discard the MPL Data
Message. Thus, according to [RFC2460] the three high order bits of
the Option Type are set to '011'. The Option Data length is
variable.
Hui & Kelsey Expires May 28, 2015 [Page 12]
Internet-Draft MPL November 2014
The seed-id uniquely identifies an MPL Seed. When seed-id is 128
bits (S=3), the MPL Seed MAY use an IPv6 address assigned to one of
its interfaces that is unique within the MPL Domain. Managing MPL
Seed Identifiers is not within scope of this document.
The sequence field establishes a total ordering of MPL Data Messages
generated by an MPL Seed for an MPL Domain. The MPL Seed MUST
increment the sequence field's value on each new MPL Data Message
that it generates for an MPL Domain. Implementations MUST follow the
Serial Number Arithmetic as defined in [RFC1982] when incrementing a
sequence value or comparing two sequence values.
Future updates to this specification may define additional fields
following the seed-id field.
6.2. MPL Control Message
An MPL Forwarder uses ICMPv6 messages to communicate information
contained in an MPL Domain's Seed Set and Buffered Message Set to
neighboring MPL Forwarders. The MPL Control Message has the
following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Code | Checksum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. MPL Seed Info[0..n] .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IP Fields:
Source Address An IPv6 address in the AddressSet of the
corresponding MPL Interface and MUST be valid
within the MPL Domain.
Destination Address The link-scoped MPL Domain Address corresponding
to the MPL Domain.
Hop Limit 255
ICMPv6 Fields:
Type MPL_ICMP_TYPE
Hui & Kelsey Expires May 28, 2015 [Page 13]
Internet-Draft MPL November 2014
Code 0
Checksum The ICMP checksum. See [RFC4443].
MPL Seed Info[0..n] List of zero or more MPL Seed Info entries.
The MPL Control Message indicates the sequence numbers of MPL Data
Messages that are within the MPL Domain's Buffered Message Set. The
MPL Control Message also indicates the sequence numbers of MPL Data
Messages that an MPL Forwarder is willing to receive. The MPL
Control Message allows neighboring MPL Forwarders to determine
whether there are any new MPL Data Messages to exchange.
6.3. MPL Seed Info
An MPL Seed Info encodes the minimum sequence number for an MPL Seed
maintained in the MPL Domain's Seed Set. The MPL Seed Info also
indicates the sequence numbers of MPL Data Messages generated by the
MPL Seed that are stored within the MPL Domain's Buffered Message
Set. The MPL Seed Info has the following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| min-seqno | bm-len | S | seed-id (0/2/8/16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. buffered-mpl-messages (variable length) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
min-seqno 8-bit unsigned integer. The lower-bound sequence
number for the MPL Seed.
bm-len 6-bit unsigned integer. The size of buffered-
mpl-messages in octets.
S 2-bit unsigned integer. Identifies the length of
seed-id. 0 indicates that the seed-id value is
the IPv6 Source Address and not included in the
MPL Seed Info. 1 indicates that the seed-id
value is a 16-bit unsigned integer. 2 indicates
that the seed-id value is a 64-bit unsigned
integer. 3 indicates that the seed-id is a
128-bit unsigned integer.
Hui & Kelsey Expires May 28, 2015 [Page 14]
Internet-Draft MPL November 2014
seed-id Variable-length unsigned integer. Indicates the
MPL Seed associated with this MPL Seed Info.
buffered-mpl-messages Variable-length bit vector. Identifies the
sequence numbers of MPL Data Messages maintained
in the corresponding Buffered Message Set for the
MPL Seed. The i'th bit represents a sequence
number of min-seqno + i. '0' indicates that the
corresponding MPL Data Message does not exist in
the Buffered Message Set. '1' indicates that the
corresponding MPL Data Message does exist in the
Buffered Message Set.
The MPL Seed Info does not have any octet alignment requirement.
7. Information Base
7.1. Local Interface Set
The Local Interface Set records the local MPL Interfaces of an MPL
Forwarder. The Local Interface Set consists of Local Interface
Tuples, one per MPL Interface: (AddressSet).
AddressSet - a set of unicast addresses assigned to the MPL
Interface.
7.2. Domain Set
The Domain Set records the MPL Interfaces that subscribe to each MPL
Domain Address. The Domain Set consists of MPL Domain Tuples, one
per MPL Domain: (MPLInterfaceSet).
MPLInterfaceSet - a set of MPL Interfaces that subscribe to the MPL
Domain Address that identifies the MPL Domain.
7.3. Seed Set
A Seed Set records a sliding window used to determine the sequence
numbers of MPL Data Messages that an MPL Forwarder is willing to
accept generated by the MPL Seed. An MPL Forwarder maintains a Seed
Set for each MPL Domain that it participates in. A Seed Set consists
of MPL Seed Tuples: (SeedID, MinSequence, Lifetime).
SeedID - the identifier for the MPL Seed.
MinSequence - a lower-bound sequence number that represents the
sequence number of the oldest MPL Data Message the MPL Forwarder
is willing to receive or transmit. An MPL Forwarder MUST ignore
Hui & Kelsey Expires May 28, 2015 [Page 15]
Internet-Draft MPL November 2014
any MPL Data Message that has sequence value less than than
MinSequence.
Lifetime - indicates the minimum remaining lifetime of the Seed Set
entry. An MPL Forwarder MUST NOT free a Seed Set entry before the
remaining lifetime expires.
7.4. Buffered Message Set
A Buffered Message Set records recently received MPL Data Messages
from an MPL Seed within an MPL Domain. An MPL Forwarder uses a
Buffered Message Set to buffer MPL Data Messages while the MPL
Forwarder is forwarding the MPL Data Messages. An MPL Forwarder
maintains a Buffered Message Set for each MPL Domain that it
participates in. A Buffered Message Set consists of Buffered Message
Tuples: (SeedID, SequenceNumber, DataMessage).
SeedID - the identifier for the MPL Seed that generated the MPL Data
Message.
SequenceNumber - the sequence number for the MPL Data Message.
DataMessage - the MPL Data Message.
All MPL Data Messages within a Buffered Message Set MUST have a
sequence number greater than or equal to MinSequence for the
corresponding SeedID. When increasing MinSequence for an MPL Seed,
the MPL Forwarder MUST delete any MPL Data Messages from the
corresponding Buffered Message Set that have sequence numbers less
than MinSequence.
8. MPL Seed Sequence Numbers
Each MPL Seed maintains a sequence number for each MPL Domain that it
serves. The sequence numbers are included in MPL Data Messages
generated by the MPL Seed. The MPL Seed MUST increment the sequence
number for each MPL Data Message that it generates for an MPL Domain.
Implementations MUST follow the Serial Number Arithmetic as defined
in [RFC1982] when incrementing a sequence value or comparing two
sequence values. This sequence number is used to establish a total
ordering of MPL Data Messages generated by an MPL Seed for an MPL
Domain.
9. MPL Data Messages
Hui & Kelsey Expires May 28, 2015 [Page 16]
Internet-Draft MPL November 2014
9.1. MPL Data Message Generation
MPL Data Messages are generated by MPL Seeds when these messages
enter the MPL Domain. All MPL Data messages have the following
properties:
o The IPv6 Source Address MUST be an address in the AddressSet of a
corresponding MPL Interface and MUST be valid within the MPL
Domain.
o The IPv6 Destination Address MUST be set to the MPL Domain Address
corresponding to the MPL Domain.
o An MPL Data Message MUST contain an MPL Option in its IPv6 Header
to identify the MPL Seed that generated the message and the
ordering relative to other MPL Data Messages generated by the MPL
Seed.
When the destination address is an MPL Domain Address and the source
address is in the AddressLIst of an MPL Interface that belongs to
that MPL Domain Address, the application message and the MPL Data
Message MAY be identical. In other words, the MPL Data Message may
contain a single IPv6 header that includes the MPL Option.
Otherwise, IPv6-in-IPv6 encapsulation MUST be used to satisfy the MPL
Data Message requirements listed above [RFC2473]. The complete IPv6-
in-IPv6 message forms an MPL Data Message. The outer IPv6 header
conforms to the MPL Data Message requirements listed above. The
encapsulated IPv6 datagram encodes the multicast data message that is
communicated beyond the MPL Domain.
9.2. MPL Data Message Transmission
An MPL Forwarder manages transmission of MPL Data Messages in its
Buffered Message Sets using the Trickle algorithm [RFC6206]. An MPL
Forwarder MUST use a separate Trickle timer for each MPL Data Message
that it is actively forwarding. In accordance with Section 5 of RFC
6206 [RFC6206], this document defines the following:
o This document defines a "consistent" transmission as receiving an
MPL Data Message that has the same MPL Domain Address, seed-id,
and sequence value as the MPL Data Message managed by the Trickle
timer.
o This document defines an "inconsistent" transmission as receiving
an MPL Data Message that has the same MPL Domain Address, seed-id
value, and the M flag set, but has a sequence value less than MPL
Data Message managed by the Trickle timer.
Hui & Kelsey Expires May 28, 2015 [Page 17]
Internet-Draft MPL November 2014
o This document does not define any external "events".
o This document defines MPL Data Messages as Trickle messages.
o The actions outside the Trickle algorithm that the protocol takes
involve managing the MPL Domain's Seed Set and Buffered Message
Set.
As specified in [RFC6206], a Trickle timer has three variables: the
current interval size I, a time within the current interval t, and a
counter c. MPL defines a fourth variable, e, which counts the number
of Trickle timer expiration events since the Trickle timer was last
reset.
After DATA_MESSAGE_TIMER_EXPIRATIONS Trickle timer events, the MPL
Forwarder MUST disable the Trickle timer. When a buffered MPL Data
Message does not have an associated Trickle timer, the MPL Forwarder
MAY delete the message from the Buffered Message Set by advancing
MinSequence of the corresponding MPL Seed in the Seed Set. When the
MPL Forwarder no longer buffers any messages for an MPL Seed, the MPL
Forwarder MUST NOT increment MinSequence for that MPL Seed.
When transmitting an MPL Data Message, the MPL Forwarder MUST either
set the M flag to zero or set it to a level that indicates whether or
not the message's sequence number is the largest value that has been
received from the MPL Seed.
9.3. MPL Data Message Processing
Upon receiving an MPL Data Message, the MPL Forwarder first processes
the MPL Option and updates the Trickle timer associated with the MPL
Data Message if one exists.
Upon receiving an MPL Data Message, an MPL Forwarder MUST perform one
of the following actions:
o Accept the message and enter the MPL Data Message in the MPL
Domain's Buffered Message Set.
o Accept the message and update the corresponding MinSequence in the
MPL Domain's Seed Set to 1 greater than the message's sequence
number.
o Discard the message without any change to the MPL Information
Base.
Hui & Kelsey Expires May 28, 2015 [Page 18]
Internet-Draft MPL November 2014
If a Seed Set entry exists for the MPL Seed, the MPL Forwarder MUST
discard the MPL Data Message if its sequence number is less than
MinSequence or exists in the Buffered Message Set.
If a Seed Set entry does not exist for the MPL Seed, the MPL
Forwarder MUST create a new entry for the MPL Seed before accepting
the MPL Data Message.
If memory is limited, an MPL Forwarder SHOULD reclaim memory
resources by:
o Incrementing MinSequence entries in a Seed Set and deleting MPL
Data Messages in the corresponding Buffered Message Set that fall
below the MinSequence value.
o Deleting other Seed Set entries that have expired and the
corresponding MPL Data Messages in the Buffered Message Set.
If the MPL Forwarder accepts the MPL Data Message, the MPL Forwarder
MUST perform the following actions:
o Reset the Lifetime of the corresponding Seed Set entry to
SEED_SET_ENTRY_LIFETIME.
o If PROACTIVE_FORWARDING is true, the MPL Forwarder MUST initialize
and start a Trickle timer for the MPL Data Message.
o If the MPL Control Message Trickle timer is not running and
CONTROL_MESSAGE_TIMER_EXPIRATIONS is non-zero, the MPL Forwarder
MUST initialize and start the MPL Control Message Trickle timer.
o If the MPL Control Message Trickle timer is running, the MPL
Forwarder MUST reset the MPL Control Message Trickle timer.
10. MPL Control Messages
10.1. MPL Control Message Generation
An MPL Forwarder generates MPL Control Messages to communicate an MPL
Domain's Seed Set and Buffered Message Set to neighboring MPL
Forwarders. Each MPL Control Message is generated according to
Section 6.2, with an MPL Seed Info for each entry in the MPL Domain's
Seed Set. Each MPL Seed Info entry has the following content:
o S set to the size of the seed-id field in the MPL Seed Info entry.
o min-seqno set to MinSequence of the MPL Seed.
Hui & Kelsey Expires May 28, 2015 [Page 19]
Internet-Draft MPL November 2014
o bm-len set to the size of buffered-mpl-messages in octets.
o seed-id set to the MPL seed identifier.
o buffered-mpl-messages with each bit representing whether or not an
MPL Data Message with the corresponding sequence number exists in
the Buffered Message Set. The i'th bit represents a sequence
number of min-seqno + i. '0' indicates that the corresponding MPL
Data Message does not exist in the Buffered Message Set. '1'
indicates that the corresponding MPL Data Message does exist in
the Buffered Message Set.
10.2. MPL Control Message Transmission
An MPL Forwarder transmits MPL Control Messages using the Trickle
algorithm. An MPL Forwarder maintains a single Trickle timer for
each MPL Domain. When CONTROL_MESSAGE_TIMER_EXPIRATIONS is 0, the
MPL Forwarder does not execute the Trickle algorithm and does not
transmit MPL Control Messages. In accordance with Section 5 of RFC
6206 [RFC6206], this document defines the following:
o This document defines a "consistent" transmission as receiving an
MPL Control Message that results in a determination that neither
the receiving nor transmitting node has any new MPL Data Messages
to offer.
o This document defines an "inconsistent" transmission as receiving
an MPL Control Message that results in a determination that either
the receiving or transmitting node has at least one new MPL Data
Message to offer.
o The Trickle timer is reset in response to external "events." This
document defines an "event" as increasing MinSequence of any entry
in the corresponding Seed Set or adding a message to the
corresponding Buffered Message Set.
o This document defines an MPL Control Message as a Trickle message.
As specified in [RFC6206], a Trickle timer has three variables: the
current interval size I, a time within the current interval t, and a
counter c. MPL defines a fourth variable, e, which counts the number
of Trickle timer expiration events since the Trickle timer was last
reset. After CONTROL_MESSAGE_TIMER_EXPIRATIONS Trickle timer events,
the MPL Forwarder MUST disable the Trickle timer.
Hui & Kelsey Expires May 28, 2015 [Page 20]
Internet-Draft MPL November 2014
10.3. MPL Control Message Processing
An MPL Forwarder processes each MPL Control Message that it receives
to determine if it has any new MPL Data Messages to receive or offer.
An MPL Forwarder determines if a new MPL Data Message has not been
received from a neighboring node if any of the following conditions
hold true:
o The MPL Control Message includes an MPL Seed that does not exist
in the MPL Domain's Seed Set.
o The MPL Control Message indicates that the neighbor has an MPL
Data Message in its Buffered Message Set with sequence number
greater than MinSequence (i.e. the i-th bit is set to 1 and min-
seqno + i > MinSequence) and is not included in the MPL Domain's
Buffered Message Set.
When an MPL Forwarder determines that it has not yet received an MPL
Data Message buffered by a neighboring device, the MPL Forwarder MUST
reset its Trickle timer associated with MPL Control Message
transmissions. If an MPL Control Message Trickle timer is not
running, the MPL Forwarder MUST initialize and start a new Trickle
timer.
An MPL Forwarder determines if an MPL Data Message in the Buffered
Message Set has not yet been received by a neighboring MPL Forwarder
if any of the following conditions hold true:
o The MPL Control Message does not include an MPL Seed for the MPL
Data Message.
o The MPL Data Message's sequence number is greater than or equal to
min-seqno and not included in the neighbor's corresponding
Buffered Message Set (i.e. the MPL Data Message's sequence number
does not have a corresponding bit in buffered-mpl-messages set to
1).
When an MPL Forwarder determines that it has at least one MPL Data
Message in its corresponding Buffered Message Set that has not yet
been received by a neighbor, the MPL Forwarder MUST reset the MPL
Control Message Trickle timer. Additionally, for each of those
entries in the Buffered Message Set, the MPL Forwarder MUST reset the
Trickle timer and reset e to 0. If a Trickle timer is not associated
with the MPL Data Message, the MPL Forwarder MUST initialize and
start a new Trickle timer.
Hui & Kelsey Expires May 28, 2015 [Page 21]
Internet-Draft MPL November 2014
11. Acknowledgements
The authors would like to acknowledge the helpful comments of Robert
Cragie, Esko Dijk, Ralph Droms, Paul Duffy, Adrian Farrel, Ulrich
Herberg, Owen Kirby, Philip Levis, Kerry Lynn, Joseph Reddy, Michael
Richardson, Ines Robles, Don Sturek, Dario Tedeschi, and Peter van
der Stok, which greatly improved the document.
12. IANA Considerations
This document defines one IPv6 Option, a type that must be allocated
from the IPv6 "Destination Options and Hop-by-Hop Options" registry
of [RFC2780].
This document defines one ICMPv6 Message, a type that must be
allocated from the "ICMPv6 "type" Numbers" registry of [RFC4443].
This document registers a well-known multicast address from the
Variable Scope Multicast Address registry.
12.1. MPL Option Type
IANA is requested to allocate an IPv6 Option Type from the IPv6
"Destination Options and Hop-by-Hop Options" registry of [RFC2780],
as specified in Table 1 below:
+-----------+-----+-----+-------+-------------+---------------+
| Hex Value | act | chg | rest | Description | Reference |
+-----------+-----+-----+-------+-------------+---------------+
| 0x6D | 01 | 1 | 01101 | MPL Option | This Document |
+-----------+-----+-----+-------+-------------+---------------+
Table 1: IPv6 Option Type Allocation
12.2. MPL ICMPv6 Type
IANA is requested to allocate an ICMPv6 Type from the "ICMPv6 "type"
Numbers" registry of [RFC4443], as specified in Table 2 below:
+------+---------------------+---------------+
| Type | Name | Reference |
+------+---------------------+---------------+
| TBD | MPL Control Message | This Document |
+------+---------------------+---------------+
Table 2: IPv6 Option Type Allocation
Hui & Kelsey Expires May 28, 2015 [Page 22]
Internet-Draft MPL November 2014
In this document, the mnemonic MPL_ICMP_TYPE was used to refer to the
ICMPv6 Type above, which is TBD by IANA.
12.3. Well-known Multicast Addresses
IANA is requested to allocate an IPv6 multicast address, with Group
ID in the range [0x01,0xFF] for 6LoWPAN compression [RFC6282],
"ALL_MPL_FORWARDERS" from the "Variable Scope Multicast Addresses"
sub-registry of the "IPv6 Multicast Address Space" registry [RFC3307]
as specified in Table 3 below:
+---------------------+--------------------+-----------+------------+
| Address(s) | Description | Reference | Date |
| | | | Registered |
+---------------------+--------------------+-----------+------------+
| FF0X:0:0:0:0:0:0:FC | ALL_MPL_FORWARDERS | This | 2013-04-10 |
| | | Document | |
+---------------------+--------------------+-----------+------------+
Table 3: Variable Scope Multicast Address Allocation
13. Security Considerations
MPL uses sequence numbers to maintain a total ordering of MPL Data
Messages from an MPL Seed. The use of sequence numbers allows a
denial-of-service attack where an attacker can spoof a message with a
sufficiently large sequence number to: (i) flush messages from the
Buffered Message List and (ii) increase the MinSequence value for an
MPL Seed in the corresponding Seed Set. The former side effect
allows an attacker to halt the forwarding process of any MPL Data
Messages being disseminated. The latter side effect allows an
attacker to prevent MPL Forwarders from accepting new MPL Data
Messages that an MPL Seed generates while the sequence number is less
than MinSequence.
More generally, the basic ability to inject messages into a Low-power
and Lossy Network can be used as a denial-of-service attack
regardless of what forwarding protocol is used. For these reasons,
Low-power and Lossy Networks typically employ link-layer security
mechanisms to disable an attacker's ability to inject messages.
To prevent attackers from injecting packets through an MPL Forwarder,
the MPL Forwarder MUST NOT accept or forward MPL Data Messages from a
communication interface that does not subscribe to the MPL Domain
Address identified in message's destination address.
MPL uses the Trickle algorithm to manage message transmissions and
the security considerations described in [RFC6206] apply.
Hui & Kelsey Expires May 28, 2015 [Page 23]
Internet-Draft MPL November 2014
14. References
14.1. Normative References
[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
August 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in
IPv6 Specification", RFC 2473, December 1998.
[RFC2780] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For
Values In the Internet Protocol and Related Headers", BCP
37, RFC 2780, March 2000.
[RFC3307] Haberman, B., "Allocation Guidelines for IPv6 Multicast
Addresses", RFC 3307, August 2002.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification", RFC 4443, March 2006.
[RFC6206] Levis, P., Clausen, T., Hui, J., Gnawali, O., and J. Ko,
"The Trickle Algorithm", RFC 6206, March 2011.
[RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6
Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
September 2011.
[RFC6550] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R.,
Levis, P., Pister, K., Struik, R., Vasseur, JP., and R.
Alexander, "RPL: IPv6 Routing Protocol for Low-Power and
Lossy Networks", RFC 6550, March 2012.
[RFC7346] Droms, R., "IPv6 Multicast Address Scopes", RFC 7346,
August 2014.
Hui & Kelsey Expires May 28, 2015 [Page 24]
Internet-Draft MPL November 2014
14.2. Informative References
[Clausen2013]
Clausen, T., Colin de Verdiere, A., and J. Yi,
"Performance Analysis of Trickle as a Flooding Mechanism",
November 2013.
[RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol
Independent Multicast - Dense Mode (PIM-DM): Protocol
Specification (Revised)", RFC 3973, January 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006.
Authors' Addresses
Jonathan W. Hui
Cisco
170 West Tasman Drive
San Jose, California 95134
USA
Phone: +408 424 1547
Email: jonhui@cisco.com
Richard Kelsey
Silicon Labs
25 Thomson Place
Boston, Massachusetts 02210
USA
Phone: +617 951 1225
Email: richard.kelsey@silabs.com
Hui & Kelsey Expires May 28, 2015 [Page 25]