Re: [Roll] naming and other goals for RPL Unaware Leaves

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 22 October 2019 13:52 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 34318120086 for <roll@ietfa.amsl.com>; Tue, 22 Oct 2019 06:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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=jq7Ut95a; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=G5uQMl0i
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 wn79fBkHUJPp for <roll@ietfa.amsl.com>; Tue, 22 Oct 2019 06:52:01 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8FEA120013 for <roll@ietf.org>; Tue, 22 Oct 2019 06:52:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12408; q=dns/txt; s=iport; t=1571752321; x=1572961921; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=TkMACmkQMGKjjOCfaTFZUV0yAUZ9+pCVfMyX2lLkfmk=; b=jq7Ut95ajY3FLv5WorGsa6CCumH5MZHT1UkNsNX1E1EJMVkvYxWLe/Jz Qazjuucm7iYpT/hiHJCKIgZbr6AYURhSUq+U6chmCs/oVu09zRQY5tgnd tBcgvPMoS5ITkvlyDWKTZHWzWR37hf5NUZeSP7pLqIgxF1pNYcMUu7Kse E=;
IronPort-PHdr: =?us-ascii?q?9a23=3AeRvzcRw6DZTadhrXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZudFU3mJvPwcwQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A2AAAyCK9d/5BdJa1lGwEBAQEBAQE?= =?us-ascii?q?FAQEBEQEBAwMBAQGBaQQBAQELAYEbLyQsBWxXIAQLKoQmg0cDileVfoRhgS6?= =?us-ascii?q?BJANUCQEBAQwBASUIAgEBhEACF4MTJDYHDgIDCQEBBAEBAQIBBQRthTcMhUw?= =?us-ascii?q?CBBIRChMBATcBDwIBCEICAgIwJQIEDg0agwGBeU0DLgECDKcEAoE4iGF1gTK?= =?us-ascii?q?CfgEBBYUJGIIXAwaBNgGFFYZ5GIFAP4EQAUaCHi4+gmIBAQIBgWAMH4JjMoI?= =?us-ascii?q?sjUGCN4U6JJgMCoIkhw6OM4I7h1OPQJZdkSACBAIEBQIOAQEFgVkDL4FYcBW?= =?us-ascii?q?DJ1AQFIMGg3OFFIU/dAEBgSeOfAEB?=
X-IronPort-AV: E=Sophos;i="5.67,327,1566864000"; d="scan'208,217";a="637723086"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Oct 2019 13:52:00 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x9MDq0ga026918 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 Oct 2019 13:52:00 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 22 Oct 2019 08:51:59 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 22 Oct 2019 08:51:57 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 22 Oct 2019 08:51:56 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HDV6tdI1iEuHZiZYSL26ugIaP9dUubVUiuBvkhlhQnDIgRP5FRSmAzbA5gNmZ/Oc5SkokM3tTiuqTNXHe7648N+1Omr7DKG3FU7yViBXqQ3YbZ5bcMn/OlCwBgbHoNvblopOkT+YoDn9ak23jJqwAVXA2JT9HPYKXBbRZ1mrGzrcs8qGVBvyLPoh6kyYiS27VlAK/WyIg11ADk9b5BYVI/9hJd8daC6cIibkYhQ4CNCSysC7aH6J3hMxp3eFBw1wrukellK7DHVYZMniYn63PcWBUYlp/NNtNmp6OVWQIoqhorDN+IV2otje9/DSqODTDiGWVigqELw323l3S+mvqA==
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=TkMACmkQMGKjjOCfaTFZUV0yAUZ9+pCVfMyX2lLkfmk=; b=O85v2o3k/UXGid/gImcrZg6tdII+8l3oaYvQmKXmRmBivVCxXAMHt678AGeIyZ9RgLSk9Ex8ZUjKVgSZKYXbOFYYRR1hqkQZaKN4FEaLAi8O4vOmt5jq4gGVfpBucS/E0rRjSeqy4hMIeaqiXbTogHOyeIiRZ2Fgedi9LpCH+LNX87aoSBBOYi4CSL9j+fAkTZMgOtENABLT9aQaHBxv5gxYEHP/pHS7XyFQq7tIRMG2FCDsAPjZDygRNBy3tGD2wW968k6W50YytmGcvLuW7DC7J5wm3DjFq1YmfquhE2oWpUrCCry4ZH9RN2YfMXBmdj5TFrjVn4WTqA5w/Zu5pw==
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=TkMACmkQMGKjjOCfaTFZUV0yAUZ9+pCVfMyX2lLkfmk=; b=G5uQMl0ighM+B8NX6FrhNa5yJWB3WKDZq+P2cAkxq+rbzncpaNoa2iM/6mMBWbUwFCdo6OAzWVu2WL5xpbzoRhybFKg8zzURCRvHMp4DzyzSKAWOXVxbbMbqlLJl9Cz2b7DqRp6SPlAB8Tn+xAv2h6wGQOEZzx8vbZq2VPIsF/k=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3869.namprd11.prod.outlook.com (20.179.150.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.18; Tue, 22 Oct 2019 13:51:56 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::31c9:3a31:3c07:a920]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::31c9:3a31:3c07:a920%6]) with mapi id 15.20.2387.019; Tue, 22 Oct 2019 13:51:56 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
CC: Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [Roll] naming and other goals for RPL Unaware Leaves
Thread-Index: AQHViNj5v6oSJb/bFU2sklmHRjeKLqdmomHg
Date: Tue, 22 Oct 2019 13:50:43 +0000
Deferred-Delivery: Tue, 22 Oct 2019 13:48:16 +0000
Message-ID: <MN2PR11MB3565C02CC46CD6644D2C75F9D8680@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <11891.1570805812@dooku.sandelman.ca> <CAP+sJUftMdV1bMrVTqJaYU4GL7-8rU+pZKn2MdPG-4iP14HFag@mail.gmail.com>
In-Reply-To: <CAP+sJUftMdV1bMrVTqJaYU4GL7-8rU+pZKn2MdPG-4iP14HFag@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2001:420:44f3:1300:fc9e:730:2c16:4060]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7aaf1535-5298-4a41-e68c-08d756f70070
x-ms-traffictypediagnostic: MN2PR11MB3869:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB3869697752053EA8F3428F5FD8680@MN2PR11MB3869.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(376002)(136003)(346002)(366004)(396003)(199004)(189003)(8676002)(74316002)(102836004)(486006)(476003)(6116002)(11346002)(446003)(25786009)(86362001)(790700001)(2906002)(6506007)(186003)(7736002)(229853002)(6436002)(99286004)(4326008)(7696005)(9686003)(54896002)(6916009)(46003)(81166006)(6306002)(81156014)(76176011)(14454004)(478600001)(6246003)(236005)(606006)(33656002)(8936002)(55016002)(66476007)(64756008)(66556008)(5660300002)(316002)(52536014)(256004)(14444005)(71200400001)(6666004)(71190400001)(66446008)(66946007)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3869; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jIJ1RQfba5K78TusWISHAAxNp+6sYxynn0g448v7Mqyp+kp5KVoEF5Zj2JRTuJketA1gW2GUp8GaGh402CJcD17i+2WTrPv3S1mmGthBPBU05gW7yUH+wNIE7zfcM51xXhIx6967Ez9lM0CV5HBYHOvXUKiRmnRFpsktw8gYtzDHGP7vdODgiepj78BvxWh9KyKtdRjK9V8J8Ics5IyEClOT+3kmX/phFCeIK7S+CkPnieYF5EMTIZBPOzs6C/4KIYElX2GmLJS/SLYG2haIPv+706EpW+0VkiaD2J+WCleeibaCTjc0K5nJh2OdrV5JWtCExxtVlybLL1dMw1EedYYO2UU1DE7wUybwD5zS2czrNqpBVMtVSTQa+NYonrJLmigSV711XtdxqU/W/mUfS063vPOy/3OnHEg9rhqBWOLi95RMkZANt5KbyRjnbCkNtfiqW4K4WinWk/EY3nJQyg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3565C02CC46CD6644D2C75F9D8680MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7aaf1535-5298-4a41-e68c-08d756f70070
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2019 13:51:55.8845 (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: PLEc71L4OibegofdISGBOeRhaDJ8ZFAEiz36KvfpF746Hf6PzHRm0vRskiKSaJticfVe7bqROZ5EblHna8eO3g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3869
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/BHzekLy8tsH00lVl1K2yNw2Zp74>
Subject: Re: [Roll] naming and other goals for RPL Unaware Leaves
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: Tue, 22 Oct 2019 13:52:04 -0000

Hello Ines :

Currently the useofrplinfo draft states:

   RPL-aware-node: A device which implements RPL.  Please note that the
   device can be found inside the LLN or outside LLN.

   <<< This would be the number 3 of Michael descriptions
   Should we extend the definition to insert 3.A, 3.b, 3.C, 3D descriptions???? >>>>

   RPL-Aware-Leaf(RAL): A RPL-aware-node which is a leaf of a
   (Destination Oriented Directed Acyclic Graph) DODAG.

   RPL-unaware-node: A device which does not implement RPL, thus the
   device is not-RPL-aware.  Please note that the device can be found
   inside the LLN.


   <<< This would be the number 2 of Michael descriptions,
   I am wondering if we could add the need of RFCs6775, RFC8138 and the others that Michael mentioned
   into section 9 Operational Considerations of supporting not-RPL-aware-leaves. >>>>

<Pascal> I like those definitions because they are RPL related in a RPL draft. RFC 8138 is also ROLL and is orthogonal. We can say a RFC-8138-complient node without a defining a fancy name. The others are external to ROLL. </Pascal>

   RPL-Unaware-Leaf(RUL): A RPL-unaware-node which is a leaf of a
   (Destination Oriented Directed Acyclic Graph) DODAG.
This is all consistent with option 1 the other thread and with the way the RUL draft is written today.

This is interesting for the control plane because we know a RUL cannot speak RPL. The RUL drafts asks the RUL to speak RFC 8505 in a certain way instead.


This is less interesting for useofrplinfo because it is data plane. The data plane does not care about RPL but about the way a host treats a consumed RH or a HbH option, and that’s RFC 8200 not RPL. The data plane also cares about IP in IP encapsulation. When useofrplinfo says what to do with a RUL (e.g., in section 7.1.4<https://tools.ietf.org/html/draft-ietf-roll-useofrplinfo-31#section-7.1.4>)  that really applies to a node that can do those things whether it is a RAL or a RUL. Suggestion, we call that thing a Leaf. Because a thing that does not do any of that is an external destination for which the only thing useofrplinfo can do is tunnel to the 6LR and terminate all IP in IP, artifacts and compression there. We already have text in useofrplinfo for those.



: )



Pascal