Re: [6tisch] removing the 'e'

I will try to add me opinion here.

I am strongly in favor, that at this point to change the reference to 
IEEE 802.15.4-2015 for IEEE 802.15.4-2011 plus 802.15.4e.

I am ASSuMEing that you are referencing 802.15.4-2011 and not -2006?  
What is incomplete about 15.4e, is that you need to reference 15.4-2011.

But when we were plowing through the security portion of 15.4-2011 to 
work out what 802.15.9 would be 'controlling', we learned many vendors 
were still implementing the -2006 security, not the -2011, which was 
considered more broken that the -2006.  Most noteably the 15.4g vendors 
were making these statements.

So what went on at the 802.15.4 maintenance sessions?  'Oh, that is 
REALLY broken.  How did we miss that?'  A lot of attention was given to 
not breaking deployed code, but in a few places, broken things needed to 
be fixed.  Tero (and I to some extent) really worked over the security 
section.  Rekeying a PAN really did not work with the way the frame 
counter was described, for example.  We had to move some fields around 
in the security tables.

Review?  Well get on the sponsor ballot, if you still can.  Changes for 
the sake of changing or for a particular vendor's 'needs'?  I did not 
see that happening.  But I am NOT the expert on most of the features, 
and someone could easily slip that by me.

Restructuring, a little bit, the Information Elements to allow for SDO 
requests; most vocal being ETSI.

I strongly recommend moving forward with referencing 802.15.4-2015.

On 03/30/2015 11: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