Found 2 records.

Status: Held for Document Update (2)

RFC 7774, "Multicast Protocol for Low-Power and Lossy Networks (MPL) Parameter Configuration Option for DHCPv6", March 2016

Errata ID: 5057
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: James K.
Date Reported: 2017-06-29
Held for Document Update by: Alvaro Retana
Date Held: 2017-11-06

Section 2.1 says:

DM_IMAX (unsigned 8-bit integer):  DATA_MESSAGE_IMAX.  The actual
      maximum timeout is described as a number of doublings of
      DATA_MESSAGE_IMIN, as described in [RFC6206], Section 4.1.
      0 and 0xff are reserved and MUST NOT be used.

It should say:

DM_IMAX (unsigned 8-bit integer):  DATA_MESSAGE_IMAX.  The actual
      maximum timeout is described as a number of doublings of
      DATA_MESSAGE_IMIN, as described in [RFC6206], Section 4.1.
      0xff is reserved and MUST NOT be used.

Notes:

RFC6206
The maximum interval size, Imax, is described as a number of
doublings of the minimum interval size.

RFC7731
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.
also
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 and then uses MPL Control Messages to trigger
additional MPL Data Message retransmissions where message drops are
detected. Setting DATA_MESSAGE_IMAX to the same value 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.

For DATA_MESSAGE_IMAX == DATA_MESSAGE_IMIN implies DM_IMAX=0. 0 is a valid value for DM_IMAX.

=====
[Alvaro Retana]

The pointer to rfc7731 seems to indicate that the description for is incorrect. However, this document uses Normative language to define the DM_IMAX parameter.

I am then not marking this report as Verified, but as "Hold for Document Update", which means that when this document is updated, the validity should be considered then. [1]

[1] https://www.ietf.org/iesg/statement/errata-processing.html

Errata ID: 5063
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: James K.
Date Reported: 2017-07-06
Held for Document Update by: Alvaro Retana
Date Held: 2017-11-06

Section 2.1 says:

   C_T_EXP (unsigned 16-bit integer):
      CONTROL_MESSAGE_TIMER_EXPIRATIONS.  0 and 0xffff are reserved and
      MUST NOT be used.

It should say:

   C_T_EXP (unsigned 16-bit integer):
      CONTROL_MESSAGE_TIMER_EXPIRATIONS.  0xffff is reserved and
      MUST NOT be used.

Notes:

[RFC 7731] states:

9.3. MPL Data Message Processing

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.

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.

Thus, 0 is a valid configuration for C_T_EXP to disable Reactive Forwarding.

=====
[Alvaro Retana]

The pointer to rfc7731 seems to indicate that the description for CONTROL_MESSAGE_TIMER_EXPIRATIONS is incorrect. However, this document uses Normative language to define the C_T_EXP parameter.

I am then not marking this report as Verified, but as "Hold for Document Update", which means that when this document is updated, the validity should be considered then. [1]

[1] https://www.ietf.org/iesg/statement/errata-processing.html

Report New Errata