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

Timothy Winters <twinters@iol.unh.edu> Thu, 20 July 2017 13:09 UTC

Return-Path: <twinters@iol.unh.edu>
X-Original-To: dhcpv6bis@ietfa.amsl.com
Delivered-To: dhcpv6bis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBCA12EBF7 for <dhcpv6bis@ietfa.amsl.com>; Thu, 20 Jul 2017 06:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 5LwtUvrKaeql for <dhcpv6bis@ietfa.amsl.com>; Thu, 20 Jul 2017 06:09:16 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (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 C83D3126E3A for <dhcpv6bis@ietf.org>; Thu, 20 Jul 2017 06:09:15 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id o8so21865377qtc.5 for <dhcpv6bis@ietf.org>; Thu, 20 Jul 2017 06:09:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3qEFzaQmOU95tM4JIWSGfnF4U2OQT9RiPFnW5mg5nYs=; b=U1ONWhBcch0WGxY7Lv3Qr61tAu8skhmhaRI1tMitIRCn0tA0kWADdj3lkR2MUocBl7 cl4x4jEl6QguF0NlVq6fd35Yd7IfT+CY7LBfkRhQihdHotT8vA4/wuXYRi7VrSzC6Hou ROUYPG1yLPoc//63fbCY9UgpWWkGTgCeOmzqE=
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=3qEFzaQmOU95tM4JIWSGfnF4U2OQT9RiPFnW5mg5nYs=; b=Cg2YZYfxrbYu2gGqb0sVSBE5P2Wf/fpBy4V+TnkchOCMbv8w3Q8zW3CXBYPp7aZyor frY1ZE3umEYA9FSONkDE4mfFBvVEO6u/+gnW0ppgIG0eP5Lbe5bLGH2yZ7Y7NrSBXkeD 388hIa3w8eQmWxt1SLDJBgeX3Jq/ovOFohw4XYD0Ha1WCXYCr58CsgxL6s6CisOl4DLf cn472ijW0Rfp/sav1cmtV8wKBYuo7ibH6b2SuCdlYaqQ/jOm5Gd0odLgS224sUS9aYX1 kJp+/6Gk06ErfCIaY/dI0vD/MNCKf5zcyYXk//UAiUstgjAfx7ktQVr8hAEuKpgUfVx9 Jq0g==
X-Gm-Message-State: AIVw112ld0x7fw/69lSIea2BLQAUHOyxmDygOTwXov1OLxZdHJr4sLgh IVl8kaJy7cnCt2qtRgYwlIICwpmH5NHt
X-Received: by 10.200.38.234 with SMTP id 39mr4605946qtp.252.1500556154636; Thu, 20 Jul 2017 06:09:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.37.106 with HTTP; Thu, 20 Jul 2017 06:08:53 -0700 (PDT)
In-Reply-To: <C4A2C527-D371-40F0-B053-2A1C473192D2@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> <FD6C17FB-B842-4919-AE7D-CAB89641E9F5@cisco.com> <CAOSSMjX_nQvuJ0hW1UTWruOctxWPeaeY6ZQnTYUijJSKCGCobA@mail.gmail.com> <C4A2C527-D371-40F0-B053-2A1C473192D2@cisco.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Thu, 20 Jul 2017 09:08:53 -0400
Message-ID: <CAOSSMjVh+X42W6pPs_8nYjm=XeoTmLQTdwx7O2bba6pSjD1hcg@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140e18e904cc90554bf741d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcpv6bis/AFXLgX-3ZCpOQeKaKkVUg5wGD1E>
Subject: Re: [Dhcpv6bis] Fwd: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt
X-BeenThere: dhcpv6bis@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "DHCPv6 \(RFC3315\) bis discussion list" <dhcpv6bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcpv6bis>, <mailto:dhcpv6bis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcpv6bis/>
List-Post: <mailto:dhcpv6bis@ietf.org>
List-Help: <mailto:dhcpv6bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcpv6bis>, <mailto:dhcpv6bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 13:09:18 -0000

I think that's the text from the rate limiting in other Sections?   I'm
also fine going silent on the time and just say rate-limiting.

~Tim

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

> Ok. Will plan to update draft to change.
>
> Also, not sure if the rate limit example of once every 30 seconds should
> be tweaked?
>
> - Bernie (from iPhone)
>
> On Jul 20, 2017, at 2:40 PM, Timothy Winters <twinters@iol.unh.edu> wrote:
>
> Hi Bernie,
>
> Yes I was thinking the same thing, probably a SHOULD.
>
> The story that I hear about this roaming on wireless-type network.
>
> ~Tim
>
> On Thu, Jul 20, 2017 at 8:35 AM, Bernie Volz (volz) <volz@cisco.com>
> wrote:
>
>> Hi:
>>
>> For -10, should we consider making this (see below) a SHOULD:
>>
>> 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
>>
>>
>> Also, while this is true, do we think that is a serious issue? How
>> frequently are network prefixes changed? With v6 they are probably more
>> stable than they have been for v4. So likely a false argument.
>>
>> - Bernie (from iPhone)
>>
>> Begin forwarded message:
>>
>> *From:* Lorenzo Colitti <lorenzo@google.com>
>> *Date:* July 20, 2017 at 11:42:56 AM GMT+2
>> *To:* "Bernie Volz (volz)" <volz@cisco.com>
>> *Cc:* Tore Anderson <tore@fud.no>, james woodyatt <jhw@google.com>, IPv6
>> Operations <v6ops@ietf.org>
>> *Subject:* *Re: [v6ops] New Version Notification for
>> draft-hilliard-v6ops-host-addr-update-00.txt*
>>
>> 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.
>>
>>
>> _______________________________________________
>> Dhcpv6bis mailing list
>> Dhcpv6bis@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcpv6bis
>>
>>
>
>
> --
>
> Now offering testing for SDN applications and controllers in our SDN
> switch test bed. Learn more today http://bit.ly/SDN_IOLPR
>
>


-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR