Re: IPv6 certification - IPv6 Router Advertisement Lifetime 0 and Reachable time 10 seconds

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 25 January 2021 09:24 UTC

Return-Path: <alexandre.petrescu@gmail.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 702453A0D5D for <ipv6@ietfa.amsl.com>; Mon, 25 Jan 2021 01:24:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.155
X-Spam-Level: ***
X-Spam-Status: No, score=3.155 tagged_above=-999 required=5 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=no 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 LbsdoYrb_cIf for <ipv6@ietfa.amsl.com>; Mon, 25 Jan 2021 01:24:34 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 8A7AE3A0D58 for <ipv6@ietf.org>; Mon, 25 Jan 2021 01:24:34 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 10P9OVcf003348 for <ipv6@ietf.org>; Mon, 25 Jan 2021 10:24:31 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4BB13205398 for <ipv6@ietf.org>; Mon, 25 Jan 2021 10:24:31 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3FA3A205375 for <ipv6@ietf.org>; Mon, 25 Jan 2021 10:24:31 +0100 (CET)
Received: from [10.14.2.198] ([10.14.2.198]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 10P9OUxp029483 for <ipv6@ietf.org>; Mon, 25 Jan 2021 10:24:31 +0100
Subject: Re: IPv6 certification - IPv6 Router Advertisement Lifetime 0 and Reachable time 10 seconds
To: ipv6@ietf.org
References: <CAGeZV=Q=awxFd=vsfBiBC2vt7o3Wkm9ECMSi+UU90ATKmHY32Q@mail.gmail.com> <BAB67E82-9BE8-4E7A-8548-5475E93FD137@employees.org> <CAGeZV=T4B5m7RYrKL4a4peQjZAoJiUqNv7V=0iaz5VdWeSTKng@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <08841dc2-9a4e-dacb-174a-a8f4cdfca1c7@gmail.com>
Date: Mon, 25 Jan 2021 10:24:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <CAGeZV=T4B5m7RYrKL4a4peQjZAoJiUqNv7V=0iaz5VdWeSTKng@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-Pp355eD-ngan5u-AtOMmvhIhsY>
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: Mon, 25 Jan 2021 09:24:36 -0000


Le 25/01/2021 à 05:55, Isaac a écrit :
> Ole/Tim Winters/IETF team,
> 
> Yes, we understand these knobs but we wanted to understand more on 
> the scenario/topology. More importantly we wanted to understand the
> real world scenario when this combination of RA lifetime 0 and
> reachable time 10 seconds is used and the technical merit of it

The technical merit of it is this: when the default router has a
reachable time of 10seconds the backup router has to do the same.

The merit is in that the Host receiving the RA continues as before when
the backup becomes the normal.

This is an explanation I am trying, but I never tried it in practice.
It might be wrong.

Alex


  for which we did not
> get clear response (especially in the modern global IPv6 networks 
> context). It's surprising that the certification bodies haven't
> clearly mandated only common/practical (although IETF has mentioned
> that these paramers need to be configurable but never said explicitly
> that all permutation/combination of values need to be supported.
> Vendors (definitely want) comply to RFCs but do not want allow
> impractical values) use cases but have listed even the corner
> scenario which may never be used. We understand that there are
> thousand vendors who have implemented this combination. But we fear
> that these are extra burden for vendors considering that vendors go
> ahead for certification without questioning the certification body
> itself believing that the certification body does its job of
> validating the modern technical relevance. Ideally, we expect the
> certification body (if not IETF) to re visit all the tests
> periodically to understand the relevancy as time passes and modify if
> required (which is the purpose of the certification body we believe).
> Sorry to have spilled certain discussions pertaining to certification
> body in this forum. But we do not have much option as we want
> technical answer from the IETF group. Let's not stop with the high
> statements in RFC. The reason we approcahed IETF is to go one level 
> deep (especially in the context of modern day global networks) to 
> undertand the relevance of RA lifetime 0 and reachable time 10
> seconds whether it makes sense to support. These are our 2 cents
> contribution to the community (if there is someone to listen!)
> 
> Thanks, Isaac.
> 
> On Mon, Jan 25, 2021 at 2:30 AM Ole Troan <otroan@employees.org 
> <mailto:otroan@employees.org>> wrote:
> 
> Isaac,
> 
>> Need a favor, (if you have it handy) could you please point to a 
>> configuration by Cisco router (any of the product type would do) 
>> which sends out the RA lifetime 0 and reachable time 10 seconds and
>> how commonly (practically) that is used? (Especially in the context
>> of modern global networks where customers want things done 
>> autonmously/automatically with the least number of knobs possible)
> 
> A quick search would have found that information for you. Basically: 
> interface Ethernet0 ipv6 nd ra lifetime 0 ipv6 nd reachable-time
> 10000
> 
> https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6/command/ipv6-cr-book/ipv6-i3.html
>
> 
<https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6/command/ipv6-cr-book/ipv6-i3.html>
> 
> Best regards, Ole
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>