Return-Path: X-Original-To: roll@ietfa.amsl.com Delivered-To: roll@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD15A12080E for ; Tue, 17 Dec 2019 05:56:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 VnkvAFDEy_mS for ; Tue, 17 Dec 2019 05:56:06 -0800 (PST) Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D93E6120834 for ; Tue, 17 Dec 2019 05:56:05 -0800 (PST) Received: by mail-ot1-x32f.google.com with SMTP id i4so13865321otr.3 for ; Tue, 17 Dec 2019 05:56:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=BNBOWv5NW7/uR9x0Ncc7WClX7gMfDuzvSozzISZndpQ=; b=BdJX9EG1SGN8yWRmjQVK3/vgP3d/YdGLQy9IDl9LmtuMEdiQFcfa8aNkJFzUWFf9Sh PXb/XMI7SurW95f8ffjHDrIcPLQrvPwXPFq/Zj8TaqJbeEK0GXGtRKfvRBaph2eniwT9 /cUjtz4uP1VK4DC40+vnzgMSUnID/O+HpyooCnkEmSo9RHVhpBPkS4a6yxH7/zvR4KUd 22Jx5mRtRC4tlwSl97zGyLbkBIQ5bRo4kn/j1Fx25aOpEhk9dM6M9zHSoOOjeQ5fJXq2 VWQiM+p7kOTrneBRTHOf7uOq5/iSrwsV8Hxx9NcP+l6UNP6B1fTNRZi+uCIja8nZbkgw Hy7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=BNBOWv5NW7/uR9x0Ncc7WClX7gMfDuzvSozzISZndpQ=; b=pZSVw2YF7bP//9Ib6D6cdIzh8fYuGQXZnWAtRBCACOBjgIPrIA9Io9PHs0kR/uprVK J+17tstPW3dl2kLStait7SYen/9nlACetnHqTuKvshXdKTv4Ffb1RSjhqLKHcvDkujd6 NlCItUBCu6JghM3y49c8neZEz4fDb+uSQCHI4fFb+bKMgXl3FM21U45z0QtLjA4c7WhS s2naUqVfZUsbPw9PKQO+jP1tKGDhn1KiD/PFLsDTLapNuZ/dItk7Is1PS82Cpbm0CThE 6qYoGXKOfPOSWUhZ2GqOxSxkSZUUA4PPd0hdDDLEYCwa3idqwHD5NxtNYMao7wwhM7P3 qdWA== X-Gm-Message-State: APjAAAVA9rx4g6Ix/+p+wvgCfl/BwHkF1Hw8tCe4J+YCuImv3HHWvQaU NSYSEhv/L3AqWMk+rJTE+xsN570eCnifgrU7OPXN7w== X-Google-Smtp-Source: APXvYqwjxAgWpg7lEkX3ly/DzHN8r1YdaFmGuUYQtdNrBH7wlPbQ3rRnb+yRy7Es2xT4lE8T4EMOErdzWbfPfX+oQ9w= X-Received: by 2002:a05:6830:1499:: with SMTP id s25mr36304354otq.223.1576590964244; Tue, 17 Dec 2019 05:56:04 -0800 (PST) MIME-Version: 1.0 References: <8458_1576085645_5DF1288D_8458_93_1_DA16E503.6D4F2%dominique.barthel@orange.com> In-Reply-To: From: Abdussalam Baryun Date: Tue, 17 Dec 2019 15:55:49 +0200 Message-ID: To: Routing Over Low power and Lossy networks Content-Type: multipart/alternative; boundary="00000000000061463b0599e6b039" Archived-At: Subject: Re: [Roll] WG Adoption for turnon-8138 at IETF 106 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2019 13:56:10 -0000 --00000000000061463b0599e6b039 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Dec 17, 2019 at 3:15 PM Pascal Thubert (pthubert) < pthubert@cisco.com> wrote: > This was debated at length during the IETF meeting, which is available on > youtube. > I did not attend but the WG mailing list is important to discuss these issues > * I also posted a discussion on this ML. * > We need to work together to make progress, I don't mind discussing but I hope authors help in progress. once I asked an author in another organisation and I asked him why you used this type of technology and his answer was why no. So it is difficult to discuss while requests are replied by requests, furthermore, no need for two/three proposals only if we work as individuals. > * We ended up with a time bomb on the bits, they=E2=80=99ll be defines on= ly for > RPL v1 (MOP<7).* > This should be discussed on the WG list more, and not quickly (why the hurry we still have time to be perfect, doing it quickly mostly means mistakes) I did not see this, but will follow up. AB > > > > > > > > > > > > > > *Pascal From: Roll > On Behalf Of Abdussalam Baryun Sent: mardi 17 d=C3=A9cembre 2019 11:35 To: Rou= ting Over Low power and Lossy networks > Subject: Re: [Roll] WG Adoption for turnon-8138 at IETF 106 On Wed, Dec 11, 2019 at 7:34 PM > wrote: Dear all, The call for WG adoption of draft-thubert-roll-turnon-rfc8138 has been open since Nov 19th. Based on the reaction at the WG meeting in Singapore (IETF106) and on the mailing list after that, the WG chairs declare consensus on the matter. Therefore, Pascal, can you please republish the draft as a WG document? For the record: - There were positive opinions, including from people who actively contribute to the writing of drafts at ROLL and related WGs, and who contribute to developing or evaluating their implementations.- There was one opposition, arguing that RFC8138 turn on should be done another way. - There is no substantiated technical proposal on the table other than draft-thubert-roll-turnon-rfc8138. Adding to the WG record, that that draft is using a reserved bits for configuring the RPL DAG, and it is using it for configuring the data compression. The argument on the WG list with authors was WHY that use of reserved (important question), IMO they did not answer that but asked for another proposal. Usually IMHO if we get a proposal we discuss that one proposal and find ways to modify and answer question of why it was designed that way, because we are working as an ietf group not as individuals. AB De : Roll > on behalf of Ines Robles > R=C3=A9pondre =C3=A0 = : "roll@ietf.org " > Date : Tuesday 19 November 2019 02:24 =C3=80 : "roll@ietf.org " > Objet : [Roll] WG Adoption for turnon-8138 at IETF 106 Dear all, Today at ROLL Meeting we will discuss the adoption of turnon-8138. It would be nice if you could state your opinion on-site or remotely. The adoption call will be confirmed by ML also, Thanks, Ines, Dominique and Peter. ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ 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 > * --00000000000061463b0599e6b039 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Dec 17, 2019 at 3:15 PM Pasca= l Thubert (pthubert) <pthubert@cis= co.com> wrote:

This was debated at length duri= ng the IETF meeting, which is available on youtube.

I did not attend but the WG mailin= g list is important to discuss these issues
=C2=A0

=

I also posted a discussion on t= his ML.


We need to= =C2=A0work together to make progress, I don't mind discussing but I hop= e authors help in progress. once I asked an author in=C2=A0another organisa= tion and I asked him why you used this=C2=A0type of technology and his answ= er was why no. So it is difficult to=C2=A0discuss while requests are replie= d by requests, furthermore, no need for two/three proposals=C2=A0only if we= work as individuals.=C2=A0

We ended up with a time bomb on= the bits, they=E2=80=99ll be defines only for RPL v1 (MOP<7).


This should b= e discussed on the WG=C2=A0list more, and not quickly (why the hurry we sti= ll have time to be perfect, doing it quickly mostly means mistakes) I did n= ot see this, but will follow up. =C2=A0


=
AB












Pascal

=C2=A0

=

From: Roll <roll-bounces@ietf.org> On Behalf Of Abdussalam Baryun
Sent: mardi 17 d=C3=A9cembre 2019 11:35
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] WG Adoption for turnon-8138 at IETF 106

=C2=A0

=

=C2=A0

=

=C2=A0

=

On Wed, Dec 11, 2019 at 7:34 PM= <dominique.barthel@orange.com> wrote:

Dear all,

=C2=A0

The call for WG adoption of draft-thubert-roll-turnon-rfc8138 has b= een open since Nov 19th.

Based on the reaction at the WG meeting in Singapore (IETF106) and = on the mailing list after that, the WG chairs declare consensus on the matt= er.

Therefore, Pascal, can you please republish the draft as a WG docum= ent?

=C2=A0

For the= record:

  • There were positive opinion= s, including from people who actively contribute to the writing of drafts a= t ROLL and related WGs, and who contribute to developing or evaluating thei= r implementations.
  • There was one opposition, a= rguing that RFC8138 turn on should be done another way.=C2=A0=
<= u>
  • There is no substantiated t= echnical proposal on the table other than draft-thubert-roll-turnon-rfc8138= .

Adding to the WG record, that t= hat draft is using a reserved bits for configuring the RPL DAG, and it is u= sing it for configuring the data compression. The argument on the WG list w= ith authors was WHY that use of reserved (important question), IMO they did not answer that but asked for another p= roposal. Usually=C2=A0IMHO if we get a proposal we discuss that one proposa= l and find ways to modify and answer question of why it was designed that w= ay, because we are working as an ietf=C2=A0group not as individuals.=C2=A0

=C2=A0

=

AB

<= u>

=C2=A0

=

=C2=A0

=C2=A0

De=C2= =A0: Roll <= roll-bounces@ietf.org> on behalf of Ines Robles <mariainesrobles=3D40googlemail.com@dmarc.ietf.org>
R=C3=A9pondre =C3=A0=C2=A0: "ro= ll@ietf.org&qu= ot; <roll@ietf.org>
Date=C2=A0: Tuesday 19 November 2019 02:24
=C3=80=C2=A0: "roll@ietf.org" <roll@ietf.org>
Objet=C2=A0: [Roll] WG Adoption for turnon-8138 at IETF 106

=C2=A0

Dear all,

=C2=A0

Today at ROLL Meeting we will discuss the adoption of turnon-8138. = It would be nice if you could state your opinion on-site or remotely. The a= doption call will be confirmed by ML also,

=C2=A0

Thanks,

=C2=A0

Ines, D= ominique and Peter.=C2=A0

__________________________________________=
___________________________________________________________________________=
____
=C2=A0
Ce message et ses pieces jointes peuvent c=
ontenir des informations confidentielles ou privilegiees et ne doivent donc=

pas etre diffuses, exploites ou copies san=
s autorisation. Si vous avez recu ce message par erreur, veuillez le signal=
er
a l'expediteur et le detruire ainsi qu=
e les pieces jointes. Les messages electroniques etant susceptibles d'a=
lteration,
Orange decline toute responsabilite si ce =
message a ete altere, deforme ou falsifie. Merci.
=C2=A0=

This message and its attach=
ments may contain confidential or privileged information that may be protec=
ted by law;
they should not be distribu=
ted, used or copied without authorisation.
If you have received this e=
mail in error, please notify the sender and delete this message and its att=
achments.
As emails may be altered, O=
range is not liable for messages that have been modified, changed or falsif=
ied.
Thank you.
<= u>

_______________________________= ________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll=

=
<= div class=3D"gmail-m_-1858176079219931572WordSection1">
<= /div>
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll
--00000000000061463b0599e6b039--