IETF Logo Mail Archive

[Sidrops] Distributing RPKI Validated Cache in JSON over HTTPS

Di Ma <madi@rpstir.net> Wed, 20 May 2020 05:32 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 EC8323A3A8C for <sidrops@ietfa.amsl.com>; Tue, 19 May 2020 22:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 2SRpttFM9s-J for <sidrops@ietfa.amsl.com>; Tue, 19 May 2020 22:32:37 -0700 (PDT)
Received: from out20-111.mail.aliyun.com (out20-111.mail.aliyun.com [115.124.20.111]) (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 AF7523A3A89 for <sidrops@ietf.org>; Tue, 19 May 2020 22:32:34 -0700 (PDT)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.2959157|-1; CH=green; DM=|CONTINUE|false|; DS=CONTINUE|ham_social|0.200959-0.0147545-0.784287; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03295; MF=madi@rpstir.net; NM=1; PH=DS; RN=1; RT=1; SR=0; TI=SMTPD_---.Hb.kedz_1589952743;
Received: from 192.168.218.230(mailfrom:madi@rpstir.net fp:SMTPD_---.Hb.kedz_1589952743) by smtp.aliyun-inc.com(10.147.42.198); Wed, 20 May 2020 13:32:24 +0800
From: Di Ma <madi@rpstir.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Message-Id: <DADF530A-9285-45C3-B2CA-73B9D8F3ABE7@rpstir.net>
Date: Wed, 20 May 2020 13:31:54 +0800
To: SIDR Operations WG <sidrops@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/157bCg7GS-9tVemeLegEFLhDoX0>
Subject: [Sidrops] Distributing RPKI Validated Cache in JSON over HTTPS
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: Wed, 20 May 2020 05:32:40 -0000

Hi, folks

I briefed a method for RPKI inter-cache synchronization called Distributing RPKI Validated Cache in JSON over HTTPS and our implementation with RPSTIR2 in IETF 106 Singapore meeting.

After that we were drafting a document that tries to specify the standardized way to do so, as I promised :-)

We realized that the document should focus on the necessary minimum information for data exchange not the detailed interaction and signaling which I believe can leave to different private implementations. 

This document is therefore intended to define a method for transferring RPKI validated cache by making use of SLURM.

Looking forwards to your comments.

https://datatracker.ietf.org/doc/draft-madi-sidrops-rush/

Di

v2.23.0 | Report a Bug | By Email