Re: draft-ietf-6man-slaac-renum: Honoring small Lifetime values

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Fri, 28 August 2020 13:24 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 3AE5F3A0BE3 for <ipv6@ietfa.amsl.com>; Fri, 28 Aug 2020 06:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=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 GTzVSH4WZOHu for <ipv6@ietfa.amsl.com>; Fri, 28 Aug 2020 06:24:31 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B77E3A0B8B for <ipv6@ietf.org>; Fri, 28 Aug 2020 06:24:31 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kBeMg-0000INC; Fri, 28 Aug 2020 15:24:22 +0200
Message-Id: <m1kBeMg-0000INC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Subject: Re: draft-ietf-6man-slaac-renum: Honoring small Lifetime values
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <aae92430-0beb-b5e7-4652-381b38ffcf70@si6networks.com> <5d8d34ee-b1bd-1843-9868-3c9558c7936d@si6networks.com> <CAN-Dau2T_jHSwGYZeyBMjYNYfgM66mrBfXOEeEgpdJfzOXi2Ug@mail.gmail.com> <21b2340d-e1c8-de8b-7082-39122f63c2e0@si6networks.com> <CAN-Dau18UE86mw3RJaO-n-QdLdJBY=AeNQguyarrkRFR=B+xug@mail.gmail.com>
In-reply-to: Your message of "Thu, 27 Aug 2020 15:42:55 -0500 ." <CAN-Dau18UE86mw3RJaO-n-QdLdJBY=AeNQguyarrkRFR=B+xug@mail.gmail.com>
Date: Fri, 28 Aug 2020 15:24:21 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/e0yAGSZMnRKv8eN6Fn_UVlcALgo>
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: Fri, 28 Aug 2020 13:24:33 -0000

>I don't think this perverse misconfiguration by itself is a sufficient
>reason to not make the change you are proposing, but we need to try to
>think of all the corner case scenarios, be they perverse or
>simple misconfigurations, where this change could have bad results. Are
>there other corner case scenarios that should be considered?

I don't follow this line of reasoning. There is an endless number of ways to
configure a router, or collection of routers such that network connectivity
is broken.

Of course it is possible that some misconfigurations are common enough that
we need to do something, either publish more guidance or in specification
changes.

However, that should start with scenarios that are likely to occur.
Do we really want to speculate on what errors operators of enterprise
networks are going to make?