-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdraft-ietf-regext-rdap-rpki.txt
2296 lines (1759 loc) · 70.4 KB
/
draft-ietf-regext-rdap-rpki.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Registration Protocols Extensions (regext) J. Singh
Internet-Draft ARIN
Intended status: Standards Track A. Newton
Expires: 8 August 2025 ICANN
4 February 2025
Registration Data Access Protocol (RDAP) Extension for Resource Public
Key Infrastructure (RPKI) Registration Data
draft-ietf-regext-rdap-rpki-00
Abstract
The Resource Public Key Infrastructure (RPKI) is used to secure
inter-domain routing on the internet. This document defines a new
Registration Data Access Protocol (RDAP) extension, "rpki1", for
accessing the RPKI registration data in the Internet Number Registry
System (INRS) through RDAP. The Internet Number Registry System
(INRS) is composed of Regional Internet Registries (RIRs), National
Internet Registries (NIRs), and Local Internet Registries (LIRs).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 8 August 2025.
Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
Singh & Newton Expires 8 August 2025 [Page 1]
Internet-Draft rdap-rpki February 2025
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Common Data Members . . . . . . . . . . . . . . . . . . . . . 4
3. Route Origin Authorization . . . . . . . . . . . . . . . . . 5
3.1. Object Class . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Lookup . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3. Search . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3.1. Search Results . . . . . . . . . . . . . . . . . . . 9
3.4. Reverse Search . . . . . . . . . . . . . . . . . . . . . 11
3.5. Relationship with IP Network Object Class . . . . . . . . 11
4. Autonomous System Provider Authorization . . . . . . . . . . 14
4.1. Object Class . . . . . . . . . . . . . . . . . . . . . . 14
4.2. Lookup . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3. Search . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3.1. Search Results . . . . . . . . . . . . . . . . . . . 17
4.4. Reverse Search . . . . . . . . . . . . . . . . . . . . . 19
4.5. Relationship with Autonomous System Number Object
Class . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5. X.509 Resource Certificate . . . . . . . . . . . . . . . . . 22
5.1. Object Class . . . . . . . . . . . . . . . . . . . . . . 22
5.2. Lookup . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.3. Search . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.3.1. Search Results . . . . . . . . . . . . . . . . . . . 29
5.4. Reverse Search . . . . . . . . . . . . . . . . . . . . . 31
5.5. Relationship with Other Object Classes . . . . . . . . . 31
6. RDAP Conformance . . . . . . . . . . . . . . . . . . . . . . 35
7. Security Considerations . . . . . . . . . . . . . . . . . . . 35
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
8.1. RDAP Extensions Registry . . . . . . . . . . . . . . . . 35
8.2. RDAP Reverse Search Registry . . . . . . . . . . . . . . 35
8.3. RDAP Reverse Search Mapping Registry . . . . . . . . . . 37
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.1. Normative References . . . . . . . . . . . . . . . . . . 38
10.2. Informative References . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41
Singh & Newton Expires 8 August 2025 [Page 2]
Internet-Draft rdap-rpki February 2025
1. Introduction
The network operators are increasingly deploying the Resource Public
Key Infrastructure (RPKI, [RFC6480]) to secure inter-domain routing
([RFC4271]) on the internet. RPKI enables Internet Number Resource
(INR) holders to cryptographically assert about their registered IP
addresses and autonomous system numbers to prevent route hijacks and
leaks. To that end, RPKI defines the following cryptographic
profiles:
* Route Origin Authorization (ROA, [RFC9582]) where a Classless
Inter-Domain Routing (CIDR, [RFC1519]) address block holder
cryptographically asserts about the origin autonomous system (AS,
[RFC4271]) for routing that CIDR address block.
* Autonomous System Provider Authorization (ASPA,
[I-D.ietf-sidrops-aspa-profile]) where an autonomous system number
(ASN, [RFC5396]) holder cryptographically asserts about the
provider AS for that ASN.
* X.509 Resource Certificate ([RFC6487]) where the issuer grants the
subject a right-of-use for the listed IP addresses and/or
autonomous system numbers.
This document defines a new RDAP extension, "rpki1", for accessing
the RPKI registration data within the Internet Number Registry System
(INRS) for aforementioned RPKI profiles through RDAP. The Internet
Number Registry System (INRS) is composed of Regional Internet
Registries (RIRs), National Internet Registries (NIRs), and Local
Internet Registries (LIRs).
The motivation here is that such RDAP data could complement the
existing RPKI diagnostic tools when troubleshooting a route hijack or
leak, by conveniently providing access to registration information
from a registry's database beside what is inherently available from
an RPKI profile object. There is registration metadata that is often
needed for troubleshooting that does not appear in, say, a ROA or a
VRP (Verified ROA Payload); such as:
* When did the initial version of a ROA get published?
* Was a ROA created in conjunction with an Internet Routing Registry
(IRR, [RFC2622]) route?
* Which IRR route is related with a ROA?
* Which IP network is associated with a ROA?
Furthermore, correlating registered RPKI data with registered IP
networks and autonomous system numbers would also give access to the
latter's contact information through RDAP entity objects, which
should aid troubleshooting.
Singh & Newton Expires 8 August 2025 [Page 3]
Internet-Draft rdap-rpki February 2025
In addition to troubleshooting, serving RPKI metadata over RDAP
offers a convenience to network operators through a simple lookup
mechanism. As is demonstrated in [RDAP-GUIDE], constructing custom
RDAP scripts is relatively easy and beneficial to network operators
for the purposes of reporting. Though not RDAP-based, systems such
as [JDR] and [CLOUDFLARE] have shown the utility of an approach that
allows users to explore the RPKI hierarchy in a visual fashion,
without interacting with the signed objects directly.
For these purposes, this specification defines RDAP object classes,
as well as lookup and search path segments, for the ROA, ASPA, and
X.509 resource certificate registration data.
1.1. Requirements Language
The keywords "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
[BCP14] when, and only when, they appear in all capitals, as shown
here.
Indentation and whitespace in examples are provided only to
illustrate element relationships, and are not a REQUIRED feature of
this protocol.
"..." in examples is used as shorthand for elements defined outside
of this document.
2. Common Data Members
The RDAP object classes for RPKI (Section 3.1, Section 4.1,
Section 5.1) can contain one or more of the following common members:
* "handle" -- a string representing the registry-unique identifier
of an RPKI object registration
* "name" -- a string representing the identifier assigned to an RPKI
object registration by the registration holder
* "notValidBefore" -- a string that contains the time and date in
Zulu (Z) format with UTC offset of 00:00 ([RFC3339]), representing
the not-valid-before date of an X.509 resource certificate for an
RPKI object (Section 4 of [RFC6487])
* "notValidAfter" -- a string that contains the time and date in
Zulu (Z) format with UTC offset of 00:00 ([RFC3339]), representing
the not-valid-after date of an X.509 resource certificate for an
RPKI object (Section 4 of [RFC6487])
* "publicationUri" -- a URI string pointing to the location of an
RPKI object within an RPKI repository; the URI scheme is "rsync",
per Section 4 of [RFC6487]
Singh & Newton Expires 8 August 2025 [Page 4]
Internet-Draft rdap-rpki February 2025
* "notificationUri" -- an HTTPS URI string pointing to the location
of the RPKI Repository Delta Protocol (RRDP) update notification
file for an RPKI repository (Section 3 of [RFC8182])
* "entities" -- an array of entity objects (Section 5.1 of
[RFC9083]), including the organization (entity) registered as the
authoritative source for an RPKI object
* "rpkiType" -- a string literal representing various combinations
of an RPKI repository and a Certification Authority (CA), with the
following possible values:
- "hosted" -- both the repository and CA are operated by a
registry for an organization with allocated resources
- "delegated" -- both the repository and CA are operated by an
organization with resources allocated by a registry
- "hybrid" -- the repository is operated by a registry for an
organization with allocated resources whereas the CA is
operated by the organization itself
RRDP is intended as the long-term replacement for rsync in RPKI. For
a CA that implements RRDP, the update notification file location is
expected to be set in each X.509 resource certificate it issues
(Section 3.2 of [RFC8182]). Consequently, the "notificationUri" data
should help inform about the RPKI repository and/or CA operated
downstream from a registry by an organization with resources
allocated by that registry.
3. Route Origin Authorization
3.1. Object Class
The Route Origin Authorization (ROA) object class can contain the
following members:
* "objectClassName" -- the string "rpki1_roa"
* "handle" -- see Section 2
* "name" -- see Section 2
* "roaIps" -- an array of objects representing CIDR address blocks
within a ROA; such an object can contain the following members:
- "ip" -- a string representing an IPv4 or IPv6 CIDR address
block with the "<CIDR prefix>/<CIDR length>" format (Section 4
of [RFC9582])
- "maxLength" -- a number representing the maximum prefix length
of the CIDR address block that the origin AS is authorized to
advertise; up to 32 for IPv4 and up to 128 for IPv6 (Section 4
of [RFC9582])
* "originAutnum" -- an unsigned 32-bit integer representing the
origin autonomous system number (Section 4 of [RFC9582])
* "notValidBefore" -- see Section 2
* "notValidAfter" -- see Section 2
Singh & Newton Expires 8 August 2025 [Page 5]
Internet-Draft rdap-rpki February 2025
* "publicationUri" -- see Section 2
* "notificationUri" -- see Section 2
* "entities" -- see Section 2
* "rpkiType" -- see Section 2
* "events" -- see Section 4.5 of [RFC9083]
* "links" -- "self" link, and "related" links for IP network and IRR
(when defined) objects (Section 4.2 of [RFC9083])
* "remarks" -- see Section 4.3 of [RFC9083]
Here is an elided example of a ROA object:
{
"objectClassName": "rpki1_roa",
"handle": "XXXX",
"name": "ROA-1",
"roaIps":
[
{
"ip": "2001:db8::/48",
"maxLength": 64
},
...
],
"originAutnum": 65536,
"notValidBefore": "2024-04-27T23:59:59Z",
"notValidAfter": "2025-04-27T23:59:59Z",
"publicationUri": "rsync://example.net/path/to/XXXX.roa",
"notificationUri": "https://example.net/path/to/notification.xml",
"entities":
[
{
"objectClassName": "entity",
"handle": "XYZ-RIR",
...
},
...
],
"rpkiType": "hosted",
"events":
[
{
"eventAction": "registration",
"eventDate": "2024-01-01T23:59:59Z"
},
...
],
"links":
[
Singh & Newton Expires 8 August 2025 [Page 6]
Internet-Draft rdap-rpki February 2025
{
"value": "https://example.net/rdap/rpki1/roa/XXXX",
"rel": "self",
"href": "https://example.net/rdap/rpki1/roa/XXXX",
"type": "application/rdap+json"
},
{
"value": "https://example.net/rdap/rpki1/roa/XXXX",
"rel": "related",
"href": "https://example.net/rdap/ip/2001:db8::/48",
"type": "application/rdap+json"
},
...
],
"remarks":
[
{
"description": [ "ROA" ]
}
]
}
3.2. Lookup
The resource type path segment for exact or closest match lookup of a
ROA object is "rpki1/roa".
The following lookup path segments are defined for a ROA object:
Syntax: rpki1/roa/<handle>
Syntax: rpki1/roa/<IP address>
Syntax: rpki1/roa/<CIDR prefix>/<CIDR length>
A lookup query for ROA information by handle is specified using this
form:
rpki1/roa/XXXX
XXXX is a string representing the "handle" property of a ROA, as
described in Section 3.1. The following URL would be used to find
information for a ROA that exactly matches the
"8a848ab0729f0f4f0173ba2013bc5eb3" handle:
https://example.net/rdap/rpki1/roa/8a848ab0729f0f4f0173ba2013bc5eb3
Singh & Newton Expires 8 August 2025 [Page 7]
Internet-Draft rdap-rpki February 2025
A lookup query for ROA information by IP address is specified using
this form:
rpki1/roa/YYYY
YYYY is a string representing an IPv4 or IPv6 address. The following
URL would be used to find information for a ROA that completely
encompasses the "192.0.2.0" IP address:
https://example.net/rdap/rpki1/roa/192.0.2.0
Similarly, for the "2001:db8::" IP address:
https://example.net/rdap/rpki1/roa/2001%3Adb8%3A%3A
A lookup query for ROA information by CIDR is specified using this
form:
rpki1/roa/YYYY/ZZZZ
YYYY/ZZZZ is a string representing the "ip" property of a CIDR
address block within a ROA, as described in Section 3.1. The
following URL would be used to find information for the most-specific
ROA matching the "192.0.2.0/25" CIDR:
https://example.net/rdap/rpki1/roa/192.0.2.0/25
Similarly, for the "2001:db8::/64" CIDR:
https://example.net/rdap/rpki1/roa/2001%3Adb8%3A%3A/64
In the "links" array of a ROA object, the context URI ("value"
member) of each link should be the lookup URL by its handle, and if
that's not available, then the lookup URL by one of its IP addresses.
3.3. Search
The resource type path segment for searching ROA objects is "rpki1/
roas".
The following search path segments are defined for ROA objects:
Syntax: rpki1/roas?name=<name search pattern>
Syntax: rpki1/roas?originAutnum=<autonomous system number>
Searches for ROA information by name are specified using this form:
Singh & Newton Expires 8 August 2025 [Page 8]
Internet-Draft rdap-rpki February 2025
rpki1/roas?name=XXXX
XXXX is a search pattern per Section 4.1 of [RFC9082], representing
the "name" property of a ROA, as described in Section 3.1. The
following URL would be used to find information for ROA names
matching the "ROA-*" pattern:
https://example.net/rdap/rpki1/roas?name=ROA-*
Searches for ROA information by origin autonomous system number are
specified using this form:
rpki1/roas?originAutnum=BBBB
BBBB is an autonomous system number representing the "originAutnum"
property of a ROA, as described in Section 3.1. The following URL
would be used to find information for ROAs with origin autonomous
system number 65536:
https://example.net/rdap/rpki1/roas?originAutnum=65536
3.3.1. Search Results
The ROA search results are returned in the "rpki1_roaSearchResults"
member, which is an array of ROA objects (Section 3.1).
Here is an elided example of the search results when finding
information for ROAs with origin autonomous system number 65536:
{
"rdapConformance":
[
"rdap_level_0",
"rpki1",
...
],
...
"rpki1_roaSearchResults":
[
{
"objectClassName": "rpki1_roa",
"handle": "XXXX",
"name": "ROA-1",
"roaIps":
[
{
"ip": "2001:db8::/48",
"maxLength": 64
Singh & Newton Expires 8 August 2025 [Page 9]
Internet-Draft rdap-rpki February 2025
},
...
],
"originAutnum": 65536,
"notValidBefore": "2024-04-27T23:59:59Z",
"notValidAfter": "2025-04-27T23:59:59Z",
"publicationUri": "rsync://example.net/path/to/XXXX.roa",
"notificationUri": "https://example.net/path/to/notification.xml",
"entities":
[
{
"objectClassName": "entity",
"handle": "XYZ-RIR",
...
},
...
],
"rpkiType": "hosted",
"events":
[
{
"eventAction": "registration",
"eventDate": "2024-01-01T23:59:59Z"
},
...
],
"links":
[
{
"value": "https://example.net/rdap/rpki1/roa/XXXX",
"rel": "self",
"href": "https://example.net/rdap/rpki1/roa/XXXX",
"type": "application/rdap+json"
},
{
"value": "https://example.net/rdap/rpki1/roa/XXXX",
"rel": "related",
"href": "https://example.net/rdap/ip/2001:db8::/48",
"type": "application/rdap+json"
},
...
]
},
...
]
}
Singh & Newton Expires 8 August 2025 [Page 10]
Internet-Draft rdap-rpki February 2025
3.4. Reverse Search
Per Section 2 of [RFC9536], if a server receives a reverse search
query with a searchable resource type of "ips" (Section 5 of
[I-D.ietf-regext-rdap-rir-search]), a related resource type of
"rpki1_roa", and a ROA property of "originAutnum" or "ip", then the
reverse search will be performed on the IP network objects from its
data store.
Section 8.2 and Section 8.3 include registration of entries for IP
network searches in the RDAP Reverse Search and RDAP Reverse Search
Mapping IANA registries when the related resource type is
"rpki1_roa".
3.5. Relationship with IP Network Object Class
An IP network object can span multiple ROA objects, and vice-versa.
Their relationship is affected by IP address transfers and splits in
a registry. It would be useful to show all the ROA objects
associated with an IP network object. To that end, this extension
adds a new "rpki1_roas" member to the IP Network object class
(Section 5.4 of [RFC9083]):
* "rpki1_roas" -- an array of ROA objects (Section 3.1) associated
with an IP network object; if the array is too large, the server
MAY truncate it, per Section 9 of [RFC9083]
Here is an elided example for an IP network object with ROAs:
{
"objectClassName": "ip network",
"handle": "ZZZZ-RIR",
"startAddress": "2001:db8::",
"endAddress": "2001:db8:ffff:ffff:ffff:ffff:ffff:ffff",
"ipVersion": "v6",
...
"rpki1_roas":
[
{
"objectClassName": "rpki1_roa",
"handle": "XXXX",
"name": "ROA-1",
"roaIps":
[
{
"ip": "2001:db8::/48",
"maxLength": 64
},
Singh & Newton Expires 8 August 2025 [Page 11]
Internet-Draft rdap-rpki February 2025
...
],
"originAutnum": 65536,
"notValidBefore": "2024-04-27T23:59:59Z",
"notValidAfter": "2025-04-27T23:59:59Z",
"publicationUri": "rsync://example.net/path/to/XXXX.roa",
"notificationUri": "https://example.net/path/to/notification.xml",
"entities":
[
{
"objectClassName": "entity",
"handle": "XYZ-RIR",
...
},
...
],
"rpkiType": "hosted",
"events":
[
{
"eventAction": "registration",
"eventDate": "2024-01-01T23:59:59Z"
},
...
],
"links":
[
{
"value": "https://example.net/rdap/rpki1/roa/XXXX",
"rel": "self",
"href": "https://example.net/rdap/rpki1/roa/XXXX",
"type": "application/rdap+json"
},
{
"value": "https://example.net/rdap/rpki1/roa/XXXX",
"rel": "related",
"href": "https://example.net/rdap/ip/2001:db8::/48",
"type": "application/rdap+json"
},
...
]
},
{
"objectClassName": "rpki1_roa",
"handle": "YYYY",
"name": "ROA-2",
"roaIps":
[
Singh & Newton Expires 8 August 2025 [Page 12]
Internet-Draft rdap-rpki February 2025
{
"ip": "2001:db8:1::/48",
"maxLength": 64
},
...
],
"originAutnum": 65537,
"notValidBefore": "2024-04-27T23:59:59Z",
"notValidAfter": "2025-04-27T23:59:59Z",
"publicationUri": "rsync://example.net/path/to/YYYY.roa",
"notificationUri": "https://example.net/path/to/notification.xml",
"entities":
[
{
"objectClassName": "entity",
"handle": "XYZ-RIR",
...
},
...
],
"rpkiType": "hosted",
"events":
[
{
"eventAction": "registration",
"eventDate": "2024-01-01T23:59:59Z"
},
...
],
"links":
[
{
"value": "https://example.net/rdap/rpki1/roa/YYYY",
"rel": "self",
"href": "https://example.net/rdap/rpki1/roa/YYYY",
"type": "application/rdap+json"
},
{
"value": "https://example.net/rdap/rpki1/roa/YYYY",
"rel": "related",
"href": "https://example.net/rdap/ip/2001:db8:1::/48",
"type": "application/rdap+json"
},
...
]
},
...
]
Singh & Newton Expires 8 August 2025 [Page 13]
Internet-Draft rdap-rpki February 2025
}
4. Autonomous System Provider Authorization
4.1. Object Class
The Autonomous System Provider Authorization (ASPA) object class can
contain the following members:
* "objectClassName" -- the string "rpki1_aspa"
* "handle" -- see Section 2
* "name" -- see Section 2
* "autnum" -- an unsigned 32-bit integer representing an autonomous
system number of the registration holder (Section 3 of
[I-D.ietf-sidrops-aspa-profile])
* "providerAutnums" -- an array of unsigned 32-bit integers, each
representing the autonomous system number of an AS that is
authorized as a provider (Section 3 of
[I-D.ietf-sidrops-aspa-profile])
* "notValidBefore" -- see Section 2
* "notValidAfter" -- see Section 2
* "publicationUri" -- see Section 2
* "notificationUri" -- see Section 2
* "entities" -- see Section 2
* "rpkiType" -- see Section 2
* "events" -- see Section 4.5 of [RFC9083]
* "links" -- "self" link, and "related" links for autonomous system
number and IRR (when defined) objects (Section 4.2 of [RFC9083])
* "remarks" -- see Section 4.3 of [RFC9083]
Here is an elided example of an ASPA object:
{
"objectClassName": "rpki1_aspa",
"handle": "XXXX",
"name": "ASPA-1",
"autnum": 65536,
"providerAutnums":
[
65542,
...
],
"notValidBefore": "2024-04-27T23:59:59Z",
"notValidAfter": "2025-04-27T23:59:59Z",
"publicationUri": "rsync://example.net/path/to/XXXX.aspa",
"notificationUri": "https://example.net/path/to/notification.xml",
"entities":
[
Singh & Newton Expires 8 August 2025 [Page 14]
Internet-Draft rdap-rpki February 2025
{
"objectClassName": "entity",
"handle": "XYZ-RIR",
...
},
...
],
"rpkiType": "hosted",
"events":
[
{
"eventAction": "registration",
"eventDate": "2024-01-01T23:59:59Z"
},
...
],
"links":
[
{
"value": "https://example.net/rdap/rpki1/aspa/XXXX",
"rel": "self",
"href": "https://example.net/rdap/rpki1/aspa/XXXX",
"type": "application/rdap+json"
},
{
"value": "https://example.net/rdap/rpki1/aspa/XXXX",
"rel": "related",
"href": "https://example.net/rdap/autnum/65536",
"type": "application/rdap+json"
},
...
],
"remarks":
[
{
"description": [ "ASPA" ]
}
]
}
4.2. Lookup
The resource type path segment for exact match lookup of an ASPA
object is "rpki1/aspa".
The following lookup path segments are defined for an ASPA object:
Syntax: rpki1/aspa/<handle>
Singh & Newton Expires 8 August 2025 [Page 15]
Internet-Draft rdap-rpki February 2025
Syntax: rpki1/aspa/<autonomous system number>
A lookup query for ASPA information by handle is specified using this
form:
rpki1/aspa/XXXX
XXXX is a string representing the "handle" property of an ASPA, as
described in Section 4.1. The following URL would be used to find
information for an ASPA that exactly matches the
"47ab80ed8693f25d0187d93a07db4484" handle:
https://example.net/rdap/rpki1/aspa/47ab80ed8693f25d0187d93a07db4484
A lookup query for ASPA information by autonomous system number is
specified using this form:
rpki1/aspa/YYYY
YYYY is an autonomous system number representing the "autnum"
property of an ASPA, as described in Section 4.1. The following URL
would be used to find information for an ASPA with autonomous system
number 65536:
https://example.net/rdap/rpki1/aspa/65536
In the "links" array of an ASPA object, the context URI ("value"
member) of each link should be the lookup URL by its handle, and if
that's not available, then the lookup URL by its autonomous system
number.
4.3. Search
The resource type path segment for searching ASPA objects is "rpki1/
aspas".
The following search path segments are defined for ASPA objects:
Syntax: rpki1/aspas?name=<name search pattern>
Syntax: rpki1/aspas?providerAutnum=<autonomous system number>
Searches for ASPA information by name are specified using this form:
rpki1/aspas?name=XXXX
Singh & Newton Expires 8 August 2025 [Page 16]
Internet-Draft rdap-rpki February 2025
XXXX is a search pattern per Section 4.1 of [RFC9082], representing
the "name" property of an ASPA, as described in Section 4.1. The
following URL would be used to find information for ASPA names
matching the "ASPA-*" pattern:
https://example.net/rdap/rpki1/aspas?name=ASPA-*
Searches for ASPA information by provider autonomous system number
are specified using this form:
rpki1/aspas?providerAutnum=YYYY
YYYY is an autonomous system number within the "providerAutnums"
property of an ASPA, as described in Section 4.1. The following URL
would be used to find information for ASPAs with provider autonomous
system number 65542:
https://example.net/rdap/rpki1/aspas?providerAutnum=65542
4.3.1. Search Results
The ASPA search results are returned in the "rpki1_aspaSearchResults"
member, which is an array of ASPA objects (Section 4.1).
Here is an elided example of the search results when finding
information for ASPAs with provider autonomous system number 65542:
{
"rdapConformance":
[
"rdap_level_0",
"rpki1",
...
],
...
"rpki1_aspaSearchResults":
[
{
"objectClassName": "rpki1_aspa",
"handle": "XXXX",
"name": "ASPA-1",
"autnum": 65536,
"providerAutnums":
[
65542,
...
],
"notValidBefore": "2024-04-27T23:59:59Z",
Singh & Newton Expires 8 August 2025 [Page 17]
Internet-Draft rdap-rpki February 2025
"notValidAfter": "2025-04-27T23:59:59Z",
"publicationUri": "rsync://example.net/path/to/XXXX.aspa",
"notificationUri": "https://example.net/path/to/notification.xml",
"entities":
[
{
"objectClassName": "entity",
"handle": "XYZ-RIR",
...
},
...
],
"rpkiType": "hosted",
"events":
[
{
"eventAction": "registration",
"eventDate": "2024-01-01T23:59:59Z"
},
...
],
"links":
[
{
"value": "https://example.net/rdap/rpki1/aspa/XXXX",
"rel": "self",
"href": "https://example.net/rdap/rpki1/aspa/XXXX",
"type": "application/rdap+json"
},
{
"value": "https://example.net/rdap/rpki1/aspa/XXXX",
"rel": "related",
"href": "https://example.net/rdap/autnum/65536",
"type": "application/rdap+json"
},
...
],
...
},
...
]
}