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

Bob Hinden <bob.hinden@gmail.com> Mon, 25 January 2021 18:14 UTC

Return-Path: <bob.hinden@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 F36D13A16FD for <ipv6@ietfa.amsl.com>; Mon, 25 Jan 2021 10:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 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, 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 r1CtVRzf3az9 for <ipv6@ietfa.amsl.com>; Mon, 25 Jan 2021 10:14:39 -0800 (PST)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 813653A1725 for <ipv6@ietf.org>; Mon, 25 Jan 2021 10:14:29 -0800 (PST)
Received: by mail-wr1-x42a.google.com with SMTP id d16so13281403wro.11 for <ipv6@ietf.org>; Mon, 25 Jan 2021 10:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RO8iGanyYOsc0ItPZxwl66DuslPunwUiL8pi21njqMQ=; b=Cuqc2+TqfUApQ/llnL5+/XuYxeVlrMNhGYoXV+XkWe2iDgrJR2hDPJl51yrbMAexUc os7dDzghv8A4rL22vhtfddr7iYbUJc9HOKpqdKBnlxJIcuLqoz8Y14H8jcKHtP1dhBEO aDGip5WvqfYsGgtuXO6/rXJXqMSegqZtxff/0cAGJgeXcmdXna/xrPp2Xw1poFPzTyYG 8G6usf0SAk+WSaAPmDGsEtyuVW7i+5i/Ga2UDgqC6HOHlBWrcEWUpXZ9JnkKz36ugRmt 6yYBT11+JQpbPN90jycdb0uHSY+pbgQbyurvyLcY1peonWZn58aSao/ciODBVgDqJELX 4mjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RO8iGanyYOsc0ItPZxwl66DuslPunwUiL8pi21njqMQ=; b=ZgNCU7oLeUoK2J869Qx1UPz+Z0BwVbcCYA3MftAoitHfX7QJmAIZYMrSeNxiOlpE/+ afUVylF1xVNMHKhouieJYZ1BBlPsguA9lJVNFfSKx5RRCY3Hq01DePbAVIqo35tpLY3y rcxT5UdwAPqZHDxiU5B+YI5PKnByTAQ6YLZxOXdlsdHsTCvzjYp0YmDnpdM+wSq1F/xk ZIdNrxonIZ4jwLD87XXqmkaIaJxCce/YjdOW13yIQKtu9sH7srGiXws4AYM53spPO6sU j4tJRn0J6If/4r+TWT6WojYFu5vSrIx4P60aXyAXINy4UlITpAE7pHt3g7dyLPXhxPqq /Peg==
X-Gm-Message-State: AOAM533x411eZ5rrXe1GxBUMVGi815jyUCp769OZjrX75TlqtUZY/NCm 7ReApWZmCDEEbLwEWVDYmCs=
X-Google-Smtp-Source: ABdhPJxuB+iZ+zbGLfCwjmmmR8lzBidfSqoucReOj/a6rZxtt4gHK4pGhAOXPK7YuqVi1CpndvoqMA==
X-Received: by 2002:a5d:47ae:: with SMTP id 14mr2330236wrb.378.1611598467769; Mon, 25 Jan 2021 10:14:27 -0800 (PST)
Received: from [10.0.0.199] (c-24-5-53-184.hsd1.ca.comcast.net. [24.5.53.184]) by smtp.gmail.com with ESMTPSA id y24sm76088wmi.47.2021.01.25.10.14.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Jan 2021 10:14:26 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <399341CD-36A8-4218-8F7D-D85F415D3962@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_65999FA6-4BBB-4A52-819D-33FAFA5B1680"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Subject: Re: [EXTERNAL] IPv6 certification - IPv6 Router Advertisement Lifetime 0 and Reachable time 10 seconds
Date: Mon, 25 Jan 2021 10:14:22 -0800
In-Reply-To: <CAGeZV=SPczCEk-FixqSM+q5KDiEQf_pdsUWkzUj7f398dSGY8A@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>, IPv6 List <ipv6@ietf.org>
To: Isaac <isaactheogaraj@gmail.com>
References: <CAGeZV=Q=awxFd=vsfBiBC2vt7o3Wkm9ECMSi+UU90ATKmHY32Q@mail.gmail.com> <BAB67E82-9BE8-4E7A-8548-5475E93FD137@employees.org> <CAGeZV=T4B5m7RYrKL4a4peQjZAoJiUqNv7V=0iaz5VdWeSTKng@mail.gmail.com> <fd7bc4a5272f4081afddfdc1a00ad527@boeing.com> <CAGeZV=SPczCEk-FixqSM+q5KDiEQf_pdsUWkzUj7f398dSGY8A@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/iF959pz0p9ch72BV89NFztlQC_4>
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 18:14:41 -0000

Isaac,

> On Jan 24, 2021, at 9:40 PM, Isaac <isaactheogaraj@gmail.com> wrote:
> 
> Bert,
> 
> In a way, yes. Do you think this combination of RA lifetime 0 and reachable time 10 seconds need to be mandated for all vendors?

As many people have said, they are separate parameters.   Support for them needs to be implemented that way.

> 
> I have a question to the IETF group here, when RA lifetime is 0 (which means the the router is no longer to be used as gateway by hosts) and prefixes are provided

The key word is not being used as a "default router".  It can still be used as a router for a specific prefix.

> (prefixes have their own lifetime and flags and in this rare scenario there is going to be a second router acting as gateway), why do we need reachable time of 10 seconds for the 1st router?

It’s not that rare.

I think you have gotten the answer to your question(s).

Bob


> 
> Thanks,
> Isaac.
> 
> On Mon, Jan 25, 2021 at 10:45 AM Manfredi (US), Albert E <albert.e.manfredi@boeing.com> wrote:
> From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Isaac
> 
> > 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 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!)
> 
> Isaac, I'm trying to understand your point. At least one scenario in which the RA lifetime is set to 0, and reachable time is set to 10 seconds, was explained a couple of times. It can be used for a router to provide the IPv6 prefix, for example for SLAAC, but for that same router NOT to be used as the default router, for the subnet in question.
> 
> Is it that this scenario seems unrealistic and unnecessary, to you?
> 
> Thanks,
> Bert
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------