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

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Tue, 30 March 2021 07:32 UTC

Return-Path: <giuseppe.fioccola@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 446E03A156B for <v6ops@ietfa.amsl.com>; Tue, 30 Mar 2021 00:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 VewxOIGPaJdS for <v6ops@ietfa.amsl.com>; Tue, 30 Mar 2021 00:32:54 -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 7C3B93A14F1 for <v6ops@ietf.org>; Tue, 30 Mar 2021 00:32:54 -0700 (PDT)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F8gwb6R6Cz683Xm; Tue, 30 Mar 2021 15:26:07 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 30 Mar 2021 09:32:49 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2106.013; Tue, 30 Mar 2021 09:32:49 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-v6ops-ipv6-deployment
Thread-Index: AQHXIsXkv/dCiwCMNkqKworNQJ5cEKqbDJKAgAEWE1A=
Date: Tue, 30 Mar 2021 07:32:49 +0000
Message-ID: <f4c3cef649184f66bc0b13554fc709cc@huawei.com>
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <59B5C1F7-48E4-4915-BAAC-41D8ADA29E8F@gmail.com> <18ea74665936408bb33f20630da95311@huawei.com> <E0757B36-8FFB-43A8-8F8B-A7F152F81156@gmail.com> <2cfecf2c-5526-92d0-716d-5e07d4d9061a@gmail.com>
In-Reply-To: <2cfecf2c-5526-92d0-716d-5e07d4d9061a@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.211.187]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UEGUVjbjF2gu3vjm0uLguFOSgf4>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment and 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: Tue, 30 Mar 2021 07:32:59 -0000

Hi Alexandre,
Thanks for your support!
Please see my responses inline tagged as [GF].

Regards,

Giuseppe


-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Monday, March 29, 2021 6:38 PM
To: v6ops@ietf.org
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment and draft-vf-v6ops-ipv6-deployment



Le 27/03/2021 à 05:58, Fred Baker a écrit :
> 
> 
>> On Mar 19, 2021, at 1:39 AM, Paolo Volpato <paolo.volpato@huawei.com> 
>> wrote:
>> 
>> For lmhp-v6ops-transition-comparison, on behalf of the authors of 
>> draft-vf-v6ops-ipv6-deployment I can say we are in favor of the WG 
>> adoption. Not only is it a good description of the transition 
>> technologies to IPv6, but it also constitutes a basis for our draft.
> 
> OK, let me put this to the working group. We asked about adoption of 
> draft-lmhp-v6ops-transition-comparison once before (in January 2020), 
> and got essentially no response. It has come up on the list twice 
> since, in July and in November. The authors of 
> draft-vf-v6ops-ipv6-deployment would like to see it adopted. The two 
> sets of authors are disjoint. I therefore have at least nine people 
> that would like to see us adopt and publish it. What other folks have 
> opinions, pro or con?
> 
> Along the same lines, are there opinions regarding the adoption of 
> draft-vf-v6ops-ipv6-deployment?

Hi, Fred,

Generally speaking I am in favor of immediate adoption of drafts that describe IPv6 deployments, so of these ones too.

I have some input to offer from my experiments on an IPv6-only computer connected to the Internet.  For example I would suggest to not use any URL that does not work.

There is an 'IPv6 survey' reported in the draft, so I could offer another results of IPv6 survey, in English, but from France.

[GF]: Happy to receive your contribution here.

There is advice that is provided in the draft as well.  I might agree with some advice and disagree with some other, and suggest another one.

[GF]: Yes, we have tried to derive some advice based on the survey. Anyway the main scope of the draft is to give a global picture of IPv6 so we can revise that part according to the feedback received.

I would suggest to describe more of the pure translation-less IPv6 deployments on 'bare metal' where IPv4 is completely absent.  Maybe use more of a perspective where IPv4 does not exist and IP is all there is to be (to signify IPv6).

[GF]: Sure, this prospective can be added, even if it is not the most common situation.

Then there is the 64bit problem that I really believe to be a problem of
IPv6 deployments and mobile networks, but which is not mentioned.

[GF]: A new section on mobile networks can be introduced in the next version.

Alex


> 
> https://mailarchive.ietf.org/arch/search/?qdr=a&q=%22draft-lmhp-v6ops-
> transition-comparison%22
>
> 
https://mailarchive.ietf.org/arch/search/?qdr=a&q=%22draft-vf-v6ops-ipv6-deployment%22
> 
> 
> _______________________________________________ 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