Return-Path: <tengfei.chang@gmail.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 87C4A3A08A3;
 Tue, 24 Mar 2020 04:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01,
 URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id S5OjEWMQ-nGB; Tue, 24 Mar 2020 04:23:43 -0700 (PDT)
Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com
 [IPv6:2607:f8b0:4864:20::a31])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 3A6623A0043;
 Tue, 24 Mar 2020 04:22:17 -0700 (PDT)
Received: by mail-vk1-xa31.google.com with SMTP id s139so4673220vka.13;
 Tue, 24 Mar 2020 04:22:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=RHbbBcrcx5ByjIviWXzPnWqTTw9UlRWtQHuqXDuKFNw=;
 b=tTw0x2WFn2j36pO7AKVeScFPix1zQs1gmrKjPqGF6crYea0KN2sbLM8UhiAoaHYr5l
 8Fy7o4TtsInW1QgpmkFEr/8AhaeOzwUnHnFJ3CQaiMJVeHPHmB+2ban8Hcy3fAq0fJKE
 r1U0BC5/Wd9RVOA5fM9YEMA69EhgjPctSbZW3v6G47lbTaWVFoHLv1ds7se0dGpE2N/i
 SlfA/IRMqs3c1rLJp6ZklQJdIwBDCJUTEXhdJ5vJD858BOvYRjWfQGrdHTU9Pzw4oYsv
 IpyttevLPyLxLNHR59k8hUzadRqb1dSVhqt+NL3b14IjYlEdlWf3NCSImYclwuWrRbSu
 Kblg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=RHbbBcrcx5ByjIviWXzPnWqTTw9UlRWtQHuqXDuKFNw=;
 b=a6Ki2N/Kgv4ZjqcO4V7Gz3L5WCj1r4vfA8Ftdp/jD0Xpim2VF13XEMq7CNJwzCw4wC
 fgKQw94glkWRASCRd/pkUBlwfY0bTxHTuuDbz68+WZWFKNlaGvS9+1NbGOQKJWn8MM/J
 C2lnKdgQKUPTrmOrFS+Svl03RbIUAI1v5XaUI1eSd81IGkVhSFhm5KNSQ+L6HDaGTmco
 ygjmH7Ojg5AE5VlTty8tC0pDXql+myWWu2dMBVpIvTiZ7SXWfgDdXTU6irl/FP0JFeo5
 ys5ODCeeN109VL2DsSN/WTDMRiy39IrV41lnbWAnj924/RTGd5mVbxkM76AKaQ5qHnid
 UnGA==
X-Gm-Message-State: ANhLgQ0X5bjYwMuWGCTCERA6BKWtmsnwZ9spKsoaCLnW1eCeBbBuuGBy
 +NSMImHNS2D08g54HzJUD49AQNHdSn73WeEjYNg=
X-Google-Smtp-Source: ADFU+vvWPIThK3YHJpt/6OktftS46z8YpXmxWEMshszWTkXtGhG6k/1kMj7Bw49AKg7oiyLi7JTFdFXpLr7CeS9To3U=
X-Received: by 2002:a1f:32cf:: with SMTP id y198mr18310026vky.96.1585048934346; 
 Tue, 24 Mar 2020 04:22:14 -0700 (PDT)
MIME-Version: 1.0
References: <158394932747.1671.4699004253009791924@ietfa.amsl.com>
In-Reply-To: <158394932747.1671.4699004253009791924@ietfa.amsl.com>
From: Tengfei Chang <tengfei.chang@gmail.com>
Date: Tue, 24 Mar 2020 12:22:02 +0100
Message-ID: <CAAdgstSMOf7wDSfbWMv5tEzpx1=otQZX_TZ+Xevm77f-1ZztNw@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-6tisch-msf@ietf.org,
 6tisch <6tisch@ietf.org>, 
 6tisch-chairs@ietf.org, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary="000000000000aef28205a197f60c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/oxe9vx84kbYMZmwpWGMeN2GYjCA>
Subject: Re: [6tisch] Benjamin Kaduk's Discuss on draft-ietf-6tisch-msf-12:
 (with DISCUSS and COMMENT)
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode
 of IEEE 802.15.4e,
 and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>,
 <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>,
 <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2020 11:23:54 -0000

--000000000000aef28205a197f60c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Benjamin,

I replied inline starting with '>'

Thanks so much those detailed comments!

On Wed, Mar 11, 2020 at 6:55 PM Benjamin Kaduk via Datatracker <
noreply@ietf.org> wrote:

> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-6tisch-msf-12: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-6tisch-msf/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> I'm concerned that the scheduling function for autonomous cells can
> cause an infinite loop in the case of hash collision -- Section 3
> specifies that AutoTxCell always takes precedence over AutoRxCell, but
> if those two cells collide, the corresponding cells on the peer in
> question will also collide.  If both peers try to send at the same time
> and the hashes collide, they will both attempt to transmit indefinitely
> and never be received.
>

>. Notice that the AutoTxCell  is a shared cell, where the back-off
mechanism is applied.
> In case there is a collision on that cell, a back-off with different
exponent will be used on each side.
> The cell will be used AutoTxCell on each side at different timing.

There seems to be some "passing the buck" going on with respect to
> rate-limiting unauthenticated (join) traffic:
> draft-ietf-6tisch-minimal-security (Section 6.1.1) says that the SF
> "SHOULD NOT allocate additional cells as a result of traffic with code
> point AF43"; this document is implementing a SF, and yet we try to avoid
> the issue, saying that "[t]he at IPv6 layer SHOULD ensure that this join
> traffic is rate-limited before it is passed to 6top sublayer where MSF
> can observe it".  I think we need a clear and consistent story about
> where this rate-limiting is supposed to happen.
>

> Thanks for the comments! This has been discussed in some  previous
revision of MSF.
> It is not "passing the buck" but a decision based on the scheduling
function and security context.
> In the point of avoiding layer violation, the upper layer information
suppose NOT see-able for linker layer where 6P and MSF are.
> But regarding to security, it seems it is not avoidable.
> IMO, the scheduling function is aiming to provide algorithm to add/remove
cell according to traffic.
> The traffic could contains unauthenticated  join request from both normal
devices and malicious devices.
> The function does NOT have enough information to differentiate them.
> We are assuming some other entity out side of MSF needs to resolve this
issue.

>> If assuming the security info in the Ipv6 header is passed to MSF, we
could abandon rate-limiting approach and simply jumping over a slot if the
AF43 packet is sent on that slot.
> Hence the adapting traffic never happens to traffic marked as AF43.

>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I support Roman's Discuss -- we need more information for this to be a
> useful reference; even what seem to be the official DASFAA 1997
> proceedings (https://dblp.org/db/conf/dasfaa/dasfaa97) do not have an
> associated document).
>
> Basing various scheduling aspects on (a hash of) the EUI64 ties
> functionality to a persistent identifier for a device.  How significant
> a disruption would be incurred if a device periodically changes its
> presented EUI64 for anonymization purposes?
>

> I assume you are saying a malicious device?
> There is no doubt this will influence the performance of joining process
for normal devices.
> But normal devices still have a chance to join.
> the join proxy won't be affect as well since the cell will be removed
right after the packet is sent out.

>
> There seems to be a general pattern of "if you don't have a
> 6P-negotiated Tx cell, install and AutoTxCell to send your one message
> and then remove it after sending"; I wonder if it would be easier on the
> reader to consolidate this as a general principle and not repeat the
> details every time it occurs.
>

>  Yes, this is the feature of autonomous cell. Not sure if it would easier
to understand state just one time.
> There is little different for each adding/removing, e.g which node to do
so, parent/JP?
> I personally feel it's clear to repeat this every time,  with various
type of node, so highlighting the difference.

>
> Requirements Language
>
> "NOT RECOMMENDED" is not in the RFC2119 boilerplate (but is a BCP 14
> keyword).
>

> Thanks for pointing out. It will be removed in next revision.
> We also updated the RFC to RFC8174 instead of RFC2119.

>
> Section 1
>
>    the 6 steps described in Section 4.  The end state of the join
>    process is that the node is synchronized to the network, has mutually
>    authenticated to the network, has identified a routing parent, and
>
> nit(?): I guess maybe "mutually authenticated with" is more correct for
> the bidirectional operation.
>

> will update in next revision.

>
>    It does so for 3 reasons: to match the link-layer resources to the
>    traffic, to handle changing parent, to handle a schedule collision.
>
> nit: end the list with "or" (or "and"?).
>

> will update in next revision.

>
>    MSF works closely with RPL, specifically the routing parent defined
>    in [RFC6550].  This specification only describes how MSF works with
>    one routing parent, which is phrased as "selected parent".  The
>
> nit: I suggest '''one routing parent; this parent is referred to as the
> "selected parent"'''.
>

> will update in next revision.

>
>    activity of MSF towards to single routing parent is called as a "MSF
>
> nit: "towards the"
>

> will update in next revision.

>
>    *  We added sections on the interface to the minimal 6TiSCH
>       configuration (Section 2), the use of the SIGNAL command
>       (Section 6), the MSF constants (Section 14), the MSF statistics
>       (Section 15).
>
> nit: end the list with "and".
>

> will update in next revision.

>
> Section 2
>
>    In a TSCH network, time is sliced up into time slots.  The time slots
>    are grouped as one of more slotframes which repeat over time.  The
>
> nit(?): should this be "one or more"?
>

> it should be 'one or multiple slotframes". Will update in next revision

>
>    channel) is indicated as a cell of TSCH schedule.  MSF is one of the
>    policies defining how to manage the TSCH schedule.
>
> nit: if there is only one such policy active at a given time for a given
> network, I suggest "MSF is a policy for managing the TCSH schedule".
> (If multiple policies are active simultaneously, no change is needed.)
>

> As indicated in RFC8480: A node MAY implement multiple SFs  and run them
at the same time.
> so MSF is* one of the policies* defining how to manage the TSCH schedule.

>
>    MSF uses the minimal cell for broadcast frames such as Enhanced
>    Beacons (EBs) [IEEE802154] and broadcast DODAG Information Objects
>    (DIOs) [RFC6550].  Cells scheduled by MSF are meant to be used only
>    for unicast frames.
>
> If this paragraph was moved before the previous paragraph, then EB and
> DIO would be defined before their first usage.
>

> Maybe I understand it wrong. Do you mean you prefer to move this
paragraph before the previous one?
> The EB and DIO are defined in the references, not sure we still need
define them in MSF.

>
>    bandwidth of minimal cell.  One of the algorithm met the rule is the
>    Trickle timer defined in [RFC6206] which is applied on DIO messages
>    [RFC6550].  However, any such algorithm of limiting the broadcast
>
> nit(?): "One of the algorithms that fulfills this requirement"?
>

> will update accordingly.

>
>    MSF RECOMMENDS the use of 3 slotframes.  MSF schedules autonomous
>    cells at Slotframe 1 (Section 3) and 6P negotiated cells at Slotframe
>    2 (Section 5) , while Slotframe 0 is used for the bootstrap traffic
>    as defined in the Minimal 6TiSCH Configuration.  It is RECOMMENDED to
>    use the same slotframe length for Slotframe 0, 1 and 2.  Thus it is
>
> Perhaps this is just a question of writing style, but if an
> implementation is free to use an alternative SF or a variant of MSF,
> could we not say that "MSF uses 3 slotframts", "MSF uses the same
> slotframe length for", etc.?
>

> updated to "3 slotframes are used in MSF. " , "The same slotframe length
for Slotframe 0, 1 and 2 is RECOMMENDED".

>
> Section 3
>
> Is there any risk of unwanted correlation between slot and channel
> offsets when using the same hash function and input for both
> calculations?
>
>    hash function.  Other optional parameters defined in SAX determine
>    the performance of SAX hash function.  Those parameters could be
>    broadcasted in EB frame or pre-configured.  For interoperability
>    purposes, an example how the hash function is implemented is detailed
>    in Appendix B.
>
> Given the lack of usable reference for [SAX-DASFAA], I assume that the
> content in Appendix B is going to be used as a specification, not just
> an example.
>

> the new reference for SAX is updated in the new revision.

>
>    *  The AutoRxCell MUST always remain scheduled after synchronized.
>
> nit: s/synchronized/synchronization/
>
>    AutoRxCell.  In case of conflicting with a negotiated cell,
>    autonomous cells take precedence over negotiated cell, which is
>    stated in [IEEE802154].  However, when the Slotframe 0, 1 and 2 use
>    the same length value, it is possible for negotiated cell to avoid
>    the collision with AutoRxCell.
>
> Presumably this factors in to the recommendation to have the three
> listed slotframes use the same length, but mentioning it explicitly
> (whether here or where the recommendation is made) might be nice.
>

> it is mentioned before as:  *The same slotframe length for Slotframe 0, 1
and 2 is RECOMMENDED.*

>
> Section 4
>
>    network.  Alternative behaviors may involved, for example, when
>    alternative security solution is used for the network.  Section 4.1
>
> nit: singular/plural mismatch "behaviors"/"solution is used"
>

> will be fixed in next revision.

>
> Section 4.1
>
>    A node implementing MSF SHOULD implement the Minimal Security
>    Framework for 6TiSCH [I-D.ietf-6tisch-minimal-security].  As a
>
> Didn't this get renamed to CoJP?
>

> Thanks for pointing it out! Will update in next revision.

>
> Section 4.2
>
> I a little bit wonder if there is a better description than "available
> frequencies" but don't have one to offer.
>

> The frequency to be selected is randomly picked. There is no one that is
preferred comparing to others.

>
> Section 4.3
>
>    While the exact behavior is implementation-specific, it is
>    RECOMMENDED that after having received the first EB, a node keeps
>    listen for at most MAX_EB_DELAY seconds until it has received EBs
>    from NUM_NEIGHBOURS_TO_WAIT distinct neighbors, which is defined in
>    [RFC8180].
>
> nit(?): this phrasing implies that only NUM_NEIGHBOURS_TO_WAIT is
> defined in RFC 8180, but MAX_EB_DELAY is also defined there.
>

> The "which" here indicates the whole behavior.
> It will be rephrased  as "This behavior is defined in [RFC8180]".

>
> not-nit: this phrasing is ambiguous as to whether one of MAX_EB_DELAY
> and NUM_NEIGHBOURS_TO_WAIT is sufficient to move to the next step or
> whether both are required.
>

> The two are actually explaining two situations:
> 1 .keep listening, when EBs from NUM_NEIGHBOURS_TO_WAIT are received, it
stops listening and synchronize to one of the neighbors  .
> 2. if after  MAX_EB_DELAY timeout,  EBs are received from number of
neighbors <  NUM_NEIGHBOURS_TO_WAIT, it stops listening as well and
synchronize to the neighbor or one of neighbors.

>
> Section 4.4
>
>    After selected a JP, a node generates a Join Request and installs an
>    AutoTxCell to the JP.  The Join Request is then sent by the pledge to
>    its JP over the AutoTxCell.  The AutoTxCell is removed by the pledge
>
> editorial: I'd suggest s/its JP/its selected JP/
>

> Will be updated in next revision.

>
>    Response is sent out.  The pledge receives the Join Response from its
>    AutoRxCell, thereby learns the keying material used in the network,
>    as well as other configurations, and becomes a "joined node".
>
> nit: maybe "other configuration values" or "other configuration
> settings"?
>

> Will be updated in next revision.

>
> Section 4.6
>
>    Once it has selected a routing parent, the joined node MUST generate
>    a 6P ADD Request and install an AutoTxCell to that parent.  The 6P
>    ADD Request is sent out through the AutoTxCell with the following
>    fields:
>
>    *  CellOptions: set to TX=3D1,RX=3D0,SHARED=3D0
>    *  NumCells: set to 1
>    *  CellList: at least 5 cells, chosen according to Section 8
>
> Is this listing describing the contents of the ADD request or the
> AuthTxCell used to send it?  (I presume the former, in which case I
> suggest to use "containing" or similar in preference to "with".)
>

> yes, it is the former. Will update in the next revision.

>
> Section 5.1
>
>    The goal of MSF is to manage the communication schedule in the 6TiSCH
>    schedule in a distributed manner.  For a node, this translates into
>    monitoring the current usage of the cells it has to the selected
>    parent:
>
> Is this goal strictly limited to traffic "to the selected parent" vs.
> all traffic?
>

> Theoretically MSF does not limit to traffic to the selected parent but
any neighbors.
> However, all the experiment result with MSF we have made to verify it is
to the selected parent only.
> Hence, We state here "the selected parent" only.

>
>    *  If the node determines that the number of link-layer frames it is
>       attempting to exchange with the selected parent per unit of time
>       is larger than the capacity offered by the TSCH negotiated cells
>       it has scheduled with it, the node issues a 6P ADD command to that
>       parent to add cells to the TSCH schedule.
>    *  If the traffic is lower than the capacity, the node issues a 6P
>       DELETE command to that parent to delete cells from the TSCH
>       schedule.
>
> As written, this would potentially lead to oscillation when demand is
> basically at capacity, due to the quantization of capacity.  Perhaps
> some provisioning for hysteresis is appropriate?
>

> Yes, if referring to the MSF cell usage algorithm in the following, more
cell are scheduled than what needed.
> Here is to explain the basic concept of this scheduling function.

>
>    The cell option of cells listed in CellList in 6P Request frame
>    SHOULD be either Tx=3D1 only or Rx=3D1 only.  Both NumCellsElapsed and
>    NumCellsUsed counters can be used to both type of negotiated cells.
>
> Would this be more clear as "(Tx=3D1,Rx=3D0) or (Tx=3D0,Rx=3D1)"?
>

> Yes it's more clear. Will update in next revision

>
>    *  NumCellsElapsed is incremented by exactly 1 when the current cell
>       is AutoRxCell.
>
> This holds for all peers/parents we're keeping counters for, so the
> AutoRxCell can get "double counted"?
>

> one pair of counters is associated to one neighbor.
> If there is multiple parents, then there are two NumCellsElapsed
counters, one for each of the parents.

>
>    In case that a node booted or disappeared from the network, the cell
>    reserved at the selected parent may be kept in the schedule forever.
>    A clean-up mechanism MUST be provided to resolve this issue.  The
>    clean-up mechanism is implementation-specific.  It could either be a
>    periodic polling to the neighbors the nodes have negotiated cells
>    with, or monitoring the activities on those cells.  The goal is to
>    confirm those negotiated cells are not used anymore by the associated
>    neighbors and remove them from the schedule.
>
> I'm not sure that "monitoring the activities on those cells" is safe
> with the current level of specification; if a node negotiates a 6P
> transmit cell to a parent and uses it only sparingly, with the parent
> eventually reclaiming it due to inactivity, I don't see a mechanism by
> which the node will reliably discover the negotiated cell to be
> nonfunctional and fall back to (e.g.) the corresponding AutoTxCell.  It
> may be most prudent to just not mention that as an example (a "periodic
> polling" procedure does not seem to have the same potential for
> information skew)
>

> Thanks for the comment! I will just remove that sentence from this
paragraph.

>
> Section 5.3
>
>    schedule is executed and the node sends frames to that parent.  When
>    NumTx reaches MAX_NUMTX, both NumTx and NumTxAck MUST be divided by
>    2.  For example, when MAX_NUMTX is set to 256, from NumTx=3D255 and
>    NumTxAck=3D127, the counters become NumTx=3D128 and NumTxAck=3D64 if o=
ne
>    frame is sent to the parent with an Acknowledgment received.  This
>    operation does not change the value of the PDR, but allows the
>    counters to keep incrementing.  The value of MAX_NUMTX is
>    implementation-specific.
>
> Does MAX_NUMTX need to be a power of two (to avoid errors when the
> division occurs)?
>

> Agree, it's better to be a power of two. Will state in the text.

>
>    4.  For any other cell, it compares its PDR against that of the cell
>        with the highest PDR.  If the difference is larger than
>        RELOCATE_PDRTHRES, it triggers the relocation of that cell using
>        a 6P RELOCATE command.
>
> The recommended RELOCATE_PDRTHRES is given as "50 %".  Is this
> "difference" performed as a subtraction (so that if the highest PDR is
> less than 50%, no cells can ever be relocated) or a ratio (a PDR that's
> half than the maximum PDR or smaller will trigger relocation)?
>

> This is "difference" performed as a subtraction.
> Yes it's sure if highest PDR is less than 50%, no cell can be relocated.
> But it can't tell those cells are link quality bad or because of
collision.
> If all cell PDR is so low, highly chance the routing will be affected and
switch to another neighbor.
> In experiments,  we never encounter highest PDR less 50% all time.

>
> Section 7
>
> Maybe reference Section 17.1 where the allocation will occur?
>

> Will add this in next revision.

>
> Section 8
>
>    *  The slotOffset of a cell in the CellList SHOULD be randomly and
>       uniformly chosen among all the slotOffset values that satisfy the
>       restrictions above.
>    *  The channelOffset of a cell in the CellList SHOULD be randomly and
>       uniformly chosen in [0..numFrequencies], where numFrequencies
>       represents the number of frequencies a node can communicate on.
>
> Do these random selections need to be independent from each other?  (I
> note that the selection for the autonomous cells are not.)
>
> > For channelOffset, they are independently random selected.
> For slotOffset, since once a slotOffset is picked, the next time to
select slotOffset, that one can't be selected.
> This is indicated in the text already as "chosen among all the slotOffset
values *that satisfy the*
*      restrictions above*"


> Section 9
>
> Is there a reference for these three parameters (MAXBE, MAXRETRIES,
> SLOTFRAME_LENGTH)?  SLOTFRAME_LENGTH seems new in this document and is
> listed in the table in Section 14, but the other two are not listed
> there.
>

> The MAXBE, MAXRETRIES are defined in IEEE802.15.4 standard.
> Their values various on different network systems, according to the size
and density.
> Hence we didn't give a recommended value in this draft.

>
> Section 14
>
> Why is MAX_NUMTX not listed in the table?
>
> Can we really give a recommended NUM_CH_OFFSET value, since this is in
> effect dependent on the number of channels available?
>

> We give a recommended value as this is a parameter used in the SAX
hashing algorithm.
>  This doesn't provide implementer to use other values.

>
> KA_PERIOD is defined but not used elsewhere in the document.
>

> This is a legacy of MSF draft, which we forgot to remove. Will update in
next revision

>
> What are the considerations in using a power of 10 vs. a power of 2 as
> MAX_NUM_CELLS?
>

> We pick power of 10 simply because it's easy for reader to understand.
Nothing specific.
> There is no restriction to use power of 2, such as 128.

>
> Section 16
>
>    MSF defines a series of "rules" for the node to follow.  It triggers
>    several actions, that are carried out by the protocols defined in the
>    following specifications: the Minimal IPv6 over the TSCH Mode of IEEE
>    802.15.4e (6TiSCH) Configuration [RFC8180], the 6TiSCH Operation
>
> I'd suggest a brief note that the security considerations of those
> protocols continue to apply (even though it ought to be obvious);
> reading them could help a reader understand the behavior of this
> document as well.
>
>    Sublayer Protocol (6P) [RFC8480], and the Minimal Security Framework
>    for 6TiSCH [I-D.ietf-6tisch-minimal-security].  In particular, MSF
>
> [CoJP again]
>
>    prevent it from receiving the join response.  This situation should
>    be detected through the absence of a particular node from the network
>    and handled by the network administrator through out-of-band means,
>    e.g. by moving the node outside the radio range of the attacker.
>
> "the radio range of the attacker" is not exactly a fixed constant ...
> attackers are not in general bound by legal limits and can increase Tx
> power subject only to their equipment and budget.
>

> Yes, I agree. For action, I will simply remove the example.

>
>    MSF adapts to traffics containing packets from IP layer.  It is
>    possible that the IP packet has a non-zero DSCP (Diffserv Code Point
>    [RFC2597]) value in its IPv6 header.  The decision whether to hand
>
> RFC 2597 is talking more about specifically assured forwarding PHB groups
> than "DSCP codepoint"s per se.
>

> Yes, RFC2472 is the one defined the DSCP codepoint. Will update the
reference.

>
> Section 18.1
>
> RFC 6206 seems to only be used as an example (Trickle), and could
> probably be informative.
>
> RFC 8505 might also not need to be normative.
>

> They will be moved to informative reference section

>
> Appendix B
>
>    In MSF, the T is replaced by the length slotframe 1.  String s is
>
> nit: "length of"
>
>    2.  sum the value of L_shift(h,l_bit), R_shift(h,r_bit) and ci
>
> Is this addition performed in "infinite precision" integer arithmetic or
> limited to the output width of h, e.g., by modular division?  (It's not
> clear to me whether this is the role T plays or not.)
>

> What I know here the sum is used by most of the classic string hashing
functions.
> The deep reason why using sum here is more mathematics question, which I
am not an expertise on it:-(
> The T here used for modular is to make sure the result fall into the
range of slotframe ( to pick slotOffset), or available frequencies ( to
pick channelOffset).

>
>    8.  assign the result of Step 5 to h
>
> The value from step 5 *is* h, so taken literally this says "assign h to
> h" and is not needed.
>

>  Yes, this step is removed in next revision.

Thanks so much for your comments. Will prepare revision 13 to resolve them!

>
>
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>
>

--=20
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94

Dr. Tengfei, Chang
Postdoctoral Research Engineer, Inria

www.tchang.org/
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94

--000000000000aef28205a197f60c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi=C2=A0Benjamin,<div><br></div><div>I re=
plied inline starting with &#39;&gt;&#39;</div><div><br></div><div>Thanks s=
o much those detailed comments!</div></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 11, 2020 at 6:55 PM Benjam=
in Kaduk via Datatracker &lt;<a href=3D"mailto:noreply@ietf.org" target=3D"=
_blank">noreply@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Benjamin Kaduk has entered the following ballot pos=
ition for<br>
draft-ietf-6tisch-msf-12: Discuss<br>
<br>
When responding, please keep the subject line intact and reply to all<br>
email addresses included in the To and CC lines. (Feel free to cut this<br>
introductory paragraph, however.)<br>
<br>
<br>
Please refer to <a href=3D"https://www.ietf.org/iesg/statement/discuss-crit=
eria.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/s=
tatement/discuss-criteria.html</a><br>
for more information about IESG DISCUSS and COMMENT positions.<br>
<br>
<br>
The document, along with other ballot positions, can be found here:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6tisch-msf/" rel=3D"=
noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-6=
tisch-msf/</a><br>
<br>
<br>
<br>
----------------------------------------------------------------------<br>
DISCUSS:<br>
----------------------------------------------------------------------<br>
<br>
I&#39;m concerned that the scheduling function for autonomous cells can<br>
cause an infinite loop in the case of hash collision -- Section 3<br>
specifies that AutoTxCell always takes precedence over AutoRxCell, but<br>
if those two cells collide, the corresponding cells on the peer in<br>
question will also collide.=C2=A0 If both peers try to send at the same tim=
e<br>
and the hashes collide, they will both attempt to transmit indefinitely<br>
and never be received.<br></blockquote><div>=C2=A0</div><div>&gt;. Notice t=
hat the AutoTxCell=C2=A0 is a shared cell, where the back-off mechanism is =
applied.</div><div>&gt; In case there is a collision on that cell, a back-o=
ff with different exponent will be used on each side.=C2=A0</div><div>&gt; =
The cell will be used AutoTxCell on each side at different timing.</div><di=
v><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
There seems to be some &quot;passing the buck&quot; going on with respect t=
o<br>
rate-limiting unauthenticated (join) traffic:<br>
draft-ietf-6tisch-minimal-security (Section 6.1.1) says that the SF<br>
&quot;SHOULD NOT allocate additional cells as a result of traffic with code=
<br>
point AF43&quot;; this document is implementing a SF, and yet we try to avo=
id<br>
the issue, saying that &quot;[t]he at IPv6 layer SHOULD ensure that this jo=
in<br>
traffic is rate-limited before it is passed to 6top sublayer where MSF<br>
can observe it&quot;.=C2=A0 I think we need a clear and consistent story ab=
out<br>
where this rate-limiting is supposed to happen.<br></blockquote><div><br></=
div><div>&gt; Thanks for the comments! This has been discussed in some=C2=
=A0 previous revision of MSF.</div><div>&gt; It is not &quot;passing the bu=
ck&quot; but a decision based on the scheduling function and security conte=
xt.</div><div>&gt; In the point of avoiding layer violation, the upper laye=
r information suppose NOT see-able for linker layer where 6P and MSF are.</=
div><div>&gt; But regarding to security, it seems it is not avoidable.</div=
><div>&gt; IMO, the scheduling function is aiming to provide algorithm to a=
dd/remove cell according to traffic.</div><div>&gt; The traffic could conta=
ins=20

unauthenticated=C2=A0 join request from both normal devices and malicious d=
evices.</div><div>&gt; The function does NOT have enough=C2=A0information t=
o differentiate them.</div><div>&gt; We are assuming some other entity out =
side=C2=A0of MSF needs to resolve this issue.</div><div><br></div><div>&gt;=
&gt; If assuming the security info in the Ipv6 header is passed to MSF, we =
could abandon rate-limiting approach and simply jumping over a slot if the =
AF43 packet is sent on that slot.</div><div>&gt; Hence the adapting traffic=
 never happens to traffic marked as AF43.</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
<br>
<br>
----------------------------------------------------------------------<br>
COMMENT:<br>
----------------------------------------------------------------------<br>
<br>
I support Roman&#39;s Discuss -- we need more information for this to be a<=
br>
useful reference; even what seem to be the official DASFAA 1997<br>
proceedings (<a href=3D"https://dblp.org/db/conf/dasfaa/dasfaa97" rel=3D"no=
referrer" target=3D"_blank">https://dblp.org/db/conf/dasfaa/dasfaa97</a>) d=
o not have an<br>
associated document).<br>
<br>
Basing various scheduling aspects on (a hash of) the EUI64 ties<br>
functionality to a persistent identifier for a device.=C2=A0 How significan=
t<br>
a disruption would be incurred if a device periodically changes its<br>
presented EUI64 for anonymization purposes?<br></blockquote><div><br></div>=
<div>&gt; I assume you are saying a malicious device?</div><div>&gt; There =
is no doubt this will influence the performance of joining process for norm=
al devices.</div><div>&gt; But normal devices still have a chance to join.<=
/div><div>&gt; the join proxy won&#39;t be affect as well since the cell wi=
ll be removed right after the packet is sent out.</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">
<br>
There seems to be a general pattern of &quot;if you don&#39;t have a<br>
6P-negotiated Tx cell, install and AutoTxCell to send your one message<br>
and then remove it after sending&quot;; I wonder if it would be easier on t=
he<br>
reader to consolidate this as a general principle and not repeat the<br>
details every time it occurs.<br></blockquote><div><br></div><div>&gt;=C2=
=A0 Yes, this is the feature of autonomous cell. Not sure if it would easie=
r to understand state just one time.</div><div>&gt; There is little differe=
nt for each adding/removing, e.g which node to do so, parent/JP?=C2=A0=C2=
=A0</div><div>&gt; I personally feel it&#39;s clear to repeat this every ti=
me,=C2=A0 with various type of node, so highlighting the difference.=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Requirements Language<br>
<br>
&quot;NOT RECOMMENDED&quot; is not in the RFC2119 boilerplate (but is a BCP=
 14 keyword).<br></blockquote><div><br></div><div>&gt; Thanks for pointing =
out. It will be removed in next revision.=C2=A0</div><div>&gt; We also upda=
ted the RFC to RFC8174 instead of RFC2119.</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">
<br>
Section 1<br>
<br>
=C2=A0 =C2=A0the 6 steps described in Section 4.=C2=A0 The end state of the=
 join<br>
=C2=A0 =C2=A0process is that the node is synchronized to the network, has m=
utually<br>
=C2=A0 =C2=A0authenticated to the network, has identified a routing parent,=
 and<br>
<br>
nit(?): I guess maybe &quot;mutually authenticated with&quot; is more corre=
ct for<br>
the bidirectional operation.<br></blockquote><div><br></div><div>&gt; will =
update in next revision.=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
=C2=A0 =C2=A0It does so for 3 reasons: to match the link-layer resources to=
 the<br>
=C2=A0 =C2=A0traffic, to handle changing parent, to handle a schedule colli=
sion.<br>
<br>
nit: end the list with &quot;or&quot; (or &quot;and&quot;?).<br></blockquot=
e><div><br></div><div>

&gt; will update in next revision.=C2=A0

=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0MSF works closely with RPL, specifically the routing parent de=
fined<br>
=C2=A0 =C2=A0in [RFC6550].=C2=A0 This specification only describes how MSF =
works with<br>
=C2=A0 =C2=A0one routing parent, which is phrased as &quot;selected parent&=
quot;.=C2=A0 The<br>
<br>
nit: I suggest &#39;&#39;&#39;one routing parent; this parent is referred t=
o as the<br>
&quot;selected parent&quot;&#39;&#39;&#39;.<br></blockquote><div><br></div>=
<div>

&gt; will update in next revision.=C2=A0

=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0activity of MSF towards to single routing parent is called as =
a &quot;MSF<br>
<br>
nit: &quot;towards the&quot;<br></blockquote><div><br></div><div>

&gt; will update in next revision.=C2=A0

=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0*=C2=A0 We added sections on the interface to the minimal 6TiS=
CH<br>
=C2=A0 =C2=A0 =C2=A0 configuration (Section 2), the use of the SIGNAL comma=
nd<br>
=C2=A0 =C2=A0 =C2=A0 (Section 6), the MSF constants (Section 14), the MSF s=
tatistics<br>
=C2=A0 =C2=A0 =C2=A0 (Section 15).<br>
<br>
nit: end the list with &quot;and&quot;.<br></blockquote><div><br></div><div=
>

&gt; will update in next revision.=C2=A0

=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 2<br>
<br>
=C2=A0 =C2=A0In a TSCH network, time is sliced up into time slots.=C2=A0 Th=
e time slots<br>
=C2=A0 =C2=A0are grouped as one of more slotframes which repeat over time.=
=C2=A0 The<br>
<br>
nit(?): should this be &quot;one or more&quot;?<br></blockquote><div><br></=
div><div>&gt; it should be &#39;one or multiple slotframes&quot;. Will upda=
te in next revision</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0channel) is indicated as a cell of TSCH schedule.=C2=A0 MSF is=
 one of the<br>
=C2=A0 =C2=A0policies defining how to manage the TSCH schedule.<br>
<br>
nit: if there is only one such policy active at a given time for a given<br=
>
network, I suggest &quot;MSF is a policy for managing the TCSH schedule&quo=
t;.<br>
(If multiple policies are active simultaneously, no change is needed.)<br><=
/blockquote><div><br></div><div>

&gt; As indicated in RFC8480:=C2=A0A node MAY implement multiple SFs=C2=A0 =
and run them at the same time. </div><div>&gt; so MSF is<b> one of the poli=
cies</b>=20

 defining how to manage the TSCH schedule.</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">
<br>
=C2=A0 =C2=A0MSF uses the minimal cell for broadcast frames such as Enhance=
d<br>
=C2=A0 =C2=A0Beacons (EBs) [IEEE802154] and broadcast DODAG Information Obj=
ects<br>
=C2=A0 =C2=A0(DIOs) [RFC6550].=C2=A0 Cells scheduled by MSF are meant to be=
 used only<br>
=C2=A0 =C2=A0for unicast frames.<br>
<br>
If this paragraph was moved before the previous paragraph, then EB and<br>
DIO would be defined before their first usage.<br></blockquote><div><br></d=
iv><div>&gt; Maybe I understand it wrong. Do you mean you prefer to move th=
is paragraph before the previous one?</div><div>&gt; The EB and DIO are def=
ined in the references, not sure we still need define them in MSF.=C2=A0=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0bandwidth of minimal cell.=C2=A0 One of the algorithm met the =
rule is the<br>
=C2=A0 =C2=A0Trickle timer defined in [RFC6206] which is applied on DIO mes=
sages<br>
=C2=A0 =C2=A0[RFC6550].=C2=A0 However, any such algorithm of limiting the b=
roadcast<br>
<br>
nit(?): &quot;One of the algorithms that fulfills this requirement&quot;?<b=
r></blockquote><div><br></div><div>&gt; will update accordingly.=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0MSF RECOMMENDS the use of 3 slotframes.=C2=A0 MSF schedules au=
tonomous<br>
=C2=A0 =C2=A0cells at Slotframe 1 (Section 3) and 6P negotiated cells at Sl=
otframe<br>
=C2=A0 =C2=A02 (Section 5) , while Slotframe 0 is used for the bootstrap tr=
affic<br>
=C2=A0 =C2=A0as defined in the Minimal 6TiSCH Configuration.=C2=A0 It is RE=
COMMENDED to<br>
=C2=A0 =C2=A0use the same slotframe length for Slotframe 0, 1 and 2.=C2=A0 =
Thus it is<br>
<br>
Perhaps this is just a question of writing style, but if an<br>
implementation is free to use an alternative SF or a variant of MSF,<br>
could we not say that &quot;MSF uses 3 slotframts&quot;, &quot;MSF uses the=
 same<br>
slotframe length for&quot;, etc.?<br></blockquote><div><br></div><div>&gt; =
updated to &quot;3 slotframes are used in MSF. &quot; ,=C2=A0&quot;The same=
 slotframe length for Slotframe 0, 1 and 2 is RECOMMENDED&quot;.</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 3<br>
<br>
Is there any risk of unwanted correlation between slot and channel<br>
offsets when using the same hash function and input for both<br>
calculations?<br>
<br>
=C2=A0 =C2=A0hash function.=C2=A0 Other optional parameters defined in SAX =
determine<br>
=C2=A0 =C2=A0the performance of SAX hash function.=C2=A0 Those parameters c=
ould be<br>
=C2=A0 =C2=A0broadcasted in EB frame or pre-configured.=C2=A0 For interoper=
ability<br>
=C2=A0 =C2=A0purposes, an example how the hash function is implemented is d=
etailed<br>
=C2=A0 =C2=A0in Appendix B.<br>
<br>
Given the lack of usable reference for [SAX-DASFAA], I assume that the<br>
content in Appendix B is going to be used as a specification, not just<br>
an example.<br></blockquote><div><br></div><div>&gt; the new reference for =
SAX is updated in the new revision.=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
<br>
=C2=A0 =C2=A0*=C2=A0 The AutoRxCell MUST always remain scheduled after sync=
hronized.<br>
<br>
nit: s/synchronized/synchronization/<br>
<br>
=C2=A0 =C2=A0AutoRxCell.=C2=A0 In case of conflicting with a negotiated cel=
l,<br>
=C2=A0 =C2=A0autonomous cells take precedence over negotiated cell, which i=
s<br>
=C2=A0 =C2=A0stated in [IEEE802154].=C2=A0 However, when the Slotframe 0, 1=
 and 2 use<br>
=C2=A0 =C2=A0the same length value, it is possible for negotiated cell to a=
void<br>
=C2=A0 =C2=A0the collision with AutoRxCell.<br>
<br>
Presumably this factors in to the recommendation to have the three<br>
listed slotframes use the same length, but mentioning it explicitly<br>
(whether here or where the recommendation is made) might be nice.<br></bloc=
kquote><div><br></div><div>&gt; it is mentioned before as:=C2=A0=C2=A0<i>Th=
e same slotframe length for Slotframe 0, 1 and 2 is RECOMMENDED.</i></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 4<br>
<br>
=C2=A0 =C2=A0network.=C2=A0 Alternative behaviors may involved, for example=
, when<br>
=C2=A0 =C2=A0alternative security solution is used for the network.=C2=A0 S=
ection 4.1<br>
<br>
nit: singular/plural mismatch &quot;behaviors&quot;/&quot;solution is used&=
quot;<br></blockquote><div><br></div><div>&gt; will be fixed in next revisi=
on.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 4.1<br>
<br>
=C2=A0 =C2=A0A node implementing MSF SHOULD implement the Minimal Security<=
br>
=C2=A0 =C2=A0Framework for 6TiSCH [I-D.ietf-6tisch-minimal-security].=C2=A0=
 As a<br>
<br>
Didn&#39;t this get renamed to CoJP?<br></blockquote><div><br></div><div>&g=
t; Thanks for pointing it out! Will update in next revision.=C2=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 4.2<br>
<br>
I a little bit wonder if there is a better description than &quot;available=
<br>
frequencies&quot; but don&#39;t have one to offer.<br></blockquote><div><br=
></div><div>&gt; The frequency to be selected is randomly picked. There is =
no one that is preferred comparing to others.</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">
<br>
Section 4.3<br>
<br>
=C2=A0 =C2=A0While the exact behavior is implementation-specific, it is<br>
=C2=A0 =C2=A0RECOMMENDED that after having received the first EB, a node ke=
eps<br>
=C2=A0 =C2=A0listen for at most MAX_EB_DELAY seconds until it has received =
EBs<br>
=C2=A0 =C2=A0from NUM_NEIGHBOURS_TO_WAIT distinct neighbors, which is defin=
ed in<br>
=C2=A0 =C2=A0[RFC8180].<br>
<br>
nit(?): this phrasing implies that only NUM_NEIGHBOURS_TO_WAIT is<br>
defined in RFC 8180, but MAX_EB_DELAY is also defined there.<br></blockquot=
e><div><br></div><div>&gt; The &quot;which&quot; here indicates the whole=
=C2=A0behavior.=C2=A0</div><div>&gt; It will be rephrased=C2=A0 as &quot;Th=
is behavior is defined in [RFC8180]&quot;.</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">
<br>
not-nit: this phrasing is ambiguous as to whether one of MAX_EB_DELAY<br>
and NUM_NEIGHBOURS_TO_WAIT is sufficient to move to the next step or<br>
whether both are required.<br></blockquote><div><br></div><div>&gt; The two=
 are actually explaining two situations:=C2=A0</div><div>&gt; 1 .keep liste=
ning, when EBs from NUM_NEIGHBOURS_TO_WAIT are received, it stops listening=
 and synchronize to one of the=20

neighbors=C2=A0 .</div><div>&gt; 2. if after=C2=A0 MAX_EB_DELAY timeout,=C2=
=A0 EBs are received from number of neighbors &lt;=C2=A0

NUM_NEIGHBOURS_TO_WAIT, it stops listening as well and synchronize to the n=
eighbor or one of neighbors.</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
Section 4.4<br>
<br>
=C2=A0 =C2=A0After selected a JP, a node generates a Join Request and insta=
lls an<br>
=C2=A0 =C2=A0AutoTxCell to the JP.=C2=A0 The Join Request is then sent by t=
he pledge to<br>
=C2=A0 =C2=A0its JP over the AutoTxCell.=C2=A0 The AutoTxCell is removed by=
 the pledge<br>
<br>
editorial: I&#39;d suggest s/its JP/its selected JP/<br></blockquote><div><=
br></div><div>&gt; Will be updated in next revision.=C2=A0=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0Response is sent out.=C2=A0 The pledge receives the Join Respo=
nse from its<br>
=C2=A0 =C2=A0AutoRxCell, thereby learns the keying material used in the net=
work,<br>
=C2=A0 =C2=A0as well as other configurations, and becomes a &quot;joined no=
de&quot;.<br>
<br>
nit: maybe &quot;other configuration values&quot; or &quot;other configurat=
ion<br>
settings&quot;?<br></blockquote><div><br></div><div>&gt; Will be updated in=
 next revision.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
<br>
Section 4.6<br>
<br>
=C2=A0 =C2=A0Once it has selected a routing parent, the joined node MUST ge=
nerate<br>
=C2=A0 =C2=A0a 6P ADD Request and install an AutoTxCell to that parent.=C2=
=A0 The 6P<br>
=C2=A0 =C2=A0ADD Request is sent out through the AutoTxCell with the follow=
ing<br>
=C2=A0 =C2=A0fields:<br>
<br>
=C2=A0 =C2=A0*=C2=A0 CellOptions: set to TX=3D1,RX=3D0,SHARED=3D0<br>
=C2=A0 =C2=A0*=C2=A0 NumCells: set to 1<br>
=C2=A0 =C2=A0*=C2=A0 CellList: at least 5 cells, chosen according to Sectio=
n 8<br>
<br>
Is this listing describing the contents of the ADD request or the<br>
AuthTxCell used to send it?=C2=A0 (I presume the former, in which case I<br=
>
suggest to use &quot;containing&quot; or similar in preference to &quot;wit=
h&quot;.)<br></blockquote><div><br></div><div>&gt; yes, it is the former. W=
ill update in the next revision.=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">
<br>
Section 5.1<br>
<br>
=C2=A0 =C2=A0The goal of MSF is to manage the communication schedule in the=
 6TiSCH<br>
=C2=A0 =C2=A0schedule in a distributed manner.=C2=A0 For a node, this trans=
lates into<br>
=C2=A0 =C2=A0monitoring the current usage of the cells it has to the select=
ed<br>
=C2=A0 =C2=A0parent:<br>
<br>
Is this goal strictly limited to traffic &quot;to the selected parent&quot;=
 vs.<br>
all traffic?<br></blockquote><div><br></div><div>&gt; Theoretically MSF doe=
s not limit to traffic to the selected parent but any neighbors.=C2=A0</div=
><div>&gt; However, all the experiment result with MSF we have made to veri=
fy it is to the selected parent only.</div><div>&gt; Hence, We state here &=
quot;the selected parent&quot; only.</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
<br>
=C2=A0 =C2=A0*=C2=A0 If the node determines that the number of link-layer f=
rames it is<br>
=C2=A0 =C2=A0 =C2=A0 attempting to exchange with the selected parent per un=
it of time<br>
=C2=A0 =C2=A0 =C2=A0 is larger than the capacity offered by the TSCH negoti=
ated cells<br>
=C2=A0 =C2=A0 =C2=A0 it has scheduled with it, the node issues a 6P ADD com=
mand to that<br>
=C2=A0 =C2=A0 =C2=A0 parent to add cells to the TSCH schedule.<br>
=C2=A0 =C2=A0*=C2=A0 If the traffic is lower than the capacity, the node is=
sues a 6P<br>
=C2=A0 =C2=A0 =C2=A0 DELETE command to that parent to delete cells from the=
 TSCH<br>
=C2=A0 =C2=A0 =C2=A0 schedule.<br>
<br>
As written, this would potentially lead to oscillation when demand is<br>
basically at capacity, due to the quantization of capacity.=C2=A0 Perhaps<b=
r>
some provisioning for hysteresis is appropriate?<br></blockquote><div><br><=
/div><div>&gt; Yes, if referring to the MSF cell usage algorithm in the fol=
lowing, more cell are scheduled than what needed.</div><div>&gt; Here is to=
 explain the basic concept of this scheduling function.=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0The cell option of cells listed in CellList in 6P Request fram=
e<br>
=C2=A0 =C2=A0SHOULD be either Tx=3D1 only or Rx=3D1 only.=C2=A0 Both NumCel=
lsElapsed and<br>
=C2=A0 =C2=A0NumCellsUsed counters can be used to both type of negotiated c=
ells.<br>
<br>
Would this be more clear as &quot;(Tx=3D1,Rx=3D0) or (Tx=3D0,Rx=3D1)&quot;?=
<br></blockquote><div><br></div><div>&gt; Yes it&#39;s more clear. Will upd=
ate in next revision=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">
<br>
=C2=A0 =C2=A0*=C2=A0 NumCellsElapsed is incremented by exactly 1 when the c=
urrent cell<br>
=C2=A0 =C2=A0 =C2=A0 is AutoRxCell.<br>
<br>
This holds for all peers/parents we&#39;re keeping counters for, so the<br>
AutoRxCell can get &quot;double counted&quot;?<br></blockquote><div><br></d=
iv><div>&gt; one pair of counters is associated to one neighbor.=C2=A0</div=
><div>&gt; If there is multiple parents, then there are two NumCellsElapsed=
 counters, one for each of the parents.</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">
<br>
=C2=A0 =C2=A0In case that a node booted or disappeared from the network, th=
e cell<br>
=C2=A0 =C2=A0reserved at the selected parent may be kept in the schedule fo=
rever.<br>
=C2=A0 =C2=A0A clean-up mechanism MUST be provided to resolve this issue.=
=C2=A0 The<br>
=C2=A0 =C2=A0clean-up mechanism is implementation-specific.=C2=A0 It could =
either be a<br>
=C2=A0 =C2=A0periodic polling to the neighbors the nodes have negotiated ce=
lls<br>
=C2=A0 =C2=A0with, or monitoring the activities on those cells.=C2=A0 The g=
oal is to<br>
=C2=A0 =C2=A0confirm those negotiated cells are not used anymore by the ass=
ociated<br>
=C2=A0 =C2=A0neighbors and remove them from the schedule.<br>
<br>
I&#39;m not sure that &quot;monitoring the activities on those cells&quot; =
is safe<br>
with the current level of specification; if a node negotiates a 6P<br>
transmit cell to a parent and uses it only sparingly, with the parent<br>
eventually reclaiming it due to inactivity, I don&#39;t see a mechanism by<=
br>
which the node will reliably discover the negotiated cell to be<br>
nonfunctional and fall back to (e.g.) the corresponding AutoTxCell.=C2=A0 I=
t<br>
may be most prudent to just not mention that as an example (a &quot;periodi=
c<br>
polling&quot; procedure does not seem to have the same potential for<br>
information skew)<br></blockquote><div><br></div><div>&gt; Thanks for the c=
omment! I will just remove that sentence from this paragraph.</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
<br>
Section 5.3<br>
<br>
=C2=A0 =C2=A0schedule is executed and the node sends frames to that parent.=
=C2=A0 When<br>
=C2=A0 =C2=A0NumTx reaches MAX_NUMTX, both NumTx and NumTxAck MUST be divid=
ed by<br>
=C2=A0 =C2=A02.=C2=A0 For example, when MAX_NUMTX is set to 256, from NumTx=
=3D255 and<br>
=C2=A0 =C2=A0NumTxAck=3D127, the counters become NumTx=3D128 and NumTxAck=
=3D64 if one<br>
=C2=A0 =C2=A0frame is sent to the parent with an Acknowledgment received.=
=C2=A0 This<br>
=C2=A0 =C2=A0operation does not change the value of the PDR, but allows the=
<br>
=C2=A0 =C2=A0counters to keep incrementing.=C2=A0 The value of MAX_NUMTX is=
<br>
=C2=A0 =C2=A0implementation-specific.<br>
<br>
Does MAX_NUMTX need to be a power of two (to avoid errors when the<br>
division occurs)?<br></blockquote><div><br></div><div>&gt; Agree, it&#39;s =
better to be a power of two. Will state in the text.=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A04.=C2=A0 For any other cell, it compares its PDR against that =
of the cell<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0with the highest PDR.=C2=A0 If the difference is=
 larger than<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0RELOCATE_PDRTHRES, it triggers the relocation of=
 that cell using<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0a 6P RELOCATE command.<br>
<br>
The recommended RELOCATE_PDRTHRES is given as &quot;50 %&quot;.=C2=A0 Is th=
is<br>
&quot;difference&quot; performed as a subtraction (so that if the highest P=
DR is<br>
less than 50%, no cells can ever be relocated) or a ratio (a PDR that&#39;s=
<br>
half than the maximum PDR or smaller will trigger relocation)?<br></blockqu=
ote><div><br></div><div>&gt; This is &quot;difference&quot; performed as a =
subtraction.=C2=A0</div><div>&gt; Yes it&#39;s sure if highest PDR is less =
than 50%, no cell can be relocated.=C2=A0</div><div>&gt; But it can&#39;t t=
ell those cells=C2=A0are link quality bad or because of collision.=C2=A0</d=
iv><div>&gt; If all cell PDR is so low, highly chance the routing will be a=
ffected and switch to another neighbor.</div><div>&gt; In experiments,=C2=
=A0 we never encounter highest PDR less 50% all time.</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<br>
Section 7<br>
<br>
Maybe reference Section 17.1 where the allocation will occur?<br></blockquo=
te><div><br></div><div>&gt; Will add this in next revision.=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 8<br>
<br>
=C2=A0 =C2=A0*=C2=A0 The slotOffset of a cell in the CellList SHOULD be ran=
domly and<br>
=C2=A0 =C2=A0 =C2=A0 uniformly chosen among all the slotOffset values that =
satisfy the<br>
=C2=A0 =C2=A0 =C2=A0 restrictions above.<br>
=C2=A0 =C2=A0*=C2=A0 The channelOffset of a cell in the CellList SHOULD be =
randomly and<br>
=C2=A0 =C2=A0 =C2=A0 uniformly chosen in [0..numFrequencies], where numFreq=
uencies<br>
=C2=A0 =C2=A0 =C2=A0 represents the number of frequencies a node can commun=
icate on.<br>
<br>
Do these random selections need to be independent from each other?=C2=A0 (I=
<br>
note that the selection for the autonomous cells are not.)<br>
<br></blockquote><div>&gt; For channelOffset, they are independently random=
 selected.</div><div>&gt; For slotOffset, since once a slotOffset is picked=
, the next time to select slotOffset, that one can&#39;t be selected.</div>=
<div>&gt; This is indicated in the text already as &quot;chosen among all t=
he slotOffset values <b>that satisfy the</b></div><div><b>=C2=A0 =C2=A0 =C2=
=A0 restrictions above</b>&quot;</div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">
Section 9<br>
<br>
Is there a reference for these three parameters (MAXBE, MAXRETRIES,<br>
SLOTFRAME_LENGTH)?=C2=A0 SLOTFRAME_LENGTH seems new in this document and is=
<br>
listed in the table in Section 14, but the other two are not listed<br>
there.<br></blockquote><div><br></div><div>&gt; The=20

MAXBE, MAXRETRIES are defined in IEEE802.15.4 standard.=C2=A0</div><div>&gt=
; Their values various on different network systems, according to the size =
and density.</div><div>&gt; Hence we didn&#39;t give a recommended value in=
 this draft.</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 14<br>
<br>
Why is MAX_NUMTX not listed in the table?<br>
<br>
Can we really give a recommended NUM_CH_OFFSET value, since this is in<br>
effect dependent on the number of channels available?<br></blockquote><div>=
<br></div><div>&gt; We give a recommended value as this is a parameter used=
 in the SAX hashing algorithm.=C2=A0</div><div>&gt;=C2=A0 This doesn&#39;t =
provide implementer to use other values.</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
<br>
KA_PERIOD is defined but not used elsewhere in the document.<br></blockquot=
e><div><br></div><div>&gt; This is a legacy of MSF draft, which we forgot t=
o remove. Will update in next revision=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">
<br>
What are the considerations in using a power of 10 vs. a power of 2 as<br>
MAX_NUM_CELLS?<br></blockquote><div><br></div><div>&gt; We pick power of 10=
 simply because it&#39;s easy for reader to understand. Nothing specific.</=
div><div>&gt; There is no restriction to use power of 2, such as 128.=C2=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 16<br>
<br>
=C2=A0 =C2=A0MSF defines a series of &quot;rules&quot; for the node to foll=
ow.=C2=A0 It triggers<br>
=C2=A0 =C2=A0several actions, that are carried out by the protocols defined=
 in the<br>
=C2=A0 =C2=A0following specifications: the Minimal IPv6 over the TSCH Mode =
of IEEE<br>
=C2=A0 =C2=A0802.15.4e (6TiSCH) Configuration [RFC8180], the 6TiSCH Operati=
on<br>
<br>
I&#39;d suggest a brief note that the security considerations of those<br>
protocols continue to apply (even though it ought to be obvious);<br>
reading them could help a reader understand the behavior of this<br>
document as well.<br>
<br>
=C2=A0 =C2=A0Sublayer Protocol (6P) [RFC8480], and the Minimal Security Fra=
mework<br>
=C2=A0 =C2=A0for 6TiSCH [I-D.ietf-6tisch-minimal-security].=C2=A0 In partic=
ular, MSF<br>
<br>
[CoJP again]<br>
<br>
=C2=A0 =C2=A0prevent it from receiving the join response.=C2=A0 This situat=
ion should<br>
=C2=A0 =C2=A0be detected through the absence of a particular node from the =
network<br>
=C2=A0 =C2=A0and handled by the network administrator through out-of-band m=
eans,<br>
=C2=A0 =C2=A0e.g. by moving the node outside the radio range of the attacke=
r.<br>
<br>
&quot;the radio range of the attacker&quot; is not exactly a fixed constant=
 ...<br>
attackers are not in general bound by legal limits and can increase Tx<br>
power subject only to their equipment and budget.<br></blockquote><div><br>=
</div><div>&gt; Yes, I agree. For action, I will simply remove the example.=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=C2=A0 =C2=A0MSF adapts to traffics containing packets from IP layer.=C2=A0=
 It is<br>
=C2=A0 =C2=A0possible that the IP packet has a non-zero DSCP (Diffserv Code=
 Point<br>
=C2=A0 =C2=A0[RFC2597]) value in its IPv6 header.=C2=A0 The decision whethe=
r to hand<br>
<br>
RFC 2597 is talking more about specifically assured forwarding PHB groups<b=
r>
than &quot;DSCP codepoint&quot;s per se.<br></blockquote><div><br></div><di=
v>&gt; Yes, RFC2472 is the one defined the DSCP codepoint. Will update the =
reference.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 18.1<br>
<br>
RFC 6206 seems to only be used as an example (Trickle), and could<br>
probably be informative.<br>
<br>
RFC 8505 might also not need to be normative.<br></blockquote><div><br></di=
v><div>&gt; They will be moved to informative reference section=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Appendix B<br>
<br>
=C2=A0 =C2=A0In MSF, the T is replaced by the length slotframe 1.=C2=A0 Str=
ing s is<br>
<br>
nit: &quot;length of&quot;<br>
<br>
=C2=A0 =C2=A02.=C2=A0 sum the value of L_shift(h,l_bit), R_shift(h,r_bit) a=
nd ci<br>
<br>
Is this addition performed in &quot;infinite precision&quot; integer arithm=
etic or<br>
limited to the output width of h, e.g., by modular division?=C2=A0 (It&#39;=
s not<br>
clear to me whether this is the role T plays or not.)<br></blockquote><div>=
<br></div><div>&gt; What I know here the sum is used by most of the classic=
 string hashing functions.</div><div>&gt; The deep reason why using sum her=
e is more mathematics question, which I am not an expertise on it:-(</div><=
div>&gt; The T here used for modular is to make sure the result fall into t=
he range of slotframe=C2=A0( to pick slotOffset), or available frequencies =
( to pick channelOffset).</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">
<br>
=C2=A0 =C2=A08.=C2=A0 assign the result of Step 5 to h<br>
<br>
The value from step 5 *is* h, so taken literally this says &quot;assign h t=
o<br>
h&quot; and is not needed.<br></blockquote><div><br></div><div>&gt;=C2=A0 Y=
es, this step is removed in next revision.</div><div><br></div><div>Thanks =
so much for your comments. Will prepare revision 13 to resolve them!</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
<br>
_______________________________________________<br>
6tisch mailing list<br>
<a href=3D"mailto:6tisch@ietf.org" target=3D"_blank">6tisch@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/6tisch" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/6tisch<br></a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div dir=3D"l=
tr"><div style=3D"background-color:rgb(253,253,253)"><font color=3D"#000000=
" face=3D"monospace, monospace">=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
</font></div><div style=3D"background-color:rgb(253,253,253)"><font color=
=3D"#000000" face=3D"monospace, monospace"><br></font></div><div style=3D"f=
ont-size:12.8px;background-color:rgb(253,253,253)"><font face=3D"monospace,=
 monospace" size=3D"2" color=3D"#000000">Dr. Tengfei, Chang</font></div><sp=
an style=3D"font-size:12.8px"><font face=3D"monospace, monospace" size=3D"2=
" color=3D"#000000"><div style=3D"background-color:rgb(253,253,253)"><span =
style=3D"background-color:rgb(255,255,255)">Postdoctoral Research Engineer<=
/span>, Inria</div><div style=3D"background-color:rgb(253,253,253)"><br></d=
iv><div style=3D"background-color:rgb(253,253,253)"><a href=3D"http://www.t=
chang.org/" target=3D"_blank">www.tchang.org/</a></div><div style=3D"backgr=
ound-color:rgb(253,253,253)">=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94</d=
iv></font></span></div></div></div></div></div></div></div></div>

--000000000000aef28205a197f60c--

