Re: [Sidrops] draft-spaghetti-sidrops-rpki-prefixlist-00 (chapter #2 of what does IRR have that RPKI doesn't?)

[Geoff Huston <[e-mail]>]

Hi,

I see the Prefix List as completing a “hankshake”. The ROA is a declaration
by a prefix holder that does not necessarily have the acknowledgement of the
AS holder, and the Prefix List is a declaracter by the AS that does not
necessarily have the acknowledgement of the prefix holder(s). But when
looked at together then it is possible to infer an agreement between 
the two parties/roles.

thanks

Geoff


> On 30 Mar 2023, at 5:26 pm, Job Snijders <job=[e-mail]> wrote:
> 
> Hi folks,
> 
> Following my presentation "ASGroups (or, exploring sunsetting IRR?)" [1]
> Geoff commented along the lines of "porting IRR as-sets is the wrong way
> to go about it, you should port IRR route-sets!"
> 
> Geoff's proposal is that Autonomous System resource holders should
> publish a self-asserted list of IP prefixes the subject ASN MAY
> originate. Then remote peers can then use this list to construct filters
> for various purposes.
> 
> [ Note: this is not a replacement for RPKI-ROV! Operationally I think
>   along the the lines of: reject RPKI-ROV invalid routes and
>   additionally reject routes not listed in the RPKI-PrefixList (in
>   addition to rejecting ASPA-invalid routes, bogon ASNs, etc, etc) ]
> 
> So, to progress the conversation about "what would it take to sunset
> IRR/RPSL; what features or properties does IRR have that are missing in
> one form or another in the RPKI?" - we authored the below draft for your
> consideration.
> 
> I consider both ASGroups & PrefixList steps in an exploratory study, and
> I fully anticipate that by shaking this tree more ideas will fall into
> our laps.
> 
> I'm very open to hear from the community what they perceive as valuable
> properties of IRR/RPSL, and I am happy to collaborate (read: I'm happy
> to do the required ASN.1 work and write running code, even if its for
> ideas we abandon down the road). Let me hear your thoughts on what's
> beautiful about IRR!
> 
> Kind regards,
> 
> Job / Geoff
> 
> 
> [1]: https://datatracker.ietf.org/meeting/116/materials/slides-116-sidrops-asgroups-thoughts-about-irr-rpki-feature-parity-sunsetting-irr-00
> 
> 
> 
> ----- Forwarded message from [e-mail] -----
> 
> Date: Thu, 30 Mar 2023 01:01:56 -0700
> From: [e-mail]
> To: Geoff Huston <[e-mail]>, Job Snijders <[e-mail]>
> Subject: New Version Notification for
> draft-spaghetti-sidrops-rpki-prefixlist-00.txt
> 
> 
> A new version of I-D, draft-spaghetti-sidrops-rpki-prefixlist-00.txt
> has been successfully submitted by Job Snijders and posted to the
> IETF repository.
> 
> Name: draft-spaghetti-sidrops-rpki-prefixlist
> Revision: 00
> Title: A profile for RPKI Signed Lists of Prefixes
> Document date: 2023-03-30
> Group: Individual Submission
> Pages: 13
> URL:            https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-prefixlist-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-prefixlist/
> Html:           https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-prefixlist-00.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-prefixlist
> 
> 
> Abstract:
>   This document defines a "RPKI Prefix List", a Cryptographic Message
>   Syntax (CMS) protected content type for use with the Resource Public
>   Key Infrastructure (RPKI) to carry the complete list of prefixes
>   which an Autonomous System (AS) may originate to all or any of its
>   routing peers.  The validation of a RPKI Prefix List confirms that
>   the holder of the listed ASN produced the object, and that this list
>   is a current, accurate and complete description of address prefixes
>   that may be announced into the routing system originated by this AS.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> ----- End forwarded message -----
> 
> _______________________________________________
> Sidrops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sidrops