Re: [sunset4] Declaring IPv4 Historic

Tassos Chatzithomaoglou <achatz@forthnet.gr> Wed, 16 March 2016 18:26 UTC

Return-Path: <achatz@forthnet.gr>
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 A460712DA78 for <sunset4@ietfa.amsl.com>; Wed, 16 Mar 2016 11:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forthnet.gr
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 Pp3qiTrOF5vx for <sunset4@ietfa.amsl.com>; Wed, 16 Mar 2016 11:26:39 -0700 (PDT)
Received: from zm-out-01.forthnet.gr (zm-out-01.forthnet.gr [194.219.0.13]) (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 B344412DA7B for <sunset4@ietf.org>; Wed, 16 Mar 2016 11:26:38 -0700 (PDT)
Received: from zm-in-01.cloud.forthnet.prv (zm-in-01.cloud.forthnet.prv [10.24.31.15]) by zm-out-01.forthnet.gr (Postfix) with ESMTP id 6280312200C for <sunset4@ietf.org>; Wed, 16 Mar 2016 20:26:36 +0200 (EET)
Received: from localhost (localhost6.localdomain6 [IPv6:::1]) by zm-in-01.cloud.forthnet.prv (Postfix) with ESMTP id 5622D1202A3; Wed, 16 Mar 2016 20:26:36 +0200 (EET)
X-DSPAM-Result: Innocent
Authentication-Results: zm-in-01.cloud.forthnet.prv (amavisd-new); dkim=pass (1024-bit key) header.d=forthnet.gr
Received: from zm-in-01.cloud.forthnet.prv ([IPv6:::1]) by localhost (zm-in-01.cloud.forthnet.prv [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 2r-UgJ2jy4Cc; Wed, 16 Mar 2016 20:26:34 +0200 (EET)
Received: from localhost (localhost6.localdomain6 [IPv6:::1]) by zm-in-01.cloud.forthnet.prv (Postfix) with ESMTP id 843AA1202B4; Wed, 16 Mar 2016 20:26:34 +0200 (EET)
DKIM-Filter: OpenDKIM Filter v2.9.2 zm-in-01.cloud.forthnet.prv 843AA1202B4
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forthnet.gr; s=zm; t=1458152794; bh=y+UGHYIyQZXjovfFJJIwce6132ZUTD6dRWokvzzjSW0=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=Wa/ExaB32swhSPDW0Q/9iJfgqQ/AvDLw0MfeNooNckPL5o1VPb4oQ7SDt+9msl1gm kv5AgL5T6iY3XV0yY1Axo/YMeTobZmYhskzB6zaD7TiFWIg/wAwQB/aXk5QEveO/cu bEHE5I/NkBavy32euxQf9Bx6KKckQ+2N4fsaYUXE=
X-Virus-Scanned: amavisd-new at zm-in-01.cloud.forthnet.prv
Received: from zm-in-01.cloud.forthnet.prv ([IPv6:::1]) by localhost (zm-in-01.cloud.forthnet.prv [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id MGgaD7KCUwK3; Wed, 16 Mar 2016 20:26:34 +0200 (EET)
Received: from [IPv6:2a02:2149:8745:de00:cd47:d697:91f4:74f] (ip-2a02-2149-8745-de00-cd47-d697-91f4-074f.ip6.forthnet.gr [IPv6:2a02:2149:8745:de00:cd47:d697:91f4:74f]) by zm-in-01.cloud.forthnet.prv (Postfix) with ESMTPA id 56E081202A3; Wed, 16 Mar 2016 20:26:34 +0200 (EET)
Message-ID: <56E9A555.7000808@forthnet.gr>
Date: Wed, 16 Mar 2016 20:26:29 +0200
From: Tassos Chatzithomaoglou <achatz@forthnet.gr>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32.1
MIME-Version: 1.0
To: "sunset4@ietf.org" <sunset4@ietf.org>
References: <D30D72DC.D9C56%Lee@asgard.org>
In-Reply-To: <D30D72DC.D9C56%Lee@asgard.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/sunset4/le2tW1LimVe0VHB0LGhjDmOTOks>
Subject: Re: [sunset4] Declaring IPv4 Historic
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.17
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 Mar 2016 18:26:42 -0000

I support the idea of this draft, but...
>    The IETF does not update Historic RFCs.  Therefore, the IETF will no
>    longer work on IPv4 technologies, including transition technologies.
...i would like to see included some clarifications about the transition technologies.
It seems risky to "abandon" softwires/behave work without having good exposure on operators.
It's like we assume that everything transition-related will either work fine or won't be needed.

Also i would to have more information about the draft's effect on DHCP and any new options may come out.

--
Tassos

Lee Howard wrote on 15/3/16 09:09:
> As noted below, I’ve posted a draft. I thought I’d start a thread for discussing it.
>
> PLEASE Please please read the draft before commenting. It’s very short, less than 500 words, and I anticipate a lot of people having strong feelings about it. I would really rather not waste time arguing about things it doesn’t say.
>
> To that end, I’ve also written a blog post, explaining in a level of detail I thought inappropriate for the draft: http://www.wleecoyote.com/blog/ipv4-historic.htm
>
> Thank you,
>
> Lee
>
> From: sunset4 <sunset4-bounces@ietf.org <mailto:sunset4-bounces@ietf.org>> on behalf of Wesley George <Wesley.George@twcable.com <mailto:Wesley.George@twcable.com>>
> Date: Monday, March 14, 2016 at 6:28 PM
> To: "sunset4@ietf.org <mailto:sunset4@ietf.org>" <sunset4@ietf.org <mailto:sunset4@ietf.org>>
> Subject: [sunset4] Agenda items?
>
>     As you can see, we have a meeting scheduled for BA. 
>     As of right now, we have a single agenda item:
>
>     https://tools.ietf.org/html/draft-howard-sunset4-v4historic-00
>
>     While I fully expect that this item can expand to fill all available time, if there are other things that the WG wishes to discuss, please respond ASAP to request agenda time. 
>
>     Thanks,
>
>      
>
>     Wes
>
>      
>
>     Anything below this line has been added by my company’s mail server, I have no control over it.
>
>     -----------
>
>
>     ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>     This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
>     _______________________________________________ sunset4 mailing list sunset4@ietf.org <mailto:sunset4@ietf.org> https://www.ietf.org/mailman/listinfo/sunset4 
>
>
>
> _______________________________________________
> sunset4 mailing list
> sunset4@ietf.org
> https://www.ietf.org/mailman/listinfo/sunset4