Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-02.txt

Mark Andrews <marka@isc.org> Mon, 05 March 2018 07:55 UTC

Return-Path: <marka@isc.org>
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 6271312741D for <v6ops@ietfa.amsl.com>; Sun, 4 Mar 2018 23:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 dERdLzUQnF_Z for <v6ops@ietfa.amsl.com>; Sun, 4 Mar 2018 23:55:47 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75BD5126579 for <v6ops@ietf.org>; Sun, 4 Mar 2018 23:55:47 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 1F2673AB001; Mon, 5 Mar 2018 07:55:45 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 05E08160069; Mon, 5 Mar 2018 07:55:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E4E47160068; Mon, 5 Mar 2018 07:55:44 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OWcEmXMYi4vM; Mon, 5 Mar 2018 07:55:44 +0000 (UTC)
Received: from [172.30.42.66] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id E11C6160046; Mon, 5 Mar 2018 07:55:43 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <20180305084214.6389aec9@echo.ms.redpill-linpro.com>
Date: Mon, 05 Mar 2018 18:55:41 +1100
Cc: Lorenzo Colitti <lorenzo@google.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E282363-869B-49D5-AD90-B7AA38EAF606@isc.org>
References: <152021615239.27925.6946415833371012617@ietfa.amsl.com> <CAKD1Yr00qjz7z8VF5=WeZ+baBPxJfmnYVhvNqKn_m7gu9H2GTA@mail.gmail.com> <0E0957B6-FA65-4CB0-965F-832699118204@isc.org> <CAKD1Yr3eLjO4vdQLjJgi2M=kyO_P9Mpw99ctY06GbzPFZZ6V5g@mail.gmail.com> <9C6ADA3B-8EC8-4E30-94C9-36285A9FFCCA@isc.org> <CAKD1Yr1u8Ph5+Pr52YO6nf6qxEDXZmS=-1-aUwUzVK1M_iB26g@mail.gmail.com> <02EF1B15-1344-4316-8F96-3105D82F4E4D@isc.org> <20180305084214.6389aec9@echo.ms.redpill-linpro.com>
To: Tore Anderson <tore@fud.no>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/RVXdkyMe_FeOjxbU2SIEXSJ3OUc>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-02.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: Mon, 05 Mar 2018 07:55:49 -0000

> On 5 Mar 2018, at 6:42 pm, Tore Anderson <tore@fud.no> wrote:
> 
> * Mark Andrews <marka@isc.org>
> 
>>> On 5 Mar 2018, at 5:54 pm, Lorenzo Colitti <lorenzo@google.com> wrote:
>>> 
>>> DNS servers don't differ between cell towers. The thing that
>>> differs is the /64 assigned to the device.
>>> 
>>> The phone announces its address in that /64 as the DNS server. When
>>> the phone's /64 prefix changes, the old address is no longer valid
>>> and potentially belongs to another customer of the network. But
>>> with stateless DHCPv6, there's no way for the phone to tell clients
>>> not to use it any more.  
>> 
>> So you are tearing down the network too fast in the phone.  The point
>> to “deprecating” the prefix is to keep stuff like this working for a
>> while using the deprecated addresses.  If the stateless DHCPv6 is
>> adverting resources with TTLs longer than the RA timers then you as a
>> developer of the phone have build a broken product.
> 
> You're forgetting that the network could be torn down for all sorts of
> reasons outside the phone's control, like driving through a tunnel.
> When you emerge from the tunnel 10 seconds later, the phone might
> receive a new /64.

So?  The existing /64 is STILL valid. You just have 2 prefixes.

> Tore

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org