IETF Logo Mail Archive

Re: [Roll] turnon-8138 review

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 08 July 2019 08:27 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 06330120164; Mon, 8 Jul 2019 01:27:24 -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=d93bVJJW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=PwiMfh0K
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 1RU1g6cW3S8u; Mon, 8 Jul 2019 01:27:22 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19D32120189; Mon, 8 Jul 2019 01:27:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8391; q=dns/txt; s=iport; t=1562574442; x=1563784042; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lU7QmarJYgSe7X9kbHcpcLbOPPfM+iMx9d/tXzhQUns=; b=d93bVJJWzNRiTb29CuJimMkzBc2BOdrGVzQuXhQloOEKuF/Kg136/n09 Ql2t3Z78S3AbSt39xPuIDiUx08n32gY8+Gr4u4FD14se777bRvsS1z8PS N5mLVaCyzyWwzM89GAgAoClnMBmcRLdbWLOsFcCSqNGA1w8WWRLEtpvzT k=;
IronPort-PHdr: 9a23:eXSfARcQVf/0I9++o9U9PPdglGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dzA6Ac5PTkNN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAABR/SJd/5RdJa1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRQvUANqVSAECygKh1kDhFKJdoJbknKEVIEuFIEQA1QJAQEBDAEBIwoCAQGEQAKCNCM0CQ4BAwEBBAEBAgEFbYo3DIVKAQEBBAwGGxMBATcBDwIBCBEEAQEvMh0IAQEEAQ0FCBqDAYEdTQMdAQIMnAgCgTiIYIIjgnkBAQWBNgIOQYJ0GIISAwaBNAGEcYZtF4FAP4FXgkw+gmEBAQIBARaBDxwFGSuDD4Imk22WaQkCgheGVo1JgiyHIY4xjTCBMIYQj30CBAIEBQIOAQEFgVA4gVhwFYMngkEHg2qFFIU/coEpjDABgSABAQ
X-IronPort-AV: E=Sophos;i="5.63,466,1557187200"; d="scan'208,217";a="586017448"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Jul 2019 08:27:20 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x688RKh0011847 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Jul 2019 08:27:20 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 03:27:20 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 8 Jul 2019 03:27:19 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 8 Jul 2019 03:27:18 -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=aDeJgENNq0oDt02xW/+cGQRPcYoHOgWqjvaLBwOHciw=; b=PwiMfh0KzkSdsCk2XaLGsCR15ITb4BZ5GPLRzH2bxKZwmc88mrfDy1+I2BqbgMgXSPg42F/0o/5gQsYxPogE+94X9ZexSB9qVGwyN28CGHIyfQgZ55v1hjDt3SDOV6tZbnbx0pLr1RL1Tl5OfTi2PZSEYKveY78JuHEi4JA0nv4=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3806.namprd11.prod.outlook.com (20.178.254.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.19; Mon, 8 Jul 2019 08:27:17 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::1ce9:1582:146c:c50a%6]) with mapi id 15.20.2052.020; Mon, 8 Jul 2019 08:27:17 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>, "draft-thubert-roll-turnon-rfc8138@ietf.org" <draft-thubert-roll-turnon-rfc8138@ietf.org>
CC: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: turnon-8138 review
Thread-Index: AdU1IIlA6w1MYnH1Rd6eOKlcXhIIwAARgMqQ
Date: Mon, 08 Jul 2019 08:27:04 +0000
Deferred-Delivery: Mon, 8 Jul 2019 08:26:13 +0000
Message-ID: <MN2PR11MB3565CDAD9BD6E7A9F7232A84D8F60@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <982B626E107E334DBE601D979F31785C5DF34E04@BLREML503-MBX.china.huawei.com>
In-Reply-To: <982B626E107E334DBE601D979F31785C5DF34E04@BLREML503-MBX.china.huawei.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: [173.38.220.48]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7b181f01-0662-4cf3-6e7b-08d7037e16c1
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3806;
x-ms-traffictypediagnostic: MN2PR11MB3806:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <MN2PR11MB380680AF10FA16E7602D5347D8F60@MN2PR11MB3806.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(396003)(366004)(376002)(346002)(136003)(189003)(199004)(6666004)(2906002)(8936002)(66476007)(66446008)(64756008)(66556008)(73956011)(66946007)(8676002)(99286004)(81156014)(81166006)(86362001)(478600001)(52536014)(6246003)(7696005)(110136005)(316002)(6436002)(606006)(14444005)(76116006)(256004)(74316002)(71200400001)(71190400001)(14454004)(6306002)(68736007)(53546011)(54896002)(33656002)(5660300002)(9686003)(476003)(186003)(55016002)(26005)(11346002)(966005)(6506007)(25786009)(66066001)(7736002)(76176011)(486006)(446003)(790700001)(6116002)(2501003)(53936002)(3846002)(236005)(229853002)(4326008)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3806; 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: NTzbOJ8a1G/srmUL/UjWznxdALYWQ/TqzQw6iniOARWyokO9Dq+47ZKn8ff3papt3pdJUz7CaHAFEP3bT/HI3BJg4YodPKLLm14xG9l3SbXZ3JI7P1vHwlKfcKpDDc+DexWZiJR6R/YXpMAjqnwc563pYEexhQ6DD4ucgiUQumSRURMZfyvwwDioVbkL5kYML8fLQTEZWSfV3iizguXkgDEJI7XDKhEG3W/H+V4MMRiP4yw5CKtAaqSSTLpYVPbQ9JZIxiqOYf53DXSx6GuIwvoHSdtqiwzAUlmfsIEGXhT9O1jIJw92R1PIlH0Q6na0Kmh7XJ1OGRA2mLaUXOBDqDCNgKBOp34VT2qj3Cu8f3vStg2tfmiJYQTRiznrMw9Ur47KndtlNVnTv5+Z6h9zoeAxEybDLWRlKwoc2wbALQc=
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3565CDAD9BD6E7A9F7232A84D8F60MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7b181f01-0662-4cf3-6e7b-08d7037e16c1
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 08:27:17.6613 (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: pthubert@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3806
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.21, xch-rcd-011.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/QtDp9f4gzupw4PEtWh8cprFSirc>
Subject: Re: [Roll] turnon-8138 review
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, 08 Jul 2019 08:27:31 -0000

Dear Rahul and all:

I published 03



Htmlized:       https://datatracker.ietf.org/doc/html/draft-thubert-roll-turnon-rfc8138

Diff:           https://www.ietf.org/rfcdiff?url2=draft-thubert-roll-turnon-rfc8138-03

To address your comments. Please let me know if I missed something.

All the best,

Pascal

From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
Sent: lundi 8 juillet 2019 02:40
To: draft-thubert-roll-turnon-rfc8138@ietf.org
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: turnon-8138 review

Hello Authors,

Following is my review of draft-thubert-roll-turnon-rfc8138-02:

Section 5.4. "Rolling Back", says, the administrator SHOULD make sure that all nodes have converged to the "T" flag reset before allowing nodes that do not support the compression in the network.
[RJ] How would a root know that all the nodes have accepted the T-reset? Doesn't this require use of capability flag ? Also I'm not sure if the same capability flag used before can be used here?

Section 5.3. "Double Instance Scenario", says that nodes that do not support 8138 would either not be configured for the new instance, or would be configured to join it as leaves only.
[RJ] Thus I believe there is some non-RPL management involved to tell the legacy nodes to not join the Instance-with-T-flag.

Section 5.2. "Single Instance Scenario", The root encapsulates packets to the leaves all the way to the parent, which decapsulates and distribute the uncompresses inner packet to the leaf.
[RJ] When it says encapsulate/decapsulate, it means IP-in-IP encapsulation/decapsulation, right?

Section 4. "Updating RFC 8138"
[RJ] I didn't find any updates to 8138! I believe the text in the section does not result in 8138 update.

Regards,
Rahul

v2.23.0 | Report a Bug | By Email