Re: [v6ops] IPv6-only Terminology Definition

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

Return-Path: <prvs=1340af7d02=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 801B63A0A7E for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 03:44:49 -0700 (PDT)
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 35R55-vC00-7 for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 03:44:48 -0700 (PDT)
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 745B53A0A53 for <v6ops@ietf.org>; Thu, 12 Mar 2020 03:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1584009885; x=1584614685; 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=8hTmHJFm 1k2uS60GL6VwUkXNszSz3RlS9C2LuR/49UM=; b=KiMtvOEvg2gPgi5yqaoaauPm 30k7DrtK/TEIuowiHxsQsT2uOR2kjWB2nNq46DWtP3r+9hyo4Ym0KSxmqUtijmYx aIUymBjTLRLHL+r9DA55pbANQlhU5jsVwfqbH0r7IEfnESwFy7jS/vMYob/ztJmy dak5BDCiB3VClTmwxbU=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 12 Mar 2020 11:44:45 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 12 Mar 2020 11:44:44 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000089001.msg for <v6ops@ietf.org>; Thu, 12 Mar 2020 11:44:44 +0100
X-MDRemoteIP: 2001:470:1f09:495:e0a6:81ab:ea8d:1a06
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Thu, 12 Mar 2020 11:44:44 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1340af7d02=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.35.20030802
Date: Thu, 12 Mar 2020 11:44:43 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <AA669C3B-BF00-4B46-839F-5101549E2D9B@consulintel.es>
Thread-Topic: [v6ops] IPv6-only Terminology Definition
References: <4A886236-7D17-41F2-8291-0BC1B49F7A59@consulintel.es> <ECC49840-B99A-4A4A-B5F0-0C013DD98E27@gmail.com>
In-Reply-To: <ECC49840-B99A-4A4A-B5F0-0C013DD98E27@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/U1BHbYsW9hlYOGIoXivaxvR43pQ>
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: Thu, 12 Mar 2020 10:44:50 -0000

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.