Amsterdam Netherlands job@sobornost.net

RIPE NCC

Netherlands bbakker@ripe.net

RIPE NCC

Netherlands tbruijnzeels@ripe.net

ops SIDROPS security cryptography X.509 This document specifies a Canonical Cache Representation (CCR) content type for use with the Resource Public Key Infrastructure (RPKI). CCR is a DER-encoded data interchange format which can be used to represent various aspects of the state of a validated cache at a particular point in time. The CCR profile is a compact and versatile format well-suited for a diverse set of applications such as audit trail keeping, validated payload dissemination, and analytics pipelines.

Introduction This document specifies a Canonical Cache Representation (CCR) content type for use with the Resource Public Key Infrastructure (RPKI). A validated cache contains all RPKI objects that the Relying Party (RP) has verified to be valid according to the rules for validation (see , , ). CCR is a data interchange format using Distinguished Encoding Rules (DER, ) which can be used to represent various aspects of the state of a validated cache at a particular point in time. The CCR profile is a compact and versatile format well-suited for a diverse set of applications such as audit record keeping, validated payload dissemination, and analytics pipelines. The format was primarily designed to support comparative analysis of uniformities and differences among multiple RP instances using different RPKI transport protocols (such as , , and ).

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

The Canonical Cache Representation content type The contentType for a CCR currently is defined as id-ct-rpkiCanonicalCacheRepresentation, with temporary Object Identifier (OID) 1.3.6.1.4.1.41948.825. Note: as part of the standardization process, at a future point in time, the aforementioned contentType value will change from the current Private Enterprise Number () to an OID assigned by IANA.

The Canonical Cache Representation content The content of a Canonical Cache Representation is formally defined as follows: RpkiCanonicalCacheRepresentation-2025 { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) smime(16) mod(0) id-mod-rpkiCCR-2025(TBD) } DEFINITIONS EXPLICIT TAGS ::= BEGIN IMPORTS CONTENT-TYPE, Digest, DigestAlgorithmIdentifier, SubjectKeyIdentifier FROM CryptographicMessageSyntax-2010 -- in [RFC6268] { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) modules(0) id-mod-cms-2009(58) } -- in [draft-spaghetti-sidrops-rpki-erik-protocol-02] ManifestRef FROM RpkiErikPartition-2025 { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) smime(16) mod(0) id-mod-rpkiErikPartition-2025(TBD) } ASID, ROAIPAddressFamily FROM RPKI-ROA-2023 -- in [RFC9582] { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) smime(16) mod(0) id-mod-rpkiROA-2023(75) } SubjectPublicKeyInfo FROM PKIX1Explicit-2009 { iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-mod-pkix1-explicit-02(51) } ; ct-rpkiCanonicalCacheRepresentation CONTENT-TYPE ::= { TYPE RpkiCanonicalCacheRepresentation IDENTIFIED BY id-ct-rpkiCanonicalCacheRepresentation } id-ct-rpkiCanonicalCacheRepresentation OBJECT IDENTIFIER ::= { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) snijders(41948) ccr(825) } RpkiCanonicalCacheRepresentation ::= SEQUENCE { version [0] INTEGER DEFAULT 0, hashAlg DigestAlgorithmIdentifier, producedAt GeneralizedTime, mfts [1] ManifestState OPTIONAL, vrps [2] ROAPayloadState OPTIONAL, vaps [3] ASPAPayloadState OPTIONAL, tas [4] TrustAnchorState OPTIONAL, rks [5] RouterKeyState OPTIONAL, ... } -- at least one of mfts, vrps, vaps, or tas MUST be present ( WITH COMPONENTS { ..., mfts PRESENT } | WITH COMPONENTS { ..., vrps PRESENT } | WITH COMPONENTS { ..., vaps PRESENT } | WITH COMPONENTS { ..., tas PRESENT } | WITH COMPONENTS { ..., rks PRESENT } ) ManifestState ::= SEQUENCE { mftrefs SEQUENCE OF ManifestRef, mostRecentUpdate GeneralizedTime, hash Digest } ROAPayloadState ::= SEQUENCE { rps SEQUENCE OF ROAPayloadSet, hash Digest } ROAPayloadSet ::= SEQUENCE { asID ASID, ipAddrBlocks SEQUENCE (SIZE(1..2)) OF ROAIPAddressFamily } ASPAPayloadState ::= SEQUENCE { aps SEQUENCE OF ASPAPayloadSet, hash Digest } ASPAPayloadSet ::= SEQUENCE { customerASID ASID, providers SEQUENCE (SIZE(1..MAX)) OF ASID } TrustAnchorState ::= SEQUENCE { skis SEQUENCE (SIZE(1..MAX)) OF SubjectKeyIdentifier, hash Digest } RouterKeyState ::= SEQUENCE { rksets SEQUENCE OF RouterKeySet, hash Digest } RouterKeySet ::= SEQUENCE { asID ASID, routerKeys SEQUENCE (SIZE(1..MAX)) OF RouterKey } RouterKey ::= SEQUENCE { ski SubjectKeyIdentifier, spki SubjectPublicKeyInfo } END

version The version field contains the format version for the RpkiCanonicalCacheRepresentation structure, in this version of the specification it MUST be 0.

hashAlg The hashAlg field specifies the algorithm used to construct the message digests. This profile uses SHA-256 , therefore the OID MUST be 2.16.840.1.101.3.4.2.1.

producedAt The producedAt field contains a GeneralizedTime and indicates the moment in time the CCR was generated.

State aspect fields Each CCR contains one or more fields representing particular aspects of the cache's state. Implementers should note the ellipsis extension marker in the RpkiCanonicalCacheRepresentation ASN.1 notation and anticipate future changes as new signed object types are standardized. Each state aspect generally consists of a sequence of details extracted from RPKI Objects of a specific type, along with a digest computed by hashing the aforementioned DER-encoded sequence, optionally including some metadata.

ManifestState An instance of ManifestState represents the set of valid, current Manifests () in the cache. It contains three fields: The mftrefs field contains a SEQUENCE of ManifestRef structures (see ) sorted in ascending order by hash value. The hash value in each instance of ManifestRef MUST be unique with respect to the other instances of ManifestRef. The mostRecentUpdate is a metadata field which contains the most recent thisUpdate amongst all Manifests. If the mftrefs field contains an empty sequence, the mostRecentUpdate MUST be set to the POSIX Epoch ("19700101000000Z"). The hash field contains a message digest computed using the mftrefs value (encoded in DER format) as input message.

ROAPayloadState An instance of ROAPayloadState contains a field named rps which represents the current set of Validated ROA Payloads () encoded as a SEQUENCE of ROAPayloadSet instances. The ROAPayloadSet structure is modeled after the RouteOriginAttestation (). The asID value in each instance of ROAPayloadSet MUST be unique with respect to other instances of ROAPayloadSet. The contents of the ipAddrBlocks field MUST appear in canonical form and ordered as defined in . The hash field contains a message digest computed using the rps value (encoded in DER format) as input message.

ASPAPayloadState An instance of ASPAPayloadState contains an aps field which represents the current set of deduplicated and merged ASPA payloads () ordered by ascending customerASID value encoded as a SEQUENCE of ASPAPayloadSet instances. The customerASID value in each instance of ASPAPayloadSet MUST be unique with respect to other instances of ASPAPayloadSet. The ASPAPayloadSet structure is modeled after the ProviderASSet (). The hash field contains a message digest computed using the aps value (encoded in DER format) as input message.

TrustAnchorState An instance of TrustAnchorState represents the set of valid Trust Anchor (TA) Certification Authority (CA) resource certificates used by the relying party when producing the CCR. Each SubjectKeyIdentifier is the 160-bit SHA-1 hash of the value of the DER-encoded ASN.1 bit string of the TA's Subject Public Key, as described in . The skis field contains a sequence of Subject Key Identifiers (SKI) sorted in ascending order by interpreting the SKI value as an unsigned 160-bit integer. The hash field contains a message digest computed using the skis value (encoded in DER format) as input message.

RouterKeyState An instance of RouterKeyState contains an rksets field which represents the current set of valid BGPsec Router Keys encoded as a SEQUENCE of RouterKeySet instances. The asID value in each instance of RouterKeySet MUST be unique with respect to other instances of RouterKeySet. Instances of RouterKeySet are sorted by ascending value of asID. Instances of RouterKey are sorted by ascending value of ski by interpreting the SKI value as an unsigned 160-bit integer. The hash field contains a message digest computed using the rks value (encoded in DER format) as input message.

Operational Considerations Comparing the ManifestState mostRecentUpdate timestamp value with the producedAt timestamp might help offer insight into the timing and propagation delays of the RPKI supply chain. Given the absence of public keys and fairly repetitive content in RPKI AccessDescription instances, it should be noted CCR content compresses well.

Verifying CCR file integrity The integrity of a CCR object can be checked by confirming whether the hash values embedded inside state aspects match the computed hash value of the respective state aspect payload structure.

Security Considerations CCR objects are not signed objects.

IANA Considerations

SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1) IANA is requested to allocate the following in the "SMI Security for S/MIME CMS Content Type (1.2.840.113549.1.9.16.1)" registry:

Decimal	Description	References
TBD	id-ct-rpkiCanonicalCacheRepresentation	draft-spaghetti-sidrops-rpki-ccr

RPKI Repository Name Schemes IANA is requested to add the Canonical Cache Representation file extension to the "RPKI Repository Name Schemes" registry as follows:

Filename Extension	RPKI Object	Reference
.ccr	Canonical Cache Representation	draft-spaghetti-sidrops-rpki-ccr

SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0) IANA is requested to allocate the following in the "SMI Security for S/MIME Module Identifier (1.2.840.113549.1.9.16.0)" registry:

Decimal	Description	References
TBD	id-mod-rpkiCCR-2025	draft-spaghetti-sidrops-rpki-ccr

Media Types IANA is requested to register the media type "application/rpki-ccr" in the "Media Types" registry as follows:

Canonical Cache Representation Media Type

Type name:

application

Subtype name:

rpki-ccr

Required parameters:

N/A

Optional parameters:

N/A

Encoding considerations:

binary

Security considerations:

This media type contains no active content.

Interoperability considerations:

N/A

Published specification:

draft-spaghetti-sidrops-rpki-ccr

Applications that use this media type:

RPKI operators

Fragment identifier considerations:

N/A

Additional information:

Content:

This media type is a RPKI Canonical Cache Representation object, as defined in draft-spaghetti-sidrops-rpki-ccr.

Magic number(s):

N/A

File extension(s):

.ccr

Macintosh file type code(s):

N/A

Person & email address to contact for further information:

Job Snijders (job@sobornost.net)

Intended usage:

COMMON

Restrictions on usage:

N/A

Author:

Job Snijders (job@sobornost.net)

Change controller:

IETF

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document defines a profile for the structure of the Resource Public Key Infrastructure (RPKI) distributed repository. Each individual repository publication point is a directory that contains files that correspond to X.509/PKIX Resource Certificates, Certificate Revocation Lists and signed objects. This profile defines the object (file) naming scheme, the contents of repository publication points (directories), and a suggested internal structure of a local repository cache that is intended to facilitate synchronization across a distributed collection of repository publication points and to facilitate certification path construction. [STANDARDS-TRACK] This document defines a standard profile for X.509 certificates for the purpose of supporting validation of assertions of "right-of-use" of Internet Number Resources (INRs). The certificates issued under this profile are used to convey the issuer's authorization of the subject to be regarded as the current holder of a "right-of-use" of the INRs that are described in the certificate. This document contains the normative specification of Certificate and Certificate Revocation List (CRL) syntax in the Resource Public Key Infrastructure (RPKI). This document also specifies profiles for the format of certificate requests and specifies the Relying Party RPKI certificate path validation procedure. [STANDARDS-TRACK] This document defines a generic profile for signed objects used in the Resource Public Key Infrastructure (RPKI). These RPKI signed objects make use of Cryptographic Message Syntax (CMS) as a standard encapsulation format. [STANDARDS-TRACK] To help reduce well-known threats against BGP including prefix mis- announcing and monkey-in-the-middle attacks, one of the security requirements is the ability to validate the origination Autonomous System (AS) of BGP routes. More specifically, one needs to validate that the AS number claiming to originate an address prefix (as derived from the AS_PATH attribute of the BGP route) is in fact authorized by the prefix holder to do so. This document describes a simple validation mechanism to partially satisfy this requirement. [STANDARDS-TRACK] RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document defines a "manifest" for use in the Resource Public Key Infrastructure (RPKI). A manifest is a signed object (file) that contains a listing of all the signed objects (files) in the repository publication point (directory) associated with an authority responsible for publishing in the repository. For each certificate, Certificate Revocation List (CRL), or other type of signed objects issued by the authority that are published at this repository publication point, the manifest contains both the name of the file containing the object and a hash of the file content. Manifests are intended to enable a relying party (RP) to detect certain forms of attacks against a repository. Specifically, if an RP checks a manifest's contents against the signed objects retrieved from a repository publication point, then the RP can detect replay attacks, and unauthorized in-flight modification or deletion of signed objects. This document obsoletes RFC 6486. This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to one or more prefixes within the address block. This document obsoletes RFC 6482. Yandex JetLend Internet Initiative Japan Vigil Security, LLC Workonline This document defines a Cryptographic Message Syntax (CMS) protected content type for Autonomous System Provider Authorization (ASPA) objects for use with the Resource Public Key Infrastructure (RPKI). An ASPA is a digitally signed object through which the issuer (the holder of an Autonomous System identifier), can authorize one or more other Autonomous Systems (ASes) as its upstream providers. When validated, an ASPA's eContent can be used for detection and mitigation of route leaks. This document specifies the Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI). Erik Synchronization can be characterized as a data replication system using Merkle trees, a content-addressable naming scheme, concurrency control using monotonically increasing sequence numbers, and HTTP transport. Relying Parties can combine information retrieved via Erik Synchronization with other RPKI transport protocols. The protocol's design is intended to be efficient, fast, and easy to implement. National Institute of Standards and Technology ITU-T Informative References This document specifies the rsync Uniform Resource Identifier (URI) scheme. This document is not an Internet Standards Track specification; it is published for informational purposes. In the Resource Public Key Infrastructure (RPKI), Certificate Authorities (CAs) publish certificates, including end-entity certificates, Certificate Revocation Lists (CRLs), and RPKI signed objects to repositories. Relying Parties retrieve the published information from those repositories. This document specifies a new RPKI Repository Delta Protocol (RRDP) for this purpose. RRDP was specifically designed for scaling. It relies on an Update Notification File which lists the current Snapshot and Delta Files that can be retrieved using HTTPS (HTTP over Transport Layer Security (TLS)), and it enables the use of Content Distribution Networks (CDNs) or other caching infrastructures for the retrieval of these files. This document describes BGPsec, an extension to the Border Gateway Protocol (BGP) that provides security for the path of Autonomous Systems (ASes) through which a BGP UPDATE message passes. BGPsec is implemented via an optional non-transitive BGP path attribute that carries digital signatures produced by each AS that propagates the UPDATE message. The digital signatures provide confidence that every AS on the path of ASes listed in the UPDATE message has explicitly authorized the advertisement of the route. This document describes how Private Enterprise Numbers (PENs) are registered by IANA. It shows how to request a new PEN and how to modify a current PEN. It also gives a brief overview of PEN uses.

Acknowledgements The authors wish to thank and for their generous feedback on this specification,

The below is a Base64-encoded example CCR object. For a more elaborate example based on the global RPKI, see the URL in . MIII/wYKKwYBBAGCx1yGOaCCCO8EggjrMIII5wYJYIZIAWUDBAIBGA8yMDI1MDkxNTEyMjg0 MVqhggVHMIIFQzCCBQwwgdEEIAAAiSH0phBIZFlYrQgsHFJqSJ+ax/asiFndLzYVUuLBAgIH zgQUqgvXjKLKpeuP87noI3dNwbdN6+sCAgVQGA8yMDI1MDkxNTA5MDE1MlowfjB8BggrBgEF BQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC9jMy85Nzg4 MzctMTAyMy00YjM5LTliMzctYTEwOGRiZTBmZDFmLzEvcWd2WGpLTEtwZXVQODdub0kzZE53 YmRONi1zLm1mdDCB0QQgAAIINi/FNk2gG24RmitkMFRwPv2mr4OuSOeTnChnM2ECAgeEBBRM cenyPurKaMchy+QoBhALdeFXcAICBUQYDzIwMjUwOTE1MDQwMTM3WjB+MHwGCCsGAQUFBzAL hnByc3luYzovL3Jwa2kucmlwZS5uZXQvcmVwb3NpdG9yeS9ERUZBVUxULzE2Lzk0ZjY2Mi01 MDZiLTRlYzktYTdhYS1jOWI3ZWIyY2VhNTcvMS9USEhwOGo3cXltakhJY3ZrS0FZUUMzWGhW M0EubWZ0MIHUBCAAAmznsh/USQWDhOQsuF0UsFIu8uvGjQVEwz8XHXyuSAICCNwEFI6N1bLB AbmDp5nJOKoOQKZR/L4HAgIBLxgPMjAyNTA5MTUwNTAxMjlaMIGAMH4GCCsGAQUFBzALhnJy c3luYzovL3Jwa2kuYXBuaWMubmV0L21lbWJlcl9yZXBvc2l0b3J5L0E5MTU2MzM0L0U3Q0RE RkNFQzhEODExRUU5RjRBQjk2REM0RjlBRTAyL2pvM1Zzc0VCdVlPbm1jazRxZzVBcGxIOHZn Yy5tZnQwgeIEIAACk3htPo58kvOxNTrL+VTUvxdYjfPp0tNhnWsqwfBuAgIIwAQUV419yXeb J4Feu1w/X88HzFg3CLMCAgEhGA8yMDI1MDkxNTAwMjA1NVowgY4wgYsGCCsGAQUFBzALhn9y c3luYzovL3JzeW5jLnBhYXMucnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L2VjYTI1MzUwLTll M2YtNDZlMS1hZTJiLTFjNjFiNmVhNWFlMi8wLzU3OEQ3REM5Nzc5QjI3ODE1RUJCNUMzRjVG Q0YwN0NDNTgzNzA4QjMubWZ0MIHRBCAABdMuNuWiXRU47KUgaQAp1Qeej1PCy2yUN+SDzXws VAICDZEEFBufIboE5eMHezkePUj/WwpQszafAgIKvxgPMjAyNTA5MTUxMTAxMDNaMH4wfAYI KwYBBQUHMAuGcHJzeW5jOi8vcnBraS5yaXBlLm5ldC9yZXBvc2l0b3J5L0RFRkFVTFQvMjIv ZjY3YTc4LTE4M2QtNDk0YS05OTVlLWY1MWM1ZmIzZGY5YS8xL0c1OGh1Z1RsNHdkN09SNDlT UDliQ2xDek5wOC5tZnQwgdEEIAAHsnERrXUhPz3IFrxam/4W+HF+d3GAlfFatYjlLPRfAgIH hAQUOe9KpZd/HzcTPnMQgJ//iTXAyLwCAgPeGA8yMDI1MDkxNTEyMDE0NFowfjB8BggrBgEF BQcwC4ZwcnN5bmM6Ly9ycGtpLnJpcGUubmV0L3JlcG9zaXRvcnkvREVGQVVMVC9mZS8xNDhm NzEtYWIyYy00NDA5LWFlMWYtZTdkNWZjZTZiZmFjLzEvT2U5S3BaZF9IemNUUG5NUWdKX19p VFhBeUx3Lm1mdBgPMjAyNTA5MTUxMjAxNDRaBCARm9fasElYJ3tNOED50oo4u6Y8pJYv3yWy 289+U6Pph6KCAXIwggFuMIIBSDBkAgEHMF8wSAQCAAEwQjAJAwQAwCNeAgEgMAkDBADAQysC ASAwCQMEAMIgRQIBIDAJAwQBwiDaAgEgMAkDBADCIooCASAwCQMEAcI9XAIBIDATBAIAAjAN MAsDBQMqCztAAgIAgDCBowICIFswgZwwfgQCAAEweDAGAwQAW9AiMAYDBABejvAwBgMEA16O 8DAGAwQAXo7xMAYDBABejvIwBgMEAF6O9DAGAwQAXo71MAYDBABejvYwBgMEAF6O9zAGAwQA uTTgMAYDBAK5NOAwBgMEALk04TAGAwQAuTTiMAYDBAC5NOMwBgMEAMs4LDAaBAIAAjAUMAkD BwAgAQZ4BogwBwMFACoCCJgwOgICPMowNDAyBAIAAjAsMAkDBwAgAQZ8IIwwCQMHACABBygY CDAJAwcAKg6yQAAAMAkDBwAqDrJAARgEIAJfihdmpfxPBloevnOquIqGrimX4wGRErhD32bn VO0Mo4GWMIGTMG8wDgICA7EwCAICBY0CAjOdMBcCAh4nMBECAgOxAgIFjQICM50CAwDu0jAP AgJIrzAJAgJP+QIDAyp/MAoCAwCYWjADAgEAMCcCAwCi+DAgAgIArgICBRMCAiMqAgMAxr0C AwDqpAIDAxq2AgMDPhwEIBeP7Zc4aZi+GCoXMcr/DKHazjIGckNbl4z+LxHLcE7OpFIwUDAs BBQLnMqQ3Q16ijdmaxkhf+DYQDe3ogQU6FUrH9bRpPfkBMbY5WgNHrwWP8MEIP+wmtCcK45g tkciIlpky13WtimBp00mgS+Yvpr0vi+HpYIBGTCCARUwgfAwge0CAjzKMIHmMHEEFF1CUOLY HURI2KKe/OkdKf8HXsniMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEgFcjQ/g//LAQerAH 2Mpp+GucoDAGBbhIqD33wNPsXxnAGb+mtZ7XQrVO9DQ6UlAShtig5+QfEKpTtFgiqfiAFTBx BBS+iJtV0Lc3OX11xJ9IW4WPqYrRHzBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABOBcSa9J 9m7sdbl9RL5fkFsGWLyGnT4y7hV9psairgBlISp6+1Syw4KxPvpfaeXh9pFkzVQDdthVFN3W /0SqRNsEILpftEnO+2ugDzYSeWKi7qboZ/6FErvdrenG5Li8FsHS It decodes as follows: File: /var/db/rpki-client/rpki.ccr Hash identifier: k5quWMYc3o8nIzijN+dNEWNBNbHmjjtGfFvzdhT8MsM= CCR produced at: Mon 15 Sep 2025 12:28:41 +0000 Manifest state hash: MTE5QkQ3REFCMDQ5NTgyNzdCNEQzODQwRjlEMjhBMzg= Manifest last update: Mon 15 Sep 2025 12:01:44 +0000 Manifest references: hash:AACJIfSmEEhkWVitCCwcUmpIn5rH9qyIWd0vNhVS4sE= size:1998 aki:AA0BD78CA2CAA5EB8FF3B9E823774DC1B74DEBEB seqnum:0550 thisupdate:1757926912 sia:rsync://rpki.ripe.net/repository/DEFAULT/c3/978837-1023-4b39-9b37-a108dbe0fd1f/1/qgvXjKLKpeuP87noI3dNwbdN6-s.mft hash:AAIINi/FNk2gG24RmitkMFRwPv2mr4OuSOeTnChnM2E= size:1924 aki:4C71E9F23EEACA68C721CBE42806100B75E15770 seqnum:0544 thisupdate:1757908897 sia:rsync://rpki.ripe.net/repository/DEFAULT/16/94f662-506b-4ec9-a7aa-c9b7eb2cea57/1/THHp8j7qymjHIcvkKAYQC3XhV3A.mft hash:AAJs57If1EkFg4TkLLhdFLBSLvLrxo0FRMM/Fx18rkg= size:2268 aki:8E8DD5B2C101B983A799C938AA0E40A651FCBE07 seqnum:012F thisupdate:1757912489 sia:rsync://rpki.apnic.net/member_repository/A9156334/E7CDDFCEC8D811EE9F4AB96DC4F9AE02/jo3VssEBuYOnmck4qg5AplH8vgc.mft hash:AAKTeG0+jnyS87E1Osv5VNS/F1iN8+nS02GdayrB8G4= size:2240 aki:578D7DC9779B27815EBB5C3F5FCF07CC583708B3 seqnum:0121 thisupdate:1757895655 sia:rsync://rsync.paas.rpki.ripe.net/repository/eca25350-9e3f-46e1-ae2b-1c61b6ea5ae2/0/578D7DC9779B27815EBB5C3F5FCF07CC583708B3.mft hash:AAXTLjblol0VOOylIGkAKdUHno9TwstslDfkg818LFQ= size:3473 aki:1B9F21BA04E5E3077B391E3D48FF5B0A50B3369F seqnum:0ABF thisupdate:1757934063 sia:rsync://rpki.ripe.net/repository/DEFAULT/22/f67a78-183d-494a-995e-f51c5fb3df9a/1/G58hugTl4wd7OR49SP9bClCzNp8.mft hash:AAeycRGtdSE/PcgWvFqb/hb4cX53cYCV8Vq1iOUs9F8= size:1924 aki:39EF4AA5977F1F37133E7310809FFF8935C0C8BC seqnum:03DE thisupdate:1757937704 sia:rsync://rpki.ripe.net/repository/DEFAULT/fe/148f71-ab2c-4409-ae1f-e7d5fce6bfac/1/Oe9KpZd_HzcTPnMQgJ__iTXAyLw.mft ROA payload state hash: MDI1RjhBMTc2NkE1RkM0RjA2NUExRUJFNzNBQUI4OEE= ROA payload entries: 192.35.94.0/24-32 AS 7 192.67.43.0/24-32 AS 7 194.32.69.0/24-32 AS 7 194.32.218.0/23-32 AS 7 194.34.138.0/24-32 AS 7 194.61.92.0/23-32 AS 7 2a0b:3b40::/29-128 AS 7 91.208.34.0/24 AS 8283 94.142.240.0/24 AS 8283 94.142.240.0/21 AS 8283 94.142.241.0/24 AS 8283 94.142.242.0/24 AS 8283 94.142.244.0/24 AS 8283 94.142.245.0/24 AS 8283 94.142.246.0/24 AS 8283 94.142.247.0/24 AS 8283 185.52.224.0/24 AS 8283 185.52.224.0/22 AS 8283 185.52.225.0/24 AS 8283 185.52.226.0/24 AS 8283 185.52.227.0/24 AS 8283 203.56.44.0/24 AS 8283 2001:678:688::/48 AS 8283 2a02:898::/32 AS 8283 2001:67c:208c::/48 AS 15562 2001:728:1808::/48 AS 15562 2a0e:b240::/48 AS 15562 2a0e:b240:118::/48 AS 15562 ASPA payload state hash: MTc4RkVEOTczODY5OThCRTE4MkExNzMxQ0FGRjBDQTE= ASPA payload entries: customer: 945 providers: 1421, 13213 customer: 7719 providers: 945, 1421, 13213, 61138 customer: 18607 providers: 20473, 207487 customer: 39002 providers: 0 customer: 41720 providers: 174, 1299, 9002, 50877, 60068, 203446, 212508 Trust anchor state hash: RkZCMDlBRDA5QzJCOEU2MEI2NDcyMjIyNUE2NENCNUQ= Trust anchor keyids: 0B9CCA90DD0D7A8A37666B19217FE0D84037B7A2, E8552B1FD6D1A4F7E404C6D8E5680D1EBC163FC3 Router key state hash: QkE1RkI0NDlDRUZCNkJBMDBGMzYxMjc5NjJBMkVFQTY= Router keys: asid:15562 ski:5D4250E2D81D4448D8A29EFCE91D29FF075EC9E2 pubkey:MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEgFcjQ/g//LAQerAH2Mpp+GucoDAGBbhIqD33wNPsXxnAGb+mtZ7XQrVO9DQ6UlAShtig5+QfEKpTtFgiqfiAFQ== asid:15562 ski:BE889B55D0B737397D75C49F485B858FA98AD11F pubkey:MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE4FxJr0n2bux1uX1Evl+QWwZYvIadPjLuFX2mxqKuAGUhKnr7VLLDgrE++l9p5eH2kWTNVAN22FUU3db/RKpE2w== Validation: N/A

Implementation status This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

• Example .ccr files were created by Job Snijders. A current example CCR (regenerated every few minutes) is available here:
• A CCR serializer and deserializer implementation based on was provided by Job Snijders.