Re: [6tisch] removing the 'e'

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 31 March 2015 06:49 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 056E91B2AED for <6tisch@ietfa.amsl.com>; Mon, 30 Mar 2015 23:49:23 -0700 (PDT)
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 W960xD4fp6-m for <6tisch@ietfa.amsl.com>; Mon, 30 Mar 2015 23:49:21 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C8951B2AEB for <6tisch@ietf.org>; Mon, 30 Mar 2015 23:49:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5040; q=dns/txt; s=iport; t=1427784561; x=1428994161; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=MVaeYHf45OTKf5YSnfbqcZPhh8+jYJb6fBKQbWnTtZs=; b=ZLNzKn92Bj2qmO0COPMLsWCdiE7+Z5SnOMCaW7hiONGsFhsjrT/pUUvG nYLQJr+YF66aeyhEJaHGLD1tFKUp+7SqFslEqcnCOYLZLLHor5qZvxs9q N+cQbF1pS/MARIVLXekNzTpF/IlKDFGfF0/2B/Zpbqr/9qJj3OxBw+YYv M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C+CQC7QhpV/5BdJa1UCA6CeFJcBMMkgjEKhSpJAoE5TAEBAQEBAX2EFAEBAQICAQEBNzQXBAIBCBEEAQEBChQJBycLFAkIAQEEARIIAYgmDcwgAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sphBYMBQEfLAwGgxGBFgWQXIl1gRuDMo9nIoMxPW8BgQMHFwYcfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,499,1422921600"; d="scan'208";a="408323008"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-2.cisco.com with ESMTP; 31 Mar 2015 06:49:20 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t2V6nKhb017842 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Mar 2015 06:49:20 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.104]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Tue, 31 Mar 2015 01:49:20 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Turner, Randy" <Randy.Turner@landisgyr.com>, Kris Pister <ksjp@berkeley.edu>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: [6tisch] removing the 'e'
Thread-Index: AdBq/V4RtXFpTNrNQeKFEmkDS/GJkAAOS0IAAAKa1IAADwDncA==
Date: Tue, 31 Mar 2015 06:49:19 +0000
Deferred-Delivery: Tue, 31 Mar 2015 06:49:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD849D913F0@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD849D905A6@xmb-rcd-x01.cisco.com> <551983E0.3030008@berkeley.edu> <DB4PR01MB04310E3861BFAB98563AA7DB80F50@DB4PR01MB0431.eurprd01.prod.exchangelabs.com>
In-Reply-To: <DB4PR01MB04310E3861BFAB98563AA7DB80F50@DB4PR01MB0431.eurprd01.prod.exchangelabs.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.68.224]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/TJq8-i0KEsYOJBQ-egHlEFCmiOE>
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 06:49:23 -0000

Hello Randy:

I do agree that Kris is right, but probably not on the same point as you do here.  6TiSCH does not have much choice. We do not own 802.15.4, we reference it.
And the question of backward compatibility does not really affect 6TiSCH since 6TiSCH never shipped before, and there certainly will be quite a development effort to build a 6TiSCH product anyway.

6TiSCH cannot be locked referencing an interim specification, so there is no question in my mind that 6TiSCH will ultimately refer to the new standard when it ships. What we're after is the minimum hassle on that path.

The question that was asked to the group is about the current charter, and the current WG docs that we are shipping to IESG, in particular minimal.
If we keep referencing 15.4e, we will be creating a backward compatibility issue with ourselves, and that's probably not a good idea. I'm looking for a consensus to avoid that.

Another aspect of that question is the plug test in Prague. Considering the time frame, it will be difficult for the implementations to migrate to 802.15.4-2015, and there may be interop problems at the MAC layer.
What should we be shooting for?

Pascal

> -----Original Message-----
> From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Turner, Randy
> Sent: lundi 30 mars 2015 20:27
> To: Kris Pister; 6tisch@ietf.org
> Subject: Re: [6tisch] removing the 'e'
> 
> 
> 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.
> 
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch