Re: [Roll] AD Review of draft-ietf-roll-unaware-leaves-18

[Michael Richardson <[e-mail]>]

Pascal Thubert \(pthubert\) <pthubert=[e-mail]> wrote:
    >    [USEofRPLinfo] introduces the terms RPL-Aware-Leaf (RAL) and RPL-
    > Unaware Leaf (RUL).  A RAL is a Leaf that injects Host routes in RPL to
    > manage the reachability of its IPv6 addresses.  Conversely, a RUL does
    > not participate to RPL and cannot inject routes.  Section 5 details a
    > Host-to-Router interface that the RUL needs to implement to advertise
    > its IPv6 addresses to a Router that supports this specification.  The
    > document specifies how the Router injects those addresses as Host
    > Routes in the RPL network on behalf of the RUL.

I would go on with two additional paragraphs:

  An RAL is an RPL router node that just happens to have no children, either by
  design (e.g., it sleeps too much to be useful), or circumstance.

  An RUL could connect to any mesh network that supports RFC8505, even if it
  operates with a mesh protocol other than RPL.  Assuming of course that the
  physical layers were compatible: radios types, frequencies, scheduling, etc..


Maybe this is beating people over the head, but I think, in the introduction,
that's okay.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [