[Sidrops] [sidrops] FW: New Version Notification for draft-geng-sidrops-rtr-selective-sync-01.txt
gengnan <gengnan@huawei.com> Fri, 08 September 2023 06:38 UTC
Return-Path: <gengnan@huawei.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 EEDBFC151985 for <sidrops@ietfa.amsl.com>; Thu, 7 Sep 2023 23:38:06 -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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=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_BLOCKED=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 Eb68RENnxkQ9 for <sidrops@ietfa.amsl.com>; Thu, 7 Sep 2023 23:38:02 -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 1D8D4C14CE53 for <sidrops@ietf.org>; Thu, 7 Sep 2023 23:38:02 -0700 (PDT)
Received: from lhrpeml100004.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RhmX74Hwnz6J6Lm for <sidrops@ietf.org>; Fri, 8 Sep 2023 14:33:27 +0800 (CST)
Received: from kwepemi100002.china.huawei.com (7.221.188.188) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 8 Sep 2023 07:37:58 +0100
Received: from kwepemm600009.china.huawei.com (7.193.23.164) by kwepemi100002.china.huawei.com (7.221.188.188) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Fri, 8 Sep 2023 14:37:56 +0800
Received: from kwepemm600009.china.huawei.com ([7.193.23.164]) by kwepemm600009.china.huawei.com ([7.193.23.164]) with mapi id 15.01.2507.031; Fri, 8 Sep 2023 14:37:56 +0800
From: gengnan <gengnan@huawei.com>
To: "sidrops@ietf.org" <sidrops@ietf.org>
CC: Zhuangshunwan <zhuangshunwan@huawei.com>, "Huangmingqing (Michael)" <huangmingqing@huawei.com>
Thread-Topic: [sidrops] FW: New Version Notification for draft-geng-sidrops-rtr-selective-sync-01.txt
Thread-Index: AdniHVDk5AxkQWX/TeOPQQVdfF8mWw==
Date: Fri, 08 Sep 2023 06:37:56 +0000
Message-ID: <2ba5e2baccef4157a867eaaae786e90a@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.101]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/AVV0t915Fchc90l6I5KENtNFM0M>
Subject: [Sidrops] [sidrops] FW: New Version Notification for draft-geng-sidrops-rtr-selective-sync-01.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2023 06:38:07 -0000
Dear WG, We have submitted a draft titled with "Selective Synchronization for RPKI to Router Protocol " The RPKI-to-Router (RTR) protocol synchronizes all the verified RPKI data to routers. However, routers may be interested in a part of data types, instead of all. In such cases, storing unused data on the router is unreasonable, and synchronizing all types of data will induce some unnecessary transmission and storage overhead. Furthermore, there may be more types of data in the cache in the future, which makes the above issue more significant and worse. This document proposes to extend the existing RTR protocol to support selective data synchronization. Selective synchronization can avoid some unnecessary synchronizations. The router can obtain only the data that it really needs, and it does not need to save the data that are not needed. Welcome your feedback and comments! Best, Nan -----Original Message----- From: internet-drafts@ietf.org <internet-drafts@ietf.org> Sent: Friday, September 8, 2023 11:50 AM To: Huangmingqing (Michael) <huangmingqing@huawei.com>; gengnan <gengnan@huawei.com>; Zhuangshunwan <zhuangshunwan@huawei.com> Subject: New Version Notification for draft-geng-sidrops-rtr-selective-sync-01.txt A new version of Internet-Draft draft-geng-sidrops-rtr-selective-sync-01.txt has been successfully submitted by Nan Geng and posted to the IETF repository. Name: draft-geng-sidrops-rtr-selective-sync Revision: 01 Title: Selective Synchronization for RPKI to Router Protocol Date: 2023-09-08 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-geng-sidrops-rtr-selective-sync-01.txt Status: https://datatracker.ietf.org/doc/draft-geng-sidrops-rtr-selective-sync/ HTML: https://www.ietf.org/archive/id/draft-geng-sidrops-rtr-selective-sync-01.html HTMLized: https://datatracker.ietf.org/doc/html/draft-geng-sidrops-rtr-selective-sync Diff: https://author-tools.ietf.org/iddiff?url2=draft-geng-sidrops-rtr-selective-sync-01 Abstract: The RPKI-to-Router (RTR) protocol synchronizes all the verified RPKI data to routers. This document proposes to extend the existing RTR protocol to support selective data synchronization. Selective synchronization can avoid some unnecessary synchronizations. The router can obtain only the data that it really needs, and it does not need to save the data that are not needed. The IETF Secretariat