RE: ID: More Accurately Naming IPv6 RA Router Lifetime (Re: New Version Notification for draft-smith-6man-accurate-ra-router-lifetime-00.txt)

Vasilenko Eduard <vasilenko.eduard@huawei.com> Thu, 06 May 2021 11:15 UTC

Return-Path: <vasilenko.eduard@huawei.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 4EDC83A1DAD for <ipv6@ietfa.amsl.com>; Thu, 6 May 2021 04:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 1S15TC0RgSIn for <ipv6@ietfa.amsl.com>; Thu, 6 May 2021 04:15:48 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA3203A1DAF for <ipv6@ietf.org>; Thu, 6 May 2021 04:15:47 -0700 (PDT)
Received: from fraeml712-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FbW1f5M5fz72fF4; Thu, 6 May 2021 19:04:38 +0800 (CST)
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 6 May 2021 13:15:38 +0200
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml703-chm.china.huawei.com (10.219.141.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 6 May 2021 14:15:38 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2176.012; Thu, 6 May 2021 14:15:38 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Mark Smith <markzzzsmith@gmail.com>
CC: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: ID: More Accurately Naming IPv6 RA Router Lifetime (Re: New Version Notification for draft-smith-6man-accurate-ra-router-lifetime-00.txt)
Thread-Topic: ID: More Accurately Naming IPv6 RA Router Lifetime (Re: New Version Notification for draft-smith-6man-accurate-ra-router-lifetime-00.txt)
Thread-Index: AQHXQYKAY1VjsWp26U6Cd+gYrjzKEarUWEYAgAH2DOA=
Date: Thu, 06 May 2021 11:15:38 +0000
Message-ID: <f48b674f4d16481fac5163973b88a887@huawei.com>
References: <162011606497.27748.2372985755866817594@ietfa.amsl.com> <CAO42Z2xWLnEe8L4Zy3jXZcecGMGV45eyKfpFtKprOD2AdQ+LWA@mail.gmail.com> <CAO42Z2zioVfudbB0_b9Ous4gUaE4ASU8RAp83s4mGQXX2oV+Fg@mail.gmail.com> <2df7c730-20da-f4f5-f441-b2ec2028f3ba@gmail.com>
In-Reply-To: <2df7c730-20da-f4f5-f441-b2ec2028f3ba@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.196.76]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FgJ1EGnraDOvdF_AwT1u9EU1X1Q>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 May 2021 11:15:52 -0000

Hi Mark,
I believe too that naming things in a self-explanatory way is a good idea.
But is it a big enough problem for separate RFC? Is it possible to create an Errata to RFC 4861?
Eduard
-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Wednesday, May 5, 2021 11:15 AM
To: ipv6@ietf.org
Subject: Re: ID: More Accurately Naming IPv6 RA Router Lifetime (Re: New Version Notification for draft-smith-6man-accurate-ra-router-lifetime-00.txt)



Le 05/05/2021 à 09:43, Mark Smith a écrit :
> Now with a more exciting email subject!

Thanks,

The idea sounds great and it would solve a common problem of understanding the meaning of that field.  A better understanding would lead to better implementations.

But, there might be drawbacks as well: will it confuse a reader of an old code commented with 'Router Lifetime' everywhere and not finding that 'Router Lifetime' text in a potentially updated RFC?

> The Router Lifetime field of an RA indicates whether or not the
>    advertising router will act as a default router for the receiving
>    IPv6 hosts, and if so, for how many seconds it will perform that
>    role, unless it is refreshed by a subsequent RA from the router.

YEs, it is well formulated.  Maybe to be complete it should say that the 'how many seconds' is non-zero.

>    If the RA Router Lifetime field value is zero, it means that the
>    router is not or will no longer be acting as a default router.

yes, but it will still be able to act as a router.  Maybe as a router for more specific routes, or maybe as a router to advertise the MTU of the link, or maybe for SLAAC (maybe for VSLAAC too).

(also, a side note, I think nothing prohibits a Host receiving that RA containing a 0 router lifetime to actually use it in whatever way it feels necessary.  That concept of 'default' route is a concept in the Host.  The Host might use it as it wants, irrespective of what the router suggests.)

Alex

> 
> On Tue, 4 May 2021 at 18:24, Mark Smith <markzzzsmith@gmail.com> wrote:
>>
>> Hi All,
>>
>> I've been thinking for a while that the Router Lifetime field name 
>> wasn't as accurate and expressive as it could be, and then we had 
>> somebody asking fairly recently on the mailing list about how Router 
>> Lifetime and ND lifetime (IIRC) values interacted on the mailing list.
>>
>> So an ID proposing to rename the field to Default Router Lifetime, 
>> and also providing an example scenario of when a zero value Default 
>> Router Lifetime would be used to demonstrate that a zero value RA is 
>> valid and useful in some scenarios.
>>
>> Comments and suggestions most welcome.
>>
>> Thanks very much,
>> Mark.
>>
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: <internet-drafts@ietf.org>
>> Date: Tue, 4 May 2021 at 18:14
>> Subject: New Version Notification for 
>> draft-smith-6man-accurate-ra-router-lifetime-00.txt
>> To: Mark Smith <markzzzsmith@gmail.com>
>>
>>
>>
>> A new version of I-D, 
>> draft-smith-6man-accurate-ra-router-lifetime-00.txt
>> has been successfully submitted by Mark Smith and posted to the IETF 
>> repository.
>>
>> Name:           draft-smith-6man-accurate-ra-router-lifetime
>> Revision:       00
>> Title:          More Accurately Naming IPv6 RA Router Lifetime
>> Document date:  2021-05-04
>> Group:          Individual Submission
>> Pages:          4
>> URL:
>> https://www.ietf.org/archive/id/draft-smith-6man-accurate-ra-router-l
>> ifetime-00.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-smith-6man-accurate-ra-router-
>> lifetime/
>> Htmlized:
>> https://datatracker.ietf.org/doc/html/draft-smith-6man-accurate-ra-ro
>> uter-lifetime
>> Htmlized:
>> https://tools.ietf.org/html/draft-smith-6man-accurate-ra-router-lifet
>> ime-00
>>
>>
>> Abstract:
>>     IPv6 Router Advertisements (RAs) have a "Router Lifetime" field,
>>     which specifies how long the advertising router will act as a default
>>     router for the receiving hosts, unless refreshed with another
>>     advertisement.  The field name "Router Lifetime" is quite general,
>>     and could easily be misunderstood to mean the bounded lifetime of all
>>     of the information contained in the RA.  This memo more accurately
>>     renames this field "Default Router Lifetime".
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of 
>> submission until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------