IETF Logo Mail Archive

Re: [dhcwg] [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Ted Lemon <mellon@fugue.com> Wed, 30 October 2019 22:43 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684D712011B for <dhcwg@ietfa.amsl.com>; Wed, 30 Oct 2019 15:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=fugue-com.20150623.gappssmtp.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 vOyUau2G2dWw for <dhcwg@ietfa.amsl.com>; Wed, 30 Oct 2019 15:43:21 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 E70F61200C1 for <dhcwg@ietf.org>; Wed, 30 Oct 2019 15:43:20 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id 71so4743010qkl.0 for <dhcwg@ietf.org>; Wed, 30 Oct 2019 15:43:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i/rXSzfzJxCJp/9K58VstvQ5w1XNieCx/NFJ/fHZhgs=; b=e9LD0riRSlu+UvWyg8q2IWIzHCKiGL4FjEBIBchoqKR0y0XxpzxLAnJenL7GImCG4F sxoHeK1mq9eh5gRKOHipipgGXDUFDzxn2f2G2cgDExLnhH6b3OtunTRt7QFHvKiLNmwJ UYquBPK17U6/ShJ3zw0IDoEt3Z/Tlu4LDOGWvynm7Eg7dqA+gp5VRdPsMSIAlGL6NThl iBqnC5B5hNBTS+wTYAaqqSUoVUbAVVDEMALzeAluCsTNGtl4CG2/IhX8Pz2PdASx6/AV FOyXy2gqTHYTIUOL/jAuPby+n1/91HEeeY4abGmrI8o7BpIQ/oyTv7K0+FZUNSoD1lHp UaEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i/rXSzfzJxCJp/9K58VstvQ5w1XNieCx/NFJ/fHZhgs=; b=oakNfHMbyQf3Zisik2J0KyeZIOZzdK28p8ZyZCPcKzjSGIk/z60USCxmhbD7lhjOo8 y9/SUGcIwK4h8E0w3SO1mwGNVKut/0iYYJz/9NZbTyU3Vp9ldDJYskbrvPrDctDWnYnj 6aIEFM5UFg6+v8DneJqkuxHKF4qwoanWeecfkkbemaYdd4Nd11+fVIXld6UoKkTcnkeE M1LdrZEJSm38xBRjX8MMB/7BBg2ZuXqlK5KigKYSEkPkgdsyTSb5X58p2BcMoTcJGIKj GJX98vxaB+EvIcM8AWbAG7HQzvnLvxyMjrJhTKlX6qWSkH81e1NJxHbVXem9862CFdM6 xyHg==
X-Gm-Message-State: APjAAAVcL7BSxqSayCA0WxZVAnv3en4ztvTcPfXiAWbzIZnOr6uXEy7W W4gSwyUinu7rbQIgu3/A9TEuHw==
X-Google-Smtp-Source: APXvYqwdxOHD75G2ToIEqoC9E4JUngtaNYuCRWaYjrig/h4VEKcipuoiwv/+AvrY5ST9jN922H8kmQ==
X-Received: by 2002:a05:620a:5e4:: with SMTP id z4mr1890868qkg.310.1572475399843; Wed, 30 Oct 2019 15:43:19 -0700 (PDT)
Received: from ?IPv6:2601:18b:300:36ee:c5ad:3e58:9e29:c076? ([2601:18b:300:36ee:c5ad:3e58:9e29:c076]) by smtp.gmail.com with ESMTPSA id o3sm1277891qta.3.2019.10.30.15.43.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Oct 2019 15:43:19 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <8755B40E-4075-4AAC-BF59-19B6DF9BA6D1@cisco.com>
Date: Wed, 30 Oct 2019 18:43:17 -0400
Cc: Bud Millwood <budm@weird-solutions.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B23EE439-1509-43FB-9813-F330117DBF42@fugue.com>
References: <MWHPR1101MB2288616D545F3DAD1D1734A1CF600@MWHPR1101MB2288.namprd11.prod.outlook.com> <CAOpJ=k06SRAHR7S+UmvFu=zvyk8j_uica2gdbBij+5pr+Jykww@mail.gmail.com> <C0A66DA1-29DE-456A-934D-7ECC07575336@cisco.com> <8755B40E-4075-4AAC-BF59-19B6DF9BA6D1@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/dnu7JUfAfWMdp0tEK797IwaGgZo>
Subject: Re: [dhcwg] [v6ops] SLAAC renum: Problem Statement & Operational workarounds
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2019 22:43:23 -0000

On Oct 30, 2019, at 6:23 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I should point out that having the dhcp server supply this information may not work all the time. It really depends on what configuration changes were made and the server implementation. And of course is useless if you “move” the CPE.

In this case the prefix would presumably no longer be valid; if it was valid and was offered as a deprecated prefix, it would cause no harm.

I am not suggesting that this should just start happening with no testing.   What I am suggesting is that forcing firmware updates on CPE routers isn’t something we should be as chary of as we used to be.

v2.23.0 | Report a Bug | By Email