IETF Logo Mail Archive

Re: [Sidrops] [WGLC] draft-ietf-sidrops-rp - ENDS: Mar 7, 2019

Zhuangshunwan <zhuangshunwan@huawei.com> Tue, 19 March 2019 03:40 UTC

Return-Path: <zhuangshunwan@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 F074D1279A2; Mon, 18 Mar 2019 20:40:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 qtcMZrbh097Z; Mon, 18 Mar 2019 20:40:35 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 1350F127990; Mon, 18 Mar 2019 20:40:35 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 1079A8F9E8A1654B1FB7; Tue, 19 Mar 2019 03:40:33 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Mar 2019 03:40:32 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0415.000; Tue, 19 Mar 2019 11:40:20 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Chris Morrow <morrowc@ops-netman.net>, "sidrops@ietf.org" <sidrops@ietf.org>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>, "sidrops-ads@ietf.org" <sidrops-ads@ietf.org>
Thread-Topic: [Sidrops] [WGLC] draft-ietf-sidrops-rp - ENDS: Mar 7, 2019
Thread-Index: AQHU3J1hmdOs/WXLGkSH88b/R4CbKaYSS45w
Date: Tue, 19 Mar 2019 03:40:19 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858DC59D8E0@NKGEML515-MBX.china.huawei.com>
References: <yj9ozhpt51ug.wl-morrowc@ops-netman.net>
In-Reply-To: <yj9ozhpt51ug.wl-morrowc@ops-netman.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.202.166]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/063DwpGx1N6NuoP5aHbZbbBQxmU>
Subject: Re: [Sidrops] [WGLC] draft-ietf-sidrops-rp - ENDS: Mar 7, 2019
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: Tue, 19 Mar 2019 03:40:37 -0000

Support.

As a developer of the routing device using the data from RP, 
I think this is a very useful reference document. 
It lets us know how RP works.

Thanks,
Shunwan

-----Original Message-----
From: Sidrops [mailto:sidrops-bounces@ietf.org] On Behalf Of Chris Morrow
Sent: Sunday, March 17, 2019 4:42 PM
To: sidrops@ietf.org; sidrops-chairs@ietf.org; sidrops-ads@ietf.org
Subject: [Sidrops] [WGLC] draft-ietf-sidrops-rp - ENDS: Mar 7, 2019

Howdy WG Folken,
The authors of:
  draft-ietf-sidrops-rp

are interested in moving their document forward, the abstract of this
document:

  "This document provides a single reference point for requirements for
   Relying Party (RP) software for use in the Resource Public Key
   Infrastructure (RPKI) in the context of securing Internet routing.
   It cites requirements that appear in several RPKI RFCs, making it
   easier for implementers to become aware of these requirements that
   are segmented with orthogonal functionalities."

Please have a read through this document, comment/complain/etc as appropriate. The decision on forward progress or necessary edits ends Mar 07, 2019.

Thanks!
-chris
(co-chair)

_______________________________________________
Sidrops mailing list
Sidrops@ietf.org
https://www.ietf.org/mailman/listinfo/sidrops

v2.23.0 | Report a Bug | By Email