Re: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt

Lorenzo Colitti <lorenzo@google.com> Thu, 20 July 2017 09:43 UTC

Return-Path: <lorenzo@google.com>
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 A478A13157A for <v6ops@ietfa.amsl.com>; Thu, 20 Jul 2017 02:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 G1vo68sGGHGv for <v6ops@ietfa.amsl.com>; Thu, 20 Jul 2017 02:43:18 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 34E2712ECCB for <v6ops@ietf.org>; Thu, 20 Jul 2017 02:43:18 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id h199so13442109ith.0 for <v6ops@ietf.org>; Thu, 20 Jul 2017 02:43:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fSBADIPEMGm7xf4IUgfYgz7YTfdRTzoiYQN3s63lAkM=; b=XoyeHXWzcojhQ5m53n0Fj0i1ZZUbAcmfMBSunXpcgCepKB9MOvGTuoY/2cs/smfXA4 jS0eqajXU8ROQOP3TfW0tS8UZmU5n1aUaJmwuGFLMWymBAR+cH3GY035LB83tRQFBys7 5JFLujc/OVcboEaUxWZW4g8cfMa4L9UCrSl/pRfb0djXAOxeoTv5tdwRRIs+sw2R1RVh zCveq+0DhGTflaXeID9zRmXSuxgcAVu8HCDP3VU4QbdfgVgF5vuRarp6hO+W5AvFQLGl MWjC3rjiI+T9iuX1rDA0kMZW3sb1hUAj9zG7MHZLXj4gCnc97wlw6yxXaRawROHRUT8K BvZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fSBADIPEMGm7xf4IUgfYgz7YTfdRTzoiYQN3s63lAkM=; b=pTFvXbYzYgJzx7AbZ0LEvSg5OaL9uBn/64ESvdn2GW7Gzif38iYKIAia0Zt7eo4wt4 F4l3kvm/C2xi7c16hxV1utO1cbHE9rinJqfPtSzF+Y/0pxP0zkPEaDCG659iFCcY1n/P 7/trJLaMqSSTrr9SEyZCqduu8aPCMAGpgm9T5bVZDJDnXiahStJ2iG2OK/s35uiSN4cO /+zR/2rroEIphTCsr2tqRYYSWvSycQvNDIHfiHPyJ9s7fBP144pLpE3Bzw8B47Yjb38u frGwh+eQxzxL55iwWUCvBrKmluGsTG74XbiyZk1je30XViMgIRPw7/U1ajq/CXzbzhe4 song==
X-Gm-Message-State: AIVw113UzfweO8DIbB6LCxbcCohuWEcfhdxfLfo6DVtysJr3IKsdPyPs hDsGUGDmFuaCmF5dG7uWGMgJ9ZQnh8k7
X-Received: by 10.36.198.133 with SMTP id j127mr2760940itg.142.1500543797302; Thu, 20 Jul 2017 02:43:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.195.137 with HTTP; Thu, 20 Jul 2017 02:42:56 -0700 (PDT)
In-Reply-To: <7776E80F-EBBF-4E30-94A5-E6570AB8B84A@cisco.com>
References: <596CF817.8040900@foobar.org> <BC0BBAF5-B016-44B5-8D73-BC9382CB79A9@google.com> <20170719090835.GC45648@Space.Net> <CAKD1Yr29MmGJuX+uhXaroB6UMRBBWBscCZPaMjaVscL0q7a7pg@mail.gmail.com> <98208c2e-7524-7afa-b0c8-865f251cd66e@gmail.com> <20170720062751.GL45648@Space.Net> <CAKD1Yr1ihnqHAzjhPcA8HB7sBBRwht2t5epJqQA-B_YGnfoTQA@mail.gmail.com> <20170720083002.GT45648@Space.Net> <20170720105009.34003050@echo.ms.redpill-linpro.com> <CAKD1Yr3SZAEbAvjr4Czv_tHN+-UVYGfnZ+SyaiJ0BNkvNr-d2g@mail.gmail.com> <7776E80F-EBBF-4E30-94A5-E6570AB8B84A@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 20 Jul 2017 11:42:56 +0200
Message-ID: <CAKD1Yr1oSB9CH1KBVrAgePAkNVsb0ZHKOTywoUmDQPHtwEp3_w@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: Tore Anderson <tore@fud.no>, james woodyatt <jhw@google.com>, IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c07dd0602ad4b0554bc94bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OX-vRBiQZDI-pVxvBBBVGlWx2KY>
Subject: Re: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Jul 2017 09:43:19 -0000

On Thu, Jul 20, 2017 at 11:23 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> >> What if the topology change was such that the global address of the
> DHCPv6 server is no longer valid due to renumbering?
>
> Address of DHCPv6 server does not matter - it can change. Clients
> generally never directly address packets to its address. They multicast to
> fe02::1:2.
>

Surely the RECONFIGURE is not multicast, but unicast from server to client?


> Also, 3315bis recommends that clients refresh information via dhcp when a
> network change occurs (such as new prefixes in an RA appear).
>

3315bis-09 does not recommend this, it says the client MAY do it and MUST
rate-limit it (with an example rate-limit of one every 30 seconds).

In any case, the server still needs to keep track of all topology changes
in order to give a correct answer.