Re: [Roll] MOPex CAPs splitup

<> Fri, 22 November 2019 04:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0ACF41200B2 for <>; Thu, 21 Nov 2019 20:33:20 -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 TktdsYCZsf3n for <>; Thu, 21 Nov 2019 20:33:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DF01212003F for <>; Thu, 21 Nov 2019 20:33:17 -0800 (PST)
Received: from (unknown [xx.xx.xx.69]) by (ESMTP service) with ESMTP id 47K3T74dYBzyv9; Fri, 22 Nov 2019 05:33:15 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.26]) by (ESMTP service) with ESMTP id 47K3T752wSzyQp; Fri, 22 Nov 2019 05:33:15 +0100 (CET)
Received: from OPEXCAUBM21.corporate.adroot.infra.ftgroup ([fe80::d42b:2e80:86c2:5905]) by OPEXCAUBM31.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Fri, 22 Nov 2019 05:33:15 +0100
To: Routing Over Low power and Lossy networks <>, Rahul Jadhav <>
Thread-Topic: [Roll] MOPex CAPs splitup
Thread-Index: AQHVoHg4aOQouMoj+kCr0yYNY9bhuaeXEE+A
Date: Fri, 22 Nov 2019 04:33:14 +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_D9FD7A496C485dominiquebarthelorangecom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Roll] MOPex CAPs splitup
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, 22 Nov 2019 04:33:20 -0000

Hello Rahul, all,

In Section 3.1, I read
"The MOPex option MUST be used only if the base DIO MOP is 7."

And the title of Section 3.2 is "Use of MOPex for MOP less than equal to 6", which I found to be a contradiction to the above statement.
The body text further says "The current set of MOPs (values 0-6) could also be used in MOPex."

Now that you are asking, I realize that I mistook your text body to mean "we could even use the mechanism of MOPex with base MOP values of 0-6", and this misunderstanding was induced by the title, which is plain misleading.

In order to avoid a misunderstand similar to mine by future readers, can I suggest you rewrite 3.2 the following way
Title "Use of values 0-6 in the MOPex option"
Text body "The MOPex option could also be allowed to re-use the values 0-6, which have been used for MOP so far. …"

Best regards


De : Roll <<>> on behalf of Rahul Jadhav <<>>
Répondre à : "<>" <<>>
Date : Thursday 21 November 2019 22:30
À : "<>" <<>>
Objet : Re: [Roll] MOPex CAPs splitup

Hi Dominique,

However, we should agree quickly what to do about 3.2, which currently
contradicts 3.1 and also ties MOPex and CAPabilities back together.

[RJ] Which is the contradictory stmt in 3.1 you are referring to?



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.