IETF Logo Mail Archive

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

Chongfeng Xie <chongfeng.xie@foxmail.com> Sun, 12 November 2023 07:46 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 A8E4EC14F5E0 for <idr@ietfa.amsl.com>; Sat, 11 Nov 2023 23:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.162
X-Spam-Level:
X-Spam-Status: No, score=-4.162 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_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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=ham 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 0WHBNvc_nESN for <idr@ietfa.amsl.com>; Sat, 11 Nov 2023 23:46:32 -0800 (PST)
Received: from out162-62-58-216.mail.qq.com (out162-62-58-216.mail.qq.com [162.62.58.216]) (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 A1104C14F749 for <idr@ietf.org>; Sat, 11 Nov 2023 23:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1699775180; bh=EnQU4PmcxdJAtRH/lsflsDjqYYRSZX8J/ubRuZakHRQ=; h=Date:From:To:Subject:References; b=g4tFjUWGyfTBfhRUVskW0HtI9IexfROWHzRbMIuUTp70GHklbmuIWNJuotw2gDdKD jcUnje//X1RuEmTRUGkz3h6iJjEM+R6cdAoys40zxZH1FGlVcVBEtq7VvaCG2JzmNg /9hdzAm5RCPWNBahpeS2dxjhnjX2fL+dQIrsC8jo=
Received: from LAPTOP-BOBOCIFS ([114.250.180.71]) by newxmesmtplogicsvrszb6-0.qq.com (NewEsmtp) with SMTP id B931EE32; Sun, 12 Nov 2023 15:46:19 +0800
X-QQ-mid: xmsmtpt1699775179t6a2nsob0
Message-ID: <tencent_CBB12F958C85FDF962D76180EB1C51662408@qq.com>
X-QQ-XMAILINFO: NQR8mRxMnur9AFHCJt/ESyJ8PhIvR9DENkObBRIgvyZWlE/IXpehY++3+u0oyq oqARI85JCWFKu8a8GHxvwsLqDsxt7ZQMgjp0jMbFCjgg5i0RnftlozmxffnBDMyzerqFVQcvDWBf KnSTLdz/wnupT5IL0/8mYgrb3M3XVX01qpNeA9F5xJseb+dwIlZ70cMA/1RQOIu1dY1v3Z84Nv+m cNEYpsb72P3O59Ph2o1poapHkwipQoqDBck7VjNGiCQWJsrsQpaSA8ikDyLq7Oqq1gqfbIoL0zTz cDVQ1Chcy/hYwK1+LGiIH5gXzaf7n7O0psWLYPCGUmi8RF5ZFZY0ACYzawd5Aul9Aj6ynsoPtnwa XQNpDTxbJmtwyIZMdNAz21/lntASS5hJ8DIeispXErfcvfakG1Ved367e3aIDz6qp1FatouVNyXb /0irPuJU5w+KN+x9qDb3H91OGKXlRJJJYm2OOUbSUqEsN1hc7z8j1A9/5G3n51aKj4S8Bct4ot2I FKDa8PcWAMhEM9WO+72bmVArbqfGQWNdB1l1n7vuYE9iTRrWMgfiFjezSymotSHWHo6wDJy+DxIg zC2Zt2vkzBkmguKz74Jv08bl3tj+6nVSlmw4r1Ac2+bV1fu7+3j0YqRDMAjqvxwz4wVxDElGAzG3 RdiwFh4ui1/Kdvx+N5j7xVYX/W0sRGR+cl/+wXXR/MOyKvdtXelknMUnDkKeTF85DGdjtBI2ypmE sHg+X7rsI/BTI3WK9jieZ4a6I7bGp/qtAgKnCSO58aN9uxEmaJzqnw0LSLXw817pUG5gYKLJEjTK gBBV13pgv7xTmhiXHvtmlk2gJAOnKOvsBt9JFrEi1OnxWZmk0C1g8iFVLulHMaq3kEv45Wpd0hpl ujnJs+tsl59+CmgLUzD4C5blazNh+m/24+XqDBkTi0NzFBtemcHe2q7ht7lfFSXQphBqPufgd8DI R0JTP1fG/YYhuTw6f745cD0LuDIRYonWp2jlIUW5Te0AfXY0NDHiySBDrmFHqEZsHahaA8PDE=
X-QQ-XMRINFO: OWPUhxQsoeAVDbp3OJHYyFg=
Date: Sun, 12 Nov 2023 15:46:18 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
References: <BYAPR08MB487294F5C1EE87A8184EDC8BB3AEA@BYAPR08MB4872.namprd08.prod.outlook.com>
X-Priority: 3
X-GUID: CC75C242-E223-41B9-9994-4AEFD50AC31E
X-Has-Attach: no
X-Mailer: Foxmail 7.2.23.121[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202311121546181683653@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart773683658714_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Tt1ilS585BsjvVe-1M-ljBchuJ0>
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, 12 Nov 2023 07:46:36 -0000

Hi Sue and all,

This use case is about IPv6-only deployment in multi-domain networks，it has been illustrated in section 3、4、5  of draft-ietf-v6ops-framework-md-ipv6only-underlay, I'd like to highlight the keypoints as below,

1，In this case, IPv6-only is used for service data forwarding, including IPv6 and IPv4 service data. For IPv4 packet that arrives at the edge of the IPv6-only network, PE will convert it into IPv6 packet by encapsulation or translation,  so IPv4 related features are required to be maitained in the PE at the network edge. Currently, all the mobile operating systems,such as Android and IOS, support translation-based IPv6-only mode, so translaton needs to be considered as well.

2， In order to support IPv4/IPv6 packet conversion in encapsulation or translation, stateless address mapping is adopted to transform the IPv4 source and destination addresses of IPv4 packets into IPv6 source and destination addresses, and vice versa. Stateless IPv4/IPv6 mapping means adding an IPv6 mapping prefix directly to the IPv4 address to generate its corresponding IPv6 address, so this is 1:1 mapping. This stateless address mapping works both for encapsulation or translation, it also has many advantages for network operation and management.

3， To meet the requirements of 1 and 2 above, PEs are required to exchange information such as  IPv4 address blocks, IPv6 address mapping prefixes and IPv4/IPv6 packet conversion methods ( i.e. encapsulation or translation) . This is the what being done in 4map6 draft.

RFC5549 was mentioned in idr seesion on Friday, RFC5549 specifies the extensions to allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address that belongs to IPv6. However, It does not provide IPv6 address mapping prefixes for the aforementioned stateless encapsulation mode, nor does it support translation, therefore, it does not meet the overall requirements of the above use case.

Best regards
Chongfeng



chongfeng.xie@foxmail.com
 
From: Susan Hares
Date: 2023-11-10 18:13
To: idr@ietf.org
Subject: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6
Chong Feng and Ketan: 
 
Would you please explain the two use cases on the list?  
 
We need to discuss the questions regarding use cases regarding: 
 
Is the use case clearly described? 
Do you think the 4 to 6 mapping is handled by another technology? 
 
Sue

v2.23.0 | Report a Bug | By Email