Re: [Roll] useofrplinfo-07

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 03 August 2016 01:44 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 0F3AE12D5DE for <roll@ietfa.amsl.com>; Tue, 2 Aug 2016 18:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level:
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 oN4Cu4VdjgF5 for <roll@ietfa.amsl.com>; Tue, 2 Aug 2016 18:44:08 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC20A12D0B7 for <roll@ietf.org>; Tue, 2 Aug 2016 18:44:07 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id AC4902047C for <roll@ietf.org>; Tue, 2 Aug 2016 21:54:23 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1DCE9638D1 for <roll@ietf.org>; Tue, 2 Aug 2016 21:44:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <9A913377-7EE4-4524-A5E5-14DDFADA87C2@landisgyr.com>
References: <9A913377-7EE4-4524-A5E5-14DDFADA87C2@landisgyr.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 02 Aug 2016 21:44:07 -0400
Message-ID: <28301.1470188647@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/LaJq-_-vZPODI-692BUzukktNY8>
Subject: Re: [Roll] useofrplinfo-07
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: Wed, 03 Aug 2016 01:44:09 -0000

Turner, Randy <Randy.Turner@landisgyr.com> wrote:
    > In section 5, “Storing Mode”, first paragraph, there is a sentence that
    > says “the sender cannot determine whether the destination is
    > RPL-capable and thus would need an IP-in-IP header.”  The last sentence
    > in this paragraph says "the sender can determine if the destination is
    > inside the LLN by looking if the destination address is matched by the
    > DIO’s PIO option.”

    > This implies that “RPL-capable” does not mean “inside the LLN”, is this
    > implication correct ?

I don't think so.
There may well be some editing that has to happen, since 2460bis assumption.
Maybe you can contribute some text to fix this so that it makes sense to you?

One can be inside the LLN, but be RPL-incapable. (a "leaf" or "IPv6 host")

One assumes that nodes outside the LLN are RPL-incapable, and one can
tell this buy looking seeing if the destination address matches the PIO.

{Clearly, with a 6BBR, one can have RPL nodes outside the local LLN
which are RPL-capable, but we can't tell that}

(or more to the point, before -07, routers would drop packets with RPL
artifacts on them. Starting at -07 we assume that RPI is okay, but RH3 is not)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-