-邮件原件-
发件人: Pascal Thubert (pthubert) [mailto:pthub...@cisco.com]
发送时间: 2019年6月28日 0:37
收件人: Qin Wu ; ops-...@ietf.org
抄送: 6tisch@ietf.org; i...@ietf.org;
draft-ietf-6tisch-architecture@ietf.org; Eliot Lear (elear)
; Carlos Pignataro (cpignata)
主题: RE: Opsdir last call review of dra
Hi, Pascal:
-邮件原件-
发件人: Pascal Thubert (pthubert) [mailto:pthub...@cisco.com]
发送时间: 2019年6月27日 22:48
收件人: Qin Wu ; ops-...@ietf.org
抄送: 6tisch@ietf.org; i...@ietf.org;
draft-ietf-6tisch-architecture@ietf.org; Eliot Lear (elear)
; Carlos Pignataro (cpignata)
主题: RE: Opsdir last call
Hello Qin
I looked at it again and found that it was great to move
3.8. Communication Paradigms and Interaction Models . . . . . 21
But not such a great idea to move
4.2. Network Access and Addressing . . . . . . . . . . . . . . 23
4.2.1. Join Process . . . . . . . . .
Hello Pascal,
Thanks, this text is fine by me.
Mališa
> On 27 Jun 2019, at 14:06, Pascal Thubert (pthubert)
> wrote:
>
> Hello Malisa
>
> Please find below the proposed text; note that last paragraph is commented
> out to leave space for minimal to complete the story.
>
>
> The
Hello Qin
Many thanks for your review and for the important amount of time you obviously
spent on our work. This is really appreciated.
Please see below:
> By looking at high level architecture section, it is hard to create a whole
> picture for what this architecture looks like and how these ar
Hello Malisa
Please find below the proposed text; note that last paragraph is commented out
to leave space for minimal to complete the story.
The operation of 6TiSCH Tracks inherits its high level operation from DetNet
and is subject to the observations in section 5 of
. As disc
Pascal,
Before the pledge selects a JP, the text from RFC8180 that is relevant seems to
be (Section 6.2):
When a node joins a network, it may hear EBs sent by different nodes
already in the network. The decision of which neighbor to
synchronize to (e.g., which neighbor becomes the node's
Hello Michael
Both ASN and sync create event horizons.
* A wrong ASN will cause MIC processing to fail and the packet will be ignored.
* If an attacker syncs a pledge outside of the network sync's beyond guard
time, the pledge will not even see that legitimate nodes are sending.
In both cases, a
