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

S Moonesamy <sm+ietf@elandsys.com> Sun, 08 October 2017 15:52 UTC

Return-Path: <sm@elandsys.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 575411346B8; Sun, 8 Oct 2017 08:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level:
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=Evcy5nBq; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=znC+/fR4
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 WKn1TYaYC4hW; Sun, 8 Oct 2017 08:51:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7228C1346C5; Sun, 8 Oct 2017 08:51:58 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.87.111]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v98FpdEJ000890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Oct 2017 08:51:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1507477911; x=1507564311; bh=BDNZe9ivW9pdPLI4FE7Mp+dEENu3WFHLjIlues72NVk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Evcy5nBqTPkVywkbLzam2ZB2R09hqhtBkdHS0QBPNTL2cHqmWxEjLz7JneJYWQTSg qzEsQKniBFZiygw305w/oYebxGi0lGXTLF5UNb1qAcdpcJVLDmxVNrAg1BZFjMbpYb e6MPVfREJe7wAqHcgLOn4X/OaTbCS5IKQWvs7Oes=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1507477911; x=1507564311; i=@elandsys.com; bh=BDNZe9ivW9pdPLI4FE7Mp+dEENu3WFHLjIlues72NVk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=znC+/fR4J5uXdK+nBN6EZm1oA2DeHsetiencptabiEo0Z8CLzf2VH0UVBstjLE7Iv oHQoh2w4y7OcoozMr/jOuq+3+yPpXF+/gPTud5BhWkHKJ2lRZPKoMUiQlczVdg2I/N VALfW/zbD+gJRv7EywmNT+gUBChijiz+hEae/5pw=
Message-Id: <6.2.5.6.2.20171008080321.0f8ded68@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 08 Oct 2017 08:43:11 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: sunset4@ietf.org, Lee Howard <Lee@asgard.org>
In-Reply-To: <150660518277.13796.5801483741214576151.idtracker@ietfa.ams l.com>
References: <150660518277.13796.5801483741214576151.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sunset4/Id-O38MD_bWlgWc4XwKqlm6bX0g>
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: Sun, 08 Oct 2017 15:52:00 -0000

Hello,

I'll disclose that there is a potential conflict of interest and I am 
involved in a RIR [1].

At 06:26 AM 28-09-2017, The IESG wrote:
>The IESG has received a request from the Sunsetting IPv4 WG (sunset4) to
>consider the following document: - 'IETF: End Work on IPv4'
>   <draft-ietf-sunset4-ipv6-ietf-01.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits final
>comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2017-10-12. Exceptionally, comments may be

I read this short draft and the document shepherd write-up.  The 
explanation about why the document should be published as a "Proposed 
Standard" is that "it creates key implications on all future 
standards track documents".  Is that what the "Proposed Standard" 
label is about?

There is the following in Section 1: "Until the time when IPv4 is no 
longer inwide use and/or declared historic ..."  It is unrealistic to 
envision a near future where the IETF would "declare" IPv4 as "Historic".

I'll commend the author for not overloading the "must" in this 
draft.  Is this document about the IETF not doing any more work on 
IPv4-related technologies unless there is a security issue to fix and 
there is consensus [2] to do that?

Regards,
S. Moonesamy

1. Please do not read the disclosure as a statement from the RIR.  My 
interest predates the RIR involvement.
2. Please see Section 2 of the draft.