IETF Logo Mail Archive

Re: [v6ops] draft-vf-v6ops-ipv6-deployment

Paolo Volpato <paolo.volpato@huawei.com> Mon, 22 March 2021 14:56 UTC

Return-Path: <paolo.volpato@huawei.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 8440A3A1735 for <v6ops@ietfa.amsl.com>; Mon, 22 Mar 2021 07:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.011
X-Spam-Level:
X-Spam-Status: No, score=0.011 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 ml2cUK9kG6k0 for <v6ops@ietfa.amsl.com>; Mon, 22 Mar 2021 07:56:08 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D353A173A for <v6ops@ietf.org>; Mon, 22 Mar 2021 07:56:08 -0700 (PDT)
Received: from fraeml708-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F3y805cMpz682B1; Mon, 22 Mar 2021 22:49:36 +0800 (CST)
Received: from fraeml740-chm.china.huawei.com (10.206.15.221) by fraeml708-chm.china.huawei.com (10.206.15.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Mar 2021 15:56:01 +0100
Received: from fraeml740-chm.china.huawei.com ([10.206.15.221]) by fraeml740-chm.china.huawei.com ([10.206.15.221]) with mapi id 15.01.2106.013; Mon, 22 Mar 2021 15:56:01 +0100
From: Paolo Volpato <paolo.volpato@huawei.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Giuseppe Fioccola <giuseppe.fioccola@huawei.com>, "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>
Thread-Topic: [v6ops] draft-vf-v6ops-ipv6-deployment
Thread-Index: AdcZodmxnT/gHUc+SxeIL8JgufiaKgC+s0iAAKNbSUA=
Date: Mon, 22 Mar 2021 14:56:01 +0000
Message-ID: <74d6dca7019f44aba09caf47ef703e2f@huawei.com>
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <CAB75xn4ioyzQ5AvUrPKVyuybjZRV__Tv1OMs70Lm-z9bo1Eo6g@mail.gmail.com>
In-Reply-To: <CAB75xn4ioyzQ5AvUrPKVyuybjZRV__Tv1OMs70Lm-z9bo1Eo6g@mail.gmail.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.89.193]
Content-Type: multipart/alternative; boundary="_000_74d6dca7019f44aba09caf47ef703e2fhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CIN_t-9OOWx02hBH6NPuxEAodNQ>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment
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: Mon, 22 Mar 2021 14:56:13 -0000

Hi Dhruv,



Many thanks for your comments.

Please see inline our considerations.



Best regards

Paolo



-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Dhruv Dhody
Sent: Friday, March 19, 2021 10:49 AM
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment



Hi,



I have read the I-D and found it to be useful in describing the current status, challenges, and next steps for IPv6 deployments.



Should we add some text on IPv6 in the campus networks at universities, they have been early adopters in past and some of the enterprise considerations that apply to them, however, business/government incentives might be different.

[PV] Good suggestion. Actually, it may give a positive perspective, as you said some of them gained a good experience on early IPv6 adoption.



I think we should highlight that we do not have visibility inside the enterprises beyond the external-facing website or email and thus it is also difficult to gauge the IPv6 deployments inside enterprises.

[PV] Ok. Probably here you refer to small-medium enterprises. For large enterprises public data on the usage of IPv6 can be retrieved (Nalini, in copy, provided a good input on IPv6 in large organizations). We will better specify this point in the next version of the draft.



Some minor nits -

- Consider updating the boilerplate from RFC 2119 to RFC8174.

- Add a reference for the IAB statement in Section 1.

- Expand RIR, 6rd on first use, you expand it later on!

- Expand SRv6, SDO

[PV]. Sure, we will integrate all of your recommendations in the next version.



Thanks!

Dhruv





On Mon, Mar 15, 2021 at 7:19 PM Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>> wrote:

>

> Folks,

>

>

>

> Each week between now and IETF 111, we will review and discuss one draft with an eye towards progressing it.

>

>

>

> This week, please review and comment on draft-vf-v6ops-ipv6-deployment.

>

>

>

>                                                              Fred and

> Ron

>

>

>

>

>

>

> Juniper Business Use Only

>

> _______________________________________________

> v6ops mailing list

> v6ops@ietf.org<mailto:v6ops@ietf.org>

> https://www.ietf.org/mailman/listinfo/v6ops



_______________________________________________

v6ops mailing list

v6ops@ietf.org<mailto:v6ops@ietf.org>

https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email