Dear Mirja,

thanks so much for your review. We are integrating your comments to the
next version of the draft.

kind regards,
Xavi

2017-02-10 17:46 GMT+01:00 Mirja Kuehlewind <[email protected]>:

> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-6tisch-minimal-19: No Objection
>
> 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-minimal/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> A couple of comments mostly on the use of normative language:
>
> 1) The following sentence contradict a little all other normative
> language in this document (basically making everything a SHOULD):
> "Any 6TiSCH compliant device SHOULD implement this mode of operation."
> Why is this a upper case SHOULD? Is this sentence needed at all?
>
> 2) Here the usage of normative language is also not clear to me:
> "The default values of the TSCH Timeslot template (defined in
>    [IEEE802154-2015]  section 8.4.2.2.3) and Channel Hopping sequence
>    (defined in [IEEE802154-2015] section 6.2.10) SHOULD be used.  A
> node
>    MAY use different values by properly announcing them in its Enhanced
>    Beacon."
>
> 3) Is it correct that these are SHOULDs?
> "EB Destination Address field SHOULD be set to 0xFFFF (short broadcast
>    address).  The EB Source Address field SHOULD be set as the node's
>    short address if this is supported.  Otherwise the long address
>    SHOULD be used."
>
> 4) What the recommended value for EB_PERIOD?:
> "In a minimal TSCH
>    configuration, a node SHOULD send an EB every EB_PERIOD."
>
> 5) This is also a weird SHOULD for me:
> "EBs SHOULD be used to obtain information about local networks, ..."
> What else should be used? Or you just don't obtain the information you
> need. I actually guess that you should simply use a lower case should in
> this sentence.
> Should it be?:
> "The default values of the TSCH Timeslot template (defined in
>    [IEEE802154-2015]  section 8.4.2.2.3) and Channel Hopping sequence
>    (defined in [IEEE802154-2015] section 6.2.10) SHOULD be used.  If a
> node
>    uses different values, it MUST properly announcing them in its
> Enhanced
>    Beacon."
> Or is this sentence just duplicating the SHOULD of the previous sentence
> slightly differently?
>
> 6) Maybe also name the recommended values for MAX_EB_DELAY and
> NUM_NEIGHBOURS_TO_WAIT in section 6.2 or give a forward reference to
> section 7.3?
>
> 7) "At any time, a node MUST maintain connectivity to at least one time
>    source neighbor. "
>   How can you ensure that you can maintain connectivity? I guess this
> must be a SHOULD... or what do you mean exactly by 'maintain
> connectivity'?
>
> 8) I think this sentence is confusing given the recommended value for
> NUM_UPPERLAYER_PACKETS is 1:
> "One entry in the queue is reserved at all times for frames of type
> BEACON."
> I guess what you want to say it that if a BEACON should be send and there
> is no space in the queue one frame should be drop and the BEACON should
> be queued instead?
>
> 9) I'm a little surprised to not see anything about 6LoWPAN in the body
> of the document (besides the intro in section 1). Shouldn't there also be
> some normative language on the use of 6LoWPAN?
>
> One editorial comment (from the abstract):
> I don't really understand this sentence
> "A minimal mode of operation is a baseline set of protocols, ..."
> I guess you want to say something like
> "This minimal mode of operation specifies the baseline set of protocols
> that need to be supported, .."
>
>
>


-- 
Dr. Xavier Vilajosana
Wireless Networks Lab

*Internet Interdisciplinary Institute (IN3)Professor*
(+34) 646 633 681
[email protected] <[email protected]>
http://xvilajosana.org
http://wine.rdi.uoc.edu
Parc Mediterrani de la Tecnologia
Av Carl Friedrich Gauss 5, B3 Building
08860 Castelldefels (Barcelona). Catalonia. Spain
[image: Universitat Oberta de Catalunya]
­
_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to