Re: [v6ops] draft-gont-v6ops-cpe-slaac-renum **Call for Adoption**

Fernando Gont <fgont@si6networks.com> Thu, 20 February 2020 11:50 UTC

Return-Path: <fgont@si6networks.com>
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 87CB512001A for <v6ops@ietfa.amsl.com>; Thu, 20 Feb 2020 03:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 xjrhHRassXkM for <v6ops@ietfa.amsl.com>; Thu, 20 Feb 2020 03:50:32 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F5D612004A for <v6ops@ietf.org>; Thu, 20 Feb 2020 03:50:32 -0800 (PST)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 6FCD086BAE; Thu, 20 Feb 2020 12:50:26 +0100 (CET)
To: Mikael Abrahamsson <swmike=40swm.pp.se@dmarc.ietf.org>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
References: <BN7PR05MB3938CECFE3021577A57783D2AE3A0@BN7PR05MB3938.namprd05.prod.outlook.com> <alpine.DEB.2.20.2002101325370.8336@uplift.swm.pp.se> <250c5eae-07c3-6b30-f2e0-4c69ff1bea2c@si6networks.com> <alpine.DEB.2.20.2002200804360.4069@uplift.swm.pp.se> <fe636e34-3a8f-1a80-50e2-21bd135b54b5@si6networks.com> <alpine.DEB.2.20.2002201157000.4069@uplift.swm.pp.se>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <38434b0a-f50b-b8fc-be8f-404c889a756e@si6networks.com>
Date: Thu, 20 Feb 2020 08:47:54 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.2002201157000.4069@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ajWD71aY265UrHX5ri0hlBKrfkU>
Subject: Re: [v6ops] draft-gont-v6ops-cpe-slaac-renum **Call for Adoption**
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Feb 2020 11:50:37 -0000

On 20/2/20 08:03, Mikael Abrahamsson wrote:
> On Thu, 20 Feb 2020, Fernando Gont wrote:
> 
>>      *  Any prefixes that were previously advertised via Router
>>         Advertisement (RA) messages for address configuration, but that
>>         are not currently intended for address configuration, MUST be
>>         advertised with a PIO with the "A" bit set to 1 and the "Valid
>>         Lifetime" and a "Preferred Lifetime" set to 0.
> 
> I think this is way too much text. Just say it should set the timers to 
> 0 and keep the flags, whatever they were. Writing this much prescriptive 
> language means there is a risk to get it wrong, or there is 
> misunderstandings.
> 
>>      *  Any prefixes that were previously advertised via RA messages as
>>         "on-link", but that are not currently not considered "on-link",
>>         MUST be advertised with a PIO with the "L" bit set to 1 and the
>>         "Valid Lifetime" and a "Preferred Lifetime" set to 0.
> 
> This can be rolled up into the previous paragraph.
> 
>>      *  If both of the previous conditions are met (a prefix was
>>         previously advertised with both the "A" and "L" bits set, but
>>         is currently *not* intended for address configuration and is
>>         *not* considered on-link), the prefix MUST be advertised with a
>>         PIO option with both the "A" and "L" bits set to 1 and the
>>         "Valid Lifetime" and a "Preferred Lifetime" set to 0.  That is.
>>         the advertisements of the previous two steps can be coalesced
>>         into a single one with both the "A" and "L" bits set.
> 
> Dito.
> 
>>      *  The aforementioned advertisement SHOULD be performed for at
>>         least the "Valid Lifetime" previously employed for such prefix.
>>
>> Thoughts?
> 
> Why not roll all of it up into:
> 
> "* Any prefixes advertised via RA MUST be announced with "Valid 
> lifetime" and "Preferred Lifetime" set to 0"

Point taken. How about:
'Any prefixes that were previously advertised via PIOs in Router 
Advertisement (RA) messages, and that have become stale, should be 
advertised with a PIOs that have both the "Valid Lifetime" and the 
"Preferred Lifetime" set to 0, and the A/L flags with the same settings 
as in the previous RA messages'


Not sure if "with the same settings" is clear enough, though.




> Guess if really needed, a sentence about "keeping A/L flags unchanged" 
> could be added.
> 
> L-13 in RFC7084 is short and sweet, why can't this one be similarily brief?

Agreed. Although L-13 of RFC7084 makes the reader assume what the proper 
settings for the flags are.


Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492