Re: [sunset4] New Version Notification for draft-bz-v4goawayflag-00.txt

"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Mon, 09 April 2018 23:10 UTC

Return-Path: <bzeeb-lists@lists.zabbadoz.net>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E160812D87B for <sunset4@ietfa.amsl.com>; Mon, 9 Apr 2018 16:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 UPZ-BuWI6r4W for <sunset4@ietfa.amsl.com>; Mon, 9 Apr 2018 16:10:17 -0700 (PDT)
Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CEA612D86F for <sunset4@ietf.org>; Mon, 9 Apr 2018 16:10:16 -0700 (PDT)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id AD8E425D3A6E; Mon, 9 Apr 2018 23:10:14 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id C0548D1F935; Mon, 9 Apr 2018 23:10:13 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id rvUz9jey0t7S; Mon, 9 Apr 2018 23:10:11 +0000 (UTC)
Received: from [192.168.1.88] (fresh-ayiya.sbone.de [IPv6:fde9:577b:c1a9:f001::2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id F05F5D1F8EF; Mon, 9 Apr 2018 23:10:10 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: David Schinazi <dschinazi@apple.com>
Cc: sunset4@ietf.org
Date: Mon, 09 Apr 2018 23:10:09 +0000
X-Mailer: MailMate (2.0BETAr6108)
Message-ID: <04C73FF5-F570-4AB8-AD06-E2495FFDA43A@lists.zabbadoz.net>
In-Reply-To: <DB594908-B54C-47F2-99D4-AAF985163094@apple.com>
References: <152253440272.23706.3081497166127801526.idtracker@ietfa.amsl.com> <1AEC6EC2-4F7B-479B-A060-185304478498@lists.zabbadoz.net> <DB594908-B54C-47F2-99D4-AAF985163094@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/uq7qGmaR26mcjASEizEq4xwW2cM>
Subject: Re: [sunset4] New Version Notification for draft-bz-v4goawayflag-00.txt
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sunset4/>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Apr 2018 23:10:20 -0000

On 3 Apr 2018, at 15:48, David Schinazi wrote:

Hi,

> A few comments:

A few answers:

> 1) The draft keeps mentioning the end node "policy" but never defines 
> it.

    3.  End node policy . . . . . . . . . . . . . . . . . . . . . . .   
4
      3.1.  Mandatory end node rules  . . . . . . . . . . . . . . . .   
4

policy:  “a set of ideas … of what to do in particular situations 
…”
rule: “an accepted principle or instruction that states the way things 
are or should be done, and tells you what you are allowed or are not 
allowed to do”


> What does "disable IPv4 on this link" mean?

What does
“Usage: networksetup -setv4off <networkservice>
         Turn IPv4 off on <networkservice>.”
mean?

disable: “to stop something such as (part of) a machine, system, or .. 
from working”


> 2) Unless you have a crystal ball that predicts the future, the 
> timeline is not useful.
> IPv4 will stop being supported when support costs outweigh user 
> benefits, not on an arbitrary anniversary.

Well, it is obvious at this point that agreeing on how to very 
gracefully getting anywhere is not working.
So the problem is not a priority or a problem at all.
If you do not have a deadline to work against, you won’t.
I give you this deadline.
Ans as we say “pick a number”;  I picked dates.

For me, the costs of supporting IPv4 started 8 years ago when I went 
ipv6-only to my edges.
Since shortly after that I have been paying extra to keep IPv4 alive for 
the people who still haven’t moved to even DS on basic infrastructure.
So don’t blame me for you not moving.
For the past years people have been telling the world that the costs for 
DS > for single stack.


> 3) Do we really need two flags (IPv4 Unavailable vs IPv4 GoAway) for 
> this purpose?

Maybe?  One is for saving resources,  the other is for making something 
go away;  if you agree on the latter the former will be obsolete in a 
few years and  is just another extra graceful step towards the end.  If 
you’d prefer to have GoAway earlier and with that not need 
Unavailable, then (a) the GoAway draft gives you the opportunity, and 
(b) I can move the dates earlier for -01 to save you the work for 
Unavailable.   Even simpler.


> 4) What problem is this trying to solve?

What is the future you are avoiding to accept?


> All in all, pretty good April Fool Draft, thank you.

Thanks, just that it’s not.


/bz