Re: [Roll] Adopting turnon 8138

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 11 November 2019 07:42 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 453BF120833 for <roll@ietfa.amsl.com>; Sun, 10 Nov 2019 23:42:48 -0800 (PST)
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=MYB62TCF; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=fIv9BGhY
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 1yo0B-Oqrhkj for <roll@ietfa.amsl.com>; Sun, 10 Nov 2019 23:42:46 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B1A8120821 for <roll@ietf.org>; Sun, 10 Nov 2019 23:42:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16655; q=dns/txt; s=iport; t=1573458166; x=1574667766; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=l9j4OpowlN/yrrQgKG0Z8pjGHXgPiSBgfGlJ2NjwXpc=; b=MYB62TCFiZLU4pfLHpHICojAR4fXAQNoTWY1JSBl/VFGpFkkYWBEyDxR nzIegc7UgPlzSrvLOLGxv2lt7d6FzzAxI3hAsOSVVfhXxv/bY3r63VV0B Q7bYsVium68TT5o7B+tIrBCoiR/QhWlqWj2ibdjyTSwJtkfJRVwnNv21k I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AzDhv1BPIzZPn2r+ggogl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBjjMP73ZSEgAOxJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AMAgCqD8ld/5RdJa1lHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgWwFAQELAYFKJCwFbFggBAsqCoQfg0YDimxOghCJWIlGhGKBLhS?= =?us-ascii?q?BEANUCQEBAQwBARgBCgoCAQGEQAIXg3kkNgcOAgMLAQEEAQEBAgEFBG2FNwy?= =?us-ascii?q?FUQEBAQEDAQEQER0BASwMDwIBCBEDAQIoAwICAh8GCxQJCAIEExsHgwABgXl?= =?us-ascii?q?NAy4BAgELnxECgTiIYHWBMoJ+AQEFgTgCgQ+CPw0LghcDBoE2AYwTGIFAP4E?= =?us-ascii?q?4H4FOSTU+ghtHAQEDgSYcPA2CYzKCLI0TEoJnhUMkl2BBCoIlhxeHQYJahBI?= =?us-ascii?q?bmXmWfYISjy4CBAIEBQIOAQEFgVkCMCqBLnAVOyoBgkFQERSQNoNzhRSFP3S?= =?us-ascii?q?BKIxeAYEOAQE?=
X-IronPort-AV: E=Sophos;i="5.68,291,1569283200"; d="scan'208,217";a="377421202"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Nov 2019 07:42:44 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id xAB7gihg031337 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Mon, 11 Nov 2019 07:42:44 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Nov 2019 01:42:44 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 11 Nov 2019 02:42:43 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 11 Nov 2019 02:42:43 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nghqa6T1AgZpVeFYiUnrE++2sX0Y787EA0POBBjX9LV0LFfro55MVLD8n1WSQdyd3Bj7S7gha2cgAANCOsnpGupG5fZovFqp1twrnA1NaWxVW3kbeS43GOjvi3LR3RudZrc1+RGP8kMeaAeOZPZ8WMVw/VOE/JqGFH9Z4pWP7BMATnuQy79Hzie9U4pyGh5VuIf8VT2ZYKBm2tIGXgDc1C1DgCKJCjcF8bav4Zvy4JtY3LVL0iZN126oAXVjCEEd2nsW8NLwX+3gcvpKXPdeYTj9duQKOnQ9RnDhh1tFSzTHCuQsS33o5Z26dZGDJWlwnkQT0RtDXeJzXEnREq+xvA==
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=l9j4OpowlN/yrrQgKG0Z8pjGHXgPiSBgfGlJ2NjwXpc=; b=Yl/ggAiXKJCec3CwE72R1MZDbXlvjGX0PD9Z/D8WEPiY1uhXAtS6oqUFsP3heq2vP2D6jvEt4lfpcFeTj3T2nlDOYZu1qiZ6Fxv5vdYP4EQlgmuunv+96dBBKveUUlyabdFIguAuW51iUGgQ983KViO3osg9w+H70c+8zcN6VSm3ggFycXkeC/AG67+3kdJ6sOOaFy7xkAMGd5WrINpm0pK6LifmJh9VM31JspcKEg+l4PAj9edRjR7vWNhKfHuLFozI1KkC0UJlV3ndm5gsuLeMh9uFRYJGAGoLEjSqlgX5Dw1jADBWeX47kXLicfYr6crOwjdxKZe+SEWdfBmLqg==
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=l9j4OpowlN/yrrQgKG0Z8pjGHXgPiSBgfGlJ2NjwXpc=; b=fIv9BGhY2u2o4vpyqEk/UeiMGoCvw146aYA9AHIEx7SkAEnL+aXLyx0wurfoeA8vqual8eJteuXMWz2VxbLV8pcP/UKjIUCUfwxt2Cn3AT2ci8DG0flZrrKxv7kzKCf3W76uuDGjlQ65Q9rtxHiblWHfcqpyH3RYAWIkdrjRBVA=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3598.namprd11.prod.outlook.com (20.178.252.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.25; Mon, 11 Nov 2019 07:42:42 +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.2430.023; Mon, 11 Nov 2019 07:42:42 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] Adopting turnon 8138
Thread-Index: AQHVkz51IaUeQ4e3TG2QSA0m4ffOf6d8L3Y6gAlj3QCAAA1igA==
Date: Mon, 11 Nov 2019 07:42:41 +0000
Message-ID: <6578CDED-E37D-4AF4-9AB7-44B940C11605@cisco.com>
References: <MN2PR11MB3565D8323B4C7860396B2F8DD8610@MN2PR11MB3565.namprd11.prod.outlook.com> <CADnDZ8-p+HiLw9eoq8zKnRh9PqiT4HGYXdg_Cqid=eGQmd=V5g@mail.gmail.com> <CAP+sJUebKNAAEixtJQ-BFTDt3Aq9X2=MvgYJw_NrCrbtd1P3=g@mail.gmail.com> <76EB15DE-5CCD-4088-AE87-FF68436BC267@cisco.com>, <CADnDZ885qdYWVfSbykavK5ziXLWCKCDo0yQsyj=3SfhgDnGbbw@mail.gmail.com>
In-Reply-To: <CADnDZ885qdYWVfSbykavK5ziXLWCKCDo0yQsyj=3SfhgDnGbbw@mail.gmail.com>
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: eb1b041e-cfed-4bb4-7cc0-08d7667abbe2
x-ms-traffictypediagnostic: MN2PR11MB3598:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB35986407777D2EA45B59B6C9D8740@MN2PR11MB3598.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(39860400002)(396003)(346002)(376002)(199004)(189003)(22974007)(186003)(3846002)(86362001)(606006)(966005)(6916009)(6116002)(2906002)(11346002)(14454004)(486006)(446003)(476003)(2616005)(26005)(66574012)(36756003)(25786009)(102836004)(478600001)(6506007)(53546011)(66066001)(33656002)(71200400001)(71190400001)(76176011)(7736002)(256004)(14444005)(561944003)(6246003)(66476007)(6306002)(6512007)(236005)(6436002)(6486002)(8936002)(99286004)(66556008)(66446008)(229853002)(64756008)(66946007)(81166006)(76116006)(81156014)(91956017)(316002)(8676002)(54896002)(5660300002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3598; 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: 2HUIc3PVHftgVerffiTc8DAhe+OPOdLRXwKG90qVmD+QJPZgQoNvUYWNq9i/DjoIMfrJBQdYP8knxHL3NUkVSLbkFg1BGA/a1Iwj54JJjCrmaP8nKD+uoc+HPGghYFSEUJ09IUZ48BWlfJ6amBehohEmvakEVIsU4iBnnYNZowkH2wHwYIC+qN5Tn+HDa82Vn7FSKtTL6ldO+Se40m87DyQwZO80XfDWmXjsEW4R3Thi6rWz/KusL/iwt1fpVYFp7A2rulwaFcpjJY4u1vpSWEuF4J6VIlW9k0VSDvWtTZJkKKYFfxp0wVqX5EvA14Z8mUYLiZfYsYTPQAOlhd+tF79Xl7vnRs4SR7AVAimBJQPdZ1we6C25PpRM1GtGLmNXE5XhWItGLPh9kkqqA5fs+bpWa9TwlRW1OFG3CjHHUbhfzBOE/O7GywEqgp2jw19/kbDVGFtQwA1j2lHyUrcTC3tfPjHTUWcz6N14c7qQaxQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_6578CDEDE37D4AF49AB744B940C11605ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: eb1b041e-cfed-4bb4-7cc0-08d7667abbe2
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2019 07:42:41.9490 (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: e0YOMppENzNcdu1yB3xTPMroEgYkVWpwWEJ5eZKNUeT3XIfWy2taUFKUqNlBMcLlutPqOhVv4amwilU0DRX76A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3598
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/qEdqNhOpLCE1lsJp-NquX14wvCA>
Subject: Re: [Roll] Adopting turnon 8138
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, 11 Nov 2019 07:42:48 -0000

Hi

Le 11 nov. 2019 à 07:55, Abdussalam Baryun <abdussalambaryun@gmail.com> a écrit :




On Tue, Nov 5, 2019 at 9:31 AM Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
DODAG configuration as it’s name indicates is configuration. The goal is to tell dynamically how the protocol is operated as opposed to configuring all nodes separately.

The draft is not about configuring the DAG, it is for compression, why your proposal mixes them?

It is a configuration knob of a RPL device so it belongs to configuration. It configures the compression of RPL artifacts and belongs to RPL. There is no inconsistency.


RPL operates in control plane and data plane. It does proactive route setup and reactive invalidation. These are all trade offs that are chosen to optimize energy and bandwidth efficiency vs. some theoretical perfection.

yes, so we need to give RPL more options and alternatives and not use its few reserved,

The current proposal does not generate any additional transmission.

how can we be sure of this if we do not separate functions specially while RPL is in both data and control planes.

The draft uses an existing bit that was wasted so far.


Defining a new protocol to set one bit might appear more perfect but would require bandwidth and code footprint that we do not have.

I agree but this draft proposed is already a new protocol defined as standard and updating standards. Updates for protocols can make things very more complicated.

You are very free to propose an alternate solution with enough details so we can understand it, even push a draft, and then the WG will make the best of all it sees.

We are now trying to understand your proposal and your request to adopt and to find good solutions, why we are asking for another draft or solutions?


You say it’s wrong. Show us what’s right...

AB



Pascal

---------- Forwarded message ---------
From: Abdussalam Baryun <abdussalambaryun@gmail.com<mailto:abdussalambaryun@gmail.com>>
Date: Fri, Nov 1, 2019 at 11:55 AM
Subject: Re: [Roll] Adopting turnon 8138
To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>


I don't think it is the right approach, why using the DODAG configuration for compression? this compression turn on/off is not for the DODAG construction but for packets. I think we should separate configurations of the RPL routing standards and of the packet compression standards. We may add another configuration option per DODAG or another way.

What do you think?

AB

On Tue, Oct 29, 2019 at 4:34 PM Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Dear all

https://tools.ietf.org/html/draft-thubert-roll-turnon-rfc8138-03 is a simple draft that completes RFC 8138 with bits in the config option to enable turning it on in an brown field.
There’s no black magic and it would be good to progress it in the background rather than forget it... Could we consider adoption?

All the best

Pascal
_______________________________________________
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
_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll