Re: [v6ops] New Version Notification for draft-ietf-v6ops-ipv6-deployment-01.txt

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 03 June 2021 06:07 UTC

Return-Path: <prvs=1788d66581=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 295A93A2B86; Wed, 2 Jun 2021 23:07:30 -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 uFbzGlmZwszf; Wed, 2 Jun 2021 23:07:23 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 25C593A2B87; Wed, 2 Jun 2021 23:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1622700440; x=1623305240; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=JIA5jdffkEmgNp4Te5wq/LecKireu3Yms2DMqx9k5vU=; b=nY9aGxYJpjSOU lEN+xsDgMd5fqzERUKPMJaSCr6o51Xx57tC/s0kTxVEV3NpxlYR4hUEBOsO8Xl+5 VF5nyHeXwMLAmvJTififRKP9Vz6MJYyzLNgKXvbG5TTunELOJhdo0yniQWaisih7 8A+QQICsjtIFspQppbLTDW8Fr6bksU=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 03 Jun 2021 08:07:20 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 03 Jun 2021 08:07:19 +0200
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000606340.msg; Thu, 03 Jun 2021 08:07:18 +0200
X-MDRemoteIP: 2001:470:1f09:495:2dd5:d0fb:1ac1:c68d
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Thu, 03 Jun 2021 08:07:18 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1788d66581=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
User-Agent: Microsoft-MacOutlook/16.49.21050901
Date: Thu, 03 Jun 2021 08:07:15 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Fred Baker <fredbaker.ietf@gmail.com>, Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
CC: "draft-ietf-v6ops-ipv6-deployment@ietf.org" <draft-ietf-v6ops-ipv6-deployment@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <4D1355CF-D62C-4BAB-8DC8-8FB2822CF854@consulintel.es>
Thread-Topic: [v6ops] New Version Notification for draft-ietf-v6ops-ipv6-deployment-01.txt
References: <162254159656.7448.7482055154071850824@ietfa.amsl.com> <9da707a66e10475bb98abae5e3f7cb3f@huawei.com> <01D305D0-276E-4D66-9AC3-ED038C5AD11E@gmail.com>
In-Reply-To: <01D305D0-276E-4D66-9AC3-ED038C5AD11E@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/nB9XtHhUGsAqoQdhMrMZc0j4rNo>
Subject: Re: [v6ops] New Version Notification for draft-ietf-v6ops-ipv6-deployment-01.txt
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, 03 Jun 2021 06:07:30 -0000

Hi Fred,

I think there was a misunderstanding then.

You asked (around March if I recall correctly) on the adoption of this draft and another one and for some reason authors understood that the signal was "go" for both documents.

I think there was only one participant not supporting the adoption (and actually confused both drafts).

Regards,
Jordi
@jordipalet
 
 

El 3/6/21 0:48, "v6ops en nombre de Fred Baker" <v6ops-bounces@ietf.org en nombre de fredbaker.ietf@gmail.com> escribió:

    Well, yes, and it appears in the draft repository under the name on the subject line. We have a cart-before-horse issue here, which is why Ron is asking the working group for adoption.

    > On Jun 1, 2021, at 3:19 AM, Giuseppe Fioccola <giuseppe.fioccola@huawei.com> wrote:
    > 
    > Hi All,
    > We just published a new version of our draft on IPv6 Deployment Status. It was thoroughly reviewed to address the high number of comments.
    > 
    > In particular, it is possible to mention the most important changes:
    > - A survey among Enterprises has been added,
    > - IPv6 overlay service design and IPv6 underlay network deployment are now described in separate sections in order to differentiate the approaches.
    > - New sections have been added on
    > 	- IPv6 web content,
    > 	- CPEs and user devices,
    > 	- Transition technologies security,
    > 	- Customer experience
    > 
    > Comments and suggestions are always welcome.
    > 
    > Best Regards,
    > 
    > Giuseppe
    > 
    > -----Original Message-----
    > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
    > Sent: Tuesday, June 1, 2021 12:00 PM
    > To: Gyan S. Mishra <gyan.s.mishra@verizon.com>; Chongfeng Xie <xiechf@chinatelecom.cn>; Giuseppe Fioccola <giuseppe.fioccola@huawei.com>; Gyan Mishra <gyan.s.mishra@verizon.com>; Jordi Martinez <jordi.palet@theipv6company.com>; Jordi Palet Martinez <jordi.palet@theipv6company.com>; Nalini Elkins <nalini.elkins@insidethestack.com>; Paolo Volpato <paolo.volpato@huawei.com>
    > Subject: New Version Notification for draft-ietf-v6ops-ipv6-deployment-01.txt
    > 
    > 
    > A new version of I-D, draft-ietf-v6ops-ipv6-deployment-01.txt
    > has been successfully submitted by Giuseppe Fioccola and posted to the IETF repository.
    > 
    > Name:		draft-ietf-v6ops-ipv6-deployment
    > Revision:	01
    > Title:		IPv6 Deployment Status
    > Document date:	2021-06-01
    > Group:		v6ops
    > Pages:		38
    > URL:            https://www.ietf.org/archive/id/draft-ietf-v6ops-ipv6-deployment-01.txt
    > Status:         https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-deployment/
    > Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-ipv6-deployment
    > Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-ipv6-deployment-01
    > 
    > Abstract:
    >   Looking globally, IPv6 is growing faster than IPv4.  This means that
    >   the networking industry is selecting IPv6 for the future.  This
    >   document provides an overview of IPv6 transition deployment status
    >   and a view on how the transition to IPv6 is progressing among network
    >   operators and enterprises that are introducing IPv6 or have already
    >   adopted an IPv6-only solution.  It also aims to analyze the
    >   transition challenges and therefore encourage actions and more
    >   investigations on some areas that are still under discussion.  The
    >   overall IPv6 incentives are also examined.
    > 
    > 
    > 
    > 
    > The IETF Secretariat
    > 
    > 
    > _______________________________________________
    > 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.