Re: [Sidrops] I-D Action: draft-ietf-sidrops-rp-03.txt

Di Ma <madi@rpstir.net> Tue, 29 January 2019 05:49 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 8914A130ED9 for <sidrops@ietfa.amsl.com>; Mon, 28 Jan 2019 21:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 MADHbuLk6EdK for <sidrops@ietfa.amsl.com>; Mon, 28 Jan 2019 21:49:24 -0800 (PST)
Received: from out20-99.mail.aliyun.com (out20-99.mail.aliyun.com [115.124.20.99]) (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 087AF130EA4 for <sidrops@ietf.org>; Mon, 28 Jan 2019 21:49:22 -0800 (PST)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.07623341|-1; CH=green; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03299; MF=madi@rpstir.net; NM=1; PH=DS; RN=2; RT=2; SR=0; TI=SMTPD_---.Ds.nIck_1548740958;
Received: from 192.168.218.235(mailfrom:madi@rpstir.net fp:SMTPD_---.Ds.nIck_1548740958) by smtp.aliyun-inc.com(10.147.41.231); Tue, 29 Jan 2019 13:49:18 +0800
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <154873952201.2863.14639503968117019865@ietfa.amsl.com>
Date: Tue, 29 Jan 2019 13:49:17 +0800
Cc: Di Ma <madi@zdns.cn>
Content-Transfer-Encoding: quoted-printable
Message-Id: <83DCD4EC-BEEF-443F-A933-E8F600E2CD58@rpstir.net>
References: <154873952201.2863.14639503968117019865@ietfa.amsl.com>
To: SIDR Operations WG <sidrops@ietf.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/vHyWILxhu1eZvRBDaFGQXDWeT5o>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rp-03.txt
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, 29 Jan 2019 05:49:29 -0000

Hi, folks,

We authors just updated this draft as follow: 

1) TAL

Considering draft-ietf-sidrops-https-tal seems to be ready for WGLC, we authors replaced RFC 7730 with it where the TAL topics are mentioned.


2) Distributing RPKI validated cache

In light of a new model of how RP service the validated cache,  which by the way, has been used by Cloudflare, we authors are slightly changed the description in Section 5 in terms of distributing RPKI validated cache. 

That is, the RP may deliver the validated cache via HTTPs to a cache server who is responsible for provisioning validated cache to BGP speakers.

https://blog.cloudflare.com/rpki-details/

We think this method is making sense for big ISPs, ICPs and a third party RP in the cloud. 

And RPSTIR (bgpsecurity.net) the RP software has also supported transferring validated cache via https, which is expected to go public in Github this year. 


We would appreciate your comments.

And if there is no major changed needed hereafter, we expect WGLC issued for this document. 

Di


> 在 2019年1月29日,13:25,internet-drafts@ietf.org 写道:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the SIDR Operations WG of the IETF.
> 
>        Title           : Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties
>        Authors         : Di Ma
>                          Stephen Kent
> 	Filename        : draft-ietf-sidrops-rp-03.txt
> 	Pages           : 11
> 	Date            : 2019-01-28
> 
> Abstract:
>   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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sidrops-rp/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sidrops-rp-03
> https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rp-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-rp-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops