IETF Logo Mail Archive

Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt

Vasilenko Eduard <vasilenko.eduard@huawei.com> Thu, 18 May 2023 15:59 UTC

Return-Path: <vasilenko.eduard@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 785A3C14CE51 for <v6ops@ietfa.amsl.com>; Thu, 18 May 2023 08:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCQcAl644CuD for <v6ops@ietfa.amsl.com>; Thu, 18 May 2023 08:59:34 -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 36FA4C17CEA4 for <v6ops@ietf.org>; Thu, 18 May 2023 08:59:09 -0700 (PDT)
Received: from mscpeml100002.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4QMZL15wypz6J6vH for <v6ops@ietf.org>; Thu, 18 May 2023 23:54:49 +0800 (CST)
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml100002.china.huawei.com (7.188.26.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Thu, 18 May 2023 18:59:06 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2507.023; Thu, 18 May 2023 18:59:06 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt
Thread-Index: AQHZiZ5pCA/PyuCfX0qFN7gqJ/vZva9gLN5A
Date: Thu, 18 May 2023 15:59:06 +0000
Message-ID: <ed88eaba055b4dbfa079a6dd0752c910@huawei.com>
References: <168442407010.2544.7512872622955254077@ietfa.amsl.com>
In-Reply-To: <168442407010.2544.7512872622955254077@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.192.248]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pMS-oXMqwMsYF1bs7lMeKCGudsU>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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, 18 May 2023 15:59:38 -0000

Section 4 is still misleading people that SLAAC (and /64 as a consequence) are mandatory.
In fact, section 4 assumes some special "complex host" that has a virtual router inside. Is it still a host? Does the virtual router need additional specifications?
Albeit, in the majority of cases, a normal host would not have a virtual router inside.
Moreover, even virtualized host (with many VMs or Containers) would have a virtual switch inside, not a router.
Hence, for the great majority of cases, SLAAC is not relevant.
Section 4 is still misleading.

Nothing in the draft is about the possibility to use prefixes different from /64.

The draft is still targeted for one corner case (with a virtual router inside the host),
Discarding the possibility to use the solution on a much broader set of use cases.

Ed/
-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Thursday, May 18, 2023 6:35 PM
To: i-d-announce@ietf.org
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the IPv6 Operations (V6OPS) WG of the IETF.

   Title           : Using DHCP-PD to Allocate Unique IPv6 Prefix per Device in Broadcast Networks
   Authors         : Lorenzo Colitti
                     Jen Linkova
                     Xiao Ma
   Filename        : draft-ietf-v6ops-dhcp-pd-per-device-00.txt
   Pages           : 14
   Date            : 2023-05-18

Abstract:
   This document discusses the IPv6 deployment scenario when individual
   devices connected to broadcast networks (like WiFi hotspots or
   enterprise networks) are allocated unique prefixes via DHCP-PD.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-dhcp-pd-per-device/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-device-00.html

Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email