Re: [Roll] WG Adoption for turnon-8138 at IETF 106

Abdussalam Baryun <> Tue, 17 December 2019 10:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7887A12081E for <>; Tue, 17 Dec 2019 02:35:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id i49ypEJMAj8V for <>; Tue, 17 Dec 2019 02:35:13 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6D1B112012C for <>; Tue, 17 Dec 2019 02:35:13 -0800 (PST)
Received: by with SMTP id p67so279042oib.13 for <>; Tue, 17 Dec 2019 02:35:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=qARvRf7H5rl7Q7cCIzIPj5fxcj3N4EJZuHwQurwcAX8=; b=GX//JqxLpayg/ctivxn611JjLS3FiIP/GgGSjqQwE0+8vdbsncLclHkn3o2yvQSjSK ZyWPZ/JoOjNaqDwMLMcpy0BVh86YyeZpXWAmQ8SDJn/ugb3pmxAB7wY/rsWK4d7aBYn6 mIUoE2l59eqNJSJbh1BdT05qgJG/fZn64fOTN8Jg2gjFD4W3u4Carpp8k3RykNO7RBn/ qC8oNZkTOdDg6heV+OQ/TwR7zf/xiBYih6KsHNMENtwmdIMeBtIMvdajN1hpDiEk/4VA VDDWNGoIfh5LUC0fCUruoMlGANxDLI7BJTY3qHWfqAES/klGr52byk4qdEShGAAvq4qT /HDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=qARvRf7H5rl7Q7cCIzIPj5fxcj3N4EJZuHwQurwcAX8=; b=n8skm6OnZSbvx5gnfg6fJxx3Gu6BCaoo+7hBfQ4Zkyp1/aMWra3H2hDDSQkEoylw8W GqczXGs1b9rebSofvqa/FuN36m8u3dZbwLCaRBQpmjvUb5/dYEm8Im6StpuPmRk21lE/ RUCqDkq50VESOIrYLC+GmIeHv84lV9oOHF/xSU0+qQwgUV4APh3VjKVcjauZtUsrMXuF inwk0xalnSKEGU98JtXaz7VKaF7XkCD1GrwZ+xMRmQMTd7h49yHgjgmLAQAKxUF2JGYE WrhhXu7NLVtWzIQU+/SFqivOcBsCBMRnG3zOAQSBhY820HdJTMYV8JHgE+vGA7W49R+G bYdw==
X-Gm-Message-State: APjAAAW8FD2NcJZc9OBaykqUf7feVDGgcNUjIgdARwfHUDBWst3ZRMoV GjtoaKC+eLGOanXQwcvqHPeeUXmzNMBkRotHxH4aIg==
X-Google-Smtp-Source: APXvYqxQvvNIYpYiAoPwurW+i5L9VHFTZbjuWjNM2bC4/xkMko6botFGchlS2ld+9ocfoJD24G6e+8NSY9uzIqfE6Cw=
X-Received: by 2002:a05:6808:6c5:: with SMTP id m5mr1091508oih.143.1576578912218; Tue, 17 Dec 2019 02:35:12 -0800 (PST)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Tue, 17 Dec 2019 12:34:58 +0200
Message-ID: <>
To: Routing Over Low power and Lossy networks <>
Content-Type: multipart/alternative; boundary="00000000000005f2dc0599e3e250"
Archived-At: <>
Subject: Re: [Roll] WG Adoption for turnon-8138 at IETF 106
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 10:35:16 -0000

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.


> De : Roll <> on behalf of Ines Robles <
> Répondre à : "" <>
> Date : Tuesday 19 November 2019 02:24
> À : "" <>
> 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