Re: SLAAC protocol improvements for flash renumbering (Fwd: New Version Notification for draft-gont-6man-slaac-renum-02.txt)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 20 February 2020 12:37 UTC

Return-Path: <mcr@sandelman.ca>
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 D68F5120893 for <ipv6@ietfa.amsl.com>; Thu, 20 Feb 2020 04:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.501
X-Spam-Level: **
X-Spam-Status: No, score=2.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 wcFkcBRlrsys for <ipv6@ietfa.amsl.com>; Thu, 20 Feb 2020 04:37:27 -0800 (PST)
Received: from relay.sandelman.ca (minerva.sandelman.ca [IPv6:2a01:7e00::3d:b000]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33B9D120251 for <6man@ietf.org>; Thu, 20 Feb 2020 04:37:27 -0800 (PST)
Received: from dooku.sandelman.ca (x59cc829e.dyn.telefonica.de [89.204.130.158]) by relay.sandelman.ca (Postfix) with ESMTPS id A6C471F458; Thu, 20 Feb 2020 12:37:25 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id BA0FF1A3B6D; Thu, 20 Feb 2020 13:37:24 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Fernando Gont <fernando@gont.com.ar>
cc: "6man@ietf.org" <6man@ietf.org>
Subject: Re: SLAAC protocol improvements for flash renumbering (Fwd: New Version Notification for draft-gont-6man-slaac-renum-02.txt)
In-reply-to: <e1a66ba1-694f-77a8-c5f0-f4bb663920b5@gont.com.ar>
References: <158191113629.5878.8466218249500554614.idtracker@ietfa.amsl.com> <1adb6745-f63b-6275-39c4-cae69cf8f924@si6networks.com> <18472.1582195844@dooku> <e1a66ba1-694f-77a8-c5f0-f4bb663920b5@gont.com.ar>
Comments: In-reply-to Fernando Gont <fernando@gont.com.ar> message dated "Thu, 20 Feb 2020 09:03:08 -0300."
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.2.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 20 Feb 2020 13:37:24 +0100
Message-ID: <24482.1582202244@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ah-dxV2nvCRnUlBpS9cstFjdG4w>
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: Thu, 20 Feb 2020 12:37:33 -0000

Fernando Gont <fernando@gont.com.ar> wrote:
    > On 20/2/20 07:50, Michael Richardson wrote:
    >>
    >> Hi, thank you for this.
    >>
    >> I want to suggest that you move the section 4.3/4.4 to
    >> draft-gont-v6ops-cpe-slaac-renum, but I can't find this document to be
    >> sure.  Maybe you are still posting it.
    >>
    >> Then, this document is all about updates to the Host side only.

    > Note: Section 4.4 is a host-side update. It does benefit from the
    > router-side change proposed in Section 4.3, though.

Yes, I think that the update should be split between which end needs to
implement it.

    >> I like section 4.4, and I really think it's actually the meat of this
    >> document.  I think that the title of the document should be less about
    >> Flash Renumbering, and just about "Improved Host Behaviour for Router
    >> Advertisements" or some such.

    > I'd agree that most of the meet is in Section 4.4. That said, at the
    > end of the day the goal is to improve the behaviour of SLAAC in
    > renumbering scenarios... and doing the right thing at routers does help
    > a bit. So I'd rather keep the router parts, too.

The issue is that I want to have a separate checkbox on routers
and hosts for whether they include the updates.
Q: "Do you support RFCXXXX"?
A: Well, yes, but not sure what to do with section 4.3, since we aren't a router,
   so we aren't compliant.

Routers can include host functionality, so they might implement both.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-