[Sidrops] Re: Call for Adoption of draft-xie-sidrops-moa-profile

Chongfeng Xie <chongfeng.xie@foxmail.com> Sat, 05 October 2024 07:57 UTC

Return-Path: <chongfeng.xie@foxmail.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7D0C180B55 for <sidrops@ietfa.amsl.com>; Sat, 5 Oct 2024 00:57:25 -0700 (PDT)
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_DNSWL_BLOCKED=0.001, 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=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 1dGd7aUUlvS6 for <sidrops@ietfa.amsl.com>; Sat, 5 Oct 2024 00:57:20 -0700 (PDT)
Received: from out203-205-221-173.mail.qq.com (out203-205-221-173.mail.qq.com [203.205.221.173]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E147AC180B4C for <sidrops@ietf.org>; Sat, 5 Oct 2024 00:57:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1728114734; bh=MsD4+MItf1H2zy7MeplGUDEO9HWWBLONZfV5E4yaUn0=; h=Date:From:To:Subject:References; b=r1ArlyE3WTzFymZnroz+057m8Q76A26k/rStXqC5c9FZleOAHIbl6hlh0WQfkjvDy tnmBQ4I5kLGT5FVVl/FMErG5TIZG2eNcPC5EEeGO17y6bLJVS4D3CcDCrnMCSM0PPu qgsMjBAeVOCwptRG+8JprBnjiqXDkbdlWx0RaSDY=
Received: from LAPTOP-BOBOCIFS ([36.112.179.229]) by newxmesmtplogicsvrszgpua4-0.qq.com (NewEsmtp) with SMTP id D0CB1C08; Sat, 05 Oct 2024 15:52:12 +0800
X-QQ-mid: xmsmtpt1728114732t0po0w92w
Message-ID: <tencent_6416601E878DD964EC65E5552151BECAF506@qq.com>
X-QQ-XMAILINFO: OATpkVjS499uUPseuPFD51mm03iti036u+93q7oS4k5nBdSQg599zdxAknp+wU Pzmb4ucnmWRB3Se4pSiVMwze7g9kkF1ityn9eSbSR9SF7eEJnozgv8QhalqZIR+ss2G8JxhudQh4 NVAyyhXsMg5PuwQdDudb63dMFZ8GA9IjYLcvbV2FegWiJ2oxH3BWgQ0PwG4f6UWYG0becSgaVhat wjx5eeqGftMTsxJc/7MS+jyXtnxhn4/G3DXSsyFzjuNfElLV43H2aQcpIfyR2ZVstP7zfklkPXJ9 LY2G4GySAegvXdehlEcXN6j1BrmzEs6vKce9+U0bJOn7BHm4WORE0cnxG3CUoS+AFufzYmi0zu4H DXZtLeALrPl8UCQ91AgtLs1WZ0L2doXJFGTV2jSMsXDOlnWiMV2iFDXmDSiuZrfP3yVReJFWH//o aeXP3OTmZNQ6uXvwzVJRfcCMsdmdPtlwkSF+eRlNTe/EfVAnhBbM6fs+9pgHwhmupfNPfwjkscwY Eo3k3T6AAC+KUkj3xWFYJ3RqvOL3MTpPbqAsToOW2znlQ+NAgFSsMQT7kSuzn7qI1730WHSNaggy giX1hMEsBAqS69Q934m8mY8KmZwf2lW0VjjRP9/h1C1k54eYFQYeWRdAU01Xj11/2U7BXXby8kP/ Jx/vcSE2VxYjyKLbWIpCpMqghOLtruEqGaoHN0d3gPu9OhjwzDwxpahqBfKaicYLfAjeE7VK3bbF JdcPkKICv8NAoDnJ69+193oWUdgv2AkPtsg8IGfNWx7GHNWNTTTNUVNPwsaR1YP80BOrvaQcX51r LbNh2QdSLh++R1w8egGyeQwYt93objighhwVLGiUz3vs5kDPOh66yf6UFJlPWRw2X4XAHJ95B3pG LHs2XlQlCiq/zc386zwQlrEv64UM/br8CXGBSQDatBcLPPVPiB4V9IkYXOIAmvPxCm7FrRs8uYTj NzMfWAlI21KWNuBPxPcRIcaqg1ZT6kLCVH9SiZOw5FGbiiaVPJ2lpWAC2Kcbp+58jS/Zpz9LNvGW eZD6gFH9RkskIc7uSaOTDX9lSKaFd68FYwSRnbcg==
X-QQ-XMRINFO: MPJ6Tf5t3I/ycC2BItcBVIA=
Date: Sat, 05 Oct 2024 15:52:12 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>, sidrops <sidrops@ietf.org>
References: <CO1PR13MB4920A074923A3FAB73BFCF3985722@CO1PR13MB4920.namprd13.prod.outlook.com>
X-Priority: 3
X-GUID: 4FE819B0-E838-42C4-8E27-F64A9CC57572
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.306[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202410051552121248084@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart172765087434_=----"
Message-ID-Hash: Y6KJLRNPGIDI6LPJGVZA6FSH2NKTV5EL
X-Message-ID-Hash: Y6KJLRNPGIDI6LPJGVZA6FSH2NKTV5EL
X-MailFrom: chongfeng.xie@foxmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [Sidrops] Re: Call for Adoption of draft-xie-sidrops-moa-profile
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/UKR-NKz-yFCR4YGgySZZ6s7rJio>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

Hi  Linda,
Thank you for your review and giving the two suggestions, I think they are insightful to improvement the document.  I will incoporate them into the next version. 

Best regards
Chongfeng 

 
From: Linda Dunbar
Date: 2024-10-05 02:12
To: SIDR Operations WG
Subject: [Sidrops] Re: Call for Adoption of draft-xie-sidrops-moa-profile
I think the problem described in the document is valid. It highlights a clear threat where a malicious actor could announce a false IPv6 mapping prefix for an IPv4 block, diverting traffic to unintended locations. This can lead to a loss of service, traffic interception, or other security vulnerabilities.
 
By introducing the MOA as a cryptographically signed object that links IPv4 prefixes with authorized IPv6 mapping prefixes, the document provides a robust method for ensuring the integrity and authenticity of these mappings. The use of MOA for Mapping Origin Validation helps prevent unauthorized mapping announcements, reducing the likelihood of hijacking. 
 
I support the adoption of the document, with the following suggestions: 
 
The Abstract of the document does not really reflect the core of the document. It would be nice to move the following sentence from the Intro section to the beginning of the Abstract: 
“This document proposes a new approach by leveraging Resource Public Key Infrastructure (RPKI) architecture to verify the authenticity of the mapping origin of an IPv4 address block.”
 
Expand on Security Considerations:
The Security Considerations section already outlines several important aspects of MOA security, but it could be improved by addressing potential failure modes:
Misconfigurations: Address the potential impact of misconfigured MOAs or PKI failures. For instance, what happens if an operator incorrectly assigns an IPv6 mapping prefix? How should networks mitigate such issues?
Compromise Scenarios: Discuss possible scenarios where the MOA PKI infrastructure itself could be compromised or where MOA signers act maliciously, and how to detect or mitigate such scenarios.
 
Best regards, 
Linda Dunbar