IETF Logo Mail Archive

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

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 07 October 2019 10:38 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 8AA2212080D; Mon, 7 Oct 2019 03:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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=ekGOQJag; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=t7LtaQYv
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 LEEB5L-HNW0O; Mon, 7 Oct 2019 03:38:02 -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 F121C120052; Mon, 7 Oct 2019 03:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1964; q=dns/txt; s=iport; t=1570444682; x=1571654282; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TKt7t1L4w2hIbBtRai33UWltX1zbOQbAyzjFRcvV8TY=; b=ekGOQJagseq2WgtfiDQ6DFL/iUnZSDJ/PokjYPglzre4Hf+zS/LJcgUR a2pwv3acAmR3T817Z6gRVEgikRtedVsNoSvX0R1UTpHnF1t/DH1w43b7K is1zVtoXvADwHZ4Ic60AwFPezsSGFQYUJXCaiA1ApcV1hUD7chPV1CmMR A=;
IronPort-PHdr: 9a23:XeJVDhcdaDJL4AO5gsOimNsGlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dzA6Ac5PTkNN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BzAAAkFZtd/4sNJK1mHAEBAQQBAQwEAQGBVAYBAQsBgUpQA4FDIAQLKgqEGYNHA4pJgjeYIYEugSQDVAkBAQEMAQEtAgEBhEACF4JCIzUIDgIDCQEBBAEBAQIBBQRthS0MhUwCBBIREQwBATcBDwIBCA4MAiYCAgIwFRACBA4ngwCBawMdAQIBoU0CgTiIYXWBMoJ9AQEFhQkYghcJgQwoAYUVhngYgUA/gTgME4IeLj6BBIZNMoImj22dUwqCIpUYG5k/iWudcwIEAgQFAg4BAQWBUwE3gVhwFWUBgkFQEBSBTxiDW4pTdIEpjyABgSIBAQ
X-IronPort-AV: E=Sophos;i="5.67,267,1566864000"; d="scan'208";a="345632891"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Oct 2019 10:38:01 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x97Ac0Hc016936 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 7 Oct 2019 10:38:01 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 7 Oct 2019 05:38:00 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 7 Oct 2019 05:37:59 -0500
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 7 Oct 2019 06:37:59 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QbID2i2WCPU21qViHxhc5RnQxQDKqqffvdc4tsgWbJquOrtF/uWzR4r+YhAn3wUwHeFR2leMl412QohQF40AiHSO2hIsNTKVG1gvT6QMYNE5WnZdWftQO2WbXer2K2t2vmniOyN8h1dhEGk+mSvSJ0Xk0R1YA2yzvjBES6waQkByi//zFrizuQmToT+pxS6eH+Y3SrQmH+ROLzgGSgDa883gSsQ5ddjDaOvDCf85iBMVsjB/EFofJRhAZg0tbEBwjN95s0kFQGc7yFtqNhweWjTYLZKK75USvNnU5qKWfueKs0LgJvN0aIPTpOSXXVKFj37sTo1/wuJAa8Vi/bpbNA==
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=TKt7t1L4w2hIbBtRai33UWltX1zbOQbAyzjFRcvV8TY=; b=MIjwINCiwUf66zJNrmxZTFigQm/pWuqvKRrMxSbuc0f/aQE+KNF+nuDiboW5vVhMoYFSBi/KP7VkqVRS280QgA8i3lP8L6pS90kfseJ2177Tdbu4WEYrorL31FLdkda8VVzfCNSJssaeBK6Vr96EoJJUv3tA81I9+Z6KJdisE2HehAcSmaYCVuC5MoXY9iNphmjlSssUwkXSOHpjxZQVy6z55IYAqgNU83jYOh8PWR/4efRfocSCycGmrCs1dCP/jTHgDe8nWd+/KCRDQv0w5Av2p8kiGzKSuWzktwaU1rAycRkermnFaeuyoicw9rcbrFY29dJ77UMZp2ikDD5Ozw==
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=TKt7t1L4w2hIbBtRai33UWltX1zbOQbAyzjFRcvV8TY=; b=t7LtaQYvkAD33kZlAU+c9txWOCoHDOc3gafYxWknJssnwVWqbCTxQRPGaXdHpXUdAjkkAf2RYWNIwe++kyFHFdKrZ5S7If5352BAqkGVjui9YfPU9MdBCE3+SbdGQR7loCfaOEbpMlm+lLBh84dcM8jOqMbF5Ljr3E2S8Ay6nDc=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4448.namprd11.prod.outlook.com (52.135.39.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.25; Mon, 7 Oct 2019 10:37:58 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::652e:fba0:4959:7ce8]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::652e:fba0:4959:7ce8%7]) with mapi id 15.20.2327.023; Mon, 7 Oct 2019 10:37:58 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Ole Troan <otroan@employees.org>
CC: Ted Lemon <mellon@fugue.com>, Markus Stenberg <homenet@ietf.org>, 6MAN <6man@ietf.org>
Thread-Topic: [homenet] Support for RFC 7084 on shipping devices...
Thread-Index: AQHVekw77QkRy9Y6CE6R9UtF1+tLladJ+OcAgAAKJgCAAGG4gIAAD5yAgAAGO4CAACobgIADRf+AgAA+NQCAAJWqAIAAQ2OA
Date: Mon, 07 Oct 2019 10:37:58 +0000
Message-ID: <CA2AA8FF-3BC4-4359-A718-93F1FCFAE8DA@cisco.com>
References: <FF34E138-469F-40F6-BA8F-7AE02F878B29@employees.org>
In-Reply-To: <FF34E138-469F-40F6-BA8F-7AE02F878B29@employees.org>
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: 81a1e3c8-d53d-441d-f401-08d74b126b9b
x-ms-traffictypediagnostic: MN2PR11MB4448:
x-microsoft-antispam-prvs: <MN2PR11MB4448EFFDEF4E873B0864EB62D89B0@MN2PR11MB4448.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:489;
x-forefront-prvs: 01834E39B7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(366004)(346002)(39860400002)(396003)(136003)(189003)(199004)(6486002)(316002)(229853002)(86362001)(4326008)(6436002)(6916009)(6512007)(305945005)(7736002)(54906003)(6246003)(256004)(66446008)(64756008)(66946007)(66476007)(66556008)(91956017)(76116006)(478600001)(71200400001)(66066001)(71190400001)(25786009)(102836004)(36756003)(14454004)(6506007)(186003)(26005)(2906002)(99286004)(6116002)(76176011)(3846002)(446003)(11346002)(33656002)(486006)(8676002)(5660300002)(476003)(81166006)(81156014)(2616005)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4448; 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: dyOZk4e26VIBa3IfDMVlfJxyp0kRpnelSbOHPMswLmO2SywjvKACDm2+bxIp+uRkrD3XFaQLDgaqzVjHMd4+wYA+TP5VGozgKS3RC4dBBHq1U39XaCtpKcMpqZ9M+Ifjam2qNm7yabPSJ0wYJyUeri6NlVBBMnglN3PZKaSG2eLCm7JdH6ry3yN3RkrEfMjDGncx4znuHr6kPFPYAhtqvKgp6LylQOxZ0/x7r/qc8sEH7FvqN9AP7n2eGGDSKRZ6D/OTT87/zf2Ep908ilA9sA6W4xa+y8/vT3HLloQRy0PIrA5WJS97BFM4vlJyJFrwxEpUZ+OAop1pz6do8WWQVdFHhJJ2/Snv/p6LPIKRlXEcc/OOgZAWl/J7JPneQz6Z+GKSOE13spkgGHSDnT7AEpFXXmauHak6HA8EUCGyvRw=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <F018F1620175E447A307EF5537BAB8B9@cisco.onmicrosoft.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 81a1e3c8-d53d-441d-f401-08d74b126b9b
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2019 10:37:58.1692 (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: uo4HenOjJF8PIa1wuswk4oS+q45zjAwt16PtVy0b3cxD5J++fmTS8M963ZibCtpXIxVg/GuJjaB1W+7IQK0BjA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4448
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.27, xch-aln-017.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/fLrQk8p4gI5b9m23OzuBZkZqax8>
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: Mon, 07 Oct 2019 10:38:05 -0000

Hello Ole and Ted:

> 
>>> Sounds like you need to set it up as a NAT.
>> 
>> I really hope you are just making a funny joke here.   But it’s not very funny.   What I want is something that’s operationally simple, not something with lots of moving parts that have to be kept track of.   NATs in particular suck for any UDP-based protocol.
> 
> for "permissionless extensions of the network" there isn't much else than NAT.
> Your other likely option is an ND proxy. If you are very sure that nothing else can be added to the network (we don't want to build a spanning tree protocol out of ND).

Agreed that ND proxy is not an alternative for routing. It is a one hop extension around a transit link and nothing more. For deeper ”mesh” extensions there are millions of nodes deployed out there that use RPL quite successfully.

The design allows to combine the 2 with a high speed backbone (Ethernet) and RPL meshes ganging off ND proxies. 

But inside a subnet RPL is used to route to hosts so there is no subnet assignment just SLAAC or DHCP. Still those networks scale to ~ten thousand. Good enough for home for a long time. 



> 
>>> I wasn't thinking of doing it exactly like the 6lowpan does it.


Too bad then... I still fail to see why the model cannot be generalized to more powerful nodes.

Anyway a transit and one level of proxy already takes us a long way.

All the best,

Pascal
>

v2.23.0 | Report a Bug | By Email