Re: [v6ops] IPv6-only Terminology Definition

Fred Baker <fredbaker.ietf@gmail.com> Fri, 13 March 2020 00:48 UTC

Return-Path: <fredbaker.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 5F07C3A0B22 for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 17:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 m_9w3_45EtRZ for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 17:48:18 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 A51FF3A0B1C for <v6ops@ietf.org>; Thu, 12 Mar 2020 17:48:18 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id m5so3949305pgg.0 for <v6ops@ietf.org>; Thu, 12 Mar 2020 17:48:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=dfjX5AQCqNNFQWlauvvxBx+gtIsfSp/SawE6fYNhBwc=; b=qipji60k9kYhpDXsRdbJPcgb35dqXGs5oUf8Zs1YdHmFZz6icFj/5WdOQXAtDLaQIJ jX39sIAXqQawDJBAa5oWOoJqE5MCsjYCpWxWip5buDbNs33xiPHbeBOjm8m65abdyKYq 9c6ZeXxUQ/4YPg6Yw+SKm4ev612y3is8GgBsSDFgG8nKuOG4aMT74yolz/vavpu9OYkn ihFDOgANeyMJuxGCdCryNyBM1ddfPo32FSr3bf2CdKlBiWZDkhwnYdZ+QBuzpGE/DDzV NZ51V3iMCAW4XP7PBYz4cVmYku7p6flavWvgWnDDM1NlfeKAmB5caYMc7sDnItOpFQLm p3Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=dfjX5AQCqNNFQWlauvvxBx+gtIsfSp/SawE6fYNhBwc=; b=oxYSZ7lt5l7dTNLYnXBete6lYxHLLCT5Y0yXGtCjEvm1xieTVPJ81OZ7CMs3fTRRaF TzZ6eI28xtg2Ax6JIkYRLmd0cxz7TywG+lM8ZSURS+bMQcvLwNX86fLJtVBQIJs6CKhb OiyIbTDnZ3DXDgu27U8SdqAUXABr+/I/zUcWzqRjQPBxWLbtttgYA58dGox6GCQ7XIz8 Utg9eOEWRtIrvhG19dXBgumcXnYsXoJHCwASBEwlsHCU4hqlOpCJCvUKgkeHOLEM6JbW 2y6pIeTs3hl6cXcSivpltXycYjAPGfgC74YzEnMBj6c9U1GFxZTdnOEm+PuiUoLdxuSR Q6+g==
X-Gm-Message-State: ANhLgQ25bmt2Ay8Ev68NStG+z1t+AWBSgfkNxlFUH3mEu23ZBKY9g1+/ bTBrf2rWVtqPPIrX7IExKPk=
X-Google-Smtp-Source: ADFU+vtM2bKcEpdoPLCXfSVfgChSF6xqm2dsq34KqikuXB53zU0yUC2/NAgbJe4ijzlYviSdSLEfLA==
X-Received: by 2002:a63:741c:: with SMTP id p28mr9421359pgc.402.1584060498050; Thu, 12 Mar 2020 17:48:18 -0700 (PDT)
Received: from ?IPv6:2600:8802:5900:13c4::101f? ([2600:8802:5900:13c4::101f]) by smtp.gmail.com with ESMTPSA id n5sm3864571pfq.35.2020.03.12.17.48.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 12 Mar 2020 17:48:17 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <AA669C3B-BF00-4B46-839F-5101549E2D9B@consulintel.es>
Date: Thu, 12 Mar 2020 17:48:16 -0700
Cc: v6ops@ietf.org
Message-Id: <9F85B373-6A38-43CD-9CC0-A31A128AB94C@gmail.com>
References: <AA669C3B-BF00-4B46-839F-5101549E2D9B@consulintel.es>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KglZhgE2bo3aQjNwSriTlz04gsc>
Subject: Re: [v6ops] IPv6-only Terminology Definition
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: Fri, 13 Mar 2020 00:48:21 -0000

Right now, as always, I’m looking for supportive working group commentary.

Sent using a machine that autocorrects in interesting ways...

> On Mar 12, 2020, at 3:45 AM, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
> 
> Yes, sorry, there is a typo there.
> 
>       However, the "end-networks", in general, need to continue supporting
>       IPv4, as there are many devices or apps, in both corporate and end-
>       user networks (smartTV, IP cameras, etc.), which are IPv4-only and it
>       is not always feasible to update or replace them.  Also if customer
>       devices in a LAN are ***IPv4-only***, they will not be able to access
>       IPv6-only services, so this means that IPv6-only services can't be
>       deployed unless it is done in such way that some transition mechanism
>       solves that problem as well (example an IPv6-only Data Center,
>       requires SIIT-DC)
> 
> 
> I've corrected in my internal draft v-06, but will wait for more inputs before publishing it.
> 
> Or maybe we could even consider a call for WG adoption?
> 
> Thanks for spotting it!
> 
> 
> El 12/3/20 7:58, "v6ops en nombre de Fred Baker" <v6ops-bounces@ietf.org en nombre de fredbaker.ietf@gmail.com> escribió:
> 
>    Section 2, fourth paragraph.
> 
>       However, the "end-networks", in general, need to continue supporting
>       IPv4, as there are many devices or apps, in both corporate and end-
>       user networks (smartTV, IP cameras, etc.), which are IPv4-only and it
>       is not always feasible to update or replace them.  Also if customer
>       devices in a LAN are IPv6-only, they will not be able to access
>       IPv6-only services, so this means that IPv6-only services can't be
>       deployed unless it is done in such way that some transition mechanism
>       solves that problem as well (example an IPv6-only Data Center,
>       requires SIIT-DC)
> 
>    I don't understand why an IPv6-only device would not be able to access an IPv6-only services. I can understand IPv4-only devices not being able to access IPv6-only services, but that's not the statement. This paragraph seems to not follow.
> 
>> On Mar 9, 2020, at 11:47 AM, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
>> 
>> Hi all,
>> 
>> After the recent discussion, I've posted a new version (minor changes) for this document:
>> 
>> https://datatracker.ietf.org/doc/draft-palet-v6ops-ipv6-only/?include_text=1
>> 
>> Comments welcome!
>> 
>> Regards,
>> Jordi
>> @jordipalet
>> 
>> 
>> 
>> 
>> 
>> **********************************************
>> 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.
>> 
>> 
>> 
>> _______________________________________________
>> 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
> 
> 
> 
> 
> **********************************************
> 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.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops