Re: [v6ops] draft-ietf-v6ops-reducing-ra-energy-consumption WGLC

Owen DeLong <owen@delong.com> Mon, 31 August 2015 17:24 UTC

Return-Path: <owen@delong.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 B410E1B339D for <v6ops@ietfa.amsl.com>; Mon, 31 Aug 2015 10:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 sT8TpGf8xYpI for <v6ops@ietfa.amsl.com>; Mon, 31 Aug 2015 10:24:47 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCB41B3232 for <v6ops@ietf.org>; Mon, 31 Aug 2015 10:24:47 -0700 (PDT)
Received: from [IPv6:2620::930:0:ae87:a3ff:fe29:7192] ([IPv6:2620:0:930:0:ae87:a3ff:fe29:7192]) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.2) with ESMTP id t7VHOdJQ018601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 31 Aug 2015 10:24:40 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_62F5AE08-81C2-40DC-AC1B-E1632AB2C198"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAMugd_Ws17WUZcTg-GWRZNpU5+-pBTtrAz=+5nPR-0JpoowXQg@mail.gmail.com>
Date: Mon, 31 Aug 2015 10:24:36 -0700
Message-Id: <C1435BF7-2AB1-4813-B984-16988675405B@delong.com>
References: <201508231800.t7NI011E029031@irp-lnx1.cisco.com> <55DF0CEB.5040500@globis.net> <CAPi140OYAnE44AyuwNRt6dzFmCm9fzpKqOPMOJb6yS3BCnb9zA@mail.gmail.com> <55E01757.7080208@globis.net> <CAPi140M-Htjz8R69gt-NLVRokgHYK9DKbk8r0+iwzumLiqSLUA@mail.gmail.com> <CAKD1Yr0tZ0CFB85Lb9_t7UM_+TpOBpDfBku_GMuA7YP_UNT1tg@mail.gmail.com> <CAMugd_Ws17WUZcTg-GWRZNpU5+-pBTtrAz=+5nPR-0JpoowXQg@mail.gmail.com>
To: Nabil Benamar <benamar73@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/fPFRDuVXuaA7gpOf3Ma8mbkAI-A>
Cc: "Ray Hunter (v6ops)" <v6ops@globis.net>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-reducing-ra-energy-consumption WGLC
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: Mon, 31 Aug 2015 17:24:48 -0000

Yes and no… A pure formula means that the output is entirely dependent on the input.

If we don’t provide good guidance on valid (arguably arbitrary) input value ranges, then
silliness in = silliness out as Lorenzo mentioned.

Owen

> On Aug 31, 2015, at 02:49 , Nabil Benamar <benamar73@gmail.com> wrote:
> 
> It makes sens Lorenzo to have exact values...but these values should be expressed using a formula not arbitrary ! 
> 
> Best regards
> Nabil    نبيل
> 
> 
> 
> On Mon, Aug 31, 2015 at 9:44 AM, Lorenzo Colitti <lorenzo@google.com <mailto:lorenzo@google.com>> wrote:
> On Fri, Aug 28, 2015 at 9:23 PM, Andrew 👽 Yourtchenko <ayourtch@gmail.com <mailto:ayourtch@gmail.com>> wrote:
> Networks that serve battery-powered devices should try to maximize the
> interval between the  multicast RAs within the limits allowed by
> protocol - unless the information in the RA packet has changed. On the
> other hand, the maximum value should be bound to allow a sufficient
> number of RAs to be sent within the router/prefix lifetimes - to
> account for the potential packet loss in the wireless network. This
> packet loss will depend on the quality of the radio spectrum/coverage
> and may need to be decided on a per-network basis. In the best-case
> scenario one would ensure that at least 3 (a chosen arbitrary value)
> RAs are transmitted within the smallest of the lifetimes for the
> parameters contained within the RA.
> 
> I'd still prefer to have an absolute lifetime here, expressed in minutes. Otherwise network administrators will do silly things like set max interval = 12s, lifetime = 4s. I say "will" instead of "might" because I have personally seen this happen on a network whose administrators should have known better.
> 
> You make a very good point that text must be clear that this only applies to periodic RAs, *not* to RAs sent when something has changed.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org <mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops <https://www.ietf.org/mailman/listinfo/v6ops>
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops