Re: [sunset4] Last Call: <draft-ietf-sunset4-ipv6-ietf-01.txt> (IETF: End Work on IPv4) to Proposed Standard

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 29 September 2017 15:25 UTC

Return-Path: <hallam@gmail.com>
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 057DD13214D; Fri, 29 Sep 2017 08:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NuHMRcgd4WrS; Fri, 29 Sep 2017 08:25:18 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 69DEF12EC30; Fri, 29 Sep 2017 08:25:18 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id x85so2535926oix.12; Fri, 29 Sep 2017 08:25:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=V1ZhOoO53Wh6w6CTZyh7HFDIz4CHtb9tCI2KY5N5ocQ=; b=Qj/riG3aqUPlVEkFuX5hBT2Ca6kbOzzZZfjQcztRjVsn9d3TDBn1wvhnsI5xzAccPS lFH9j0iHdYzk1rwxDHhp2JCAHiHFft+/Dq7J08Qdva9R8QKDJfY+yDLlSNk6ECcJpFEW ntGVV/R5xuUWDBUBFJl+NjJzfp+uj6E8oteS+GVVXNVSHUHUOmDYCIyz+jEO5EtyE3RX Vkj7N5BOjbRZsgQM9g7Xrrpl23o1IRV3qIEG8zXYs/GnCl+sp2bemXaAk66tcmd6JCjP KF7kT6Uz+y8P0lX5f2+xaWNxGL9HuwSqqRx0qPiSlzYcI7DJk++Ip9bsYRJDCZVrS8o6 nA3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=V1ZhOoO53Wh6w6CTZyh7HFDIz4CHtb9tCI2KY5N5ocQ=; b=UPArUQP0UXfycBXmah+KlOO8Sk3Y7nTzNeUnQCQwUr7apJPs4K96GjxgXM5d7K7QX1 RMmkGZ20KIAK4aFUPo2HGS6NVRpRO93wDbrLTG7+OppyMwy3wqIU/tLGYgkGcfpc2aHj ds4en7f+EkgQZb+QsubyQHf59RQGbnXtCYM1gOzUq1CV7tmtHKYvfzFwBXjmyFbPVIro FIsmyaKk3xC3szCbCcVSg0G4Xv5akMOncAItHhO1uuxhwr1JLYZE1rGGqeIpXejoNWM/ /moWA+GaOKbV1jLPmBOuN3IeJAo3ylHBqn/vexH1EZJt81HMtuJ/WhUF2jgULxOuvLjh WOBw==
X-Gm-Message-State: AMCzsaXfkd7sPckmnCYtSfkp7X354U9Wcq+hmMJ5R1toQQWDqgAx9/In Q4bdhtFUsQjO65Gb2t2nTYS8qmrnQuFjuH5TvE0=
X-Google-Smtp-Source: AOwi7QCQnDONvRmCAc56odUM8rdluKj1pKpDeJ+NljiQT+i6DTo3eyTla6RquW5rZ6nsKFFyf/bLqJj8eHxgU8DVTIw=
X-Received: by 10.202.253.209 with SMTP id b200mr2769928oii.279.1506698717803; Fri, 29 Sep 2017 08:25:17 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.95.12 with HTTP; Fri, 29 Sep 2017 08:25:17 -0700 (PDT)
In-Reply-To: <0b0b3277-e8b6-697d-f886-d332ca68185d@gmail.com>
References: <150660518277.13796.5801483741214576151.idtracker@ietfa.amsl.com> <CAMm+LwicKPpZ8+0AbrDx5+twqHWH=rTXTbrVQhPS=7VA-0a=qg@mail.gmail.com> <D5F29735.87F38%lee@asgard.org> <CAMm+Lwh97O_XL_u3j_SQK8c7yWURzLLqdBAhzTuUA+deYq0YSQ@mail.gmail.com> <0b0b3277-e8b6-697d-f886-d332ca68185d@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 29 Sep 2017 11:25:17 -0400
X-Google-Sender-Auth: mS2galZD-SJ_Cu3O_Av4DOKUu3g
Message-ID: <CAMm+LwgT0U4M-gZ3HYu0EGC-1zuUwdhOaYaCrpN=iZ9oxNCwYA@mail.gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Lee Howard <lee@asgard.org>, IETF Discussion Mailing List <ietf@ietf.org>, sunset4-chairs@ietf.org, sunset4@ietf.org, draft-ietf-sunset4-ipv6-ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d36f8dbb961055a55a16b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/dhfVhll_tLrHlA4wABE5zMUcnfI>
Subject: Re: [sunset4] Last Call: <draft-ietf-sunset4-ipv6-ietf-01.txt> (IETF: End Work on IPv4) to Proposed Standard
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: Fri, 29 Sep 2017 15:25:20 -0000

On Fri, Sep 29, 2017 at 11:14 AM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> On 29/09/2017 15:59, Phillip Hallam-Baker wrote:
>
>
>
> On Thu, Sep 28, 2017 at 12:18 PM, Lee Howard <lee@asgard.org> wrote:
>>
>> Then change the name to NPv4?
>>
>> Do we care what people do on their private networks? Is it any of our
>> business?
>>
>> Lee
>>
>>
> ​Since network use of IETF protocols is at least as important as Internet,
> yes it is very much IETF business if it wants to remain relevant.
>
> As for what the IPv4 consortium would do, I wrote out a draft list:
>
> * Determine IPR policy.
> * Chose venues for upcoming meetings.​
> * Form advisory committees.
> * Hold elections to advisory committees.
> * Set a schedule of membership fees.
>
> And that is just for starters.
>
>
> ... and they might perhaps figure out some technology wheeze that we did
> not notice, or which was less pure than we would accept, but none the less
> acceptable to most users, and thereby find a way to extend the service life
> of IPv4.
>
> - Stewart
>

​Like running IPv4 on the internal network and only translating to IPv6 at
the interface? That is exactly what I would expect such a body to develop.​
And the reason companies not represented in IETF would be more than happy
to pay to join such a consortium is that gifting $50K/year to develop
standards to keep their legacy systems running would be a lot cheaper than
paying network equipment vendors millions to upgrade all the gear in their
company.