Re: [v6ops] IPv6-only draft

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sat, 20 July 2019 15:43 UTC

Return-Path: <prvs=1104a502aa=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 E4B1C12010D for <v6ops@ietfa.amsl.com>; Sat, 20 Jul 2019 08:43:35 -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 2Q4_wAPndAsX for <v6ops@ietfa.amsl.com>; Sat, 20 Jul 2019 08:43:33 -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 30B2E120103 for <v6ops@ietf.org>; Sat, 20 Jul 2019 08:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1563637410; x=1564242210; 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=SGbR6ILL vDCxK1jVSGmpE3sYWZWMys2MNgPpbstAM1k=; b=jXWldLAu237Je8gdeM7BTBI/ t99CLPoubDqMgZawcFlesSJC6Lr4hgviE9ZsbA4pes7llSpKQ20NiXWnEl6eMzDc TTUH/UsgqOfb+6ROi4HGJlWCHck+sRmop8Jm4L6JeBapuhZxKAOyY1+dE0vGRjg0 W4vx+HopqHV4+TpDMrY=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Sat, 20 Jul 2019 17:43:30 +0200
X-Spam-Processed: mail.consulintel.es, Sat, 20 Jul 2019 17:43:30 +0200
Received: from [172.16.45.27] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006331061.msg for <v6ops@ietf.org>; Sat, 20 Jul 2019 17:43:29 +0200
X-MDRemoteIP: 82.3.55.76
X-MDHelo: [172.16.45.27]
X-MDArrival-Date: Sat, 20 Jul 2019 17:43:29 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1104a502aa=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.c.190715
Date: Sat, 20 Jul 2019 16:54:03 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>, IPv6 Operations <v6ops@ietf.org>
Message-ID: <A229DADE-7238-42BA-BDDC-2D2E6A9850E5@consulintel.es>
Thread-Topic: [v6ops] IPv6-only draft
References: <5694C033-A38F-4455-9673-EACAAC6324F3@gmail.com> <DM6PR15MB250634DDD5B709C49426080FBBCB0@DM6PR15MB2506.namprd15.prod.outlook.com>
In-Reply-To: <DM6PR15MB250634DDD5B709C49426080FBBCB0@DM6PR15MB2506.namprd15.prod.outlook.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/Id2z6NTMFQDVINuEdnQ08jG85LY>
Subject: Re: [v6ops] IPv6-only draft
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: Sat, 20 Jul 2019 15:43:36 -0000

Hi Dusan,


El 20/7/19 7:35, "v6ops en nombre de Mudric, Dusan (Dusan)" <v6ops-bounces@ietf.org en nombre de dmudric@avaya.com> escribió:

    
    
    "3.  Definition of IPv6-only
    
       Consequently, considering the context described in the section above,
       if we want to be precise and avoid confusing others, we can not use	
       the terminology "IPv6-only" in a generic way, and we need to define
       what part of the network we are referring to.
    
       From that perspective, we define the "IPv6-only" status in a given
       part(s) of a network, depending on if there is actual native
       forwarding of IPv4, so IPv4 is not configured neither managed."
    
    The document defines IPv6-only not only for the network parts but also for a host/router.

-> I see this document as to have view "end-to-end". So, from host A (source) to host B (destination), is it IPv6-only? Under that perspective, the hosts, routers, involve in that end-to-end communication, are also part of the network. If this is not clear, I could expand the text on this section to clarify that. Do you have any suggested wording?
    
    "7.  IPv6-only WAN/access
    
       IPv6-only WAN or access can be used only if the WAN or access network
       isn't actually natively forwarding IPv4."
    
    Should use affirmative kind of definitions for IPv6-only, not only here but also in other sections. Instead of "isn't actually natively forwarding IPv4" should define what it IS forwarding, like "is natively forwarding IPv6".

-> I think it is clearer with the negative form, unless this is incorrect in English? I'm not native speaker. If I use affirmative it gets more complex:
"isn't actually natively forwarding IPv4"
vs
"is actually forwarding natively IPv6 and not natively IPv4"
    
    "10.  Transitional IPv6 host/router
    
       Transitional IPv6 host/router is a dual-stack host/router with
       IPv6-only WAN where IPv4 service support is provided by means of
       transition mechanism, IPv4aaS (IPv4-as-a-service)."

-> not sure what is the input here?
    
    Dusan
    
    Why is it important to mention WAN address family? Why WAN must be IPv6-only?

-> Because the full reason or "starting-point" of the document is the IPv6-only terminology clarification.

    
    > -----Original Message-----
    > From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Fred Baker
    > Sent: Tuesday, July 16, 2019 8:27 PM
    > To: IPv6 Operations <v6ops@ietf.org>
    > Subject: [v6ops] IPv6-only draft
    > 
    > The author is asking for time on the agenda at IETF 105; I told him that if there
    > was time at the end of the meeting, it could be part of "AOB". I don't see any
    > discussion on the draft since November 2017.
    > 
    > FYI, draft-ietf-6man-ipv6only-flag is a different topic.
    > 
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__tools.ietf.org_html_draft-2Dpalet-2Dv6ops-2Dipv6-
    > 2Donly&d=DwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrh
    > IoUWB8YLZU23029sMQGQ2kY&m=1nAt78nefTz-p_aiWCrcg5YAes1Z-
    > E1BJms0WuHLM2M&s=UNkIjLs2G5OnvxDyoSyysQPWYTYrk9wTfadmnnr57kg
    > &e=
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__mailarchive.ietf.org_arch_search_-3Fqdr-3Da-26q-3D-2522draft-
    > 2Dpalet-2Dv6ops-2Dipv6-2Donly-
    > 2522&d=DwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIo
    > UWB8YLZU23029sMQGQ2kY&m=1nAt78nefTz-p_aiWCrcg5YAes1Z-
    > E1BJms0WuHLM2M&s=E1m_qHn7RsRktmhF07Nf9eanzgGmtNP7lQ29Kyr5su
    > E&e=
    > 
    > Your comments appreciated.
    > 
    > --------------------------------------------------------------------------------
    > The fact that there is a highway to hell and a stairway to heaven is an
    > interesting comment on projected traffic volume...
    > 
    > _______________________________________________
    > v6ops mailing list
    > v6ops@ietf.org
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__www.ietf.org_mailman_listinfo_v6ops&d=DwICAg&c=BFpWQw8bsuKpl
    > 1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=1nAt
    > 78nefTz-p_aiWCrcg5YAes1Z-E1BJms0WuHLM2M&s=595l-
    > RsCyu_0mPOHtZ0uecureSaBYL3jaFjC9O1xAwY&e=
    
    _______________________________________________
    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.