Re: [Sidrops] Distributing RPKI Validated Cache in JSON over HTTPS

I think its useful to document use of secured transport to fetch data.

The problem I retain in this, is the lack of strong cryptographic
validity checks on the semantic intent of the assertions themselves.

The beauty of RPKI was always the ability to demonstrate the binding
of authority (delegated) to say what was to be done with some
resource.

SLURM doesn't honour that behaviour. Inside your own IGP, its a
representation of your 'must-haves' including other peoples things,
but between IGPs, transferred over the external boundary, I worry a
LOT about "what it means"

And that goes for 'SLURM for AS0 from the RIR too' btw.

-G

On Wed, May 20, 2020 at 3:32 PM Di Ma <madi@rpstir.net> wrote:
>
> 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
>
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops