Re: [Roll] [6lo] New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt

[Jonathan Hui <[e-mail]>]

On Tue, Jun 30, 2015 at 12:09 PM, Gabriel Montenegro <
[e-mail]> wrote:

> Thanks, Pascal.
>
> I see that options 1 and 2 reuse the mesh header. And option 3 reuses
> NALP. All three of these reuse previously assigned values.
>

My reading of Option 3 in Section 3.3 is that it uses bit patterns that
have not been assigned yet.  In particular, bit patterns of the form
11x1xxxx.

I was under the impression that one of the options was going to use a new
> type out of the ESC+<type> space. Sure, as you mention in the new draft
> revision, that is not defined clearly yet (though there is something being
> prepared), but neither is any of the stuff in the draft.
>

That is certainly another option to consider.

The point is that it would be good to have at least one option that does
> not reuse anything previously assigned (other than ESC, which is there for
> that purpose and is in our control to further define).
>

I agree that we should strongly consider encodings that allow both existing
assigned bit patterns and the TBD bit patterns to co-exist in the same
6LoWPAN frame.  If we can, we should avoid straight up reuse of
bit-patterns without any way to distinguish how to interpret between the
old and new.

Oh, and request noted. It would definitely be good to discuss this in
> Prague.
>

Agree.

--
Jonathan Hui