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

Erik Kline <ek.ietf@gmail.com> Thu, 05 March 2020 16:38 UTC

Return-Path: <ek.ietf@gmail.com>
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 7B8293A17B4 for <v6ops@ietfa.amsl.com>; Thu, 5 Mar 2020 08:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 51C3Hnmx5WM1 for <v6ops@ietfa.amsl.com>; Thu, 5 Mar 2020 08:38:18 -0800 (PST)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (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 357893A17B2 for <v6ops@ietf.org>; Thu, 5 Mar 2020 08:38:18 -0800 (PST)
Received: by mail-oi1-x229.google.com with SMTP id a22so6549172oid.13 for <v6ops@ietf.org>; Thu, 05 Mar 2020 08:38:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qVMyHAr9r8AqkkQv4h8OMevLXTnvG2gNM91ahJzPKJI=; b=LLlGmMOY2Ct3gGtTfJHm7e1Llj38kFcG1jJGlnV02Dl6zEYRBam7clhHXu/VdoiCX5 ljXWp2SLAe/Y/DXi7zqcQiDz0p7IlBgHvv38CkQbMYCy6RlfwAowBQmEksKCMweh+M2n jt1AnXmaD9Mtq/GiJ77q2N2OjqUDTin6bdX/WDzisR+jDcfvT2iJFSLPUASudHBtjlDs dDM9O164U9m0ZjxUDKXwdW4sG6H8GMESGl7Ddxg1/liD0DIXUYVs8A6jR4J//2qCRs04 hA8XSOloH/aRm24uv5SisKUYzzOtzjnhjHr0SANikTES5ch3obAOACdwqhVoyIsj1RuZ lr5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qVMyHAr9r8AqkkQv4h8OMevLXTnvG2gNM91ahJzPKJI=; b=cW3TMe5sj6NI8WOc01lwhAQh3Ha2FPzYLmFvcSBrcFBYg3IBtD2j7aafXllbWCcQHJ DlOip1ckb3Mdw+V0VafwRkOR4PCvW4vrnAIEYjATZ4ENwN2LvXwaROGUYR0BDPS2Gv1k 8uxUHzB8y14u9fiO75YT6/Swjo2A0Czs/b7nYWqgE5FuAyEpNez+WsT0sfB3zi90CLdU /d33J/CjkAZEhaEDB/pqyQ51ICtxPBTGDhjg1LKpwo8C4RP9ZcsR0sj1vS0ppKjg+/mo HbXfCckQ8e/VjAgvOWhWc3+aFIXkpJ3h70mMCFfhFSCSpL+4/nxf5yfB1m9sePPKtdCg RuWA==
X-Gm-Message-State: ANhLgQ008asD72JjgIav3izaBxiv16A0g9JUoRWdF9JUHIuEsKWNKTrl TpKhhe9qKOCU575fGYJkveBkg+94qakHFadgvjQ=
X-Google-Smtp-Source: ADFU+vst25P8WLpEWgzzZ+ShL1gYlNipefKbe5s3drp9uKHrcKcEk656HWdyU6CnxoI9zDQUw/ng/AmnrZTKj2NVnos=
X-Received: by 2002:aca:4f8e:: with SMTP id d136mr6353846oib.77.1583426297491; Thu, 05 Mar 2020 08:38:17 -0800 (PST)
MIME-Version: 1.0
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <7eb4dc25-28a6-4927-2356-846e200681d2@gmail.com> <0791D4B0-8390-48D7-AF0A-CE004EC3224C@consulintel.es> <ccc75efb-8c00-ee97-5cc7-2e061e6e5a54@gmail.com> <52b6b9a4f46a49598eccee1b35e5efc5@irs.gov> <89127c25-9c51-c4bb-97ae-3567e80a4c52@gmail.com>
In-Reply-To: <89127c25-9c51-c4bb-97ae-3567e80a4c52@gmail.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Thu, 05 Mar 2020 08:38:06 -0800
Message-ID: <CAMGpriVCHFWL0O21C8XnQZGrrKaiRwANUGLRrJTcBe75cpZGJw@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fd748d05a01e291c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/depkauJ8jqMQ_DajzNJw3Mytqxw>
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 16:38:21 -0000

Eliminating IPv4 implies eliminating the use of IPv4.

Eliminating the *use* of IPv4 does not imply eliminating IPv4.

I don't see any real problem here.  Maybe they *want* the vagueness (i.e.
absence of over-specificity) to have some grey area to support NAT64/DNS64
(or maybe even 464xlat).

On Thu, Mar 5, 2020 at 6:03 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> Thank you very much for the pointer.  In it I could spot
> the following footnote: "[4] IPv6-Only refers to network environments in
> which use of the IPv4 protocol has been eliminated."
>
> In my humble opinion,
>
> I think, if I am not wrong, that there are no such networks in which
> IPv4 protocol has been eliminated.  On one hand, a network is made of
> computers, and IPv4 stacks are still present in almost all computers.
> On another hand, there might be some ptp links (not networks, but
> individual links) that run IPv6 only.
>
> That is why it is hard to agree on the assumption of IPv4 being
> eliminated somewhere.  Worse, it makes look as if the goal of that
> 'IPv6-only' is to arrive at that same situation which in fact does use
> IPv4.
>
> There is a draft at IETF in this v6ops WG, about the term 'IPv6-only'.
> We could improve that draft.  We could refer to it as well.
>
> Further, in this Req for Comments 'Transition to IPv6' this text makes
> me think they set the wrong goal:
> > In fact, many of these organizations have migrated, or are planning
> > to migrate, to “IPv6-only”4 infrastructures to reduce operational
> > concerns associated with maintaining two distinct network
> > infrastructures. The intent of this updated memorandum is to
> > communicate the requirements for completing the operational
> > deployment of IPv6 across all Federal information systems and
> > services, and help agencies overcome barriers that prevent them from
> > migrating to IPv6-only systems. Going forward, the Federal
> > government plans to deliver its information services, operate its
> > networks, and access the services of others using only IPv6.
>
> The guidance would, better, make think about the removal of the IPv4
> stack.  For example, uncheck the IPv4 box in Windows ethernet interface
> properties, or remove 127.0.0.1 from /etc/hosts, remove A entries from
> DNS, or similar.  These are criteria easily checked by more people.
>
> In my humble opinion.
>
> Alex
>
>
> Le 05/03/2020 à 14:33, Morizot Timothy S a écrit :
> > Since the formal request for comment has been published on the
> > federal register, a direct link to the draft as published on the
> > Federal CIO website (within OMB) might facilitate review and comment.
> > I see some confusion about how to read the draft memorandum itself.
> >
> >
> https://www.cio.gov/assets/resources/internet-protocol-version6-draft.pdf
> >
> >
> >
> >
> HTH,
> >
> > Scott
> >
> > -----Original Message----- From: v6ops <v6ops-bounces@ietf.org> On
> > Behalf Of Alexandre Petrescu Sent: Thursday, March 5, 2020 7:08 AM
> > To: v6ops@ietf.org Subject: Re: [v6ops] About Req for Comments -
> > "Transition to IPv6"
> >
> >
> >
> > Le 05/03/2020 à 13:25, JORDI PALET MARTINEZ a écrit :
> >> 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
> >
> > To me it might make sense to start from there.
> >
> > At this time, although I can click on the URL, it leads to a phrase
> > "The attached draft memorandum prepared by the Office of Management
> > and Budget, in collaboration with the Federal Chief Information
> > Officers Council and Federal Chief Information Security Officers
> > Council, supports the Administration’s goals for modernizing Federal
> >  Information Technology".  I can not find that 'draft memorandum'.
> >
> > I can not find precisely what are the questions to comment on.  Or
> > there might be no precise question, just an overall indication of
> > ambition.
> >
> > Alex
> >
> > _______________________________________________ v6ops mailing list
> > v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> >
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>