Re: [Roll] WG call for adoption of draft-thubert-roll-unaware-leaves

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 17 May 2019 14:47 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 6A9071200E3 for <roll@ietfa.amsl.com>; Fri, 17 May 2019 07:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=UZkogmDi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=E7dQae5W
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 vwOAq-ucD06l for <roll@ietfa.amsl.com>; Fri, 17 May 2019 07:47:53 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B890512008C for <roll@ietf.org>; Fri, 17 May 2019 07:47:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25286; q=dns/txt; s=iport; t=1558104472; x=1559314072; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=jimV2bYuNB/iAsoAubJ/TjrO1K/QjINPg6yos7/wxo0=; b=UZkogmDiBVWE5duzkNy/Y1yxIPvHX3gRa10ZoaLmL6ucuw91lNpO4bxj v5cTxwn+qQh0M3H6jMM/ky/U8w/Zcj+KcMSdyj7RAiOfTObJYPPeZ3F6W shJyMWupFIcch5fzKjk21y3pQ7ONbx4sUZVnM/oAFh7spTGcz9cnsEh5o A=;
IronPort-PHdr: 9a23:1hUEHh1rzzy1fCzYsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKGt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQEVH7MfTndTASF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAAB3yN5c/4cNJK1kGwEBAQEDAQEBBwMBAQGBUQYBAQELAYEOL1ADaVUgBAsohBKDRwOEUooiSoINlyeBLhSBEANUCQEBAQwBARgBCgoCAQGEQAIXgh0jNAkOAQMBAQQBAQIBBG0cDIVKAQEBBAEBEAsGChMBASwMDwIBCBEDAQEBKAMCAgIlCxQJCAIEEwgagwGBHU0DHQECDJ8ZAoE1iF9xgS+CeQEBBYUGGIIPAwaBNAGLUBeBQD+BV4IeLj6CYQEBgSkYAQECHh4NCYJUMoImi2KCE4RdlUgJAoILjG2GKYIdhlWNJqIIAgQCBAUCDgEBBYFPOIFXcBU7gmyBF3gMF4NMhRSFP3KBKYwWgkMBAQ
X-IronPort-AV: E=Sophos;i="5.60,480,1549929600"; d="scan'208,217";a="274586484"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 May 2019 14:47:51 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x4HElpqn014102 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Fri, 17 May 2019 14:47:51 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 17 May 2019 09:47:50 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 17 May 2019 09:47:50 -0500
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 17 May 2019 09:47:50 -0500
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=jimV2bYuNB/iAsoAubJ/TjrO1K/QjINPg6yos7/wxo0=; b=E7dQae5WyLecorYa0yGXFC8A44Gv4m+lCe+DMcRBFKuLk+ozOI0USE3U/Z6/wC1viVKXRwRAkFqCFqNeLEebWhg9hRMO4IIysSVxC+oM4+4m8yDst/fB4HVCcger13ZxOB9GGHeW5JuKU32a0PoAfjL5rsURLRnsMf4rQ8aG2wE=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4063.namprd11.prod.outlook.com (20.179.149.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.16; Fri, 17 May 2019 14:47:49 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::7cc2:b440:8820:f0fc]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::7cc2:b440:8820:f0fc%7]) with mapi id 15.20.1900.010; Fri, 17 May 2019 14:47:49 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] WG call for adoption of draft-thubert-roll-unaware-leaves
Thread-Index: AQHVDKVKtSnKc6f5fUul40p3MA7KraZvMiEAgAAns4CAAAmM8A==
Date: Fri, 17 May 2019 14:47:28 +0000
Deferred-Delivery: Fri, 17 May 2019 14:47:21 +0000
Message-ID: <MN2PR11MB35656DA8B9AF05C662480689D80B0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CAP+sJUdOmNbHVx5RnP=pFJiPjex7axfxx1kfGbgfzB0=pkWEdA@mail.gmail.com> <982B626E107E334DBE601D979F31785C5DEA5587@BLREML503-MBX.china.huawei.com> <D6643D22-2B88-4EA3-AEDE-84CDE3489662@imt-atlantique.fr> <CAH7SZV8JzDk9mzAS1Lo2EMBxtXaGRsEm1OqdUbUyTEBrVF7HKg@mail.gmail.com> <70EBECCB-DB61-47FA-9A68-2911CBCEA473@cisco.com>
In-Reply-To: <70EBECCB-DB61-47FA-9A68-2911CBCEA473@cisco.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:552f:ff32:b86:aad7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1cde9b65-2db1-4b6f-3583-08d6dad6a1d8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR11MB4063;
x-ms-traffictypediagnostic: MN2PR11MB4063:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MN2PR11MB4063BE64026309BDFCE73FABD80B0@MN2PR11MB4063.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0040126723
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(346002)(136003)(366004)(39860400002)(189003)(199004)(53546011)(476003)(86362001)(446003)(256004)(316002)(790700001)(76176011)(14454004)(6436002)(81166006)(11346002)(54896002)(6306002)(55016002)(9686003)(7696005)(229853002)(486006)(6506007)(102836004)(81156014)(46003)(7736002)(2906002)(6116002)(99286004)(186003)(236005)(8676002)(52536014)(6666004)(25786009)(71200400001)(71190400001)(478600001)(8936002)(33656002)(606006)(6246003)(53936002)(6916009)(966005)(73956011)(66946007)(76116006)(66476007)(66446008)(64756008)(66556008)(68736007)(5660300002)(74316002)(24704002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4063; 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: LtCHK/S1PAywHuvKDUo76izPEhLshE3fN34Hf9DjStPSC1mzkfJpiOZ2snYc9jYU/m20dX0MtxNu94vaecF6XPWQga34hKVIszp4VEInxdRGXmOCsJsxpo3MsPmjaqUf0Bv9dw9SA44UnA5wGrwLJtEMoNr5i2XG66pTHBCY9Ww4KXshB2P1JFa4Ddzq3C6V5sbj/tLbP+elJwaZBY4RCS3rvx1wY3n0LhOyl2Nyv5qg+4G2tAnqNmCpkcn39kZXaB5epfFOJPCLtFoaSJV7GGiKVYfwBTe2wmHs/loyvVNOSm70ipwp36K4Oj6I9yhlu34qN9LBZMm92VvKc9ICulT/S9843pxCtoUeL8kxYDBlZW2/xfNL2Pe/ws6eGVii/b4+b+L034t9TPzyIGKvy88AFoqIqdQ28cr61R/Crqo=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB35656DA8B9AF05C662480689D80B0MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1cde9b65-2db1-4b6f-3583-08d6dad6a1d8
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 May 2019 14:47:49.0742 (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-Transport-CrossTenantHeadersStamped: MN2PR11MB4063
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.26, xch-rcd-016.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/G2zkHLIn-MQczAU_mTaPCDC5z8Q>
Subject: Re: [Roll] WG call for adoption of draft-thubert-roll-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: Fri, 17 May 2019 14:47:56 -0000

True, Patrick, I’m hearing that too.

The RPL mesh in a Smartgrid has historically been powered. But there’s a new need for low power leaf devices, that would not be powered with mains.

For those, the support of RPL is:

  *   Double messaging in the constrained hop (NS/NA from RFC 8505 + DAO/ACK from RFC 6550)
  *   Double messaging inside the mesh (DAO + DAR/DAC)
  *   More Code in the constrained leaf device (All the RPL stack)


The device makers would prefer to ship devices that are agnostic of which routing protocol happens in the Smartgrid.
RFC 8505 provides the required abstraction but there’s a need for a spec that turns the abstraction into RPL and that is this draft.

All the best,

Pascal

From: Roll <roll-bounces@ietf.org> On Behalf Of Patrick Wetterwald (pwetterw)
Sent: vendredi 17 mai 2019 16:05
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] WG call for adoption of draft-thubert-roll-unaware-leaves

I support the adoption of the draft. It may be pretty useful in the smart grid environment.

Thanks,

Patrick

From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> on behalf of "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl<mailto:diego.dujovne@mail.udp.cl>>
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
Date: Friday 17 May 2019 at 13:43
To: roll <roll@ietf.org<mailto:roll@ietf.org>>
Subject: Re: [Roll] WG call for adoption of draft-thubert-roll-unaware-leaves

I support the adoption of this draft

El vie., 17 de may. de 2019 08:40, Georgios Z. Papadopoulos <georgios.papadopoulos@imt-atlantique.fr<mailto:georgios.papadopoulos@imt-atlantique.fr>> escribió:
Dear Roll,

I support the adoption of this draft.

Best,
Georgios


On May 16, 2019, at 08:23, Rahul Arvind Jadhav <rahul.jadhav@huawei.com<mailto:rahul.jadhav@huawei.com>> wrote:

I support the adoption of this draft.

This draft is natural progression for the work done in RFC 8505. It does not have much impact on the semantics of RPL and still extends it to new scenarios.

Regards,
Rahul

From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Ines Robles
Sent: 13 May 2019 20:32
To: roll <roll@ietf.org<mailto:roll@ietf.org>>
Subject: [Roll] WG call for adoption of draft-thubert-roll-unaware-leaves

Dear all,

This is a call for adoption of the draft-thubert-roll-unaware-leaves document.

The call starts today (13-05) and finalize on 27-05.

Please send your support/opposition with comments before deadline.

Thank you very much,

Ines and Peter
_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll

_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll