Re: [v6ops] Clarification/addition on the cpe-slaac doc.

Warren Kumari <warren@kumari.net> Wed, 10 February 2021 17:51 UTC

Return-Path: <warren@kumari.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9D833A110F for <v6ops@ietfa.amsl.com>; Wed, 10 Feb 2021 09:51:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=kumari-net.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 lIsJFPvmfr3k for <v6ops@ietfa.amsl.com>; Wed, 10 Feb 2021 09:51:18 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 D2E1E3A110E for <v6ops@ietf.org>; Wed, 10 Feb 2021 09:51:17 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id p21so4096529lfu.11 for <v6ops@ietf.org>; Wed, 10 Feb 2021 09:51:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=90FfCq0KhU8NpXZaoiWRA27TIrA1jng5xZ+bQ0uL2Ks=; b=QIfk1JLXoJ0cPmhvXYmn5IKo0LQn/mx2LCoEC/P4ljs8oEIFH5vDTSPkrsGuy+PKyn W4lCmYnvZXrvpZcE1X9/hxFEKPouit5cA5C2Efflbwp83rfjoY/Jce1T7x89e9mw4Pnp HJwIBUgYuC/D1CgOL8y4/9omxAe8lPhLDAQIlFzleEYDtxHDsyRznYxWqH/H7UqyLzi0 Aym5T8rRU8MVusbbtoqa4mH9QCGNIM00/lruOLwWC9RdOwyfNwQM0Z4m3DLfMuJWM0UI myYXY3Er9vLW6SKHeLE0IQhu4eRnBXn9e73t/pQeXLI1TVBgdeNRB6jKhRoi1bvSllxu kMJw==
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=90FfCq0KhU8NpXZaoiWRA27TIrA1jng5xZ+bQ0uL2Ks=; b=koKQCN4XJRraxQW3HDIFo3q1mR010sQZz2MU0zWyELvMaR2k7IeEZqrI8OG9tH/AY7 nNvJKEgYpy0+BL8ne/h7CsM4T8VGkfztMX8y8KR243izMs3IYB3utwaWnjMsfNO53F4i 0uz3D3D58s/bRu0DvF8l+XjDsoT3Zfd87UZEd/AeS4QLpmramjLwPGAz2p+h0JBISP4R wrDsTQgbe7BPpvfiW5CJbd5gQS394sy3KsdG/ynHD5g0Q/pd0MMF1vZruyJu2LAGyWZn M5fbjitnEgrNEiAAOE/DgG03H/LhUys8Y3cvYvwCl3pdvlapfk/IbZV/uFJAG27cr+7M dCqA==
X-Gm-Message-State: AOAM53091XBa7PjfiKLwxeF+txRdhti6sRhaCK89LuV2hiRo9W8dO1bA 8x4DWDMLjsOP1AfEaYiZBA34WPaZAotsp0zxpue0Cg==
X-Google-Smtp-Source: ABdhPJxgyJgVGFaR1oD77qqvF+9PCXkwN8FMAMRfmY6iw/TGopQLpwkzswPaH5u0hWPyhPNMldbqkdVeQpYgHDKuHYA=
X-Received: by 2002:a19:7f95:: with SMTP id a143mr2133167lfd.419.1612979475476; Wed, 10 Feb 2021 09:51:15 -0800 (PST)
MIME-Version: 1.0
References: <CAHw9_i+uALQiarCRs=m7rBNJ25R62PmRev2zHm+vZ=2VJw9yHw@mail.gmail.com> <888118D6-1F56-4ED3-9F3E-745DA9F590D8@employees.org> <CAHw9_iLxeJJ2nSki0mB6kc+VMP5j4RDtUnGd87KWC-20XzwtQg@mail.gmail.com> <BN7PR11MB25471C02FB6F8540DEB0C942CF8D9@BN7PR11MB2547.namprd11.prod.outlook.com>
In-Reply-To: <BN7PR11MB25471C02FB6F8540DEB0C942CF8D9@BN7PR11MB2547.namprd11.prod.outlook.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 10 Feb 2021 12:50:39 -0500
Message-ID: <CAHw9_iK6dxgbzgann6+JWeWCoAa8xTw2-jSyAJkNxJmUwyZLzA@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: Ole Troan <otroan@employees.org>, IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aa8e9305baff0c8b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9Q7wb5XSdF8aTHlQyVfaUHTwou0>
Subject: Re: [v6ops] Clarification/addition on the cpe-slaac doc.
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2021 17:51:21 -0000

On Wed, Feb 10, 2021 at 10:37 AM Bernie Volz (volz) <volz@cisco.com> wrote:

> It seems odd to me to be cherry picking things for RFC-8415 to reiterate
> as requirements?
>
>
>
> Doesn’t that open up the possibility that someone skips other things
> because “well it wasn’t in the CPE-SLAAC” requirements?
>

Maybe, but I *think* that this requirement is more closely related to the
CPE-SLAAC that the others in RFC8415. We do already have some callouts to
RFC8415 like:
"This is in line with the requirement from Section 6.3 of [RFC8415], which
states that "if the delegated prefix or a prefix derived from it is advertised
for stateless address autoconfiguration [RFC4862], the advertised preferred
and valid lifetimes MUST NOT exceed the corresponding remaining lifetimes
of the delegated prefix."

Perhaps we should just clarify that this document just draws attention to
requirements in 8415, and doesn't replace it (which should be obvious, but
I agree may be worth doing).
W


>
>
>    - Bernie
>
>
>
> *From:* v6ops <v6ops-bounces@ietf.org> *On Behalf Of * Warren Kumari
> *Sent:* Wednesday, February 10, 2021 10:09 AM
> *To:* Ole Troan <otroan@employees.org>
> *Cc:* IPv6 Operations <v6ops@ietf.org>
> *Subject:* Re: [v6ops] Clarification/addition on the cpe-slaac doc.
>
>
>
>
>
>
>
> On Wed, Feb 10, 2021 at 10:05 AM <otroan@employees.org> wrote:
>
> > During the final editing of cpe-slaac, the authors noticed that we
> should have included:
> > “WPD-10: CE routers SHOULD, by default, attempt to use a stable IAID
> value that does not change between CE restarts, DHCPv6 client restarts, or
> interface state changes. e.g., Transient PPP interfaces.”
> >
> > To me this seems like an obvious and non-contentious clarification (it's
> already required in RFC8145), and so I'm asking the authors to include it
> while addressing the other IESG comments/ballots.
>
> I think you mean 8415, but at least all the digits are there.
>
>
>
> I did indeed :-)
>
>
>
>
>
> I support the change, but I do think it should be strengthened.
> An "unintended" change in IAID has dire consequences for the end-user
> network.
>
> "WPD-10: CE routers MUST by default use a stable IAID value that does not
> change between CE restarts, DHCPv6 client restarts, or interface state
> changes. e.g., Transient PPP interfaces."
>
> 8415 has: "For any given use of an IA by the client, the IAID for that IA
> MUST be consistent across restarts of the DHCP client."...
>
>
>
> Fair enough. That's better, and the new proposed text; I actually intended
> to copy and paste the RFC 8415 (see, I *can* type :-)) but forgot....
>
> Thanks!
>
> W
>
>
>
>
>
>
> Ole
>
>
>
>
> --
>
> The computing scientist’s main challenge is not to get confused by the
> complexities of his own making.
>   -- E. W. Dijkstra
>


-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra