Re: [Roll] naming and other goals for RPL Unaware Leaves

[Michael Richardson <[e-mail]>]

Pascal Thubert (pthubert) <[e-mail]> wrote:
    > The art of RFC 6550: 1) a leaf is a node that connects to the RPL
    > network as a host and obtained reachability from the RPL domain 2) all
    > leaves need to be RPL aware. This involves sending DAOs thus speaking
    > RFC 6550.

Agreed, but can you relate it to the categories I wrote about?

    > I wrote the first rounds of the RUL draft with the expectation that: -
    > we define a new type of leaf that does 1) but not 2) .

So, this is my category:

    mcr> 3) RPL host.  Pascal and I disagree whether to call this an RPL *AWARE*
    mcr> host (because it speaks RPL data plane), or an RPL *UNAWARE* host
    mcr> (because it does not speak 6550).  It being a host, it is by definition
    mcr> a leaf.

Do others agree?
I don't care what we call it.

But, useofrplinfo used the term RUL to refer to category (2), not (3).
If all leaves are (3) then from an RPL point of view, they require no special care.

If useofrplinfo can assume (3), which is a new thing, then can useofrplinfo define (2),
explain that are difficult to deal with, and remove support for them?
If we go this way, then useofrplinfo winds up with a reference to
unaware-leaves and has to wait for it to progress.

Maybe we could change the word unaware to non-participating.
Or maybe anti-social.   

    > In contrast I called a leaf-that-is-not-a-RUL a RAL. => A leaf is
    > either a RUL or a RAL nut not both. IOW {RUL} v {RAL} = {leaves} and
    > {RUL} ^ {RAL} = 0. So the term leaf was extended and the leaves that
    > RFC 6550 presented can still be named as RAL. Combining with a RPL
    > router we obtain the RAN, RPL aware node.

A RAL speaks RPL, but is just at the edge.  Is it my category (4), or is
it 

    >    {It is distinguished from a 6LR which just happens to be leaf,
    > because there are no children that have picked it as a parent.  Such a
    > 6LR sends out peridic DIOs according trickle}

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