Re: [6tisch] Alvaro Retana's Discuss on draft-ietf-6tisch-enrollment-enhanced-beacon-13: (with DISCUSS and COMMENT)

[Michael Richardson <[e-mail]>]

I will update the new section in -14, which I'll post in a few minutes so
that the WG can review the result.

Benjamin Kaduk <[e-mail]> wrote:
    >> +## Layer-2 Selection + +In a complex Low-power and Lossy Network
    >> (LLN), the use of mulitple backbone routers connected together by
    >> technology such as {{?I-D.ietf-6lo-backbone-router}} an area may be
    >> serviced by multiple distinct

    > I think there's a botched edit in here; it doesn't seem to parse
    > properly.

Agreed.
        + In a complex Low-power and Lossy Networks (LLN), multiple LLNs may
        be connected together by backbone routers ( technology such as
        {{?I-D.ietf-6lo-backbone-router}}), resulting in an area that is
        serviced by multiple distinct Layer-2 instances.

    >> +Layer-2 instances.  +These are called PANs.  +Historically, this term
    >> meant "Personal Area Network", but the use of the word "Personal" is
    >> now deprecated.  +Each instance will have a separate Layer-2 security
    >> profile, and will be distinguished by a different PANID.  +The PANID
    >> is part of the {{ieee802154}} layer-2 header: it is a 16-bit value
    >> which is chosen to be unique, and it contributes context to the
    >> layer-2 security.

    > "security mechanisms", please.

done

    >> +The PANID provides a context similar to the ESSID does in 802.11
    >> networking, and can be conceived of in a similar fashion as the 802.3
    >> ethernet VLAN tag in that it provides context for all layer-2
    >> addresses.  + +A device which is already enrolled in a network may
    >> find after a long sleep that it needs to resynchronize to the Layer 2
    >> network.  +The enrollment keys that it has will be specific to a
    >> PANID, but it may have more than one set of keys.  +Such a device may
    >> wish to connect to a PAN that is experiencing less congestion, which
    >> has a shalower RPL tree.

    > This looks like it started out as a 3+-element list and got edited down
    > to just two, with a stray comma and no "or".

agreed.

    >> announcer is.  +Once the device synchronizes to a particular PAN's
    >> TSCH schedule then it may receive DIOs that are richer in their
    >> diversity than this value.  +How this value will be used in practice
    >> is the subject of future research, and this part of the structure +is
    >> considered experimental.

    > This makes it sound like the actual structure might change, which I
    > don't think is the intent.  So perhaps "the interpretation of this
    > value of the structure is considered experimental"?

Agreed, thank you.

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-