[Sidrops] Adoption request of draft-madi-sidrops-rush-02
Di Ma <madi@rpstir.net> Sat, 29 August 2020 10:26 UTC
Return-Path: <madi@rpstir.net>
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 0EAFD3A12D8; Sat, 29 Aug 2020 03:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NERApEE1rN1; Sat, 29 Aug 2020 03:26:50 -0700 (PDT)
Received: from out20-61.mail.aliyun.com (out20-61.mail.aliyun.com [115.124.20.61]) (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 1F2033A12D5; Sat, 29 Aug 2020 03:26:48 -0700 (PDT)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.1597086|-1; CH=green; DM=|CONTINUE|false|; DS=CONTINUE|ham_regular_dialog|0.0843744-0.0114148-0.904211; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03306; MF=madi@rpstir.net; NM=1; PH=DS; RN=5; RT=5; SR=0; TI=SMTPD_---.IPgo1HO_1598696798;
Received: from 192.168.3.24(mailfrom:madi@rpstir.net fp:SMTPD_---.IPgo1HO_1598696798) by smtp.aliyun-inc.com(10.147.40.26); Sat, 29 Aug 2020 18:26:39 +0800
From: Di Ma <madi@rpstir.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Message-Id: <F4FD13C1-B437-4A94-BD58-A5805067B6DB@rpstir.net>
Date: Sat, 29 Aug 2020 18:26:37 +0800
Cc: Chris Morrow <morrowc@ops-netman.net>, Keyur Patel <keyur@arrcus.com>, Nathalie Trenaman <nathalie@ripe.net>, SIDR Operations WG <sidrops@ietf.org>
To: SIDROps Chairs <sidrops-chairs@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/_iZZRKusRGMkAQFx-FVG2mOI5_0>
Subject: [Sidrops] Adoption request of draft-madi-sidrops-rush-02
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 29 Aug 2020 10:26:52 -0000
Chairs, We authors just update draft-madi-sidrops-rush into v2 re Randy and Job’s concern raised in last IETF SIDROPS meeting. This version articulates in Security Consideration that : "RUSH is designed to carry out RPKI cache data update from one to another, with out-of-band trust established between those cache servers. That is, the scope of RUSH usage is convergent. Cache subscription management might be employed to implement cache identification and verification. " Please consider this mail as the formal request of adoption of draft-madi-sidrops-rush-02 as WG item. Thanks. Di