Re: [homenet] Support for RFC 7084 on shipping devices...

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 10 October 2019 17:26 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2853B120115; Thu, 10 Oct 2019 10:26:13 -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=FdHyhSfh; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=x753HZy+
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 4f2o8sUojcfJ; Thu, 10 Oct 2019 10:26:11 -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 0991B12010C; Thu, 10 Oct 2019 10:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6697; q=dns/txt; s=iport; t=1570728371; x=1571937971; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=l2phyQZbbVIBgsQjf38TSwXbAb4mG32m8Hgq2zaJ+MU=; b=FdHyhSfhV0XBSanSInnvuA2htXu6fAGeaDOXSGSCM1HgNmUDqO8ejV+G DUBYR2QozfYj3XmsJ3KueTk1Kxdb6MZ8u5hESI/X/9Jwi3rqSyRfg762A eRKmHI2eFEjNX0+slT50hipP6B3Ighz+eF/sWY6xthlhF4RbzxAqdCNZv w=;
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Oct 2019 15:58:30 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x9AFwSLv014859 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 10 Oct 2019 15:58:28 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 10 Oct 2019 10:58:28 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 10 Oct 2019 10:58:27 -0500
Received: from NAM03-DM3-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; Thu, 10 Oct 2019 10:58:27 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z//FM6IN/5hchvIZ844+j7e0ApVxcn4K61CKtChsHZRLD7rojQEhgx+XPUCtz01NmjkJDh0C1Heu0V0TJS4+1rHB5G9JW8qs7++AVizJHUo7MTxrNxIAc1/n1wsJRuqoCLKNSMNW9Wo92NUeGPsqUtAIJPXSrmM2Vxy+csvNrhxxyym9sZ7FjylOKFnfhKXcjta9wrhB+PdtDGmzveagRtmoLIYIVFEqKYwKdewc5plJHnOJi6ZSBdkMc7wYalPPc9YTNXTAi18NZwwB4K95HGb45s5jPqH8emgbvvNu+vLeFftKWcz1qwcnLETeNJupgRHfpfEgNSZrbCn2TJnN4w==
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=Sb94ibkwXW/RXm9ysL6xE8j1MdadrZkM3tJt0bTXI6c=; b=bdDkbHAAOgR33lg577bIMwwx7sSHOkZTJJEdv50bwGAMbeSYk3K9iY7RclhGjCcISAKmsLqSKSdecR4fltwVX1EPqxTRbekTbRJ81DTfbMPpMOapAJ6fTanKNgoxnaFL1bWRLSU5dqkipTdLE6U2Xmr3UPv92J1PbJcWzcETWewvAh56xXQnGOyssauIsd5nMuKr2H2ktkABelmkyV/oRkdc7PcQk4x2T1V2EhV81oE8oxvpGGb0e+zam/ZwHqg0LSuPBq3Sppb2ndX3IAwg63c3H6QywwwBvwhvhQF1hbVEO7Mv5ukEYszzDnxLU3etc/v/G1ehoHrYOIOXqpdxgA==
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=Sb94ibkwXW/RXm9ysL6xE8j1MdadrZkM3tJt0bTXI6c=; b=x753HZy+HYFPYzN1uGCc4VHj0Imp8fSmDIlocQCaTWaF54c6HPoonEolfm8cD1Qg79UVCXOQ9mgr7IlWUznVTFVu71TxFM2R1ar+p7REqMGw99ixhI0zQjRvO6zArIWae6/hT6aQP8ybiXbDNiuYHXwLyLWEeyBL0yrGtCp2KYY=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3743.namprd11.prod.outlook.com (20.178.253.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.16; Thu, 10 Oct 2019 15:58:26 +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.2347.016; Thu, 10 Oct 2019 15:58:26 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Ted Lemon <mellon@fugue.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, 6MAN <6man@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: [homenet] Support for RFC 7084 on shipping devices...
Thread-Index: AQHVekw77QkRy9Y6CE6R9UtF1+tLladJ+OcAgAAKJgCAAGG4gIAAD5yAgAAGO4CAACobgIADRf+AgAA+NQCAAJWqAIAAQ2OAgAAvS4CAABSWAIAAA3FwgASiYQCAACRrUA==
Date: Thu, 10 Oct 2019 15:58:23 +0000
Deferred-Delivery: Thu, 10 Oct 2019 15:58:04 +0000
Message-ID: <MN2PR11MB356515B07CC7A9BB19C9A440D8940@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <FF34E138-469F-40F6-BA8F-7AE02F878B29@employees.org> <CA2AA8FF-3BC4-4359-A718-93F1FCFAE8DA@cisco.com> <AF4ECDF2-FD9D-4178-BDF1-A3C87A4D1DBE@fugue.com> <8808.1570459254@dooku.sandelman.ca> <MN2PR11MB3565DA20AEB5A82B75BBB315D89B0@MN2PR11MB3565.namprd11.prod.outlook.com> <4BF68CC7-2788-4029-B88E-6CD6D8D31A43@fugue.com>
In-Reply-To: <4BF68CC7-2788-4029-B88E-6CD6D8D31A43@fugue.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:c0c4:1001::233]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2e6bcd13-856b-4658-a853-08d74d9aafad
x-ms-traffictypediagnostic: MN2PR11MB3743:
x-microsoft-antispam-prvs: <MN2PR11MB37437BDDF8B7F2C8550B3D71D8940@MN2PR11MB3743.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 018632C080
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(376002)(366004)(39860400002)(136003)(346002)(189003)(199004)(6916009)(76116006)(66476007)(53546011)(6506007)(66446008)(66556008)(66946007)(25786009)(186003)(102836004)(446003)(46003)(71200400001)(71190400001)(11346002)(486006)(476003)(64756008)(86362001)(33656002)(76176011)(55016002)(7696005)(2906002)(74316002)(790700001)(99286004)(54906003)(256004)(6116002)(7736002)(81156014)(81166006)(6246003)(6666004)(52536014)(8936002)(14454004)(8676002)(229853002)(5660300002)(316002)(478600001)(236005)(9686003)(54896002)(6436002)(6306002)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3743; 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: BCL:0;
x-microsoft-antispam-message-info: gDKiL+5Mx6NF7ZInlWGu3T1jRynM2+X0ni/wB9mF4Sha61y9XVIqNUq7B1opgNyEsadJ/vuOFsE/1Nlj/d4UCPKJjWlmI1zYnSarydg7PFI7xogW2bDLwrbYNaViLMH9toML9uXGJuWnSv+IdF8RQhjgFm2+otRAr7WO/6rEdrTYq5CikXnQltzy1ELKbbwA8ByYFZ5g8z8/0VEBkJbB0VldBv9tsYurqZZg0/skbSrzTUJOAKpeDWapzMuAXQzc6+aw/6p3GOqrfBMP1Fxcy1lFuoPV+pqngAk+NmWOuGSXCylUXYiTFfjBpElSHGmZHurFU1cqeYCjcCoNgCG/TxM4lP23xiTWrqresMkw5rYr+K/lIa0FQ0f3BePxj0LDR6hKd0w5jm7kFbfQGj/s1MECwLNBfdcltQmzu6JmU9c=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB356515B07CC7A9BB19C9A440D8940MN2PR11MB3565namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2e6bcd13-856b-4658-a853-08d74d9aafad
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2019 15:58:26.1651 (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: QB8sgERJnK+lGd+mCpBzqH+7Q+ndyHz30QCJc4iLYEThvvsp9ZiiWbtJz5uZ89qVhZJrMeIGIYz/PeKBHpFs8Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3743
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/YPpv8pX0PltR_YZTxig7oT_A008>
Subject: Re: [homenet] Support for RFC 7084 on shipping devices...
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 17:26:13 -0000

Hello Ted

I do not have stats that I can expose, sorry for that, but switching parent is relatively frequent. Switching DODAG happens more often that we'd like. Either way there is nothing manual and the management is not involved. RPL handles the routing but if the other DODAG is a different subnet the node that moved needs to renumber and that is multiple round trips.

RPL is a form of L3 spanning tree when operated inside a subnet. There are advantages in forwarding at L3 within the subnet, e.g,  TTL to avoid meltdown and NECM...

Cheers,

Pascal

From: Ted Lemon <mellon@fugue.com>
Sent: jeudi 10 octobre 2019 15:39
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>ca>; 6MAN <6man@ietf.org>rg>; homenet@ietf.org
Subject: Re: [homenet] Support for RFC 7084 on shipping devices...

On Oct 7, 2019, at 10:58 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
As you indicate, a single mesh can approach 10^4. A depth can be al lot more than the 10 hops that we imagined initially. Yet it keeps working.

How frequently do things change in the mesh?   Does this require any management to set up?