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

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 16 September 2019 18:36 UTC

Return-Path: <pthubert@cisco.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 8C8A312008B for <roll@ietfa.amsl.com>; Mon, 16 Sep 2019 11:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=N/GYvh6x; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=yCJOrEoD
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 X8y7wfo-d_6A for <roll@ietfa.amsl.com>; Mon, 16 Sep 2019 11:36:10 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8375B12003E for <roll@ietf.org>; Mon, 16 Sep 2019 11:36:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2402; q=dns/txt; s=iport; t=1568658970; x=1569868570; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=pgr3eg6sZFTHtm5kEsKLaHJCh21u95sVJG1/iZ9RDuU=; b=N/GYvh6xrzV3Hc3xKYJBwRlC+tCHOtt4Vikfjp3vcwnEPY7PIutUEvPZ Z8QCS0M4ooJx8TO+QIdqCZyMy3iR6ZHIZT84UWgILRItdt2oPGMG4db1Z tNJksIsF1Utc2uflyorHfJgdRY6GoogY488EPzFzk3RRJsTMiy7fH3UgE I=;
IronPort-PHdr: 9a23:OlledRw1U1pNHBvXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZudFU3mJvPwcwQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DqAgDo1H9d/5BdJa1mHQEBBQEHBQGBVgUBCwGBRFADbVYgBAsqCoQXg0cDinJNgWoll3GCUgNUCQEBAQwBARgLCgIBAYFLgnQCF4JYIzcGDgIDCQEBBAEBAQIBBQRthS4MhUoBAQEDAQEBEBERDAEBLAwECwIBCBgCAiYCAgIlCxUQAgQTIoMAAYFqAw4PAQIBC6IiAoE4iGFzgTKCfQEBBYJIgkIYghcJgQwoAYt3GIFAP4ERJwwTgh4uPoJhAQGBYYMLMoImj06FSZdXCoIijBWIaxuZGYQvolwCBAIEBQIOAQEFgWgigVhwFTsqAYJBCYI5gx5UhRSFP3OBKY4qAYEiAQE
X-IronPort-AV: E=Sophos;i="5.64,513,1559520000"; d="scan'208";a="544583811"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Sep 2019 18:36:09 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x8GIa5h9024997 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Mon, 16 Sep 2019 18:36:05 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 16 Sep 2019 13:36:04 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 16 Sep 2019 14:36:03 -0400
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 16 Sep 2019 14:36:03 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iBLSeh5l/rdzBYW+P5lLCzGL3kT2HVtxuxgLqgvoDmYQbecRGpVwVJB40kxCo6jWwS5Iw390sTPv7Pr8+xGmW5o7pi/XDF9KKJVEP13p6/7rDuFW+udmsyFrgsPuiAeRkLG2u69qr0LZOesnUll3417sKcNO6zumn7x88wUdAdq33R0ZzEz2PYqDk7PvT1ctyHBcKi2ld+ZIP4e9EqzMj8+QMBALbJ3NUHX6Nc8JcNWjWTmBlclAC8ZFy6+BOS4fUZtVkk2Cy4B3/aZ+zvYcRhhQbWndMLu6JxQG0EpO1drdYVVsSPyLBccQDpOWQuOU5kjogHVKRRFNkmhEu5xdEg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pgr3eg6sZFTHtm5kEsKLaHJCh21u95sVJG1/iZ9RDuU=; b=LTLlkSLBlyV4QGWLR1CdAe+OSvBazjpm1fy90kORcBE7tOMyjac9T2J7hsytxeL0e5O3IMpx1Uqg/ciMVniq1GBDiJaN43kObD7rNg4eFE/lfvvosqRGyOgeJBrujT2exhB0IUzDekbky0M88W0riT1hKAh9dgmU7maJZKa+XYKmfMHOpgVlXKBaXsmEIGrlk9S+2bUqG6dC4Th6RlgEu8KFsHRYiTbmb6P03BZw+rT/KRa+zusmOyba4cOzuynTIgLcEOtyw+jSsezp5y2ryXd44ZoLTDhxGccc/xZDS3MKEMi0LH7rneitPH0WrkLsFYlYAeemuinqVCZEHumH5Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pgr3eg6sZFTHtm5kEsKLaHJCh21u95sVJG1/iZ9RDuU=; b=yCJOrEoDSJ7+ajTqnb2ZQo2PlChTfEQZmikRjLlRgQZPqwFKFgBRGx+tqS+DOiofI4UH2mzv6L7N05ZkDu0h/7kU9nI+gPGw39rY1k4JFHYLNtzkd86P7x38KxAfgdnkIA3u0lBSeS8zvng35e7lbEmF8C+P9QUGjnq1dBNoiVI=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4271.namprd11.prod.outlook.com (52.135.36.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.17; Mon, 16 Sep 2019 18:36:02 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee%7]) with mapi id 15.20.2263.023; Mon, 16 Sep 2019 18:36:02 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] unware leaves --- terminology and expectations
Thread-Index: AQHVabgO8hNPEXUEJ0WuVmRkiBF6qKcpegHwgAUYq4CAABUS2w==
Date: Mon, 16 Sep 2019 18:36:02 +0000
Message-ID: <786C0A95-6D6E-4847-ACBC-B59E312F29BB@cisco.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>, <25877.1568654437@localhost>
In-Reply-To: <25877.1568654437@localhost>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [91.69.164.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c2e5187c-0a79-4b37-33a0-08d73ad4b9eb
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB4271;
x-ms-traffictypediagnostic: MN2PR11MB4271:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4271288697AF8AA8C232B866D88C0@MN2PR11MB4271.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0162ACCC24
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(396003)(136003)(366004)(39860400002)(376002)(189003)(199004)(51444003)(14454004)(71200400001)(71190400001)(478600001)(81166006)(316002)(76176011)(81156014)(33656002)(25786009)(66946007)(66476007)(64756008)(256004)(8676002)(66446008)(66556008)(99286004)(5660300002)(229853002)(6246003)(14444005)(66066001)(6436002)(6512007)(91956017)(36756003)(76116006)(966005)(11346002)(6306002)(486006)(2616005)(3846002)(6486002)(6916009)(7736002)(86362001)(446003)(2906002)(102836004)(66574012)(6116002)(186003)(305945005)(476003)(26005)(8936002)(53936002)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4271; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: RiRzptbNXSr04mNeDYKL4M0Cr0jMyss4jsGcRHyLF6iV3fR0bG64LXXngNhQLunLedS4ZA+6sR1SRHxr7nWYUOsh4xWULTzP/mWl/OxeoTYvKLp+2FkVxcMIPDitA2ic3FzZ2ficHFMuDg92SN0Vn0LkyjUOaZY6o6jYuqqQSisXPr8zGyDlsLtw7VErhVanj1GtIJWopTQcYmWTZN+Xh8VFKa5N++bChlJG7FaffYA2JUIMGJgLE3jC9x+Tb2AK/fR3hvLimPmp9j1dkTeodxiyZiiscpUJuHB+gurVmhr3MwcfOOFVTIsGdXBwnNh1K6VT5Mopzcw3r++Xh+CHJV6vnEUshiqDDhq2bcGrERTFQWKuj/x0+bztjlU7CHSE85hw102X51xN0vhTiKc8Rg2TD1RnuiIeMZBzh1C03Ec=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c2e5187c-0a79-4b37-33a0-08d73ad4b9eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Sep 2019 18:36:02.1852 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +RAAmJawFRFcR0Cf8YiTiLI9uwAgRXSdZLJ4Xd/dK1/E5DIeCyMdwYB0Q774yBm+rJ08tqRfnEWsf3F1PGST/A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4271
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/UFgAMVZjarG-Yu2WjLZfsGYzCoE>
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 18:36:18 -0000

Yes we are trying to accomplish the same thing.
Note that the RPL data plane the the RxL supports is just following RFC 8200. That does not mean any RPL awareness. So I really do not see why it would have RPL aware in its name...


Regards,

Pascal

> Le 16 sept. 2019 à 19:21, Michael Richardson <mcr+ietf@sandelman.ca> a écrit :
> 
> 
> 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    [
> 
> 
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll