Re: [Roll] Latest version of useofrplinfo-36 Fri, 06 March 2020 09:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E613F3A0B28 for <>; Fri, 6 Mar 2020 01:36:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 fbyFFbU6MRV1 for <>; Fri, 6 Mar 2020 01:36:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 172DD3A0AF0 for <>; Fri, 6 Mar 2020 01:36:28 -0800 (PST)
Received: from (unknown [xx.xx.xx.8]) by (ESMTP service) with ESMTP id 48YjDT6LRLzFpxH; Fri, 6 Mar 2020 10:36:25 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1583487385; bh=DdypTP2Fby04quvZVnVnDN3YUAk5pJht3Yt/rQ0wPi8=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=NukKB5wYjrd4H9Qotk1ighfqVf7q0tLooYYpnZqgK1JdES6znv4SKFbM5g2qEpjAE aD4H4ZjL93+m1iM4pBXRAnbUU0qKxPYiGluevDXPnWm2bDJY34ByhODXodcQ4T2z8N dAwx/FBiTN5sZR02B3n5fn6N32kpoSBZQWlJFQnMsuKRrkjlDS4MjyP18qO0kR5Pw5 5M2Y2IdGbEOYF4jjdhdJp1oDc3BteMpqDY9/EDSlL9oRJUzLhIV6Vod6fpEgxxxg32 h1nbJ+xTp0gKXdxuW1RaIKrTfz9uzAYTeIn3UELczSPgJfzxgJm9jBy3slSwDwkwSu VhaLknEEw+40g==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.101]) by (ESMTP service) with ESMTP id 48YjDT563Lz3wbV; Fri, 6 Mar 2020 10:36:25 +0100 (CET)
Received: from OPEXCAUBM21.corporate.adroot.infra.ftgroup ([fe80::d42b:2e80:86c2:5905]) by OPEXCAUBM6F.corporate.adroot.infra.ftgroup ([fe80::c489:b768:686a:545b%23]) with mapi id 14.03.0487.000; Fri, 6 Mar 2020 10:36:25 +0100
To: roll <>
CC: Michael Richardson <>, "Pascal Thubert (pthubert)" <>, Ines Robles <>
Thread-Topic: Latest version of useofrplinfo-36
Thread-Index: AQHV85q0oxY4piYCcEqwa8WPTdod3Q==
Date: Fri, 06 Mar 2020 09:36:25 +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_DA87D4717163Adominiquebarthelorangecom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Roll] Latest version of useofrplinfo-36
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: Fri, 06 Mar 2020 09:36:32 -0000

Hello Working Group,

draft-ietf-roll-useofrplinfo has recently been updated to revision –36.
As a reminder, revision –31 was approved by the IESG in July, the RFC Editor worked on it, then the document was pulled back from the RFC Editor.
We believe that the Working Group has been well informed of the changes made to the document since then, and these changes have been discussed on the mailing list and at IETF106.
We are therefore not going to issue another Last Call within the Working Group.

However, if you have an interest in this draft and have not paid attention to the changes over the last months, here is your last chance: you can review the changes between –31 and –36 and let us know of significant concerns by Monday noon CET, in time for draft publication cutoff before IET107.

Thanks and best regards,


De : "<>" <<>>
Date : Tuesday 3 March 2020 15:55
À : "<>" <<>>
Cc : Dominique Barthel <<>>, "Michael ca>" <<>>, Pascal Thubert <<>>
Objet : Latest version of useofrplinfo-36

Dear all,

useofrplinfo draft was updated (version 36) from the last call considering:

- Advertising External Routes with Non- Storing Mode Signaling (section 4.1)

Then, for SM cases where the communication flow starts at RUL: it goes encapsulated to the root. (Figure 7 updated and the cases updated: RUL to root/RUL to Int/ RUL to RAL/ RUL to RUL)

For Non-SM cases (Figure 14):

1- From RAL to Int: It may have encapsulation to the root.
2- From RAL to RAL and RAL To RUL : It may have encapsulation to the root and must have encapsulation to the destination
3- From RUL to RAL and RUL to RUL: It must hae encapsulation to the root and to the destination (RAL) or to the 6LR parent of RUL.

Thus, new tables were added considering the "may" cases. e.g Section 8.3.1. We added new terminology as well.

Comments welcome and thank you,

The authors.


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.