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

Isaac <isaactheogaraj@gmail.com> Sun, 24 January 2021 19:10 UTC

Return-Path: <isaactheogaraj@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 2D7653A0FF1 for <ipv6@ietfa.amsl.com>; Sun, 24 Jan 2021 11:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=gmail.com
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 fGrBY_GeiS5f for <ipv6@ietfa.amsl.com>; Sun, 24 Jan 2021 11:10:48 -0800 (PST)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12DD93A104D for <ipv6@ietf.org>; Sun, 24 Jan 2021 11:10:46 -0800 (PST)
Received: by mail-yb1-xb2a.google.com with SMTP id y4so11188413ybn.3 for <ipv6@ietf.org>; Sun, 24 Jan 2021 11:10:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JdjNaL3fn1mQTyWewG1Yep931OhfyCImyhvAg/3sdlk=; b=GHSy9aUOX9oD4Ikqivmz2OL3T7U9EnO7SGEGnylFNKi34BtN+8aCh/Q2xJev4vqgKR Db7nnAnlmL8/Hahf4QdUqP6pZcNtNJjt9wpimzVyDVC/IA7WzSL1NARRBZ05E8lbsfZv iOj0WGZIykCivdCeyVHqpgCMsGfjCnrdBO1Q/SqKxgcuJOm+0XF+2b6uxsMw/MuHiaGA h1zfguq8K4q3NPTu5X8SAFT4LoAzU1VXxMCGtLaMaFemZgoDA5FJsrrvNGJo3zKt2Jn4 RY2pqxRYck/N/dMPS7bF5xs46XUzKd9gTqC2kEofKp4eh99xkH+8k6izZJ2QZVd/FdY3 D1Qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JdjNaL3fn1mQTyWewG1Yep931OhfyCImyhvAg/3sdlk=; b=CFb0wwb37jjsrX5QrXdyifjIUnNhaLwSLhCvHVD0+N4We9HdsZFglDvm7HPJzdt1ka 237IZYd8IYwhwdKHtq+H7Wv8Bmy3XNWpwD3oWLitINdNX8CDb1SPCxmjz9xcBlIMAKZ+ ZmOebe0OdZn3hfzsEqvdOIGc7dAE+yY0tbVazypAOK9lkyiDa5osjcewB7CkVN9pVwbd 8IpFcuNs2Q+Kl/akHaxAtBtXfFefD0uHDfHThzo1b1PI69b0ZIBn1yQLcnEDGM9jYfrU wQNUULoCKI9CPaliVpdm/ArGFJKgNVl0Jhz/sKPwjthfTSenbd6Gh/Ldq0rGAtTqSgC/ rDUQ==
X-Gm-Message-State: AOAM533Y0N7fXWtTPHCFIjJ05f2tZESWzXlVjdHy5tmq1AW8V1kOoaji PxbQRvHKiA59tlUkYvXO37gzxBxA6GY45robbCk28gZYKxI=
X-Google-Smtp-Source: ABdhPJxTp2blPBZYTbkNx8noZHSQnn8MytOI/oUZnNNwF9ezbqX4r67g9x7YXc0vCZKiaL59ImRx09d4O24E0NdhsKw=
X-Received: by 2002:a25:e90e:: with SMTP id n14mr20281629ybd.185.1611515445077; Sun, 24 Jan 2021 11:10:45 -0800 (PST)
MIME-Version: 1.0
References: <CAGeZV=Sv8TwA7X3tzh_ZSjKGK1EdUhbWo+nj31bUfy8DhhHg-Q@mail.gmail.com> <DB3747F0-70A3-4776-850F-4893D4B90BDF@employees.org>
In-Reply-To: <DB3747F0-70A3-4776-850F-4893D4B90BDF@employees.org>
From: Isaac <isaactheogaraj@gmail.com>
Date: Mon, 25 Jan 2021 00:40:33 +0530
Message-ID: <CAGeZV=Q2gVtWFtY7zvFb=c1Bz8ZMfpjTOpj9oozWbF=-=SRZtw@mail.gmail.com>
Subject: Re: IPv6 certification - IPv6 Router Advertisement Lifetime 0 and Reachable time 10 seconds
To: Ole Troan <otroan@employees.org>
Cc: Nick Hilliard <nick@foobar.org>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a76a9805b9aa2d01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lJGbhaxovM-dHs4sObD-vBOPtAs>
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: Sun, 24 Jan 2021 19:10:50 -0000

Thanks Ole. Do hosts rely on RA packets for updating neighbor cache
post determining that the router is no longer the default gateway? They can
use NS/NA packets also right?

BTW, what do you think is the configuration/scenario on a router which
sends a RA packet with lifetime 0 and reachable time 10 seconds? Are you
aware of any particular vendor's configuration which generates such packets?

Thanks,
Isaac.

On Sun, Jan 24, 2021 at 10:20 PM Ole Troan <otroan@employees.org> wrote:

> Isaac,
>
> The two variables are independent.
> The example you cited is perfectly fine.
>
> the RA lifetime says: “don’t use me as a default router” and the reachable
> time configures hosts on the link to consider a neighbor entry in the ND
> cache reachable for 10s (for NUD).
>
> Best regards,
> Ole, 6man co-chair
>
> On 24 Jan 2021, at 17:07, Isaac <isaactheogaraj@gmail.com> wrote:
>
> 
> Thanks Nick for the timely response!!!
>
> I understand your comment regarding the prerogative of IPv6 forum in this
> regard. Meanwhile, we need a technical answer/analysis of the combination
> of RA lifetime 0 and Reachable time 10s whether that makes sense or whether
> it was clearly envisioned in the original IPv6 design. We know that RFC
> puts forth a set of 'may', 'might' conditions which are deemed optional in
> certian corner cases (possibly). We are already having discussions with the
> certification body but we need to go with a clear cut technical response of
> whether RA lifetime 0 and reachable time 10 seconds makes sense or not.
> Same way, section 6.2.3 in RFC4861 puts forth a 'might' condition. RA with
> a lifetime 0 and with advertised prefixes might mean that there may be a
> second router in the LAN segment which advertises a positive lifetime. And
> this itself is a corner scenario we believe and common scenario would be a
> single router in a LAN segment who always advertises with a positive
> lifetime until he decides to cease to be default gatewway for clients
> (probably he is ging down as well). But the combination of RA lifetime 0
> and reachable time 10 seconds doesn't make sense to us and we are clueless
> as to how that can be supported. We do not want to deisgn some throw away
> logic just for certfication purpose and we do think thats neither the
> purpose of certification bodies nor the end customers. We need a solid
> technical answer from the IETF IPv6 official body in this regard. Please
> review and respond.
>
> Thanks,
> Isaac.
>
> On Sun, Jan 24, 2021 at 5:38 PM Nick Hilliard <nick@foobar.org> wrote:
>
>> Isaac wrote on 24/01/2021 11:02:
>> > At the moment, we are unable to find a scenario (real world usecase) to
>> > support RA lifetime of 0 and RA reachable time of 10 seconds. Please
>> > review and respond.
>>
>> Isaac,
>>
>> you're referring to an IPv6 Forum document, so they might be more
>> qualified to give an answer to your question.
>>
>> As a potential pointer, rfc4861 documents the following case in section
>> 6.2.3:
>>
>> >    A router might want to send Router Advertisements without advertising
>> >    itself as a default router.  For instance, a router might advertise
>> >    prefixes for stateless address autoconfiguration while not wishing to
>> >    forward packets.  Such a router sets the Router Lifetime field in
>> >    outgoing advertisements to zero.
>>
>> Nick
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>