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

<> Wed, 11 December 2019 17:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0435F120099 for <>; Wed, 11 Dec 2019 09:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5iILHs0l7kyk for <>; Wed, 11 Dec 2019 09:34:06 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5EFEF1200D8 for <>; Wed, 11 Dec 2019 09:34:06 -0800 (PST)
Received: from (unknown [xx.xx.xx.4]) by (ESMTP service) with ESMTP id 47Y3vK0jnDz8tH9 for <>; Wed, 11 Dec 2019 18:34:05 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.70]) by (ESMTP service) with ESMTP id 47Y3vJ74gWzCqkN for <>; Wed, 11 Dec 2019 18:34:04 +0100 (CET)
Received: from OPEXCAUBM21.corporate.adroot.infra.ftgroup ([fe80::d42b:2e80:86c2:5905]) by OPEXCAUBM33.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Wed, 11 Dec 2019 18:34:04 +0100
To: Routing Over Low power and Lossy networks <>
Thread-Topic: [Roll] WG Adoption for turnon-8138 at IETF 106
Thread-Index: AQHVsEkuWcioRg5TeEO1/CRbv2iq4w==
Date: Wed, 11 Dec 2019 17:34:04 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_DA16E5036D4F2dominiquebarthelorangecom_"
MIME-Version: 1.0
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: Wed, 11 Dec 2019 17:34:08 -0000

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.

Best regards,
Inès and Dominique

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,


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.