RE: On the "IPv6 Neighbor Discovery on Wireless Networks" draft

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 26 September 2019 14:46 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 F3A2E1208D2 for <ipv6@ietfa.amsl.com>; Thu, 26 Sep 2019 07:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14
X-Spam-Level:
X-Spam-Status: No, score=-14 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_ABOUTYOU=0.5, 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=cBM5r3nn; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=KDtGTuKi
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 89BIUpSZV1Fk for <ipv6@ietfa.amsl.com>; Thu, 26 Sep 2019 07:46:29 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17A1A1208CF for <ipv6@ietf.org>; Thu, 26 Sep 2019 07:46:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6782; q=dns/txt; s=iport; t=1569509189; x=1570718789; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ITIK10Y1+so7o/moIoh52BE6koA9FZVmij8+soqBp+s=; b=cBM5r3nnsx6N7v8bmLMdHhiBP7s3Yz9zMDq+cRY4cODxfwPo6lYJEZO9 Pp+Wd1SnEgYhQ79a+T18XEaNOMCsPzuU45oIjMNGEGyq9Jw9AWDG118v8 MJcZMUmFH6SunVRD5HiIq7JETlMGL3d47P7Ir0Pqk0q7F/6iW8VXiaNA8 c=;
IronPort-PHdr: 9a23:6GNABhweulieuzTXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZudFU3mJvPwcwQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DnBwCDzoxd/5pdJa1cCh4BBhKBXAuBS1ADbVYgBAsqhCKDRwOKeE2CD5d2gS6BJANUCQEBAQwBARgLCgIBAYRAAheDGiM1CA4CAwkBAQQBAQECAQUEbYUtDIVLAQEBBAEBEBERDAEBBScCCgsEAgEGAhEEAQEDAiYCAgIlCxUICAIEARIIGoMBgWoDHQECDJNBkGECgTiIYXOBMoJ9AQEFL4EIAoNQGIIXAwaBDCiBWooyGIFAP4ERRoFOfj6CYQEBA4EdFg8eFYJ0MoImjHMEgmWOVI5pCoIihwWFFIkNmTSOIIgXkQYCBAIEBQIOAQEFgVMBNoFYcBU7gmxQEBSBToNyhRSFP3SBKY1oAQE
X-IronPort-AV: E=Sophos;i="5.64,552,1559520000"; d="scan'208";a="333242584"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Sep 2019 14:46:27 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x8QEkRpv027300 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 26 Sep 2019 14:46:27 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 26 Sep 2019 09:46:27 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 26 Sep 2019 09:46:26 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 26 Sep 2019 09:46:26 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WZB+D0hQ40jGIT/vCJmUObVQpRNwr/nqHpc0asy/e+iW4PoEA8XKET5+fxLfj2j1jdNmdqdhu2tnYot+6/fQQhRmx4D5Zscoq0zrdBduFY+Fjj77ASJQ4ycEk4/oodJSSc0nGUpUSAyyI1vjCpwtAg0Fp/KsQi84m1bt+slIG7pbteSsvX7QNY1dpvJJTxYD3tHk/lG6QxtEaIhUufTctbsFXliphVvdfeUcFjdV0phTLKziXA/PzFG5658Ntf37jxN1jaVrKTx+SJalm2yBHaLbFIENb6SK07IBGPm1heghcfplMtB25wtjHVwgepIrG1MeHCkqm9MhJtYUtE/PxQ==
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=ITIK10Y1+so7o/moIoh52BE6koA9FZVmij8+soqBp+s=; b=nNIG3qCdeN2n+FUrxxHAsUNyFh4Q8vqeDsQMypKPxp3IyWkB8YzIOAtESDUEoPkf2HXTQxorwoX0tU4ftobegbinDDE9pmOxH7Jgs8Gd5fCSSrZpmcu5QAs4hXR6yGX+sKZBmnXyvxaDxw4Ncncacsd6kzrBSjzD8ndLzHT3iaIkSIsaKgmKChTgAKlmcmnS9WshUsnGZR++Or3kzXH1X3oIl5l2EA8T7skh88pcf0b1ul0xFnx0H+wBUKYpSS9/a9D5tU/q8BX29zPt+bObHRAMtVGMC76yq02ID3Lzycg2X7LWlE9r3SMcpc2RBMpRxSZNoXcsPVDmuMtrC9+Lag==
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=ITIK10Y1+so7o/moIoh52BE6koA9FZVmij8+soqBp+s=; b=KDtGTuKidY/E91R+KYsGbvVwR49h/O909UMAq1SS6v0gV14aUjrgDyuPTpwh4aj8z+a4fhzeFheGTa2wsFFeg4ZG2LRcfNxKoZa0I7zIMBuZaBQOTSNnl4xGoUhlVYW1JOzvkAJdEDJ2bnXWA0/o/CExbWISz6Nfsz73OzGobMY=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4334.namprd11.prod.outlook.com (52.135.38.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.21; Thu, 26 Sep 2019 14:46:25 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::6986:12d5:b54f:f5ee%7]) with mapi id 15.20.2284.023; Thu, 26 Sep 2019 14:46:25 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: On the "IPv6 Neighbor Discovery on Wireless Networks" draft
Thread-Topic: On the "IPv6 Neighbor Discovery on Wireless Networks" draft
Thread-Index: AQHVcxvz5eR/cQ9o+kiP4ArBTinnBqc8GseggADC3oCAAMAEQIAACmSAgABiDcA=
Date: Thu, 26 Sep 2019 14:45:56 +0000
Deferred-Delivery: Thu, 26 Sep 2019 14:45:44 +0000
Message-ID: <MN2PR11MB3565FB1F92C0FEA60BAF8300D8860@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CAMugd_WKZd3w1j=gK_-mRceqc_b+9cmvVMHNNb=f98ZPauQ64A@mail.gmail.com> <MN2PR11MB3565B4515050248AAAA8F68BD8870@MN2PR11MB3565.namprd11.prod.outlook.com> <cd05fd34-4026-c99e-0c3c-bf8b069d994d@gmail.com> <MN2PR11MB35655A163B6BEC12919C61D8D8860@MN2PR11MB3565.namprd11.prod.outlook.com> <2f66dc85-6e2b-86cb-b313-8370e150ea1c@gmail.com>
In-Reply-To: <2f66dc85-6e2b-86cb-b313-8370e150ea1c@gmail.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:c0c0:1003::1d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 68a295a6-cb31-4308-8183-08d742904e56
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600167)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR11MB4334;
x-ms-traffictypediagnostic: MN2PR11MB4334:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4334E4BFDFA637ACAE1290B0D8860@MN2PR11MB4334.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0172F0EF77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(396003)(346002)(366004)(39860400002)(136003)(43544003)(13464003)(51444003)(189003)(199004)(6116002)(486006)(478600001)(966005)(316002)(14454004)(66946007)(25786009)(66476007)(66556008)(64756008)(66446008)(2501003)(6506007)(76176011)(6666004)(53546011)(99286004)(8676002)(76116006)(81166006)(81156014)(5660300002)(7696005)(8936002)(2906002)(71200400001)(6306002)(66574012)(6436002)(46003)(6246003)(55016002)(186003)(71190400001)(256004)(14444005)(110136005)(9686003)(102836004)(86362001)(229853002)(446003)(305945005)(7736002)(74316002)(11346002)(33656002)(52536014)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4334; 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: I3AEFCSSqCLAQ8P5sKlKRN05VpvMmER+V0Te5aiG/NZ7A7OA83lbBwsY63yF6as5Ba5a6LyjOgFhIkY3J8h9X9HZTbhYER6w/kqWornQMeYHsFPjWII29teaOlgRAzCR2mt1KyqaySUv7fShZ/sOQGdL4TmTpRrW0Gmv23FeuGm75fYIbn3EWJR6rJ1Nj3+y5haCgTr2Zm2fX1X7vD7iFima+zSKQkJWh97NxCTfW0Qnx5EGJ9rhq1URD6HZExqZ9ONyDMEle0IoXxQD1TU+wPqAmZCuaUJMcW+M94pzYamzr+b+Sn07zIyJOYmukEfHsQUQ81Z7qdoqckuYUG/t8Joc4g5Uz9yAvLIRkdoAJBSPC1f8J5E1JsQlTGcOJ5lzCWg+DfKvdUiXkLVxFQ4Db+ZDSMJtsPIL5txPelWASS0QBbLJC/baWpvWTf3J7/nA9sMNXfAdOLUZYoHUu55lRA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 68a295a6-cb31-4308-8183-08d742904e56
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Sep 2019 14:46:25.1741 (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: qL6UbpoJ5+BDQtF9lUrZVUxb/z30THhd+EKGCDtv5YWHeLoO0/fHx+bWxAx2IPKuGWZAZGrukSqrSKq/l+24fA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4334
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.30, xch-aln-020.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/yyq5dgEpgR9sBqQvIA8uTMflT-I>
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: Thu, 26 Sep 2019 14:46:32 -0000

Very interesting reading Alex.

The part I'd be most interested in is the amount and ratio of wireless bandwidth (air time) and of battery that's wasted, e.g., receiving L2 broadcast packets when the node is not a L3 destination of the multicast message. It is  aknown problem but we do not have a good panel of experimentation with results like: amount of such messages per unit of time in various situations, average transmission time (PHY speed) in different cases like e.g., home, SoHo, coffee shop, mall, large conf, IETF plenary. 

I think that ND vs. ARP is not even battery wise; I'm afraid that IPv6 is a lot worse.

All the best

Pascal


-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Alexandre Petrescu
Sent: jeudi 26 septembre 2019 10:48
To: ipv6@ietf.org
Subject: Re: On the "IPv6 Neighbor Discovery on Wireless Networks" draft



Le 26/09/2019 à 10:36, Pascal Thubert (pthubert) a écrit :
> I've observed that my phone depletes much faster at IETF than at home,

smartphones deplete faster in areas surronded by concrete (large 
hotels), where no indoor cellular repeaters are present.   And also in 
trains, cars, plains and in tunnels.

To make statements about ND multicast guilt part of this fast depletion one would need to identify it precisely.

Remember that smartphones deplete faster on IPv6 than on IPv4, as we identified and reported in draft-petrescu-v6ops-ipv6-power-ipv4-00.txt

Alex

even with the LTE off. We are collectively guilty of that situation by our failure to adapt so far. It is high time 6MAN considers the IPv6 over wireless problem more seriously, starting with the basic building block, IPv6 ND, and RFC 8505 is a good place to begin.
> 
> Take care,
> 
> Pascal
> 
>> The root of my work on RPL was actually for cars, if you’re aware of the nested NEMO problem. RPL optimizes the amount of control at the expense of a routing stretch when not talking to the root. This is good for lower power nodes because it saves energy. But this is also great for mobile nodes such as cars that really over one another to reach the internet, because RPL filters out what they do not want to know like which are all the other cars, what topology is built to reach out, and all the mobility that takes place between them.
>>
>>   
>>
>> Many tahks again for you excellent comments : )
>>
>>   
>>
>> Pascal
>>
>>   
>>
>> *From:*ipv6 <ipv6-bounces@ietf.org> *On Behalf Of *Nabil Benamar
>> *Sent:* mardi 24 septembre 2019 23:06
>> *To:* ipv6@ietf.org
>> *Subject:* On the "IPv6 Neighbor Discovery on Wireless Networks" 
>> draft
>>
>>   
>>
>>
>> Hi Pascal,
>>
>>   
>>
>> I would like to ask you some questions about your interesting draft.
>>
>>   
>>
>> 1- You say " But in reality, IPv6 multicast
>>
>>     messages are typically broadcast on the wireless medium, and so 
>> they
>>
>>     are processed by most of the wireless nodes over the subnet 
>> (e.g.,
>>
>>     the ESS fabric).
>>
>>   
>>
>> most, some or all nodes?
>>
>>   
>>
>> 2- In the text you mentioned IEEE 802.11p. You need to replace it by IEEE 802.11-OCB since the 'p' is no more used by IEEE and it has been replaced by OCB.
>>
>> See 
>> https://tools.ietf.org/html/draft-ietf-ipwave-ipv6-over-80211ocb-52
>>
>>   
>>
>> 3- I think there are some duplications in the text about the fact that "....
>>
>>     in all the cases in this specification, the Layer-3 multicast
>>
>>     operation is always a MAC_Layer broadcast for the lack of a 
>> Layer-2
>>
>>     multicast operation that could handle a possibly very large number ofgroups in order to make the unicast efficient.."
>>
>> Already mentioned in the introduction section.
>>
>>   
>>
>> 4- You mentionned the example of cars using RPL (Route-Over MLSN)
>>
>> I think that cars do not belong to LLNs category.
>>
>>   
>>
>>   
>>
>> Yours.
>>
>>   
>>
>> Best regards
>>
>> Nabil Benamar
>>
>> -------------------
>>
>> نبيل بنعمرو
>>
>>   
>>
>>   
>>
>>   
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------