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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 26 September 2019 08:48 UTC

Return-Path: <alexandre.petrescu@gmail.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 BAE8512083D for <ipv6@ietfa.amsl.com>; Thu, 26 Sep 2019 01:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.131
X-Spam-Level:
X-Spam-Status: No, score=-2.131 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, GB_ABOUTYOU=0.5, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 EeuTHWAsFpEU for <ipv6@ietfa.amsl.com>; Thu, 26 Sep 2019 01:48:17 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 225CD120823 for <ipv6@ietf.org>; Thu, 26 Sep 2019 01:48:16 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8Q8mFDA047513 for <ipv6@ietf.org>; Thu, 26 Sep 2019 10:48:15 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 34A74202EAE for <ipv6@ietf.org>; Thu, 26 Sep 2019 10:48:15 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2A9B3202E8F for <ipv6@ietf.org>; Thu, 26 Sep 2019 10:48:15 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8Q8mFVt015749 for <ipv6@ietf.org>; Thu, 26 Sep 2019 10:48:15 +0200
Subject: Re: On the "IPv6 Neighbor Discovery on Wireless Networks" draft
To: ipv6@ietf.org
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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <2f66dc85-6e2b-86cb-b313-8370e150ea1c@gmail.com>
Date: Thu, 26 Sep 2019 10:48:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB35655A163B6BEC12919C61D8D8860@MN2PR11MB3565.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/S50n9RVAobdnA2pZBZ9J9j57nGA>
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 08:48:20 -0000


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
> --------------------------------------------------------------------
>