Re: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6

Chongfeng Xie <chongfeng.xie@foxmail.com> Sun, 10 March 2024 08:40 UTC

Return-Path: <chongfeng.xie@foxmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08853C14F680 for <idr@ietfa.amsl.com>; Sun, 10 Mar 2024 00:40:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.839
X-Spam-Level:
X-Spam-Status: No, score=0.839 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 krqqV8U7hV6W for <idr@ietfa.amsl.com>; Sun, 10 Mar 2024 00:40:34 -0800 (PST)
Received: from out203-205-251-80.mail.qq.com (out203-205-251-80.mail.qq.com [203.205.251.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB403C14F6F7 for <idr@ietf.org>; Sun, 10 Mar 2024 00:40:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1710060029; bh=ABQK9l2jCxrpTIzsiSSrub44vWK7QdHFHbRilO4CJcg=; h=Date:From:To:Cc:Subject:References; b=obcSsxJFDBz38nAEFQtieQBwNH0iLOT5TqWiLVCe9SxZ+3fqTISGFONWj5+hUd9O4 8hTNTup1Zc9lycDoMlFOOYSdtzU5pW1FRdq8qWDTb5CIuIR9Vs9bBuhAhbpI/O5qI0 oWGaVylA+kUjydGQbNPKtRZZFFbcy9PJtGvtaYmA=
Received: from DESKTOP-48H476U ([114.250.178.215]) by newxmesmtplogicsvrszc5-2.qq.com (NewEsmtp) with SMTP id 8981DADC; Sun, 10 Mar 2024 16:34:24 +0800
X-QQ-mid: xmsmtpt1710059664t29xhuvyg
Message-ID: <tencent_BE90355FEE1A05D09F03C18C2276AB72A705@qq.com>
X-QQ-XMAILINFO: MR/iVh5QLeiesT/qxp6yj3/7Gu07v00B92uPyyKvBUblZk9NjMRdDyKZ8cfOUF +xF1hS6EWS0VXNhYshrSS1Bm7h45dCTMCZnDDsvq9lNp3do1NWiZWHggZP/JNFIQMiCANaPqSmen tZXfkBz1Xm2/zfwNy1RdEeY11ZLBvZ2tAPEVrREfcUAg39l28dm18sQWeXwKFWWLJepbUUSmdrrS jmPCI5y5QdWwNS4YoG8t+sk9n7AR8mmq/223ulyCNVnOhue1lORyMwR7LcfAfNVVrlvyGoAk84An 9rLXrJsIFh0E03XYO3/5nwbigwnShk3jiwh7RS6lHtcxFUbgpiHXM/XlPtx56GL7bAorWFpOihDZ BLlosxOGG9kSaLMtE3RnUcajg8qWxQAVLMMlRfWKUnJtXa6hAhLWlh5nA5nHj4B/tDo7CnFkTzeR QHK7+r9hVhNs0krerig6Fc1la1Zf33B/C9w5TGtifu7cgeY6jiYFJRCZdYc1n0wyZT+i/cKzV5tB ABnnxwtTi35fhlGOwDeIssE9jYcXNWZjKRmTLNGQGAeKNovvBt8Gh+7EbbGZMQPUzesfqRbGfhy5 mMIndKaqaMQvrXx9PF+pzrECbcW00jdjXHDvQU581BkhtFrPRhBl9ONBNWqD71wDYU5vpfUdQRUp l9yk6d88vdRwis4YWlBaodJgZ477IXWHv3Yfps/DOkadzPakbB8yNN6hkhzuz+HiuoW/kNaQslXw XDiamw63DrFgWM/gsyvb9iwT+yTQha2O3BvRn+F/qDLfU9CFoqvx+52d9iS55L4KTbJtNWQ+prV1 XUMlWpJfsnNxDjrrdTboQKML3t3FsDYCCvjapwA/2e4mlZpCuGBWVMcQ979Hfs7F9wnEST4L/rbb v+nlJno8xv/Hx35RfyJ/QhD3FxRYdLJswPVjlzDxV2yUxDSQD8pn55Ye+BxIpyd453njvkkoLYI4 Uh25Jw0Y8WCz2Yx/wMtkT74/T1yI+s89ZO/ejdUf/UzNBrGRr2zk9r3UxXKV0HxxPLdY+pmOfNau S+O997SL1RJ/fufvfsZtz7/2TphZyKU1jcjIrC0V0YfhnXTB3NuLSFQVajub99g6bkWh3S5g==
X-QQ-XMRINFO: NyFYKkN4Ny6FSmKK/uo/jdU=
Date: Sun, 10 Mar 2024 16:34:26 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: "ketant.ietf" <ketant.ietf@gmail.com>
Cc: idr <idr@ietf.org>
References: <BYAPR08MB487294F5C1EE87A8184EDC8BB3AEA@BYAPR08MB4872.namprd08.prod.outlook.com>, <tencent_CBB12F958C85FDF962D76180EB1C51662408@qq.com>, <20240122223242.GA29681@pfrc.org>, <tencent_446B00493916CCB662EB2AC90A17F2AFAF09@qq.com>, <DB175FC2-BD0A-424A-B8E6-31345BEAC8D6@pfrc.org>, <tencent_FF24FFF11A1B308B03C3EC27F6B8B2B09005@qq.com>, <F64BDA83-5A46-4FEA-AD6F-16CDDD817EAA@pfrc.org>, <tencent_6F855FF963D740807C1C166681B1FD950908@qq.com>, <CAH6gdPzMfZ8NFXcGiMkFJu_=eA9jAW+oj6ir4sbaVvyAzbzzEQ@mail.gmail.com>
X-Priority: 3
X-GUID: C58A587D-0806-4856-812E-C7B77F15E972
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.243[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202403101634255623481@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart200360584760_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1XzCJfFnZOUUKp95Lqhu7PdDgYE>
Subject: Re: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2024 08:40:38 -0000

Hi Ketant,

Sorry for my negligence of your mail accidentally. Actually your question has been discussed early last year.  I try to answer it again as below,

As mentioned The use case of 4map6 proposal in this draft is to support IPv4aaS in the multi-domain IPv6-only networks.  It adopts address mapping rule which is the 1:1 mapping between IPv4 address and IPv6 address, and IPv4 address become part of IPv6 address. With this design,PE devices can map the source and destination addresses of IPv4 packets to the source addresses of outer IPv6 packets, respectively.  It mainly meets the following requirements:

1)Compatibility with both encapsulation and translation, as we all know, IPv4 service delivery over IPv6 network has two transition approaches: Encapsulation and translation,  both of them have been used in current networks. 4map6 proposal can meet their needs simultaneously. Especially in translation, it can support both doulbe translation and single translation.

2)Security,the outer IPv6 address is dynamically generated based on mapping, and does not require a statically configured address as the tunnel endpoint address in advance.  This will be helpful to avoid the static IPv6 address from becoming the target of the DDOS attack.

3)Load balancing,the 4map6 proposal assigns a corresponding IPv6 address to each host's IPv4 address in the IPv6 network, and the IPv6 address newly generated can more accurately identify the host. This allows for IPv6 address based load balancing and management of the host in the IPv6 network based on the IPv6 address.

 I hope this explanation can address your concerns. Welcome to continue the discussion.

Best regards
Chongfeng




chongfeng.xie@foxmail.com
 
From: Ketan Talaulikar
Date: 2024-02-12 22:57
To: Chongfeng Xie; draft-xie-idr-mpbgp-extension-4map6
CC: jhaas; Susan Hares; idr
Subject: Re: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6
Hi Chongfeng/Authors,

Thanks for your updates to the document. 

I am still struggling to find the answer to the question on why it is necessary to perform mapping from IPv4 to IPv6 and then back to IPv4 when providing IPv4 connectivity service over an IPv6 core? Why is it not sufficient to simply encapsulate the IPv4 payload into any encapsulation (e.g., IPv4-in-IPv6, SRv6, MPLS, GRE, etc.) using RFC8950 encoding for the IPv4 unicast/VPN SAFI. These solutions are documented in draft-mishra-idr-v4-islands-v6-core-4pe

Perhaps I am missing something and it would help me understand the need for such mapping by service provider PE routers.

Thanks,
Ketan


On Thu, Feb 8, 2024 at 5:14 AM Chongfeng Xie <chongfeng.xie@foxmail.com> wrote:


Hi Jeff,

We have submitted a new version of draft-xie-idr-mpbgp-extention-4map6. Based on your suggestions, the contents of new attribute is placed in a new TLV in the tunnel encapsulation attribute of RFC9012, and the format of the NLRI is revised as well. In addition, the section of operation has been changed accordingly. 


        Name:     draft-xie-idr-mpbgp-extension-4map6
        Revision: 09
        Title:    MP-BGP Extension and the Procedures for IPv4/IPv6 Mapping Advertisement
        Date:     2024-02-09
        Group:    idr
        Pages:    16
        URL: https://www.ietf.org/archive/id/draft-xie-idr-mpbgp-extension-4map6-09.txt
        Status: https://datatracker.ietf.org/doc/draft-xie-idr-mpbgp-extension-4map6/
        HTMLized: https://datatracker.ietf.org/doc/html/draft-xie-idr-mpbgp-extension-4map6
        Diff: https://author-tools.ietf.org/iddiff?url2=draft-xie-idr-mpbgp-extension-4map6-09

We express sincere thanks to you for reviewing the draft as WG chair and providing a couple of important suggestions.  We also thank idr WG for the comments and suggestions received so far. 

If you have any new comments or suggestions, please feel free to let me know. Thanks!

Best regards
Chongfeng   

 
From: 【外部账号】Jeffrey Haas
Date: 2024-02-05 00:02
To: Chongfeng Xie
CC: Sue Hares; idr; draft-xie-idr-mpbgp-extension-4map6
Subject: Re: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6
Chongfeng,


On Jan 29, 2024, at 10:38 AM, Chongfeng Xie <chongfeng.xie@foxmail.com> wrote:
Based on your comment and suggestions, we have made the following revisions and submitted a new version, 


[...]

If you have any further comments, please feel free to let me know. 

Your changes significantly address my operational concerns.  Thank you.

-- Jeff

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