RE: Wireless ND was: about violation of standards

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 29 April 2019 11:08 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA6FA1202FB for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 04:08:58 -0700 (PDT)
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=d03+gPvp; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=SShtft61
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 AP71KdRgK0Ek for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 04:08:56 -0700 (PDT)
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 8B4C412008F for <ipv6@ietf.org>; Mon, 29 Apr 2019 04:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2572; q=dns/txt; s=iport; t=1556536136; x=1557745736; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=S1MaQWpl8tuxl3/YL2tcXgo2nehhhAhUcEPOT5iBy00=; b=d03+gPvp+u7MktRNlhs1zUTqT2E5ULV/5zHNd+2yTwQ3zs/m3pkn/m4B /PzIyDqP3AAibn/+gJXTG7AuVL9dn2GNBq8s55XPQ8yF7UBTAlt2zf7Yd slBiLU5uBz2OFNQXR1hJcksUivCU2gianhAO4sc21KdoVq6vg/z0gabkU E=;
IronPort-PHdr: 9a23:OSltxBfWWGzdnW4YIaehSTODlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dzA6Ac5PTkNN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AIAADs2cZc/4UNJK1mGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBPVADgT0gBAsoh1cDhFKKO4JXlyKBLoEkA1QOAQEthEAChjIjNAkOAQMBAQQBAQIBAm0cDIVKAQEBBBIoBgEBNwELBAIBCA4DBAEBHxAyHQgCBAENBQgahGoDHAECoiECgTWIX4IggnkBAQWEehiCDgmBMgGEYYZoF4FAP4ERRoFOfj6ERoM6giaLM5tICQKCCZJOgg2GNINoiH6MDZRNAgQCBAUCDgEBBYFPOIFWcBWDJ4IPg2+KU3KBKZMRAQE
X-IronPort-AV: E=Sophos;i="5.60,409,1549929600"; d="scan'208";a="264267720"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Apr 2019 11:08:55 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x3TB8tvV011733 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 29 Apr 2019 11:08:55 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 29 Apr 2019 06:08:54 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 29 Apr 2019 06:08:54 -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; Mon, 29 Apr 2019 07:08:54 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iT1Pn+MnkSLxJNL3iWhFj9JJ2XrMrKfRhLq9oQtQBBs=; b=SShtft61ca3OMIR6cFmbOlekBMFfC9Ouc7DVsTVdCivAT97rDgiY3fG85S5xD+QsjUsmO6jVq+Qiwdih3p3BgURkCET/xSgS8qbnE4H0b4A8UT/9fiJ7MwPJb43D3ApgsY4yTMvd2LcGe5t/rZlxjuYk1kNWbeVLzARFEOdCMB8=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB3600.namprd11.prod.outlook.com (20.178.251.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1835.14; Mon, 29 Apr 2019 11:08:52 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::68f6:21c8:b681:c73]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::68f6:21c8:b681:c73%4]) with mapi id 15.20.1835.010; Mon, 29 Apr 2019 11:08:52 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Ole Troan <otroan@employees.org>, Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: Wireless ND was: about violation of standards
Thread-Topic: Wireless ND was: about violation of standards
Thread-Index: AQHU9hjz0VelQW2CM0S4qjQG7Nm8iaZCZ5mAgAAz6wCAAAwogIAAZyaogAZSawCAABw6IIAAFwgAgADV+ICAAESpAIAAGoiAgABMtvCABtsXeoAA9UYAgAAidqA=
Date: Mon, 29 Apr 2019 11:08:38 +0000
Deferred-Delivery: Mon, 29 Apr 2019 11:08:23 +0000
Message-ID: <MN2PR11MB35658F481A58E4F78D5B6648D8390@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <bb7f7606-2adf-e669-8bcd-e41f17800782@gmail.com> <CAJE_bqd9frqX5-yeVPj8MYXpZ4737HqK1gmfD9cQV3A-Ea5HrQ@mail.gmail.com> <6bd5db47-408a-727e-5c13-f34a3465f986@si6networks.com> <CAJE_bqfTLqRbLp4fLu2ASZuZ+4G5c2G+RXkO92kXfLgPTqBnng@mail.gmail.com> <EEF00EA7-2AAF-403F-99AD-1D53ED18E8B3@cisco.com> <47631828-121F-402D-8165-969684C1101B@employees.org> <MN2PR11MB35655B36540829AEE5275964D8230@MN2PR11MB3565.namprd11.prod.outlook.com> <1066F69A-824F-4D6D-B221-8EFBAD15E15A@employees.org> <018c407a-b127-8724-d1ee-e19e3b084a60@gmail.com> <CABNhwV1jWHc1SMm=-xX0Oo5V4bo4VQBeQ5-CztJhP3y9006HRw@mail.gmail.com> <alpine.DEB.2.20.1904240659270.3490@uplift.swm.pp.se> <602A5CC5-170D-4E67-8907-A4D26606DB03@cisco.com> <m1hKoNd-0000IQC@stereo.hq.phicoh.net> <36910145-BFD1-40D6-B62A-B8EC70B692F6@employees.org>
In-Reply-To: <36910145-BFD1-40D6-B62A-B8EC70B692F6@employees.org>
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:c0c0:1007::1d9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9749f4c6-8343-4190-801d-08d6cc93107d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR11MB3600;
x-ms-traffictypediagnostic: MN2PR11MB3600:
x-microsoft-antispam-prvs: <MN2PR11MB3600830816A401A60C8BF188D8390@MN2PR11MB3600.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0022134A87
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(366004)(396003)(39860400002)(136003)(199004)(189003)(13464003)(46003)(256004)(14454004)(2906002)(33656002)(86362001)(14444005)(4326008)(93886005)(6436002)(7736002)(66476007)(76116006)(66946007)(66556008)(64756008)(66446008)(476003)(73956011)(71190400001)(71200400001)(229853002)(102836004)(11346002)(186003)(76176011)(74316002)(97736004)(6506007)(4743002)(53546011)(446003)(6666004)(25786009)(305945005)(53936002)(6246003)(68736007)(486006)(9686003)(52536014)(6116002)(55016002)(110136005)(81166006)(81156014)(316002)(7696005)(99286004)(478600001)(5660300002)(8936002)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3600; 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-message-info: ScQZyIV5TPZASqmqoTKoRJMyK2cyjNcRDQ/5HTVpZ4COy/gqPsiBbxZr9Bqgd9Lt65Oluxms6fbxPQqaXfm7BzbrDt9w8H8q7Ebxx2GvapWn5UBoVeyvvK7wJJvkk8iQTobMmbPsepDPhfzR0B/n0AwzLtlr0WFO1M5AUwAwShq/0Ai7dcn8TVwo6UZpL7iDI7U0Q6VNsJml/R3SVu+aFiCs8nvjVXddNS//Tx9Ekp8q0l2X3liPC+IAl9Qq5DGmdNdRbzMrpOVih2MKJ/nCxrvuuo/pyXC2k+22wMP1h+7j3ccCAJb2XokT618i+5ZXyOVKFkFVELBIIwZ92GlIwc6VQnZheRPO4+gh5i6MG6A1z8bOXaohGSrgQ5akIH+qTNW+dpwfFcCfGNJs5i3ac1bJkWHxJZs+ziXtcfGRk9U=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9749f4c6-8343-4190-801d-08d6cc93107d
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Apr 2019 11:08:52.7612 (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-Transport-CrossTenantHeadersStamped: MN2PR11MB3600
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bUrgSbj8Eokik2LyChDZLT_zOE0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 11:08:59 -0000

Hello Ole:

Yes, that's a starting point. I have an answer  on the works but it urned out taking more time than I thought. Will post soon now.

Bottom line is a big ask to 6MAN. Please forget about FR and ATM, and do not use that as a pre-conceived system for wireless. Numbers are different. Links come and go all the time even in fixed deployments. Which can be damn large. Even today. 

Also, if people wish to discuss whether P2P subnets was good enough for FR or whether the NBMA and P2MP models you could find there (e.g. Proteon and IBM) are useful, please use another thread. I may discuss there for the sake of fun and old days - I was on the IBM side at the time. But that thinking is not applicable to wireless and IOT, clean slate.

All the best,

Pascal

> -----Original Message-----
> From: Ole Troan <otroan@employees.org>
> Sent: lundi 29 avril 2019 10:57
> To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
> Cc: 6man WG <ipv6@ietf.org>; Pascal Thubert (pthubert)
> <pthubert@cisco.com>
> Subject: Re: Wireless ND was: about violation of standards
> 
> >> I started an informational draft for 6MAN on WiND (wireless ND) to
> >> explain what physical models it serves and how it can be used over
> >> several MAC layer abstractions.
> >
> > I read draft-thubert-6man-ipv6-over-wireless-00. I quite like the
> > description of the issues with wireless media.
> >
> > There is however one thing I miss: The abstract says "This document
> > describes how the original IPv6 Neighbor Discovery and Wireless ND
> > (WiND) can be applied on various abstractions of wireless media."
> >
> > I'm also interested in *why* WiND should be applied. In particular,
> > Figure 2 shows a complex multi-layered setup.
> >
> > So my question is, why not use routing and keep subnets restricted to
> > one link?
> >
> > I hope there is a clear set of arguments why routing is not sufficient.
> > Right now it reads too much like a primitive routing protocol on top of ND.
> >
> > Another issue that often shows up with registration based systems
> > (such as quite common with IPv4 and wireless) is what happens if a
> > host has more addresses than supported by the registration system?
> >
> > I.e., it might scale better to have lots of point-to-point links and
> > prefix delegation than to have a single big subnet and a hierarchical
> > registration system.
> 
> That was my thinking too. If you have a set of p2p links, you don't need very
> little of ND.
> 
> Cheers,
> Ole