IETF Logo Mail Archive

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

"Bernie Volz (volz)" <volz@cisco.com> Thu, 20 July 2017 10:05 UTC

Return-Path: <volz@cisco.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 6B9E012F290 for <v6ops@ietfa.amsl.com>; Thu, 20 Jul 2017 03:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 GH7O3HPs_gIe for <v6ops@ietfa.amsl.com>; Thu, 20 Jul 2017 03:05:57 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28BBB127735 for <v6ops@ietf.org>; Thu, 20 Jul 2017 03:05:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3877; q=dns/txt; s=iport; t=1500545157; x=1501754757; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=C0ozKbcCV13/75VMk2GQ0tPIimk4447RLCyu+AeIq+k=; b=NlS0hDsK7p5E7PNUkpw9AmJXVZ7BD+E9jHU3YFowroSLg60Y5w3p5Vsn YLGl/5lR3JFtKp1xNhKbBQtbWJslkHY3qSSVyGEfK/ZQHJrWqHRPk7KpV hbuyapcDhwtE1IiQeR1iYrKy+NtDOPjZUCAJVnmKZXkO2MGRY/E0dnq4D M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CZAAAqgHBZ/4QNJK1bGQEBAQEBAQEBAQEBBwEBAQEBg1qBeI4LkWiQWYUsgTIDXIVHAoNzPxgBAgEBAQEBAQFrKIUYAQEBAQIBdwIQAgEIBBQnBzIUEQIEDgWJS1wIs2aLIAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2DKIUuK4J5hEcNg1mCMQWfPgKLE4kFggyQKIlIjBUBHzhMPnUVWwGFNYFOdoc7gj8BAQE
X-IronPort-AV: E=Sophos;i="5.40,383,1496102400"; d="scan'208,217";a="457809323"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jul 2017 10:05:53 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v6KA5qMM028939 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Jul 2017 10:05:52 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Jul 2017 05:05:52 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Thu, 20 Jul 2017 05:05:52 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Lorenzo Colitti <lorenzo@google.com>
CC: Tore Anderson <tore@fud.no>, james woodyatt <jhw@google.com>, IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt
Thread-Index: AQHS/5m/vXdeJwPr90aX1hLwXQdtQqJbMdGAgAACOoCAAReuAIAAS4SAgAAfoYCAAAKDAIAABZ+AgAAFfQD//6/jEYAAWV8A//+yl8c=
Date: Thu, 20 Jul 2017 10:05:52 +0000
Message-ID: <294352E0-557F-495D-9D0E-46DD36BCD609@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>, <CAKD1Yr1oSB9CH1KBVrAgePAkNVsb0ZHKOTywoUmDQPHtwEp3_w@mail.gmail.com>
In-Reply-To: <CAKD1Yr1oSB9CH1KBVrAgePAkNVsb0ZHKOTywoUmDQPHtwEp3_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_294352E0557F495D9D0E46DD36BCD609ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NCuUlPr9saad2waPIc7k6-rC9m4>
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 10:05:58 -0000

There are two ways to deliver Reconfigure: one is unicast, other is via Relay-Reply through relays were link-local is used to reach client.

- Bernie (from iPhone)

On Jul 20, 2017, at 11:43 AM, Lorenzo Colitti <lorenzo@google.com<mailto:lorenzo@google.com>> wrote:

On Thu, Jul 20, 2017 at 11:23 AM, Bernie Volz (volz) <volz@cisco.com<mailto: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.

v2.23.0 | Report a Bug | By Email