Re: [6tisch] removing the 'e'

Kris Pister <ksjp@berkeley.edu> Tue, 31 March 2015 18:20 UTC

Return-Path: <ksjp@berkeley.edu>
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 41B951A8ACC for <6tisch@ietfa.amsl.com>; Tue, 31 Mar 2015 11:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 qWwVU9VRrqpF for <6tisch@ietfa.amsl.com>; Tue, 31 Mar 2015 11:20:07 -0700 (PDT)
Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) (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 248791A8AA1 for <6tisch@ietf.org>; Tue, 31 Mar 2015 11:20:06 -0700 (PDT)
Received: by pdbni2 with SMTP id ni2so28500503pdb.1 for <6tisch@ietf.org>; Tue, 31 Mar 2015 11:20:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=avlaVTEp4jv2XkCYWPbCp3br3vUex0tYST6GDopNnKs=; b=DG8AUxMYfYXkVp7nc1EzaaIN5LKcGLalTnbqqaUaOqlJUe9x0Mxtq50voDqJgQQHFK cuajJc+lOsPOgLemlE+SIKXr/JxVmLGWvoxzSr6MXfAf3bcEn9tCsU+1VwjbKCaN4s0K Bi7qLBKYQXfbG775xeVKX5CaVMS5iEKJgiDiqSF1QlSfZ9MwwyrwhHQtNZcREv3euOq2 flZdIunG7FKi3GzB0z3LV1XXS9pgWxtJODA90CBrLNUuvzBgfeoo6Rgrfod/r2MomKqp AGyq/3X7nEXu+bI7U35U+TS9AThec2jYHKuw34IuMAqCj2roDN9UV3rnxMkGdK4kb0lz h9mA==
X-Gm-Message-State: ALoCoQlO5Yo7pTaDot1dRyVG7dA3lvCwls3eUjryDOeIx1HGCWllHQmUen6URJX9JVwzwhTnYGs5
X-Received: by 10.68.57.170 with SMTP id j10mr20596076pbq.89.1427826006531; Tue, 31 Mar 2015 11:20:06 -0700 (PDT)
Received: from [128.32.32.89] (dhcp-32-89.EECS.Berkeley.EDU. [128.32.32.89]) by mx.google.com with ESMTPSA id qn8sm14629871pdb.79.2015.03.31.11.20.02 for <6tisch@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Mar 2015 11:20:04 -0700 (PDT)
Message-ID: <551AE553.7080105@berkeley.edu>
Date: Tue, 31 Mar 2015 11:20:03 -0700
From: Kris Pister <ksjp@berkeley.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: 6tisch@ietf.org
References: <9rQ51q00P0xxhYs01rQ6wU> <5519C697.4040405@cox.net> <E045AECD98228444A58C61C200AE1BD849D91401@xmb-rcd-x01.cisco.com> <551A9161.3010403@innovationslab.net> <E045AECD98228444A58C61C200AE1BD849D91F16@xmb-rcd-x01.cisco.com> <551AD761.9000007@innovationslab.net>
In-Reply-To: <551AD761.9000007@innovationslab.net>
Content-Type: multipart/alternative; boundary="------------030005060508040207090001"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/z5p5QpUNZseN6zVnSCfygqOIJdY>
Subject: Re: [6tisch] removing the 'e'
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: Tue, 31 Mar 2015 18:20:08 -0000

A valid concern.  802.15.4e:2012 seems like the safest reference for the
minimal draft at the very least.

ksjp

On 3/31/2015 10:20 AM, Brian Haberman wrote:
> If we were to assume that:
>
> 1. IEEE publishes 802.15.4-2015
> 2. the 6tisch protocol spec is published*after*  802.15.4-2015
> 3. the published 6tisch protocol references generically 802.15.4
>
> what happens to the IETF spec if the IEEE publishes 802.15.4-2017, that
> spec overhauls the 15.4e behavior, and renders the 6tisch spec useless?