IETF Logo Mail Archive

[v6ops] PVD and multi-homing

Vasilenko Eduard <vasilenko.eduard@huawei.com> Wed, 20 March 2024 12:46 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 E1BD7C151995 for <v6ops@ietfa.amsl.com>; Wed, 20 Mar 2024 05:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 RvycrE8B_at1 for <v6ops@ietfa.amsl.com>; Wed, 20 Mar 2024 05:46:46 -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 B36DDC14F748 for <v6ops@ietf.org>; Wed, 20 Mar 2024 05:46:45 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4V07cV4GFvz67GCQ for <v6ops@ietf.org>; Wed, 20 Mar 2024 20:46:02 +0800 (CST)
Received: from mscpeml500003.china.huawei.com (unknown [7.188.49.51]) by mail.maildlp.com (Postfix) with ESMTPS id 94DBA1402CD for <v6ops@ietf.org>; Wed, 20 Mar 2024 20:46:42 +0800 (CST)
Received: from mscpeml500004.china.huawei.com (7.188.26.250) by mscpeml500003.china.huawei.com (7.188.49.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Wed, 20 Mar 2024 15:46:42 +0300
Received: from mscpeml500004.china.huawei.com ([7.188.26.250]) by mscpeml500004.china.huawei.com ([7.188.26.250]) with mapi id 15.02.1258.028; Wed, 20 Mar 2024 15:46:41 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: v6ops <v6ops@ietf.org>
Thread-Topic: PVD and multi-homing
Thread-Index: Adp6xKXRJAEAVvr6RFuNMnrR6ZeTnA==
Date: Wed, 20 Mar 2024 12:46:41 +0000
Message-ID: <b4dfb1a711814676bc4339df833b560e@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.189.108]
Content-Type: multipart/alternative; boundary="_000_b4dfb1a711814676bc4339df833b560ehuaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MIqeUXN8XPRSgJ5yuZI7r0ugnXU>
Subject: [v6ops] PVD and multi-homing
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: Wed, 20 Mar 2024 12:46:50 -0000

Hi all,
Answering again on PVD (because Jen has commented again):
PVD is a split of one physical router on many virtual. It has value for many purposes (DNS, Proxy, etc) except multi-homing.
PVD is very harmful to multi-homing because it creates a multi-router environment even for the situation when only one router exists on the link.
It immediately activates all multi-homing problems (mostly leaving on the host in RFC 6724).
Hence, any solution discussed in the draft-fbnvv-v6ops-site-multihoming is an *enabler* for PVD.
PVD is possible, only after the multi-homing problem is resolved (in any way).
Hence, anybody who would like the success of PVD should help with multi-homing problems first.
Or PVD would never happen. It is just an easy logical conclusion.
Eduard
From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Xipengxiao
Sent: Tuesday, February 27, 2024 17:04
To: Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org>; V6Ops Chairs <v6ops-chairs@ietf.org>
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Call for draft presentations in IETF 119

Acknowledged，Paolo.



________________________________
Xipeng Xiao
Mobile: +49-1622047661
Email: xipengxiao@huawei.com<mailto:xipengxiao@huawei.com>
发件人：Paolo Volpato <paolo.volpato=40huawei.com@dmarc.ietf.org<mailto:paolo.volpato=40huawei.com@dmarc.ietf.org>>
收件人：V6Ops Chairs <v6ops-chairs@ietf.org<mailto:v6ops-chairs@ietf.org>>
抄 送：Xipengxiao <xipengxiao@huawei.com<mailto:xipengxiao@huawei.com>>;v6ops <v6ops@ietf.org<mailto:v6ops@ietf.org>>
时 间：2024-02-27 09:58:40
主 题：RE: Call for draft presentations in IETF 119

Hi Chairs,

We’d like to have a 10 minutes slot to update on the following:

IPv6 Site Connection to Many Carriers, Paolo Volpato, 10m
https://datatracker.ietf.org/doc/draft-fbnvv-v6ops-site-multihoming/

Many thanks (on behalf of the co-authors)
Paolo

From: v6ops <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org>> On Behalf Of Xipengxiao
Sent: Saturday, February 17, 2024 10:54 AM
To: v6ops@ietf.org<mailto:v6ops@ietf.org>
Cc: V6Ops Chairs <v6ops-chairs@ietf.org<mailto:v6ops-chairs@ietf.org>>
Subject: [v6ops] Call for draft presentations in IETF 119

Hi folks,

IETF 119 agenda has been published. We get a 2h session 9:30-11:30 on Wed.  If you want a time slot to present your draft, please make your request in the following agenda format:

Use of the IPv6 Flow Label for WLCG Packet Marking, Dale Carder, 10m

  *   https://datatracker.ietf.org/doc/draft-cc-v6ops-wlcg-flow-label-marking/
Please note that having interest/discussion on the mailing list is a prerequisite for draft presentation in the WG session.  Thank you very much.

Regards,

Xipeng

v2.23.0 | Report a Bug | By Email