Re: [Roll] Default setting for config flags after MOP 7.

Sorry for the late reply. But for the record, I agree that 6lorh be turned
on by default for RFC6550-update and also 0x23 be the only option type used
for RPI (obsoleting 0x63).
Should we also start a thread listing all the mandates that RFC6550-update
might do?

Regards,
Rahul

On Tue, 21 Jul 2020 at 15:34, Pascal Thubert (pthubert) <pthubert=
40cisco.com@dmarc.ietf.org> wrote:

> Dear all:
>
> During Alvaro's review, another point was raised for which we need a group
> consensus.
>
> We said repeatedly that the turnon flag is defined only for MOPs < 7. This
> is also true for the "RPI 0x23 enable" flag defined in useofrplinfo.
>
> So we are asking implementation to check that the MOP is less than 7
> before they use the flag and only use it in that case.
>
> But then, when it finds a MOP that is >= 7, what should the code that we
> write today do? For one thing RFC 6550 makes it a leaf.
> But what about the RFC 8138 compression and the RPI 0x23?
>
> For both bits, the assumption would be that the probation phase has ended
> and that implementations have migrated.
> This means that after MOP 7 the default is that RFC 8138 is turned on, and
> that Option Type in the RPL option is 0x23.
>
> Do we agree?
>
> Pascal
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>