Re: [v6ops] About Req for Comments - "Transition to IPv6"

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 05 March 2020 12:25 UTC

Return-Path: <prvs=1333cdedec=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D21C3A13B7 for <v6ops@ietfa.amsl.com>; Thu, 5 Mar 2020 04:25:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 3gcShMOjpcvK for <v6ops@ietfa.amsl.com>; Thu, 5 Mar 2020 04:25:44 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5E153A13B5 for <v6ops@ietf.org>; Thu, 5 Mar 2020 04:25:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1583411141; x=1584015941; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=zPynW04U b7RSdS2OlJ0wXD+AjKsI2QfIj28BR0xI4F0=; b=voG7A6h05HpPVoj0X5TTpvk5 optNTBWluCbEM7vWCHvMxpVc9L8ObMgGntP3M0OLuG4DUMaNvXOyBz6GmrptsDJP 7TGEqIU/6NaiHp7wTJTyn48WKclC7ZqM4c5VeiFbbcLNxRIZRTI2a7zoyidDEUUT CZDvoJWqZztuTk43nOs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 05 Mar 2020 13:25:41 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 05 Mar 2020 13:25:41 +0100
Received: from [192.168.11.230] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000081152.msg for <v6ops@ietf.org>; Thu, 05 Mar 2020 13:25:41 +0100
X-MDRemoteIP: 2001:4288:1301:610:b07a:fd37:3fe0:635a
X-MDHelo: [192.168.11.230]
X-MDArrival-Date: Thu, 05 Mar 2020 13:25:41 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1333cdedec=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.22.0.200209
Date: Thu, 05 Mar 2020 13:25:38 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <0791D4B0-8390-48D7-AF0A-CE004EC3224C@consulintel.es>
Thread-Topic: [v6ops] About Req for Comments - "Transition to IPv6"
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <7eb4dc25-28a6-4927-2356-846e200681d2@gmail.com>
In-Reply-To: <7eb4dc25-28a6-4927-2356-846e200681d2@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Y-EC3BfP75LkOqjStE8Z0mEN-60>
Subject: Re: [v6ops] About Req for Comments - "Transition to IPv6"
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2020 12:25:49 -0000

This is why I've insisted several times in having a document describing what is IPv6-only ...

I can update it again if the WG is interested ...

https://tools.ietf.org/html/draft-palet-v6ops-ipv6-only-04
 

El 5/3/20 13:13, "v6ops en nombre de Alexandre Petrescu" <v6ops-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:

    
    I learned from an IPv6 old timer at an ITU meeting about this "Request
    for Comments on Updated Guidance for Completing the Transition to the
    Next Generation Internet Protocol, Internet Protocol Version 6 (IPv6)"
    
    https://www.federalregister.gov/documents/2020/03/02/2020-04202/request-for-comments-on-updated-guidance-for-completing-the-transition-to-the-next-generation
    
    It mainly concerns organisations in the United States of America, but
    they seek 'public' comment in 30 days, which amounts to about everyone,
    I think.
    
    One comment that I would like to make is to better explain what
    IPv6-only is.  To distinguish from the IPv6-only claimed in some cases,
    at mobile operators, which is carried by IPv4 in fact.  And to comment
    that I hope that Request for Comments' hope of transition to IPv6 is
    pure IPv6 not carried by IPv4.
    
    I could send that comment to the indicated email address
    "OFCIO@omb.eop.gov" but I suppose there might be some risk of that
    message getting lost.
    
    Alex
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.