[Sidrops] Re: Ketan Talaulikar's No Objection on draft-ietf-sidrops-rpki-ccr-09: (with COMMENT)

[Job Snijders <[e-mail]>]

Dear Ketan,

Many thanks for your careful review of this specification!

On Fri, Jun 26, 2026 at 01:54:33AM -0700, Ketan Talaulikar via Datatracker wrote:
> Ketan Talaulikar has entered the following ballot position for
> draft-ietf-sidrops-rpki-ccr-09: No Objection
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks to the authors and the WG for their work on this document.
> 
> I have a few comments, questions, and suggestions for consideration by the
> authors and the WG:
> 
> 1) Section 3: Is the hard lower limit size of 1000 fully thought out ... for
> today, tomorrow (e.g., something changes to reduce/compress?)
> 
> ManifestInstance ::= SEQUENCE {
>   hash              Digest,
>   size              INTEGER (1000..MAX), <<<< this one!
>   aki               KeyIdentifier,
>   manifestNumber    INTEGER (0..MAX),
>   thisUpdate        GeneralizedTime,
>   locations         SEQUENCE (SIZE(1..MAX)) OF AccessDescription,
>   subordinates      SEQUENCE (SIZE(1..MAX)) OF SubjectKeyIdentifier
>                       OPTIONAL }

Yes, even when the signing algorithm changes and produces smaller
signatures this is an appropriate minimum. If the _structure_ of
RPKI Manifests changes, the CCR specification will have to change
accordingly.

> 2) Section 3 - not an expert on ASN.1 nor this particular feature/technology
> ... but CertificateSerialNumber FROM PKIX1Explicit-2009 is unused. Please
> cross-check if there hasn't been an error or remove unused.

Good catch!

> 3) section 3.1
> 
> "In this version of the specification, it MUST be 0." seems a bit odd.
> 
> Perhaps: Version MUST be set to 0 for the CCR content specified in this
> document.

Sure!

> 4) section 5.3 ... a nit
> 
> "CCRs compress very well due to its data layout characteristics"
> 
> Perhaps: "CCRs compress very well due to their data layout characteristics" or
> "A CCR file compresses very well due to its data layout characteristics"

Thank you, that reads better.

The changes have been incorporated: https://github.com/job/draft-sidrops-rpki-ccr/commit/3919a61d4435f283ba274c2e2a2420c2f1726381

Kind regards,

Job