Re: [Sidrops] rfc8210bis further review - question 5

[Job Snijders <[e-mail]>]

Dear all,

Question 5
==========

In Section 5.12 "ASPA PDU" the current text says:

  "The cache MUST deliver the complete data of an ASPA record in a single
  ASPA PDU."

and

  "The router MUST see at most one ASPA from a cache for a particular
  Customer Autonomous System Number active at any time. As a number of
  conditions in the global RPKI may present multiple valid ASPA RPKI
  records for a single customer to a particular RP cache, this places a
  burden on the cache to form the union of multiple ASPA records it has
  received from the global RPKI into one ASPA PDU.

The above to me means that, logically, the Provider Autonomous System
Number fields MUST be unique with respect to each other, as the PAS
Numbers are a union set.

It will be easier for the RTR client / router to check in a single pass
whether the PAS Numbers are unique, if those fields are ordered in
ascending order.

Suggestion:

OLD:
    There are zero or more 32-bit Provider Autonomous System
    Number fields as indicated in the Provider AS Count; see
    [I-D.ietf-sidrops-aspa-profile].

NEW:
    There are zero or more 32-bit Provider Autonomous System
    Number fields as indicated in the Provider AS Count, the
    fields MUST be ordered in ascending numerical order; see
    [I-D.ietf-sidrops-aspa-profile].

The above requirement allows RTR clients to detect both the presence
of duplicate PAS Numbers and invalid ordering (both indicators that
something is off with the cache), then send a "Corrupt Data" error
report.

Kind regards,

Job