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

Andrew Yourtchenko <ayourtch@gmail.com> Fri, 17 July 2015 16:57 UTC

Return-Path: <ayourtch@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 ED64E1AC3D6 for <v6ops@ietfa.amsl.com>; Fri, 17 Jul 2015 09:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 zLktWUKn_qIy for <v6ops@ietfa.amsl.com>; Fri, 17 Jul 2015 09:57:39 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41CF41ABD3F for <v6ops@ietf.org>; Fri, 17 Jul 2015 09:57:39 -0700 (PDT)
Received: by wibud3 with SMTP id ud3so43838985wib.1 for <v6ops@ietf.org>; Fri, 17 Jul 2015 09:57:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pyQuxi7PHUtES/S1BjjKCeIRky6MyHExb+56fsCe5Y8=; b=OJ2zwxtxQFrAIIXctky67KktNJzeQgR8iPIlFcxBs21Ef30mL3yhW/6Ua8QLA4l7wg Kj9Up9Bi6Y53VEwtSLtdaqcr5HwBHWTxaL0L7XygLUw+T/fCozUDdCVpMw9YlylxkzXn PES5F6xq7XgfntX4SFc/budme9h0s+nTmnYu2rlxZiPCEhRW5ceszMYvT9w/n8AfdydR 1MNTxJ9SJUROganS5TVG38o9ZwJeYkaU7i7ibJuGpcVZWxE5wB4FvQR1eYFxdXgXTLCc 5FeIAC8A9Vj2qH8DtdyfVjiIDaPN9sgu+8MVAyVtm6l1KtCN+zOA757NudoztnSi6h5g tHIg==
X-Received: by 10.180.211.10 with SMTP id my10mr18532264wic.41.1437152258012; Fri, 17 Jul 2015 09:57:38 -0700 (PDT)
Received: from [10.79.142.123] ([188.188.83.126]) by smtp.gmail.com with ESMTPSA id fo17sm19115420wjc.46.2015.07.17.09.57.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 17 Jul 2015 09:57:36 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Andrew Yourtchenko <ayourtch@gmail.com>
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <228248C6-94FE-4C9C-A875-F732EFDC6601@cisco.com>
Date: Fri, 17 Jul 2015 18:57:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <331D6E02-167D-4E7F-9682-F63C6674BD24@gmail.com>
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>
To: "Fred Baker (fred)" <fred@cisco.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/M3iyRTn-BE8aYSWMu0U5xJlah1U>
Cc: "draft-yc-v6ops-solicited-ra-unicast@tools.ietf.org" <draft-yc-v6ops-solicited-ra-unicast@tools.ietf.org>, v6ops list <v6ops@ietf.org>
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: Fri, 17 Jul 2015 16:57:41 -0000

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

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