IETF Logo Mail Archive

Re: [v6ops] new draft: draft-yc-v6ops-solicited-ra-unicast

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 21 July 2015 14:09 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 843081B2E65 for <v6ops@ietfa.amsl.com>; Tue, 21 Jul 2015 07:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 PpQLGecAVUE7 for <v6ops@ietfa.amsl.com>; Tue, 21 Jul 2015 07:09:25 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BB641B2E4C for <v6ops@ietf.org>; Tue, 21 Jul 2015 07:08:51 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t6LE8oia027397 for <v6ops@ietf.org>; Tue, 21 Jul 2015 16:08:50 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2A2252023BD for <v6ops@ietf.org>; Tue, 21 Jul 2015 16:12:24 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 228D52020D9 for <v6ops@ietf.org>; Tue, 21 Jul 2015 16:12:24 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.35]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t6LE8n6l001645 for <v6ops@ietf.org>; Tue, 21 Jul 2015 16:08:49 +0200
To: v6ops@ietf.org
References: <201507071147.t67Bl13m009348@irp-lnx1.cisco.com> <CAO42Z2x7mNFbB_w_+W+80pY+LeCAKXaOBXMmQvkcaMSWhwW60g@mail.gmail.com> <EF21B630-5D0A-415A-A93F-9058900CC80C@cisco.com> <CAO42Z2zAqMXhBZ2wa=q0wtHGhMpMWU9TSjfFyd2quiki9w0oSw@mail.gmail.com> <85CADAA2-8DF2-4A6B-812B-7A77081936F5@cisco.com> <CAO42Z2w3fOxGJHasKqYZRfGZ2u=7FnZBm+jgLtgDvfZ7HYW=iw@mail.gmail.com> <CAO42Z2z+DwOin23HQTysrZ9dNP924+LQ-vOExmJc_xZUEB4yCQ@mail.gmail.com> <228248C6-94FE-4C9C-A875-F732EFDC6601@cisco.com> <331D6E02-167D-4E7F-9682-F63C6674BD24@gmail.com>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <55AE5270.8000301@gmail.com>
Date: Tue, 21 Jul 2015 16:08:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <331D6E02-167D-4E7F-9682-F63C6674BD24@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/ezRLCx2GIdkdOhH-7nK4thyXeHA>
Subject: Re: [v6ops] new draft: draft-yc-v6ops-solicited-ra-unicast
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 14:09:28 -0000


Le 17/07/2015 18:57, Andrew Yourtchenko a écrit :
>
> On 17 Jul 2015, at 09:34, Fred Baker (fred) <fred@cisco.com> wrote:
>
>>>
>>> So the next logical thing to do would be to have the router default to
>>> unicast Router Advertisements, measure the rate of received Router
>>> Solicitations, and switch to multicast RA mode past a certain
>>> threshold to cover this sort of situation. Once the number of RSes
>>> falls, it switches back to unicast RA mode.
>>>
>>> That would get rid of the configuration knob proposed in this ID, and
>>> is behaviour that I think could be universal for all link types,
>>> rather than just for the case of wireless ones with mobile devices.
>>
>> If it were me implementing it, I think I would go about this in a little different way, hopefully simpler. I would want to send at most one (e.g., either zero or one) RA per some interval (a second?). In the normal case, that is sent unicast. However, having sent a unicast RA at time t, if I now receive another RS before t+1, I send the next one (at time t+1) as a multicast.
>
> values of T less than 3 seconds would make performance worse than today.
>
> There are many things to optimize for:
>
> - wireless airtime
> - bandwidth used by RAs
> - CPU usage sending unicast RAs by router
> - energy consumption on devices for more than one medium

and:

- fast handovers: on some links the more frequent the multicast RAs the
faster the handovers are, i.e. less packet loss for end nodes, less
glitches in the video conference stream.

Alex

>
> Some of them are orthogonal, some of them contradict each other, some of them align. People may want to optimize differently.
>
> I'd opt for simplicity - and use the text Erik Kline posted in another email.
>
> This would allow the developers to adapt for individual use cases on the spot.
>
> --a
>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email