Re: [Roll] unware leaves --- terminology and expectations

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 16 September 2019 17:20 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 37902120147 for <roll@ietfa.amsl.com>; Mon, 16 Sep 2019 10:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 MA44g5yUJJ7I for <roll@ietfa.amsl.com>; Mon, 16 Sep 2019 10:20:38 -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 70DFB120072 for <roll@ietf.org>; Mon, 16 Sep 2019 10:20:38 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 33FDA3897B for <roll@ietf.org>; Mon, 16 Sep 2019 13:18:59 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5E48171B for <roll@ietf.org>; Mon, 16 Sep 2019 13:20:37 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <MN2PR11MB3565B466ACDA4AC77BC720A8D8B30@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB35659CC421169CC79891D1B3D8BB0@MN2PR11MB3565.namprd11.prod.outlook.com> <3940.1567790341@dooku.sandelman.ca> <MN2PR11MB3565016C170EC68801B54ED6D8B70@MN2PR11MB3565.namprd11.prod.outlook.com> <5102.1568314634@dooku.sandelman.ca> <MN2PR11MB3565B466ACDA4AC77BC720A8D8B30@MN2PR11MB3565.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+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-sha256"; protocol="application/pgp-signature"
Date: Mon, 16 Sep 2019 13:20:37 -0400
Message-ID: <25877.1568654437@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/DDdyMSyNrRhngndkvcmJObmIq_c>
Subject: Re: [Roll] unware leaves --- terminology and expectations
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 16 Sep 2019 17:20:41 -0000

Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
    > The RUL draft:
    > - specifies how a RUL uses RFC 8505 without the need to understand
    > anything about RPL
    > - does not care about RALs
    > - defines the operations that can be done by a RPL router to provide
    > connectivity to a RUL.

I think that we are trying to accomplish the same thing, but I think that we
are disagreeing about how to name things.

I think that if a device supports RFC8505, and is willing to ignore RPI, RH3
*and* IPIP headers, then it's an RAL, and it's an RFCxxxx that we want to
define what it means to be an RAL.

I think that an RUL implements RFC6775(only), and RFC2460(only).
We have to do things in useofrplinfo involving removing IPIP headers at the
previous 6LR in order to accomodate them.

If we knew that all leafs were RALs, then we would not need to do much
to support them.

** RALs do not speak RPL control plane, but tolerate RPL data plane **

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [