Re: REMINDER: 6man w.g. last call for <draft-ietf-6man-maxra-01>

Suresh Krishnan <suresh.krishnan@ericsson.com> Fri, 06 January 2017 04:01 UTC

Return-Path: <suresh.krishnan@ericsson.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 5EF04129415 for <ipv6@ietfa.amsl.com>; Thu, 5 Jan 2017 20:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 xboAQCq6M7XJ for <ipv6@ietfa.amsl.com>; Thu, 5 Jan 2017 20:01:48 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 0BA0F12896F for <ipv6@ietf.org>; Thu, 5 Jan 2017 20:01:47 -0800 (PST)
X-AuditID: c6180641-e73ff70000000a0b-43-586ec23ebac1
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by (Symantec Mail Security) with SMTP id B8.2D.02571.E32CE685; Thu, 5 Jan 2017 23:01:36 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0319.002; Thu, 5 Jan 2017 23:01:43 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: REMINDER: 6man w.g. last call for <draft-ietf-6man-maxra-01>
Thread-Topic: REMINDER: 6man w.g. last call for <draft-ietf-6man-maxra-01>
Thread-Index: AQHSW50X2LnjnTgUGkSWKZE0Ax0x4g==
Date: Fri, 06 Jan 2017 04:01:23 +0000
Message-ID: <E87B771635882B4BA20096B589152EF6440E0058@eusaamb107.ericsson.se>
References: <F21F59C0-6DBD-42A4-B2C3-64E270CCFD76@gmail.com> <D25B7F1D-6925-48FE-B4CA-E8834480A496@gmail.com> <CAKD1Yr0mxG9LofzRWrTceYOsA3TVOUEfHQzA9k-z7BqW=7gk9g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyuXSPn67DobwIg8NfjC22vt/HZvHy7Hsm i/Wn3zE6MHvsnHWX3WPBplKPJUt+MgUwR3HZpKTmZJalFunbJXBlLJi/jrWgVaDi2aPqBsa/ PF2MnBwSAiYSk49OZexi5OIQEljPKLHhxkFWCGcZo8SUXeeZQarYgKo27PzMBGKLCHhLvNjR BxTn4GAWkJW4NikSJCws4Cnxf+UOVogSL4lphz9D2XoSX1fNZgexWQRUJFZcvswGYvMK+Ep0 9F1igdi1jVFi5uTfLCAJRgExie+n1oDtYhYQl7j1ZD4TxKUCEkv2QNwjISAq8fLxP1YIW0li zutrzBD1OhILdn9ig7C1JZYtfM0MsUxQ4uTMJywTGEVmIRk7C0nLLCQts5C0LGBkWcXIUVpc kJObbmS4iREYB8ck2Bx3MO7t9TzEKMDBqMTDa6CeFyHEmlhWXJl7iFGCg1lJhFdfJD9CiDcl sbIqtSg/vqg0J7X4EKM0B4uSOO/1kPvhQgLpiSWp2ampBalFMFkmDk6pBsYq85Wrb1/OP6T8 t/xv5dStrZa9MTz3fm8L8Z39bMLczUrHm08+sVHP++GVIeNQl3X40AM5nuiyk6bxN706m1st Tz6p8fAMFk/oCZZamHdO8c+jpFlNtww8VtWZdZoXyC888uRM1fLaTXWNcbf3nTn3Pq7wzgJJ Dh2ejPWbV7/M2F/xMtPhsbwSS3FGoqEWc1FxIgAFrZRKfwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EfilL9VHfBdI7sOFm-uSUNCPFgY>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 06 Jan 2017 04:01:49 -0000

Hi Lorenzo,

On 01/05/2017 01:02 AM, Lorenzo Colitti wrote:
> I find section 3 (which provides guidance on how packet loss impacts
> reliability, and how much redundancy to use) very useful.
>
> Section 4 (which is the actual standards update) needs to be worded in more
> detail. For example, it should ensure that 0 values continue to be valid and
> have the same meaning as before the update. (At least to me, a literal
> reading of the current text suggests that 0 is no longer a valid value
> for AdvDefaultLifetime.)


Yes. I do now see that reading as possible as well. Suggest the following change

OLD:

MaxRtrAdvInterval MUST be no greater than 65535.  AdvDefaultLifetime MUST be 
between MaxRtrAdvInterval and 65535.

NEW:

MaxRtrAdvInterval MUST be no greater than 65535.  AdvDefaultLifetime MUST 
either be zero (the router is not to be used as a default router) or be a 
value between MaxRtrAdvInterval and 65535.

Does that work?

"
Perhaps a better approach would be to simply say
> that the 1800 and 9000 values specified in section 6.2.1 or RFC4861 are
> hereby replaced by 65535

See above. Either change works for me.

>
> Given that the text allows MaxRtrAdvInterval to be up to 65535, should
> the MaxRtrAdvInterval be bounded to 65534 (not 65535) to ensure that the RA
> arrives before the timer expires?

Hmm. Not sure about this. According to Section 6.2.4. of RFC4861 the 
multicast RA is sent on a "timer that is set to a uniformly distributed 
random value between MinRtrAdvInterval and MaxRtrAdvInterval".  That should 
take care of it automatically*, right?

Thanks
Suresh

*: Not sure about other implementations but I interpreted this range as 
excluding the MinRtrAdvInterval and MaxRtrAdvInterval (but this might be 
worth checking).