Re: [Roll] how to solve flow from RPL-aware-leaf to non-RPL-aware-leaf

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 22 February 2016 15:19 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0F021B3566 for <roll@ietfa.amsl.com>; Mon, 22 Feb 2016 07:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham
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 le263fZYUXiI for <roll@ietfa.amsl.com>; Mon, 22 Feb 2016 07:19:55 -0800 (PST)
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 1E9F91B3565 for <roll@ietf.org>; Mon, 22 Feb 2016 07:19:55 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A90032002A for <roll@ietf.org>; Mon, 22 Feb 2016 10:20:52 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 94C1B63750 for <roll@ietf.org>; Mon, 22 Feb 2016 10:19:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <9111.1456113115@obiwan.sandelman.ca>
References: <068.083c7610ff2ac4904b0f3d42985de0e5@trac.tools.ietf.org> <083.ab1b0b92eb7919631cac4e82fc5f8d77@trac.tools.ietf.org> <9111.1456113115@obiwan.sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
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: Mon, 22 Feb 2016 10:19:53 -0500
Message-ID: <31127.1456154393@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/K6DROurWYwTNfdCDNpYbj1FDzCI>
Subject: Re: [Roll] how to solve flow from RPL-aware-leaf to non-RPL-aware-leaf
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 22 Feb 2016 15:19:56 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > In section 5.9 (Flow from RPL-aware-leaf to RPL-aware-leaf), an IPIP is
    > not necessary, since the receiving node is RPL aware, it can remove the
    > RPI.

    > In this case, however, the end-node is not RPI aware, so the 6LR3 needs
    > to remove the RPI.  In order for that to happen, the IPIP header needs
    > to be addressed to 6LR3, but 6LN doesn't have any idea what 6LR3's
    > address.

I wanted to add that the sending node has no way of knowing if it is
in situation 5.9 or situation 5.10, so absent some signaling that there are
no non-RPL aware nodes in the DAG, then sending nodes must assume that the
receiver is not-RPI aware.

An additional possible protocol action might be to signal in the DIOs that
that the RPL network is entirely RPL-aware.  This would/could get negated by
DAOs having a bit so indicate if each target address is RPI aware (i.e. if it
was learned from ND or via DAO).

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