Re: [Roll] [6tisch] Call to confirm a rough consensus on RPL info

Randy,
Are you alluding to 6554?
Thomas

On Tue, Oct 21, 2014 at 5:56 PM, Turner, Randy <Randy.Turner@landisgyr.com>
wrote:

>
>  I think I’m +1 on the proposal – was compression of 6553 options the
> ONLY required compression in the “minimal” case ? (apologies…I wasn’t on
> the call) I did a quick search of minimal-02 and didn’t see the word
> compression anywhere.
>
>  Thanks!
> Randy
>
>   From: Thomas Watteyne <watteyne@eecs.berkeley.edu>
> Reply-To: "roll@ietf.org" <roll@ietf.org>
> Date: Tuesday, October 21, 2014 at 8:38 PM
> To: "roll@ietf.org" <roll@ietf.org>
> Cc: "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, "
> 6tisch@ietf.org" <6tisch@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>, "
> roll-chairs@tools.ietf.org" <roll-chairs@tools.ietf.org>, "
> 6tisch-chairs@tools.ietf.org" <6tisch-chairs@tools.ietf.org>
> Subject: Re: [Roll] Call to confirm a rough consensus on RPL info
>
>   +1 on the proposal.
>
> On Tue, Oct 14, 2014 at 11:45 PM, Xavier Vilajosana <
> xvilajosana@eecs.berkeley.edu> wrote:
>
>> All,
>>
>>  I fully support that approach. Hope to contribute and make it happen as
>> soon as possible.
>>
>>  regards,
>> Xavi
>>
>> 2014-10-15 8:32 GMT+02:00 Pascal Thubert (pthubert) <pthubert@cisco.com>:
>>
>>
>>  Dear all:
>>>
>>> During the 6TiSCH bi-weekly virtual interim on Friday, we agreed that
>>> the minimal I-D (draft-ietf-6tisch-minimal) must indicate the compression
>>> method for the RPL Information (see RFC 6553), so as to ensure
>>> interoperation between 6TiSCH devices.
>>>
>>> We discussed our options, basically either a 6lo approach or a Flow
>>> Label approach. The rough consensus at the call was to try and focus on a
>>> 6lo approach and evaluate where that leads us.
>>>
>>> Because this means that the minimal draft will have a normative
>>> reference on a WIP I-D, we recognized that this approach may delay the
>>> publication of the final RFC. Per IETF procedures, the minimal draft will
>>> be stalled in the RFC editor queue in MISREF state until the 6lo work
>>> completes. So the consensus was also to support the 6lo work so as to
>>> expedite it as much as possible.
>>>
>>> The idea would be to republish a standard track draft-ietf-6lo- ASAP,
>>> based on the existing proposals (which are rapidly converging); then, Xavi
>>> would include a normative reference to that work in the minimal I-D before
>>> its publication to IESG, which is scheduled in November (yes, this is
>>> aggressive).
>>>
>>> This is a call to confirm the rough consensus on the ML, open till the
>>> next interim call on October 24th. Please provide us with any relevant
>>> comment (and participate to the 6lo discussions in the meantime!).
>>>
>>> If the result is positive:
>>> - we plan to call for a 6lo WG doc adoption in Hawaii
>>> - we are looking for an aggressive schedule to limit the impact on the
>>> publication of the minimal RFC
>>>
>>> 6TiSCH may host the 6lo discussion so as to:
>>> - benefit from the early morning schedule
>>> - attract more 6TiSCH people to the discussion
>>>
>>> More the published minutes:
>>> - Webex recording:
>>> https://cisco.webex.com/ciscosales/lsr.php?RCID=36a3b7df06694258a3ac65bfc519212f
>>> - Wiki: https://bitbucket.org/6tisch/meetings/wiki/141010_webex
>>> - Slides:
>>> https://bitbucket.org/6tisch/meetings/src/master/141010_webex/slides_141010_webex.ppt
>>>
>>> Cheers,
>>>
>>> Pascal
>>>
>>> _______________________________________________
>>> Roll mailing list
>>> Roll@ietf.org
>>> https://www.ietf.org/mailman/listinfo/roll
>>>
>>
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>>
>>
>
>  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
>
>