Hello Pascal,
Seems we are mostly in agreement. But see below...
On 5/21/2018 10:38 PM, Pascal Thubert (pthubert) wrote:
Another possibility would be to reserve some initial bits of the ROVR
field itself to indicate the length of the ROVR. Old-legacy nodes
would still discard new DAR and DAC messages with a ROVR that was too
long. New-legacy nodes would know to check the first three or four
bits of the field for the length of the ROVR. But I did not think
this all the way through yet.
But old legacy will set those bits randomly. And then we have
alignment problems. I proposed the subcode as a last resort...
I don't think it's a problem for old legacy. New-legacy 6LR should
detect old-legacy 6LN and maintain legacy-ness as part of the
registration state. ROVR would have sizes of 61, 125, 189, or 253
bits. Again, not a problem, and alignment is not an issue.
Plus as a bonus we get to have our Code back as a normal Code field.
It just needs to be checked that new-legacy 6LR can detect old-legacy 6LN.
Regards,
Charlie P.
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
