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

Isaac <isaactheogaraj@gmail.com> Sun, 24 January 2021 16:07 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 70A0E3A0E02 for <ipv6@ietfa.amsl.com>; Sun, 24 Jan 2021 08:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WO6O8ptUvJnC for <ipv6@ietfa.amsl.com>; Sun, 24 Jan 2021 08:07:29 -0800 (PST)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 A4B433A0E00 for <ipv6@ietf.org>; Sun, 24 Jan 2021 08:07:29 -0800 (PST)
Received: by mail-yb1-xb30.google.com with SMTP id w24so10827238ybi.7 for <ipv6@ietf.org>; Sun, 24 Jan 2021 08:07:29 -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=CA8BZhZKwHGPP+xtaeqGacteyWAZqaRU6oRo1o9G6sI=; b=pchQk3S7btICfoQlPWDkpkPiPEzmCkbXmjRBg5mXCHMdYaFmWCBBnrjOQ1UT3KHzk7 JU4yZ06yMHEPFg78F/9qwRKXqTK9plbTDTRRwCOWfi7Z9Dgh14aaBX97jkccuLfzcOqS HtfGjZun0zdrk48B4Xn73ZTHZ42ToyyBU7mgkl3xo5ic3ltSSwnF77YOLDoMR9TVp1Ef mTrBt9p0W/O6vfwUDvMQa5CWMwVm4CxcdDgvVZ8mvuxeRvBolftpPxvKZnQFa+dqKppw SQOpwQpogrH49RcEA0uDVhv1BPHSGRxgpOZBTfH3+/JVWTuyxdtH0XvTLsKpakKW436w m0Ng==
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=CA8BZhZKwHGPP+xtaeqGacteyWAZqaRU6oRo1o9G6sI=; b=hkiP7s6b38XZYWjoYobBBJUJ3uXqNqUEPRx3W1mxqLSik8a/+QuPSnmj2Yy8+AVHQo 0mvcJ4jqxGcrXkfar4XgZcXKnbXUDVM0YSkr3MIQefHi3JWsAchTihDJOoqgADecU5xV JoD+EDzqlw3utxSx8sMh5bbtPdpcuXY605l32sFQuT4G39ubeUy3HliE/77cguCsMrus 1yc17CL00/cjxAzCepUoc/dS0YxB7Ph9VVT2iOR9KKcNdPiIajwPH3g2pe6y+UqqQApJ f+hBA4EGo8KAvmWezfg93r8EZKK7glwBS1APOQhMTh7GoJncT7FhzwuFq8hVQQHw624J n9MQ==
X-Gm-Message-State: AOAM5311yN3YhcUzcq/PHSvkyDv5ZA2smLXA22TS9ahV+MLD5HNa4XYW 09RXvTMhxft/dPje1cDz7eurJep+JbJ50z2xKlX3Gb0AA8k=
X-Google-Smtp-Source: ABdhPJz1T49Mub18cAgQtYsYnBed/bnzt8Dx4mfqyEfQ2hEmmGUJ9uyFKG1jDZFhbi5WovnahmG7gfYAzXZbk9He1E8=
X-Received: by 2002:a25:e90e:: with SMTP id n14mr19488684ybd.185.1611504448516; Sun, 24 Jan 2021 08:07:28 -0800 (PST)
MIME-Version: 1.0
References: <CAGeZV=RLrZwLgTusStv73gEuppxs40ijNXvGOWABH3U_Pqz-4Q@mail.gmail.com> <3e9138db-2b62-b145-a7d0-86d22fb1eea0@foobar.org>
In-Reply-To: <3e9138db-2b62-b145-a7d0-86d22fb1eea0@foobar.org>
From: Isaac <isaactheogaraj@gmail.com>
Date: Sun, 24 Jan 2021 21:37:17 +0530
Message-ID: <CAGeZV=Sv8TwA7X3tzh_ZSjKGK1EdUhbWo+nj31bUfy8DhhHg-Q@mail.gmail.com>
Subject: Re: IPv6 certification - IPv6 Router Advertisement Lifetime 0 and Reachable time 10 seconds
To: Nick Hilliard <nick@foobar.org>
Cc: ipv6@ietf.org
Content-Type: multipart/alternative; boundary="00000000000035385505b9a79ebe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UNYAr0CkcnuJ1UQuCN5yxgLi3i4>
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 16:07:32 -0000

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
>