Re: [Roll] DIS for given parent in draft-thubert-roll-eliding-dio-information

"Li Zhao (liz3)" <liz3@cisco.com> Thu, 21 November 2019 01:02 UTC

Return-Path: <liz3@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 20DF01208E1 for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 17:02:37 -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, 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=i0ej10/I; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=lPNZ1b5M
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 bT9ic1LBYZcX for <roll@ietfa.amsl.com>; Wed, 20 Nov 2019 17:02:34 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9063612006B for <roll@ietf.org>; Wed, 20 Nov 2019 17:02:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7920; q=dns/txt; s=iport; t=1574298154; x=1575507754; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=NZGaNzpFwk2o80r6NQ9lzq7FqssEO6lKPDTrkYkfANU=; b=i0ej10/Iz2PsevwkKAgpx9Vyn5tPGUgTumPiP8JBZI5hDo9kb2ACqD8f vNhnltQnDPfC1sNUMWQI9AnVN7/F+fpH20e05CGtjcTqGd9JMa+1AVhu+ Jv6X0hgPnv6MybIptz3yWo5MyIIgkOXX+NoR3iCwxx7sVXc405DjYNSPh U=;
IronPort-PHdr: =?us-ascii?q?9a23=3AXyORYBD4vIc+e+KUixvSUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qgw3kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMdRXUg?= =?us-ascii?q?Mdz8AfngguGsmAXEn6PqXCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DWAgAH4dVd/4sNJK1bChwBAQEBAQc?= =?us-ascii?q?BAREBBAQBAYFrBgEBCwGBSiQsBWxYIAQLKoQqg0YDimxOghCJWI4ogS4UgRA?= =?us-ascii?q?DVAkBAQEMAQEYCwoCAQGBKwGDFAIXghAkNQgOAgMNAQEEAQEBAgEFBG2FNwy?= =?us-ascii?q?FUgEBAQMBARAREQwBASwMDwIBCBgCAiYCAgIfBgsVEAIEEyKDAAGCRgMuAQ6?= =?us-ascii?q?jZAKBOIhgdYEygn4BAQWCSYJIDQuCFwMGgQ4oAYUahnuCF4E4H4IeLj6CG0c?= =?us-ascii?q?BAYE2DwUXF4J5MoIsgUABjBiCPI8QjkxBBgSCK4hqiE2EGBuCPodpj22ZFI9?= =?us-ascii?q?AAgQCBAUCDgEBBYFUAzSBWHBQKgFzgU5QERSGRoNzhRSFP3SBKJAOAQE?=
X-IronPort-AV: E=Sophos;i="5.69,223,1571702400"; d="scan'208";a="367650444"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Nov 2019 01:02:33 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id xAL12X7p002198 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Thu, 21 Nov 2019 01:02:33 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Nov 2019 19:02:32 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Nov 2019 20:02:31 -0500
Received: from NAM01-SN1-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; Wed, 20 Nov 2019 20:02:31 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EvfEtEeeY2yXQ93Lf3/doAiG5GaKaMBvjS7PNOFMSWb20JHYb5zktNyDQaGjOA4qcP4pIQIUNolrD7VXim2uMAJ2WcC2nh44yGAdoPYxhSaBZ2/NPjereNs3APGj/XW8Ef5u08kTgIq+6ama3WfaU4utrLot1S5qmTl/RdkzzbhiFaWwcTz2YeY6Jd4Lpn9lUCKzXRgqMqCQxrlksq2BMeREy1pIfdM8Z4t8dXmbtrL0pwwXgYIBK4s7V8ZbjzrX2B3JbKmj+cfpTzQ0htzYzP3+fMMiiXepRXoB3nHxx6urXohPPG+2xeEZTfn1LjeXQQr1oIwryfd99wXMNsdODQ==
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=NZGaNzpFwk2o80r6NQ9lzq7FqssEO6lKPDTrkYkfANU=; b=ZFpizs7VnW5MmtklxngTFoCUuNXiUiledRelfvyQN5taVum5ZvzJliD6kK925QQ6xdOwX90cpDY2C/lKh3vv0x91oT5xih5zWLn5gbqxRbo2gu4h3oI+uDaQs9ENXtxL0cKnnCDVwZshgXDz1WxNkkPmKiu9noq8ZhsQEJstr7da1WTFLEOghLTY+AV2ghAeJsJGaCqqLGIaoIScoMSXM4SMMiJOWfcO52iZNG6uldxQIVrKFQIX/W6z3KDWdiM3RSwnjceykv808jgQRAWE5nvrvbCHXS5xEy6qejiKNwgtgfPlnFdTOUxToZtrxWwEWAoZPRqFsnfKEiIVJkugbw==
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=NZGaNzpFwk2o80r6NQ9lzq7FqssEO6lKPDTrkYkfANU=; b=lPNZ1b5MbSt9h6ownqODaRx9Lye3qTZ9D+8+pUCiS8fjgWIEUnJWzo7I6RIzrTsqVlLYbJOj0IvpIFR4RWz57QIaIVOlhIr9KNiOGG+IPfK9wyfERS5Va1KdbgbDnFmjfNmHbGCSKW5aZBKMtggRSLwPq8+y3TlBkI7LZU0s/dQ=
Received: from MWHPR11MB1359.namprd11.prod.outlook.com (10.169.232.22) by MWHPR11MB1487.namprd11.prod.outlook.com (10.172.53.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.18; Thu, 21 Nov 2019 01:02:29 +0000
Received: from MWHPR11MB1359.namprd11.prod.outlook.com ([fe80::c482:531f:e502:96eb]) by MWHPR11MB1359.namprd11.prod.outlook.com ([fe80::c482:531f:e502:96eb%11]) with mapi id 15.20.2474.019; Thu, 21 Nov 2019 01:02:29 +0000
From: "Li Zhao (liz3)" <liz3@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] DIS for given parent in draft-thubert-roll-eliding-dio-information
Thread-Index: AQHVnpr36jrTS5isFE26D+k2w62PDKeSSFMAgAGmcAD//3+bgIAB6TeA
Date: Thu, 21 Nov 2019 01:02:29 +0000
Message-ID: <2D1D3600-D779-448B-9DCD-919C7E519362@cisco.com>
References: <B1178AE9-ACF1-4B20-AE9E-8F6DC888F3FA@cisco.com> <CAO0Djp0kvHD83YeaGPhVeho1AmxxKfY=F4Cnh-QD+f7nzzPe3g@mail.gmail.com> <D8BE9F9F-A6A7-4454-8696-63EF42BE9E14@cisco.com> <CAO0Djp1G1btbxUO3Po7hi2EMz9-JO1bJ2NLn2o6S68Xh8P6otA@mail.gmail.com>
In-Reply-To: <CAO0Djp1G1btbxUO3Po7hi2EMz9-JO1bJ2NLn2o6S68Xh8P6otA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=liz3@cisco.com;
x-originating-ip: [2001:420:588c:1252:8109:e107:9747:4e8d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9583314e-0311-4f27-0f24-08d76e1e7b46
x-ms-traffictypediagnostic: MWHPR11MB1487:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MWHPR11MB14874B5E1D484C8B4C2D5CBB8C4E0@MWHPR11MB1487.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0228DDDDD7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(39860400002)(376002)(136003)(396003)(53754006)(189003)(199004)(81156014)(8676002)(81166006)(8936002)(71190400001)(71200400001)(91956017)(76116006)(66946007)(66476007)(66556008)(64756008)(66446008)(305945005)(7736002)(5660300002)(14444005)(256004)(6916009)(86362001)(36756003)(966005)(478600001)(33656002)(6246003)(14454004)(76176011)(186003)(53546011)(6506007)(102836004)(476003)(11346002)(446003)(2616005)(46003)(486006)(25786009)(6116002)(2906002)(99286004)(6306002)(6512007)(6486002)(229853002)(6436002)(316002)(88722002); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1487; H:MWHPR11MB1359.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: BCL:0;
x-microsoft-antispam-message-info: hBInbHl8UNqTxaXWqfcmEElQKOHF5y1qYYXKbJa/o7SNsShvhro67ZVyni5PBkck7JA/B3K4VPvJB+pG9quHHvPDyErX6cp8oR5GGPednDuQP5a3NcmrBzCzbSzmtx3yUfgLvsS6+tIWiNccXfX8y/4oOezQkmPmo1vTUpOL00mFmMQ5HGWcW+9y92Ky6Ox5KSouTh2bdjmOeDjxqseh2HPDneM14vIUoRMS+XFrLyvIva+HGbPSaVVAha2TtYgjBliOHR2IS6zwtxJSvOqAZ2DfbfrPCovIQcKm2Yc4mq59w70PsowINrbmY7drvbkx1FwQio3HgL9XcIwVEpEMMAkTqu9py3eLAcFCMjeISfZTG8+2xheTMRyaqNWJA8l9DVnqxzP7QQIEhCDzTLoeslRlyUwCPmiGWHEHtwfphiAJfujxd4S0kPJUfVgqmPaaDORBDzIAPTlgrlC21ymmJo8kOiCnUR6Yc1VnXh5hjN0=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <1CA746A7BFCE5E43ABFA80D76B059851@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9583314e-0311-4f27-0f24-08d76e1e7b46
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2019 01:02:29.1838 (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: afaWLvxumsbIVbshvW2xhVvR3qSIOObm2O7AWTbdAIbbeh5eaNSRSpn4bENO4ZR+
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1487
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/8zFhZF5F-4xxYCrjFT_ufrrELwI>
Subject: Re: [Roll] DIS for given parent in draft-thubert-roll-eliding-dio-information
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: Thu, 21 Nov 2019 01:02:37 -0000

Hello Rahul,

Node can store preferred parent's info when outage. 
But after reboot, it still need DIO from this parent to confirm whether this parent is alive. Because parent may be outage too.
Reset trickle timer can let parent inform all children and accelerate the network recovery. Otherwise, all nodes need to run unicast DIS request and unicast DIO response. It wastes too much of time. 

Does it make sense?

Best regards,
Li


On 2019/11/20, 11:52, "Roll on behalf of Rahul Jadhav" <roll-bounces@ietf.org on behalf of rahul.ietf@gmail.com> wrote:

    Thanks Li for elaborating.
    
    Regarding the warm boot use-case you mentioned, the nodes certainly do
    not know whether they have individually rebooted or rebooted because
    of mass-outage.
    What I don't get is, if the child node already knows who the parent is
    why would it want to reset its Trickle timer?
    
    On Wed, 20 Nov 2019 at 11:31, Li Zhao (liz3) <liz3@cisco.com> wrote:
    >
    > Hello Rahul,
    >
    > This is about " we need other nodes sending DIS to backoff on hearing other node's DIS ".
    > The use case is for warm boot case when hundreds of nodes power outage at the same time.
    > 1. Child nodes send DIS to inform given parent to reset its trickle. (unicast or multicast DIS both work)
    > 2. Child nodes suppress or backoff sibling nodes' DIS. Only multicast DIS works.
    >     And we need enhance Solicited Information option to identify this kind of DIS.
    >
    >
    > Best regards,
    > Li
    >
    > On 2019/11/19, 18:20, "Roll on behalf of Rahul Jadhav" <roll-bounces@ietf.org on behalf of rahul.ietf@gmail.com> wrote:
    >
    >     Hi Li,
    >
    >     What is the use-case where the child node needs to inform the parent
    >     to reset its trickle unilaterally when it already knows the parent's
    >     address?
    >     Please find my comments below.
    >
    >     Best,
    >     Rahul
    >
    >     On Tue, 19 Nov 2019 at 13:34, Li Zhao (liz3) <liz3@cisco.com> wrote:
    >     >
    >     > Hello all,
    >     >
    >     >
    >     >
    >     > As we discussed today, there is a requirement that node sends out multicast DIS to only reset given parent’s Trickle.
    >
    >     [RJ] We discussed today that we need other nodes sending DIS to
    >     backoff on hearing other node's DIS. We also discussed that we need
    >     parent node to not keep on resetting the trickle timer all the time on
    >     hearing DIS.
    >     I am not sure we discussed about sending a multicast DIS to reset a
    >     given parent's Trickle. Or may be I didn't get it correctly. Can you
    >     please elaborate? Thanks
    >
    >     >
    >     >
    >     >
    >     > Can we enhance Solicited Information option to add a flag to identify given parent’s address as following?
    >     >
    >     >
    >     >
    >     >         0                   1                   2                   3
    >     >
    >     >         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    >     >
    >     >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >     >
    >     >        |   Type = 0x07 |Opt Length = 19| RPLInstanceID |V|I|D|P| Flags |
    >     >
    >     >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >     >
    >     >        |                                                               |
    >     >
    >     >        +                                                               +
    >     >
    >     >        |                                                               |
    >     >
    >     >        +                            DODAGID                            +
    >     >
    >     >        |                                                               |
    >     >
    >     >        +                                                               +
    >     >
    >     >        |                                                               |
    >     >
    >     >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >     >
    >     >        |Version Number | Parent Address     (16bytes)                  |
    >     >
    >     >        +-+-+-+-+-+-+-+-+                                               +
    >     >
    >     >        +                                                               +
    >     >
    >     >        |                                                               |
    >     >
    >     >        +                                                               +
    >     >
    >     >        |                -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >     >
    >     >        +-+-+-+-+-+-+-+-+
    >     >
    >     >
    >     >
    >     > P flag: One Bit, indicates DIS request response from given parent
    >     >
    >     >
    >     >
    >     >
    >     >
    >     > Best regards,
    >     >
    >     > Li
    >     >
    >     > _______________________________________________
    >     > Roll mailing list
    >     > Roll@ietf.org
    >     > https://www.ietf.org/mailman/listinfo/roll
    >
    >     _______________________________________________
    >     Roll mailing list
    >     Roll@ietf.org
    >     https://www.ietf.org/mailman/listinfo/roll
    >
    >
    > _______________________________________________
    > Roll mailing list
    > Roll@ietf.org
    > https://www.ietf.org/mailman/listinfo/roll
    
    _______________________________________________
    Roll mailing list
    Roll@ietf.org
    https://www.ietf.org/mailman/listinfo/roll