IETF Logo Mail Archive

Re: [Roll] RPLinfo review

Ines Robles <mariainesrobles@googlemail.com> Tue, 24 May 2016 10:16 UTC

Return-Path: <mariainesrobles@googlemail.com>
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 26C2A12D0C3 for <roll@ietfa.amsl.com>; Tue, 24 May 2016 03:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.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 9qpFOPj1oH9b for <roll@ietfa.amsl.com>; Tue, 24 May 2016 03:16:08 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 D854D12B05C for <roll@ietf.org>; Tue, 24 May 2016 03:16:07 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id y2so15092101vka.3 for <roll@ietf.org>; Tue, 24 May 2016 03:16:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ubkL883bvgd5ZBone2sbVHd4HNuCy7UBCgDnyAK1PSc=; b=zVXHbQJlrPmEmuC5unW7Pl5FbRlbw1583dbnmj5XUPwJcBXyQCoiSlu6Gqs798jvwE VZ0GkpxWCPkv+j83axndZ59U8zG08iplRx4J/6xuSmo4itR/Cw7x9GKfaLQzoFwLQJYP gVlLyql33gVs0PyHjQR+bgwBHOMHMjI9/ND33BPKORYi6VAi37QBRE/La5MGD5AwWVZB 7LdjS+zHbqUDATgaD5cjyHHSQmjP0wxrpDmd+JAkf8mF14N83NN0OVshlpBg4tkKHRzS II04EueOMfPoZ9UKa4k+cV8hG4td2Mqw5b7R7uYHpoWHYZhF+u5zvdqXH6CNj23jZKyr xPAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ubkL883bvgd5ZBone2sbVHd4HNuCy7UBCgDnyAK1PSc=; b=kdO3s41ME/fg6DX8b4ai4M3KAfzF78H4U99dW55JXcERMmSSfk8f+31bY1XDWpYyqo 1hgBjzM0rgVJjPNHZCyia5OL7fSuUr31o9z9Z2sCtOOy9pgAuZQ2Ayh3jMjdcHjkp/HR jy6QRgonb5cFP4cZynh0ff1CZpJGlrGu2mIqN7j1JIyP4QdOq8nynhQIOnd/fn0IfT+w bi6IkdlR5rvq+DOjm5SsXZaGa1tHmbEve+2HO3MpF+LL40KG/AoeEvGOf0+gEUdMS0jN YL+cTxbn0AI8kjkc5egovVHdg7cAoW8j330RyyHAg83BFHMizbR3X/6J/DJlz6jf1vLu enpQ==
X-Gm-Message-State: ALyK8tJLPp1TwNASOgtdOJCs+p0GPjBxrX852MUk/7lWC2p2ZVaq5JlOoKc2os1lj6Yv49ZWb2NLXkAmY4XyOg==
MIME-Version: 1.0
X-Received: by 10.31.158.1 with SMTP id h1mr2030671vke.5.1464084966585; Tue, 24 May 2016 03:16:06 -0700 (PDT)
Received: by 10.159.37.98 with HTTP; Tue, 24 May 2016 03:16:06 -0700 (PDT)
In-Reply-To: <bc96b8913fff031fc1f41eedfdb6bee3@xs4all.nl>
References: <09c3e3fc17b5de9b7366d226c034da28@xs4all.nl> <CAP+sJUePiV+_Nd+f-H-x_zNoTgkS0Cqe1rq7qD7ie_H3MyOorw@mail.gmail.com> <bc96b8913fff031fc1f41eedfdb6bee3@xs4all.nl>
Date: Tue, 24 May 2016 13:16:06 +0300
Message-ID: <CAP+sJUe=t7MwkVAUd33+tz_M7J6sqmHKahCQsiBm_e86eHb6cA@mail.gmail.com>
From: Ines Robles <mariainesrobles@googlemail.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>
Content-Type: multipart/alternative; boundary="001a11425eec5abfa8053393d8a9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/DmDNQvs7C8hl6kERe1vakUUou8c>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] RPLinfo review
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 10:16:09 -0000

Hi,

Thanks for the clarification.

We are just considering here one RPLInstance.

Working with different RPLInstances, involves deeply analysis, which we
could do in the future. But, actually I dont know if it is possible/useful
to send a message from one RPL Instance to another one , since for
example a RPL
node may belong to multiple RPL Instances, and it may act as a router in
some and as a leaf in others[1], for this reason it does not make sense to
me sending packet from one RPLInstance to other RPLInstance. Besides the
control messages has one field for RPLInstanceID, it does not have
RPLInstanceID origen or RPLInstanceID dst.

What do you think?

Thank you,

Ines

[1] RFC6550. Section 5. RFC 6550 describes only how a single instance
behaves

2016-05-24 12:17 GMT+03:00 peter van der Stok <stokcons@xs4all.nl>:

>
>
>> I also did not see a mapping of flow from one RPL instance to
>>> another instance.
>>>
>>
>> I do not understand this. Could you please clarify?
>>
>>
> A node belonging to one RPL instance sends a message to a node belonging
> to another RPL instance.
> This seems possible in Figure 3, with 3 RPL instances?
>
> If possible, it means an additional use case.
>
> Peter
>

v2.23.0 | Report a Bug | By Email