Re: [sunset4] Closing Sunset4

Lee Howard <lee@asgard.org> Wed, 16 May 2018 19:22 UTC

Return-Path: <lee@asgard.org>
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 0104C126BF3 for <sunset4@ietfa.amsl.com>; Wed, 16 May 2018 12:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 pKHcivNE6S8L for <sunset4@ietfa.amsl.com>; Wed, 16 May 2018 12:22:30 -0700 (PDT)
Received: from atl4mhob10.registeredsite.com (atl4mhob10.registeredsite.com [209.17.115.48]) (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 666D4124205 for <sunset4@ietf.org>; Wed, 16 May 2018 12:22:30 -0700 (PDT)
Received: from mailpod.hostingplatform.com (atl4qobmail03pod6.registeredsite.com [10.30.71.211]) by atl4mhob10.registeredsite.com (8.14.4/8.14.4) with ESMTP id w4GJMQb2004634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <sunset4@ietf.org>; Wed, 16 May 2018 15:22:26 -0400
Received: (qmail 27113 invoked by uid 0); 16 May 2018 19:22:26 -0000
X-TCPREMOTEIP: 174.64.33.182
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.102?) (lee@asgard.org@174.64.33.182) by 0 with ESMTPA; 16 May 2018 19:22:26 -0000
To: sunset4@ietf.org
References: <756C7AEB-B6B1-4034-BFFF-AC02D2DE452C@icann.org> <alpine.DEB.2.20.1805150724290.17103@uplift.swm.pp.se> <EC39B83C-CAE1-4C50-AED8-1D8EC0002422@icann.org> <24958_1526473951_5AFC24DE_24958_7465_1_30826.1526473908@dooku.sandelman.ca> <6f557ffb-3a3c-f1b4-c481-8d8e04d123a4@gmail.com>
From: Lee Howard <lee@asgard.org>
Message-ID: <5cc2c59a-5482-eff5-1854-aee15c28d805@asgard.org>
Date: Wed, 16 May 2018 15:22:26 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <6f557ffb-3a3c-f1b4-c481-8d8e04d123a4@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/W5DDF8I3EvH00_0e4rSWSLjhFzk>
Subject: Re: [sunset4] Closing Sunset4
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: Wed, 16 May 2018 19:22:33 -0000


On 05/16/2018 10:08 AM, Alexandre Petrescu wrote:
>
>
> My take is that sunset is a great name.
>
> I would have loved to learn in this group a few things:
> - is there a process in place that gives back to IANA the unused IPv4
>   space.  How much is this process used?
I believe each RIR has a separate process for the return of unused space.
https://www.apnic.net/manage-ip/manage-historical-resources/returned-ipv4-address-space/
https://www.arin.net/resources/return_revoke.html
etc.

It's used rarely, but somewhat; when an organization stops paying their 
bill, the RIR might reclaim the addresses.
Most organizations in most regions would rather sell their unneeded IPv4 
addresses, since prices are rapidly approaching US$20 per address.


> - why new technologies and sites get invented yet IPv6 is not on them
>   (deployed IoT w/ IPv4, self-driving cars w/ IPv4, new big office
>   buildings w/ IPv4, and so on).

1. Shortsightedness
2. Developers hacking together what they barely know
3. Using an OS designed for embedded systems that's based on a very old 
Linux without IPv6 support.

> - in 5G why there is no GTP replacement using QUIC instead of UDP and
>   IPv6 instead of IPv4.

5G is still in development, but I really don't know.

>
> And, my last question, my most preferred, which I know is polarizing, 
> soo feel free to ignore: why does not IETF put exclusive content on 
> IPv6?  Generally speaking I have never heard of some highly 
> interesting content that is available on IPv6. When that happens 
> immediately somebody puts in on IPv4 too.

Because as an open body, IETF content must be available to everyone, and 
not everyone has IPv6.

Any general content will need to be available over IPv4 until at least 
2024, when 90% or more of the world is IPv6-capable. Within the next 
couple of years I can imagine a phone app designed exclusively for users 
in the US that was only IPv6-capable, since US mobile is nearly all 
IPv6. Same for India, maybe, and a few other countries.

>> those DC also are almost always closed proprietary environments (even 
>> if the
>> components are open source, I can't buy a cabinet in that space, and 
>> they
>> don't run off-the-shelf OS builds).
>
> It seems though they can be accessed on the Internet, right?  I mean 
> such a data center can be accessed freely on IPv6, and for a fee put 
> content there.  That content would not be available on IPv4.
No: examples include Facebook and LinkedIn, which have very functional 
edge translation from IPv4.

>
> I think the next step would be to have free upload capability (like 
> drive.google but w/o IPv4).
Well, there was a marvelous presentation by Mythic Beasts at v6ops at 
IETF101-London.
https://datatracker.ietf.org/meeting/101/materials/slides-101-v6ops-ipv6-only-hosting-00

But if what you want is for someone to sacrifice their revenue or 
increase their costs For The Good of IPv6, I would not expect that to 
happen.

>
>>
>> I think that we wanted to be premature, such that we could get OS 
>> vendors
>> to test having no IPv4 *now*, and not discover things are broken ten 
>> years
>> later when the equipement can't be replaced.  We actually spured a 
>> few OS
>> vendors (FreeBSD, Linux, others) to try the test... many discovered
>> "127.0.0.1" hard code in many places.
>>
>> In the end, the problem is that funded OS vendors at the IETF has been
>> "reduced" to Apple and Google, neither of which is in the desktop market
>> it seems... While MS is clearly still here, funded Linux 
>> OS/networking people
>> are not at IETF (Wouters excepted!).
>>
>> So sunset4 did as much work as it could without broad OS vendor 
>> consensus.
>> I believe that the situation will change once more operators begin to
>> attempt to really turn off IPv4 in a non-3G space.
>>
>> Please keep the list alive.
>
> I agree.
>
> And make new inspiring stickers :-)

I have some for Montreal, even though I won't be there. :-)

Lee

>
> Alex
>
>>
>> -- 
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>   -= IPv6 IoT consulting =-
>>
>>
>>
>>
>>
>> _______________________________________________
>> sunset4 mailing list
>> sunset4@ietf.org
>> https://www.ietf.org/mailman/listinfo/sunset4
>>
>
> _______________________________________________
> sunset4 mailing list
> sunset4@ietf.org
> https://www.ietf.org/mailman/listinfo/sunset4