Hi Zach: I do not mind working on Anders' suggestion at all. In fact I strongly support working on fragments and his proposal is a great start.
I do not mind publishing a draft that just has Anders' proposal in it, as long as we have a design and a clear roadmap for the rest of the fragment work where that proposal would fit - as opposed to have to deprecate it (again) 6 month from now. What I think is that HC is not the right draft for that proposal. HC is about Header Compression. We won't get anywhere if we keep changing the scope or adding features to this draft - or any draft. Pascal > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Zach Shelby > Sent: Thursday, March 04, 2010 7:48 PM > To: [email protected] > Subject: Re: [6lowpan] closing on update to HC draft > > On Mar 4, 2010, at 14:09 , Carsten Bormann wrote: > > >> We could explicitly state, for clarity, that you MUST NOT compress > >> anything outside the first fragment, > > > > That is a nice editorial clarification. > > I'm in favor of adding that. > > Yep, this is the minimum required. > > Now we seem to be split on whether we need more than this. Personally I > can live with the above as this is clearly the fastest way to move this draft to > the IESG, but I don't have problems with the fix suggested by Anders. How > about we try to reach consensus by Friday afternoon, if we can't agree to > agree, then we can always use this clarification. > > It would be sooo nice to have HC already to the IESG so we can concentrate > on getting ND done in Anaheim ;-) > > Zach > > -- > http://www.sensinode.com > http://zachshelby.org - My blog "On the Internet of Things" > http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded > Internet" > Mobile: +358 40 7796297 > > Zach Shelby > Head of Research > Sensinode Ltd. > Kidekuja 2 > 88610 Vuokatti, FINLAND > > This e-mail and all attached material are confidential and may contain legally > privileged information. If you are not the intended recipient, please contact > the sender and delete the e-mail from your system without producing, > distributing or retaining copies thereof. > > > > > _______________________________________________ > 6lowpan mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6lowpan _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
