Re: [6tisch] removing the 'e'

"Turner, Randy" <Randy.Turner@landisgyr.com> Mon, 30 March 2015 18:38 UTC

Return-Path: <Randy.Turner@landisgyr.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 DA3A51AC3E4 for <6tisch@ietfa.amsl.com>; Mon, 30 Mar 2015 11:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 GSrkffJb0p6a for <6tisch@ietfa.amsl.com>; Mon, 30 Mar 2015 11:37:58 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0700.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::700]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 223601A92F7 for <6tisch@ietf.org>; Mon, 30 Mar 2015 11:37:58 -0700 (PDT)
Received: from DB4PR01MB0431.eurprd01.prod.exchangelabs.com (10.242.221.22) by DB4PR01MB0431.eurprd01.prod.exchangelabs.com (10.242.221.22) with Microsoft SMTP Server (TLS) id 15.1.118.21; Mon, 30 Mar 2015 18:26:35 +0000
Received: from DB4PR01MB0431.eurprd01.prod.exchangelabs.com ([10.242.221.22]) by DB4PR01MB0431.eurprd01.prod.exchangelabs.com ([10.242.221.22]) with mapi id 15.01.0118.022; Mon, 30 Mar 2015 18:26:35 +0000
From: "Turner, Randy" <Randy.Turner@landisgyr.com>
To: Kris Pister <ksjp@berkeley.edu>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: [6tisch] removing the 'e'
Thread-Index: AdBq/V4RtXFpTNrNQeKFEmkDS/GJkAAD0Q0AAAKGoqA=
Date: Mon, 30 Mar 2015 18:26:35 +0000
Message-ID: <DB4PR01MB04310E3861BFAB98563AA7DB80F50@DB4PR01MB0431.eurprd01.prod.exchangelabs.com>
References: <E045AECD98228444A58C61C200AE1BD849D905A6@xmb-rcd-x01.cisco.com> <551983E0.3030008@berkeley.edu>
In-Reply-To: <551983E0.3030008@berkeley.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [148.80.255.144]
authentication-results: berkeley.edu; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB4PR01MB0431;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(24454002)(479174004)(243025005)(377454003)(51704005)(13464003)(66066001)(2950100001)(50986999)(107886001)(33656002)(19580405001)(76176999)(86362001)(5890100001)(2501003)(15975445007)(19580395003)(77156002)(102836002)(62966003)(77096005)(2656002)(2171001)(74316001)(54356999)(92566002)(46102003)(87936001)(40100003)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR01MB0431; H:DB4PR01MB0431.eurprd01.prod.exchangelabs.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-microsoft-antispam-prvs: <DB4PR01MB0431905D8BBE455415790C9880F50@DB4PR01MB0431.eurprd01.prod.exchangelabs.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002010)(5005006); SRVR:DB4PR01MB0431; BCL:0; PCL:0; RULEID:; SRVR:DB4PR01MB0431;
x-forefront-prvs: 05315CBE52
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: landisgyr.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2015 18:26:35.6196 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ee2cd48b-958f-4be4-9852-b8f104c001b9
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR01MB0431
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/7kQqggJsZFMDZAJi4QBQIcKZraM>
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: Mon, 30 Mar 2015 18:38:01 -0000

If Kris is correct, and compliance with the 15.4 rollup would cause code changes to existing 4e code, then I don't think it's a good idea to remove the 'e' -- if existing 4e code would be interoperable with 15.4 rollup, then I guess referencing the rollup (for posterity) would be a good idea.

Randy

-----Original Message-----
From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Kris Pister
Sent: Monday, March 30, 2015 1:12 PM
To: 6tisch@ietf.org
Subject: Re: [6tisch] removing the 'e'

I like the IETF approach better, but I don't think that we have much choice.
If the roll-up from 15.4e to  15.4-2015 were just corrections of real problems it would be a no-brainer.
Unfortunately, there are numerous cases where IEEE members with "good ideas"
have pushed for changes that have little or no practical value, but do require a re-write of existing code, and mandate non-interoperability between the existing 15.4e and the forthcoming 15.4-2015.

ksjp

On 3/30/2015 8:23 AM, Pascal Thubert (pthubert) wrote:
> Dear all:
>
> Pat presented at the WG on Thursday his recommendation to remove the 'e' after IEEE802.15.4 in our current charter and WG Documents (slides at the end of http://www.ietf.org/proceedings/92/slides/slides-92-6tisch-2.pdf ).
>
> The net effect would be that when a new version of the standard is published - 2015 should be available soon -, our normative references will implicitly pick that latest version and inherit the fixes that were made since then, as well as the additional PHYs on which 802.15.4 TSCH can operate.
>
> Pat indicated that this procedure is the expected one when referring to IEEE documents. Subir noted that at the IETF we normally have reference on particular versions, and a change in an RFC is a new RFC thus a new reference, and the IEEE form of reference may create an issue with IETF practice. The chairs will need to validate this before proceeding.
>
> On the question whether the change is desirable, Pat made the case that 15.4e is just an amendment, which is an incomplete reference, and that it yields some incorrectness that is now fixed in the upcoming 2015 version of 802.15.4.
> All in all the group agreed that the change is desirable. We are now coming to the list to confirm the consensus. If you have an issue with removing the 'e' please speak up now.
>
> Cheers,
>
> Pascal and Thomas
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch

_______________________________________________
6tisch mailing list
6tisch@ietf.org
https://www.ietf.org/mailman/listinfo/6tisch

P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.

This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.