[6tisch] Consensus call on Summary of proposed resolution for issue 40 V3

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 18 December 2015 14:14 UTC

Return-Path: <pthubert@cisco.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 4E7B21B2BED for <6tisch@ietfa.amsl.com>; Fri, 18 Dec 2015 06:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 WkkNuQuQTqQQ for <6tisch@ietfa.amsl.com>; Fri, 18 Dec 2015 06:14:00 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98C671B3650 for <6tisch@ietf.org>; Fri, 18 Dec 2015 06:14:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9482; q=dns/txt; s=iport; t=1450448040; x=1451657640; h=from:to:subject:date:message-id:mime-version; bh=O5qapqAQYkujkqKdn/gkxJG2Us/3Hyhd6/33P28jbO8=; b=V5XyMjWx4HnTR0/BIYfDO4u0md/kU/BJY/ccRMPoS05DvPfol/gJCIzn tusXuBF4B2ivBSUr4X//lyDpTz1AtgQ8LIUe16Hm+3cP2jFHaGvLcgw7P bvslznqaY/pbqybojHgBmxNxlySuKkYtHo7UMPVNNqU9m/Tarp07mF62u 8=;
X-Files: signature.asc : 858
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DbAgBPE3RW/5hdJa1egzqBPwa9Tw6BYoYNAhyBGjgUAQEBAQEBAX8LhDQBAQEDAR0GWwcGARkBAwEBASoCBDAXBgkBBBMIBg2IDAibXY9wkXABAQEBAQEEAQEBAQEBAQEBEQmGVok8gzmBSQWHXI8jAYELgWOBYoNbhReBY4RFjiaIYQEgAUOEBHKECYEIAQEB
X-IronPort-AV: E=Sophos;i="5.20,446,1444694400"; d="asc'?scan'208";a="56684264"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Dec 2015 14:13:59 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id tBIEDxk5001703 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <6tisch@ietf.org>; Fri, 18 Dec 2015 14:13:59 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 18 Dec 2015 08:13:58 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Fri, 18 Dec 2015 08:13:58 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: Consensus call on Summary of proposed resolution for issue 40 V3
Thread-Index: AdE5nYbDzMsYDZ7aRxG4O4UrH55QBA==
Date: Fri, 18 Dec 2015 14:13:39 +0000
Deferred-Delivery: Fri, 18 Dec 2015 14:13:11 +0000
Message-ID: <2ef53fd8d663495fbc364d90fb91e92a@XCH-RCD-001.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.6.50]
Content-Type: multipart/mixed; boundary="_002_2ef53fd8d663495fbc364d90fb91e92aXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/wRPQmpxKV-kOsr4b5yglCNYMzgg>
Subject: [6tisch] Consensus call on Summary of proposed resolution for issue 40 V3
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: <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: Fri, 18 Dec 2015 14:14:07 -0000

Dear all;

In order to address Ralph's issues on the minimal draft, we proposed a rewording of the abstract and the introduction. 
This reopens  a 2-weeks period of last call for these particular sections, with the text as below.
If you disagree with the text, please let us know before January 1st.

Cheers,

Pascal


-----Original Message-----
From: Ralph Droms (rdroms) 
Sent: lundi 14 décembre 2015 19:35
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: 6tisch@ietf.org
Subject: Re: Summary of proposed resolution for issue 40 V3


> On Dec 14, 2015, at 11:16 AM 12/14/15, Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
> 
> Hello Ralph:
> 
> If you’re OK with this round, we’ll open a one week call to the WG to check consensus.
> The proposed replacement for slotted aloha is subject to change again 
> in that phase J
> 
> Please let us know;

Assessing WG consensus is OK with me.

- Ralph

> 
> Pascal
> 
> ----------------------------------------------------------------------
> -----------
> 
> Abstract update:
> 
> BEFORE
> 
> 
> --------------
> Abstract
> 
>   This document describes the minimal set of rules to operate an IEEE
>   802.15.4 Timeslotted Channel Hopping (TSCH) network.  This minimal
>   mode of operation can be used during network bootstrap, as a fall-
>   back mode of operation when no dynamic scheduling solution is
>   available or functioning, or during early interoperability testing
>   and development.
> 
> ---------------
> AFTER
> 
> ---------------
> Abstract
> 
> This document describes a minimal mode of operation for a 6TiSCH 
> Network, to provide IPv6 connectivity over a Non-Broadcast 
> Multi-Access (NBMA) mesh that is formed of IEEE 802.15.4 Timeslotted Channel Hopping (TSCH) links.
> This minimal mode uses a collection of protocols including the 6LoWPAN 
> framework and RPL to enable shared access operations over a static 
> TSCH schedule.
> 
> 
> -------------
> -------------
> -------------
> 
> Intro update:
> 
> 
> 
> BEFORE
> 
> 
> --------------
> 
> 1.  Requirements Language
> 
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>   document are to be interpreted as described in RFC 2119 [RFC2119].
> 
> 2.  Introduction
> 
>   The nodes in a IEEE 802.15.4 TSCH network follow a communication
>   schedule.  The entity (centralized or decentralized) responsible for
>   building and maintaining that schedule has precise control over the
>   trade-off between the network's latency, bandwidth, reliability and
>   power consumption.  During early interoperability testing and
>   development, however, simplicity is more important than efficiency.
>   One goal of this document is to define the simplest set of rules for
>   building a TSCH-compliant network, at the necessary price of lesser
>   efficiency.  Yet, this minimal mode of operation MAY also be used
>   during network bootstrap before any schedule is installed into the
>   network so nodes can self-organize and the management and
>   configuration information be distributed.  In addition, the minimal
>   configuration MAY be used as a fall-back mode of operation, ensuring
>   connectivity of nodes in case that dynamic scheduling mechanisms fail
>   or are not available.  The IEEE 802.15.4 specification provides a
>   mechanism whereby the details of slotframe length, timeslot timing,
>   and channel hopping pattern are communicated when a node time
>   synchronizes to the network [IEEE802154].  This document describes
>   specific settings for these parameters.
> 
> 
> ---------------------------
> 
> 
> 
> 
> AFTER
> 
> --------------
> 
> 
> 1.  Introduction
> 
>   A 6TiSCH Network provides IPv6 connectivity over a Non-Broadcast
>   Multi-Access (NBMA) mesh that is formed of IEEE 802.15.4
>   Timeslotted Channel Hopping (TSCH) links.
> 
>   The 6TiSCH [I-D.ietf-6tisch-architecture] architecture requires the
>   use of both RPL and the 6LoWPAN adaptation layer framework
>   ([RFC4944], [RFC6282]) as defined over IEEE 802.14.5.
>   6LoWPAN Neighbor Discovery [RFC6775] (ND)  is also required to
>   exchange Compression Contexts,  form IPv6 addresses and register
>   them for the purpose of Duplicate Address Detection, Address
>   Resolution and Neighbor Unreachability detection over one
>   TSCH link.
> 
>   Nodes in a IEEE 802.15.4 TSCH network follow a communication
>   schedule.  A network using the simple mode of operation uses a
>   static schedule.
> 
>   This specification defines an operational parameters and procedures
>   for a minimal mode of operation to build a 6TiSCH  Network, using
>   the Routing Protocol for LLNs (RPL) and a static TSCH Schedule.
>  The 802.15.4 TSCH mode, the 6LoWPAN framework, RPL [RFC6550],
>   and its Objective Function 0 (OF0) [RFC6552], are used unmodified,
>   but  parameters and particular operations of TSCH and RPL are
>   specified  to guarantee interoperability between nodes in a 6TiSCH
>   Network.
> 
>   More advanced work is expected in the future to complement the
>   Minimal Configuration with dynamic operations that can adapt the
>   Schedule to the needs of the traffic in run time.
> 
> 
> 2.  Requirements Language
> 
>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>   document are to be interpreted as described in RFC 2119 [RFC2119].
> 
> Pascal