Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-11.txt

David Farmer <farmer@umn.edu> Thu, 28 September 2017 21:40 UTC

Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 538E61349D5 for <v6ops@ietfa.amsl.com>; Thu, 28 Sep 2017 14:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level:
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 FeQyBE8NdcnR for <v6ops@ietfa.amsl.com>; Thu, 28 Sep 2017 14:40:42 -0700 (PDT)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 49E64132F2C for <v6ops@ietf.org>; Thu, 28 Sep 2017 14:40:42 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id 9564BB47 for <v6ops@ietf.org>; Thu, 28 Sep 2017 21:40:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nK9Tdlr5Nnnp for <v6ops@ietf.org>; Thu, 28 Sep 2017 16:40:41 -0500 (CDT)
Received: from mail-wr0-f199.google.com (mail-wr0-f199.google.com [209.85.128.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 30D6AB34 for <v6ops@ietf.org>; Thu, 28 Sep 2017 16:40:41 -0500 (CDT)
Received: by mail-wr0-f199.google.com with SMTP id f51so3735960wrf.3 for <v6ops@ietf.org>; Thu, 28 Sep 2017 14:40:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=r0sag9FwM87A3Fsj09AEw/+TG1NEFlclmkbrmWRB8Yo=; b=Xd2Ds3RG2nPhu9mhsFI25BsReeTSeFStyC1wvMzlFD3jyWr9HcVN3Q24GilpLbzHZj i1brAXa2OaFxKRfFqxU2YZjg0B5x1YjKxNuXh+/0p85Qee0q5TSCC9vtJYiiq9x10NrA a3OT7hSJLllG3C+HY/7tYEHoDLsoXbrxO90T/SNdRrpw9vs2tvrCocbs0qpmSgHATB79 TBG8txZMefXwejEO45IJEs8KR2mkOLoMqQodPhaWsC/p3zOBIzIjyRzKgxPVKI66spxG c5T63nbqxk3PHu8yz8gSFqb3li/vfBbCbOUOeAS8VBv7MMCi9MbrGhJfPiJJKTN2KzrI gRYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=r0sag9FwM87A3Fsj09AEw/+TG1NEFlclmkbrmWRB8Yo=; b=bdBbAbzMOW4M3hWA1iupjpjkl/yoXgK/i7qoE0WDZaps09KDadAXRZpFCu80OZnecV 0YuASPolpKrVgW3z6/clUReeWkbTNyfOCQ0TyEE399xLwdfGbHf4Q2KDkWv/AXlo9g/B hC/35MKlL9884YDc4sGscH65bJ8Clb7icN8mwpkNwgkyydITharTmC1vZinisTJh2z7c 4mKdkNkYC/AgMg6aW/PZYSmI9xxgAFCYNyuomJuQMg1who9D2k7o/OFptZho0X4JZceM tmIO0HJWzVq0UTqQU/zO/KcA2tOPGy0mT5qBwh2frPlS0/sPWkxSVTl3y9GAcRsduvxA jxmA==
X-Gm-Message-State: AHPjjUi3+i35gEqkxpr5MIkXDhYf6Tzuod5C+lIq3qhaCSdbI4l1H6GD ntsd46SmAg/yErOLq/XZ0C1GLQIPneop4eCIa76KCBUrsjtbHZhwNGMWZaZIOkLFBWNJAqILA9+ finNCDAgTuFxa1kxhqFqVfqMzfQ==
X-Received: by 10.46.88.68 with SMTP id x4mr2603251ljd.138.1506634839663; Thu, 28 Sep 2017 14:40:39 -0700 (PDT)
X-Google-Smtp-Source: AOwi7QB0irLtJCbzUraaaMkBo/ltjOVJAWJOg9eTmEh2UwReAqlBxpeYASYxcS/azsMDrLD6c5co7+A5KfsPthRNLI4=
X-Received: by 10.46.88.68 with SMTP id x4mr2603247ljd.138.1506634839444; Thu, 28 Sep 2017 14:40:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.25.212 with HTTP; Thu, 28 Sep 2017 14:40:38 -0700 (PDT)
In-Reply-To: <EA735459-CF2E-4BB5-9CD7-5C443B5A0B3D@gmail.com>
References: <150659896337.13704.16305576151522889075@ietfa.amsl.com> <504C386B-260F-452E-8195-3A6E3D3BF40B@nokia.com> <CAN-Dau162uPx+t_11YBeotzvp2yt5Z-GfS3eGUHoMiBasVGRug@mail.gmail.com> <EA735459-CF2E-4BB5-9CD7-5C443B5A0B3D@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 28 Sep 2017 16:40:38 -0500
Message-ID: <CAN-Dau2g2fKuzPyKLr8D7NKSqvRuvW5qqPYpvnjmNKbt9jh-Mg@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="f4030438e988696a9c055a46c25a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ClGfJ9SPbDwjZ2AP71ar05cuhpM>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-11.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 28 Sep 2017 21:40:44 -0000

On Thu, Sep 28, 2017 at 12:00 PM, Fred Baker <fredbaker.ietf@gmail.com>
wrote:

>
>
> > On Sep 28, 2017, at 7:08 AM, David Farmer <farmer@umn.edu> wrote:
> >
> > I like most of the changes, however I find the following bullet somewhat
> confusing;
> >
> > o  Maximum IPv6 Router Advertisement Interval = 300s (or when battery
> >    consumption is a concern then a MinRtrAdvInterval of 514 seconds
> >    (1/7 of an hour) is better according RFC7772 [RFC7772]).
> >
> > It starts out talking about the *Maximum* Router Advertisement Interval,
> then with little explanation shifts to talking about the *Minimum* Router
> Advertisement Interval, I fear this will easily confuse any casual
> readers.  Furthermore, the IPv6 router implementations I'm familiar with,
> don't allow you to directly set the Minimum Router Advertisement Interval,
> it is automatically computed as 75% of the Maximum Router Advertisement
> Interval, as recommended in RFC4861. Therefore, in such implementations the
> Maximum Router Advertisement Interval would need to be set at 685 seconds.
> >
> > Also, as Lorenzo pointed out, there is no discussion of IPv6 Router
> LifeTime, which is also discussed in RFC7772.
>
> The bit about the inter-router-advertisement interval was at my
> suggestion. Lorenzo had complained that the draft didn't do anything to
> meet RFC 7772. That was changed somewhere between -07 and -10. However, it
> resulted in only specifying MaxRtrAdvInterval. If we want to have no more
> than seven RAs per hour (per RFC 7772), it is MinRtrAdvInterval that is
> important. 514=3600/7, hence the specification of MinRtrAdvInterval.
>
> May I suggest you suggest text? What would you like it to say?
>

I did suggest some text, but I didn't correctly remembered what RFC4861
says, so how about this;

o  Maximum IPv6 Router Advertisement Interval (MaxRtrAdvInterval) = 300s
(or when battery
    consumption is a concern 686s, see Note below)

o  IPv6 Router LifeTime = 3600s (see Note below)

...

Note: When servicing large numbers of battery powered devices, RFC7772
suggests a maximum of 7 RAs per hour and a 45-90 minute IPv6 Router
Lifetime. To achieve a maximum of 7 RAs per hour, the Minimum IPv6 Router
Advertisement Interval (MinRtrAdvInterval) is the important parameter, and
MUST be greater than or equal to 514 seconds (1/7 of an hour). Further as
discussed in RFC4861 section 6.2.1, MinRtrAdvInterval <= 0.75 *
MaxRtrAdvInterval, therefore MaxRtrAdvInterval MUST additionally be greater
than or equal to 686 seconds. As for the recommended IPv6 Router Lifetime,
since this technique requires that RAs are sent using the link-layer
unicast address of the subscriber, the concerns over multicast delivery
discussed in RFC7772 are already mitigated, therefore the above suggestion
of 3600 seconds (an hour) seems sufficient for this use case.


This keeps the table compact and easily understandable, providing the
details in a paragraph following the table.

Thanks.


-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================