Re: [Roll] [roll-wg/draft-ietf-roll-enrollment-priority] Propose changes to reflect major points of our discussion (PR #14)

[Pascal Thubert <[e-mail]>]

Hello Rahul

RPL should not be tweaked to fix ND problems. If you problem is a number of
neighbors then we need to look at how you use RFC 8505 and whether
something is missing there.
What you can already do is trial and error. the 50th child sends a NS(EARO)
and the parent rejects with a bad status. Sadly we have
"

6LBR Registry Saturated

"
but not "

6LR Registry Saturated

"
Also we are missing the capability to indicate in the RA that the NCE is
getting saturated.
Maybe all that deserves a draft at 6lo?

Pascal



Le mar. 8 févr. 2022 à 04:46, Rahul Jadhav <[e-mail]> a
écrit :

> Regarding the scenario -- I don't know if I got it correctly -- but if you
> wanted to cut off nodes joining specific 6LRs (e.g., those having 40
> neighbor entries or more), you could have such 6LRs advertise a maximal
> value (0x7f) of their Enhanced Beacon Join priorities. You need not change
> the global min priority for that. Or did I misunderstood your example?
>
> Enhanced Beacon Join priorities works only for 6tisch scenarios. RPL has
> multiple different link layers it works for. They all face similar issues.
> My deployment scenario was using 802.15.4 link layer without tisch.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/roll-wg/draft-ietf-roll-enrollment-priority/pull/14#issuecomment-1032184406>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABYHN4I6W6SD7S3M4QJ3IY3U2CGZFANCNFSM5NXM4HUQ>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: <roll-wg/draft-ietf-roll-enrollment-priority/pull/14/c1032184406@
> github.com>
>


-- 
Pascal