[6tisch] Jonathan's review on draft-ietf-6tisch-6top-interface-01

Jonathan Simon <jsimon@linear.com> Sat, 25 October 2014 00:31 UTC

Return-Path: <jsimon@linear.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 489591A1B4B for <6tisch@ietfa.amsl.com>; Fri, 24 Oct 2014 17:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 af8h8-GVImNt for <6tisch@ietfa.amsl.com>; Fri, 24 Oct 2014 17:31:55 -0700 (PDT)
Received: from p01c11o144.mxlogic.net (p01c11o144.mxlogic.net [208.65.144.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A95FE1A0636 for <6tisch@ietf.org>; Fri, 24 Oct 2014 17:31:54 -0700 (PDT)
Received: from unknown [12.218.215.72] (EHLO smtpauth1.linear.com) by p01c11o144.mxlogic.net(mxl_mta-8.2.0-0) with ESMTP id 97fea445.0.77568.00-349.196339.p01c11o144.mxlogic.net (envelope-from <jsimon@linear.com>); Fri, 24 Oct 2014 18:31:54 -0600 (MDT)
X-MXL-Hash: 544aef7a3b88d91e-7ad371c16fbb5e40e8cb874d79fe8c6b0b16d83b
Received: from jsimonmacmini.engineering.linear.com (unknown [10.70.48.25]) by smtpauth1.linear.com (Postfix) with ESMTPSA id A03E47409C for <6tisch@ietf.org>; Fri, 24 Oct 2014 17:31:50 -0700 (PDT)
From: Jonathan Simon <jsimon@linear.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F3220487-B648-4B7C-9AEA-A585E1E0B8A6"
Message-Id: <313BE5D8-738C-49A3-BEE3-0DA050528F0A@linear.com>
Date: Fri, 24 Oct 2014 17:31:33 -0700
To: 6tisch@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
X-AnalysisOut: [v=2.1 cv=fdS5yigF c=1 sm=1 tr=0 a=glloKNylpeYNumXQcclYyA==]
X-AnalysisOut: [:117 a=glloKNylpeYNumXQcclYyA==:17 a=BLceEmwcHowA:10 a=MqD]
X-AnalysisOut: [INYqSAAAA:8 a=YlVTAMxIAAAA:8 a=t-7_KEccwApciFuiqywA:9 a=SS]
X-AnalysisOut: [bmhayvcShWjs59:21 a=if8pjTUxR7kXx1xU:21 a=pILNOxqGKmIA:10 ]
X-AnalysisOut: [a=19wCD08tTksA:10 a=vsVyj9psLt0A:10 a=qVizmW-ZYBIA:10 a=p-]
X-AnalysisOut: [HxVa_ds0YA:10 a=r-oJtTHvpvzyLgBpukMA:9 a=bYbnopWTIVHRvjzu:]
X-AnalysisOut: [21 a=z3bEG5TXDpwr4TAU:21 a=W5ep2mxUXuH_Cp4S:21 a=_W_S_7Vec]
X-AnalysisOut: [oQA:10]
X-Spam: [F=0.5000000000; CM=0.500; MH=0.500(2014102412); S=0.200(2014051901)]
X-MAIL-FROM: <jsimon@linear.com>
X-SOURCE-IP: [12.218.215.72]
Archived-At: http://mailarchive.ietf.org/arch/msg/6tisch/PGsQAewOZxsfLzbMuqmZ0iYA-1w
Subject: [6tisch] Jonathan's review on draft-ietf-6tisch-6top-interface-01
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 25 Oct 2014 00:31:57 -0000

Finally got around to reviewing this.  Better late than never?

p2 - odd sentence “This document also defines a list commands internal to the 6top sublayer.”

p5 - CellType option is mandatory (2.1), but it seems to also be implicit in how the cell is created (2.1.1 & 2.1.2). Does MUST in these sections mean that this option must be set explicitly? 

p7 - what does unicast (resp.broadcast) mean?

p9 - channelOffset should be 16-bit (per 802.15.4e-2012 table 52d)

p13 & 14 - the metrics listed do not correspond to those defined in 802.15.4e-2012 table 4i.    PDR, ETX, RSSI and LQI are not used in TSCH or macMetrics descriptions.
- 4e defines a counter size, macCounterOctets, that needs to be specified by 6top - could be a fixed value or set via YANG.
- “Window” measurement period is specified in "Number of the slotframe size” - Does “Number” here mean multiples? what if metrics apply to all slotframes?

p15 - “Peroid” instead of period.  
- CellID - cell ID’s are local to a particular slotframe, so this is meaningless without a slotframe ID
- If the period is in seconds, and the cell repeat rate is not, how is this supposed to work?

p 17 - why is last comms ASN being stored?

general questions/comments:

* Are all things in the YANG model required?  For example, must one support reading the READ.timesource for minTimeCorrection? Must all nodes support chunks, and tracks, and softcells, labelSwitching, or is this policy?
* Are all things in the YANG model expected to be encoded and sent over the air?
* There is no mechanism to specify additional IEs in an EB - is this outside of YANG?
* There’s no way to set the PANID.

* Certain PIBs must be set in a generic 15.4e MAC to get TSCH behavior. I don’t know if these are needed in YANG, but need to be in 6TiSCH:
** some Table 52n on EBs entries need to be set
** Table 60 macFrameCounterMode needs to be 5 octets for ASN to work
** The fields needed to form the IEs contained in the EB are specified, but whether they are sent explicitly or by ID isn’t defined
** macTSCHcapable, and macTSCHEnabled, macMetricsCapable, macMetricsEnabled, aren’t discussed.
** There is no explicit configuration of EBs (e.g. macUseEnhancedBeacon) at the MAC or a discussion of MLME-BEACON.request.
-- 
Jonathan Simon, Ph. D
Director of Systems Engineering
Linear Technology, Dust Networks product group
32990 Alvarado-Niles Road, Suite 910
Union City, CA 94587
(510) 400-2936
(510) 489-3799 FAX
jsimon@linear.com

**LINEAR TECHNOLOGY CORPORATION** 
*****Internet Email Confidentiality Notice***** 
 This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail, or by telephone at (510) 400-2936, and destroy the original transmission and its attachments without reading or saving in any manner. Thank you.