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
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
|
<pre>Internet Engineering Task Force (IETF) S. Turner
Request for Comments: 8608 sn3rd
Obsoletes: <a href="./rfc8208">8208</a> O. Borchert
Updates: <a href="./rfc7935">7935</a> NIST
Category: Standards Track June 2019
ISSN: 2070-1721
<span class="h1">BGPsec Algorithms, Key Formats, and Signature Formats</span>
Abstract
This document specifies the algorithms, algorithm parameters,
asymmetric key formats, asymmetric key sizes, and signature formats
used in BGPsec (Border Gateway Protocol Security). This document
updates <a href="./rfc7935">RFC 7935</a> ("The Profile for Algorithms and Key Sizes for Use
in the Resource Public Key Infrastructure") and obsoletes <a href="./rfc8208">RFC 8208</a>
("BGPsec Algorithms, Key Formats, and Signature Formats") by adding
Documentation and Experimentation Algorithm IDs, correcting the range
of unassigned algorithms IDs to fill the complete range, and
restructuring the document for better reading.
This document also includes example BGPsec UPDATE messages as well as
the private keys used to generate the messages and the certificates
necessary to validate those signatures.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc8608">https://www.rfc-editor.org/info/rfc8608</a>.
<span class="grey">Turner & Borchert Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) 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 extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Changes from <a href="./rfc8208">RFC 8208</a> . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Algorithm ID Types . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Signature Algorithms . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-2.2.1">2.2.1</a>. Algorithm ID 0x01 (1) - (ECDSA P-256) . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3">3</a>. Asymmetric Key Pair Formats . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
3.1. Asymmetric Key Pair for Algorithm ID 0x01 (1) - (ECDSA
P-256) . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.1.1">3.1.1</a>. Public Key Format . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.1.2">3.1.2</a>. Private Key Format . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4">4</a>. Signature Formats . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. Additional Requirements . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-7">7</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#appendix-A">Appendix A</a>. Examples . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#appendix-A.1">A.1</a>. Topology and Experiment Description . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#appendix-A.2">A.2</a>. Keys . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#appendix-A.3">A.3</a>. BGPsec IPv4 . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#appendix-A.4">A.4</a>. BGPsec IPv6 . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<span class="grey">Turner & Borchert Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document specifies the following:
o the digital signature algorithm and parameters,
o the hash algorithm and parameters,
o the algorithm identifier assignment and classification,
o the public and private key formats, and
o the signature formats
used by Resource Public Key Infrastructure (RPKI) Certification
Authorities (CAs) and BGPsec (Border Gateway Protocol Security)
speakers (i.e., routers). CAs use these algorithms when processing
requests for BGPsec Router Certificates [<a href="./rfc8209" title=""A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests"">RFC8209</a>]. Examples of when
BGPsec routers use these algorithms include requesting BGPsec
certificates [<a href="./rfc8209" title=""A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests"">RFC8209</a>], signing BGPsec UPDATE messages [<a href="./rfc8205" title=""BGPsec Protocol Specification"">RFC8205</a>], and
verifying signatures on BGPsec UPDATE messages [<a href="./rfc8205" title=""BGPsec Protocol Specification"">RFC8205</a>].
This document updates [<a href="./rfc7935" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure"">RFC7935</a>] to add support for a) a different
algorithm for BGPsec certificate requests, which are issued only by
BGPsec speakers; b) a different Subject Public Key Info format for
BGPsec certificates, which is needed for the specified BGPsec
signature algorithm; and c) different signature formats for BGPsec
signatures, which are needed for the specified BGPsec signature
algorithm. The BGPsec certificates are differentiated from other
RPKI certificates by the use of the BGPsec Extended Key Usage as
defined in [<a href="./rfc8209" title=""A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests"">RFC8209</a>]. BGPsec uses a different algorithm [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>]
[<a href="#ref-DSS" title=""Digital Signature Standard (DSS)"">DSS</a>] from the rest of the RPKI to provide similar security with
smaller keys, making the certificates smaller; these algorithms also
result in smaller signatures, which make the PDUs smaller.
<a href="#appendix-A">Appendix A</a> (non-normative) contains example BGPsec UPDATE messages as
well as the private keys used to generate the messages and the
certificates necessary to validate the signatures.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
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
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all
capitals, as shown here.
<span class="grey">Turner & Borchert Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Changes from <a href="./rfc8208">RFC 8208</a></span>
This section describes the significant changes between [<a href="./rfc8208" title=""BGPsec Algorithms, Key Formats, and Signature Formats"">RFC8208</a>] and
this document.
o Added <a href="#section-2.1">Section 2.1</a> containing Algorithm ID types. Also, the
interpretation of these IDs is described.
o Restructured Sections <a href="#section-2">2</a> and <a href="#section-3">3</a> to align with the corresponding
algorithm suite identifier value.
o Corrected the range for unassigned algorithm suite identifier
values.
o Added Documentation algorithm suite identifier values.
o Added Experimentation algorithm suite identifier values.
o Changed the next-hop IP in <a href="#appendix-A">Appendix A</a>'s IPv6 example to use a
private usage IPv6 address.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Algorithms</span>
The algorithms used to compute signatures on CA certificates, BGPsec
Router Certificates, and Certificate Revocation Lists (CRLs) are as
specified in <a href="./rfc7935#section-2">Section 2 of [RFC7935]</a>. This section addresses
algorithms used by BGPsec [<a href="./rfc8205" title=""BGPsec Protocol Specification"">RFC8205</a>] [<a href="#ref-DSS" title=""Digital Signature Standard (DSS)"">DSS</a>]. For example, these
algorithms are used by BGPsec routers to sign and verify BGPsec
UPDATE messages. To identify which algorithm is used, the BGPsec
UPDATE message contains the corresponding algorithm ID in each
Signature_Block of the BGPsec UPDATE message.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Algorithm ID Types</span>
Algorithms in BGPsec UPDATE messages are identified by the Algorithm
Suite Identifier field (algorithm ID) within the Signature_Block (see
<a href="./rfc8205#section-3.2">Section 3.2 of [RFC8205]</a>).
This document specifies five types of Algorithm IDs:
o Reserved Algorithm ID
Reserved algorithm IDs are the values 0x00 (0) and 0xFF (255).
These IDs MUST NOT be used in a Signature_Block, and if
encountered, the router MUST treat BGPsec UPDATE messages as
malformed [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>].
<span class="grey">Turner & Borchert Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
o Signature Algorithm ID
Signature algorithms are defined in <a href="#section-2.2">Section 2.2</a> of this document.
Processing of BGPsec UPDATE signing and validation using signature
algorithms is described at length in Sections <a href="#section-4.2">4.2</a> and <a href="#section-5.2">5.2</a> of
[<a href="./rfc8205" title=""BGPsec Protocol Specification"">RFC8205</a>].
o Unassigned Algorithm ID
This type of Algorithm ID is free for future assignments and MUST
NOT be used until an algorithm is officially assigned (see
<a href="#section-7">Section 7</a>). In case a router encounters an unassigned algorithm
ID in one of the Signature_Blocks of a BGPsec UPDATE message, the
router SHOULD process the Signature_Block as an unsupported
algorithm as specified in <a href="./rfc8205#section-5.2">Section 5.2 of [RFC8205]</a>.
o Experimentation Algorithm ID
Experimentation algorithm IDs span from 0xF7 (247) to 0xFA (250).
To allow experimentation to accurately describe deployment
examples, the use of publicly assigned algorithm IDs is
inappropriate, and a reserved block of Experimentation algorithm
IDs is required. This ensures that experimentation does not clash
with assigned algorithm IDs in deployed networks and mitigates the
risks to operational integrity of the network through
inappropriate use of experimentation to perform literal
configuration of routing elements on production systems. A router
that encounters an algorithm ID of this type outside of an
experimental network SHOULD treat it the same as an unsupported
algorithm as specified in <a href="./rfc8205#section-5.2">Section 5.2 of [RFC8205]</a>.
o Documentation Algorithm ID
Documentation algorithm IDs span from 0xFB (251) to 0xFE (254).
To allow documentation to accurately describe deployment examples,
the use of publicly assigned algorithm IDs is inappropriate, and a
reserved block of Documentation algorithm IDs is required. This
ensures that documentation does not clash with assigned algorithm
IDs in deployed networks and mitigates the risks to operational
integrity of the network through inappropriate use of
documentation to perform literal configuration of routing elements
on production systems. A router that encounters an algorithm ID
of this type SHOULD treat it the same as an unsupported algorithm
as specified in <a href="./rfc8205#section-5.2">Section 5.2 of [RFC8205]</a>.
<span class="grey">Turner & Borchert Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Signature Algorithms</span>
<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Algorithm ID 0x01 (1) - (ECDSA P-256)</span>
o The signature algorithm used MUST be the Elliptic Curve Digital
Signature Algorithm (ECDSA) with curve P-256 [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>] [<a href="#ref-DSS" title=""Digital Signature Standard (DSS)"">DSS</a>].
o The hash algorithm used MUST be SHA-256 [<a href="#ref-SHS" title=""Secure Hash Standard (SHS)"">SHS</a>].
Hash algorithms are not identified by themselves in certificates or
BGPsec UPDATE messages. They are represented by an OID that combines
the hash algorithm with the digital signature algorithm as follows:
o The ecdsa-with-SHA256 OID [<a href="./rfc5480" title=""Elliptic Curve Cryptography Subject Public Key Information"">RFC5480</a>] MUST appear in the Public-Key
Cryptography Standards #10 (PKCS #10) signatureAlgorithm field
[<a href="./rfc2986" title=""PKCS #10: Certification Request Syntax Specification Version 1.7"">RFC2986</a>] or in the Certificate Request Message Format (CRMF)
POPOSigningKey algorithm field [<a href="./rfc4211" title=""Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)"">RFC4211</a>]; where the OID is placed
depends on the certificate request format generated.
o In BGPsec UPDATE messages, the ECDSA with SHA-256 algorithm suite
identifier value 0x01 (1) (see <a href="#section-7">Section 7</a>) is included in the
Signature_Block List's Algorithm Suite Identifier field.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Asymmetric Key Pair Formats</span>
The key formats used to compute signatures on CA certificates, BGPsec
Router Certificates, and CRLs are as specified in <a href="./rfc7935#section-3">Section 3 of
[RFC7935]</a>. This section addresses key formats found in the BGPsec
Router Certificate requests and in BGPsec Router Certificates.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Asymmetric Key Pair for Algorithm ID 0x01 (1) - (ECDSA P-256)</span>
The ECDSA private keys used to compute signatures for certificate
requests and BGPsec UPDATE messages MUST be associated with the P-256
elliptic curve domain parameters [<a href="./rfc5480" title=""Elliptic Curve Cryptography Subject Public Key Information"">RFC5480</a>]. The public key pair MUST
use the uncompressed form.
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Public Key Format</span>
The Subject's public key is included in subjectPublicKeyInfo
[<a href="./rfc5280" title=""Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC5280</a>]. It has two sub-fields: algorithm and subjectPublicKey.
The values for the structures and their sub-structures follow:
o algorithm (an AlgorithmIdentifier type): The id-ecPublicKey OID
MUST be used in the algorithm field, as specified in <a href="./rfc5480#section-2.1.1">Section 2.1.1
of [RFC5480]</a>. The value for the associated parameters MUST be
secp256r1, as specified in <a href="./rfc5480#section-2.1.1.1">Section 2.1.1.1 of [RFC5480]</a>.
<span class="grey">Turner & Borchert Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
o subjectPublicKey: ECPoint MUST be used to encode the certificate's
subjectPublicKey field, as specified in <a href="./rfc5480#section-2.2">Section 2.2 of [RFC5480]</a>.
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Private Key Format</span>
Local policy determines private key format.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Signature Formats</span>
The structure for the certificate's and CRL's signature field MUST be
as specified in <a href="./rfc7935#section-4">Section 4 of [RFC7935]</a>; this is the same format used
by other RPKI certificates. The structure for the certification
request's and BGPsec UPDATE message's signature field MUST be as
specified in <a href="./rfc3279#section-2.2.3">Section 2.2.3 of [RFC3279]</a>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Additional Requirements</span>
It is anticipated that BGPsec will require the adoption of updated
key sizes and a different set of signature and hash algorithms over
time, in order to maintain an acceptable level of cryptographic
security. This profile should be updated to specify such future
requirements, when appropriate.
The recommended procedures to implement such a transition of key
sizes and algorithms are specified in [<a href="./rfc6916" title=""Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)"">RFC6916</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The security considerations of [<a href="./rfc3279" title=""Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC3279</a>], [<a href="./rfc5480" title=""Elliptic Curve Cryptography Subject Public Key Information"">RFC5480</a>], [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>],
[<a href="./rfc7935" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure"">RFC7935</a>], and [<a href="./rfc8209" title=""A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests"">RFC8209</a>] apply to certificates. The security
considerations of [<a href="./rfc3279" title=""Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC3279</a>], [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>], [<a href="./rfc7935" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure"">RFC7935</a>], and [<a href="./rfc8209" title=""A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests"">RFC8209</a>]
apply to certification requests. The security considerations of
[<a href="./rfc3279" title=""Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile"">RFC3279</a>], [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>], and [<a href="./rfc8205" title=""BGPsec Protocol Specification"">RFC8205</a>] apply to BGPsec UPDATE messages.
No new security considerations are introduced as a result of this
specification.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
The Internet Assigned Numbers Authority (IANA) has created the
"BGPsec Algorithm Suites" registry in the Resource Public Key
Infrastructure (RPKI) group. The one-octet algorithm suite
identifiers assigned by IANA identify the digest algorithm and
signature algorithm used in the BGPsec Signature_Block List's
Algorithm Suite Identifier field.
Per [<a href="./rfc8208" title=""BGPsec Algorithms, Key Formats, and Signature Formats"">RFC8208</a>], IANA registered a single algorithm suite identifier
for the digest algorithm SHA-256 [<a href="#ref-SHS" title=""Secure Hash Standard (SHS)"">SHS</a>] and for the signature
algorithm ECDSA on the P-256 curve [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>] [<a href="#ref-DSS" title=""Digital Signature Standard (DSS)"">DSS</a>]. This identifier
<span class="grey">Turner & Borchert Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
is still valid, and IANA has updated the registration to refer to
this document.
IANA has modified the range of the "Unassigned" address space from
"0x2-0xEF" to "0x02-0xF6":
Algorithm Digest Signature Specification
Suite Algorithm Algorithm Pointer
Identifier
+------------+---------------+--------------+-----------------------+
| 0x02-0xF6 | Unassigned | Unassigned | |
+------------+---------------+--------------+-----------------------+
In addition, IANA has registered the following address spaces for
"Experimentation" and "Documentation":
Algorithm Digest Signature Specification
Suite Algorithm Algorithm Pointer
Identifier
+------------+-----------------+-----------------+------------------+
| 0xF7-0xFA | Experimentation | Experimentation | This document |
+------------+-----------------+-----------------+------------------+
| 0xFB-0xFE | Documentation | Documentation | This document |
+------------+-----------------+-----------------+------------------+
The "BGPsec Algorithm Suites" registry in the RPKI group now contains
the following values:
Algorithm Digest Signature Specification
Suite Algorithm Algorithm Pointer
Identifier
+------------+-----------------+-----------------+------------------+
| 0x00 | Reserved | Reserved | This document |
+------------+-----------------+-----------------+------------------+
| 0x01 | SHA-256 | ECDSA P-256 | [<a href="#ref-SHS" title=""Secure Hash Standard (SHS)"">SHS</a>] [<a href="#ref-DSS" title=""Digital Signature Standard (DSS)"">DSS</a>] |
| | | | [<a href="./rfc6090" title=""Fundamental Elliptic Curve Cryptography Algorithms"">RFC6090</a>] |
| | | | This document |
+------------+-----------------+-----------------+------------------+
| 0x02-0xF6 | Unassigned | Unassigned | |
+------------+-----------------+-----------------+------------------+
| 0xF7-0xFA | Experimentation | Experimentation | This document |
+------------+-----------------+-----------------+------------------+
| 0xFB-0xFE | Documentation | Documentation | This document |
+------------+-----------------+-----------------+------------------+
| 0xFF | Reserved | Reserved | This document |
+------------+-----------------+-----------------+------------------+
<span class="grey">Turner & Borchert Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
Future assignments are to be made using the Standards Action process
defined in [<a href="./rfc8126" title="">RFC8126</a>]. Assignments consist of the one-octet algorithm
suite identifier value and the associated digest algorithm name and
signature algorithm name.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2986">RFC2986</a>] Nystrom, M. and B. Kaliski, "PKCS #10: Certification
Request Syntax Specification Version 1.7", <a href="./rfc2986">RFC 2986</a>,
DOI 10.17487/RFC2986, November 2000,
<<a href="https://www.rfc-editor.org/info/rfc2986">https://www.rfc-editor.org/info/rfc2986</a>>.
[<a id="ref-RFC3279">RFC3279</a>] Bassham, L., Polk, W., and R. Housley, "Algorithms and
Identifiers for the Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", <a href="./rfc3279">RFC 3279</a>, DOI 10.17487/RFC3279, April
2002, <<a href="https://www.rfc-editor.org/info/rfc3279">https://www.rfc-editor.org/info/rfc3279</a>>.
[<a id="ref-RFC4211">RFC4211</a>] Schaad, J., "Internet X.509 Public Key Infrastructure
Certificate Request Message Format (CRMF)", <a href="./rfc4211">RFC 4211</a>,
DOI 10.17487/RFC4211, September 2005,
<<a href="https://www.rfc-editor.org/info/rfc4211">https://www.rfc-editor.org/info/rfc4211</a>>.
[<a id="ref-RFC4271">RFC4271</a>] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", <a href="./rfc4271">RFC 4271</a>,
DOI 10.17487/RFC4271, January 2006,
<<a href="https://www.rfc-editor.org/info/rfc4271">https://www.rfc-editor.org/info/rfc4271</a>>.
[<a id="ref-RFC5280">RFC5280</a>] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", <a href="./rfc5280">RFC 5280</a>, DOI 10.17487/RFC5280, May 2008,
<<a href="https://www.rfc-editor.org/info/rfc5280">https://www.rfc-editor.org/info/rfc5280</a>>.
[<a id="ref-RFC5480">RFC5480</a>] Turner, S., Brown, D., Yiu, K., Housley, R., and T. Polk,
"Elliptic Curve Cryptography Subject Public Key
Information", <a href="./rfc5480">RFC 5480</a>, DOI 10.17487/RFC5480, March 2009,
<<a href="https://www.rfc-editor.org/info/rfc5480">https://www.rfc-editor.org/info/rfc5480</a>>.
<span class="grey">Turner & Borchert Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
[<a id="ref-RFC6090">RFC6090</a>] McGrew, D., Igoe, K., and M. Salter, "Fundamental Elliptic
Curve Cryptography Algorithms", <a href="./rfc6090">RFC 6090</a>,
DOI 10.17487/RFC6090, February 2011,
<<a href="https://www.rfc-editor.org/info/rfc6090">https://www.rfc-editor.org/info/rfc6090</a>>.
[<a id="ref-RFC6916">RFC6916</a>] Gagliano, R., Kent, S., and S. Turner, "Algorithm Agility
Procedure for the Resource Public Key Infrastructure
(RPKI)", <a href="https://www.rfc-editor.org/bcp/bcp182">BCP 182</a>, <a href="./rfc6916">RFC 6916</a>, DOI 10.17487/RFC6916, April
2013, <<a href="https://www.rfc-editor.org/info/rfc6916">https://www.rfc-editor.org/info/rfc6916</a>>.
[<a id="ref-RFC7935">RFC7935</a>] Huston, G. and G. Michaelson, Ed., "The Profile for
Algorithms and Key Sizes for Use in the Resource Public
Key Infrastructure", <a href="./rfc7935">RFC 7935</a>, DOI 10.17487/RFC7935,
August 2016, <<a href="https://www.rfc-editor.org/info/rfc7935">https://www.rfc-editor.org/info/rfc7935</a>>.
[<a id="ref-RFC8126">RFC8126</a>] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
<a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017,
<<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>>.
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>.
[<a id="ref-RFC8205">RFC8205</a>] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol
Specification", <a href="./rfc8205">RFC 8205</a>, DOI 10.17487/RFC8205, September
2017, <<a href="https://www.rfc-editor.org/info/rfc8205">https://www.rfc-editor.org/info/rfc8205</a>>.
[<a id="ref-RFC8208">RFC8208</a>] Turner, S. and O. Borchert, "BGPsec Algorithms, Key
Formats, and Signature Formats", <a href="./rfc8208">RFC 8208</a>,
DOI 10.17487/RFC8208, September 2017,
<<a href="https://www.rfc-editor.org/info/rfc8208">https://www.rfc-editor.org/info/rfc8208</a>>.
[<a id="ref-RFC8209">RFC8209</a>] Reynolds, M., Turner, S., and S. Kent, "A Profile for
BGPsec Router Certificates, Certificate Revocation Lists,
and Certification Requests", <a href="./rfc8209">RFC 8209</a>,
DOI 10.17487/RFC8209, September 2017,
<<a href="https://www.rfc-editor.org/info/rfc8209">https://www.rfc-editor.org/info/rfc8209</a>>.
[<a id="ref-DSS">DSS</a>] National Institute of Standards and Technology, "Digital
Signature Standard (DSS)", NIST FIPS Publication 186-4,
DOI 10.6028/NIST.FIPS.186-4, July 2013,
<<a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf">https://nvlpubs.nist.gov/nistpubs/FIPS/</a>
<a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf">NIST.FIPS.186-4.pdf</a>>.
<span class="grey">Turner & Borchert Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
[<a id="ref-SHS">SHS</a>] National Institute of Standards and Technology, "Secure
Hash Standard (SHS)", NIST FIPS Publication 180-4,
DOI 10.6028/NIST.FIPS.180-4, August 2015,
<<a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">https://nvlpubs.nist.gov/nistpubs/FIPS/</a>
<a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">NIST.FIPS.180-4.pdf</a>>.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC5398">RFC5398</a>] Huston, G., "Autonomous System (AS) Number Reservation for
Documentation Use", <a href="./rfc5398">RFC 5398</a>, DOI 10.17487/RFC5398,
December 2008, <<a href="https://www.rfc-editor.org/info/rfc5398">https://www.rfc-editor.org/info/rfc5398</a>>.
[<a id="ref-RFC6979">RFC6979</a>] Pornin, T., "Deterministic Usage of the Digital Signature
Algorithm (DSA) and Elliptic Curve Digital Signature
Algorithm (ECDSA)", <a href="./rfc6979">RFC 6979</a>, DOI 10.17487/RFC6979, August
2013, <<a href="https://www.rfc-editor.org/info/rfc6979">https://www.rfc-editor.org/info/rfc6979</a>>.
<span class="grey">Turner & Borchert Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Examples</span>
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Topology and Experiment Description</span>
Topology:
AS(64496)----AS(65536)----AS(65537)
Prefix Announcement: AS(64496), 192.0.2.0/24, 2001:db8::/32
The signature algorithm used in this example is ECDSA P-256, using
the algorithm suite identifier ID 0x01 (1) as specified in <a href="#section-7">Section 7</a>
of this document.
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Keys</span>
For this example, the ECDSA algorithm was provided with a static k to
make the result deterministic.
The k used for all signature operations was taken from <a href="./rfc6979#appendix-A.2.5">[RFC6979],
Appendix A.2.5</a>, "Signatures With SHA-256, message = 'sample'".
Note: Even though the certificates below are expired, they are still
useful within the constraint of this document.
k = A6E3C57DD01ABE90086538398355DD4C
3B17AA873382B0F24D6129493D8AAD60
Keys of AS64496:
================
ski: AB4D910F55CAE71A215EF3CAFE3ACC45B5EEC154
private key:
x = D8AA4DFBE2478F86E88A7451BF075565
709C575AC1C136D081C540254CA440B9
public key:
Ux = 7391BABB92A0CB3BE10E59B19EBFFB21
4E04A91E0CBA1B139A7D38D90F77E55A
Uy = A05B8E695678E0FA16904B55D9D4F5C0
DFC58895EE50BC4F75D205A25BD36FF5
<span class="grey">Turner & Borchert Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
Router Key Certificate example using OpenSSL 1.0.1e-fips 11 Feb 2013
--------------------------------------------------------------------
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 38655612 (0x24dd67c)
Signature Algorithm: ecdsa-with-SHA256
Issuer: CN=ROUTER-0000FBF0
Validity
Not Before: Jan 1 05:00:00 2017 GMT
Not After : Jul 1 05:00:00 2018 GMT
Subject: CN=ROUTER-0000FBF0
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (256 bit)
pub:
04:73:91:ba:bb:92:a0:cb:3b:e1:0e:59:b1:9e:bf:
fb:21:4e:04:a9:1e:0c:ba:1b:13:9a:7d:38:d9:0f:
77:e5:5a:a0:5b:8e:69:56:78:e0:fa:16:90:4b:55:
d9:d4:f5:c0:df:c5:88:95:ee:50:bc:4f:75:d2:05:
a2:5b:d3:6f:f5
ASN1 OID: prime256v1
X509v3 extensions:
X509v3 Key Usage:
Digital Signature
X509v3 Subject Key Identifier:
AB:4D:91:0F:55:CA:E7:1A:21:5E:
F3:CA:FE:3A:CC:45:B5:EE:C1:54
X509v3 Extended Key Usage:
1.3.6.1.5.5.7.3.30
sbgp-autonomousSysNum: critical
Autonomous System Numbers:
64496
Routing Domain Identifiers:
inherit
Signature Algorithm: ecdsa-with-SHA256
30:44:02:20:07:b7:b4:6a:5f:a4:f1:cc:68:36:39:03:a4:83:
ec:7c:80:02:d2:f6:08:9d:46:b2:ec:2a:7b:e6:92:b3:6f:b1:
02:20:00:91:05:4a:a1:f5:b0:18:9d:27:24:e8:b4:22:fd:d1:
1c:f0:3d:b1:38:24:5d:64:29:35:28:8d:ee:0c:38:29
<span class="grey">Turner & Borchert Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
-----BEGIN CERTIFICATE-----
MIIBiDCCAS+gAwIBAgIEAk3WfDAKBggqhkjOPQQDAjAaMRgwFgYDVQQDDA9ST1VU
RVItMDAwMEZCRjAwHhcNMTcwMTAxMDUwMDAwWhcNMTgwNzAxMDUwMDAwWjAaMRgw
FgYDVQQDDA9ST1VURVItMDAwMEZCRjAwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNC
AARzkbq7kqDLO+EOWbGev/shTgSpHgy6GxOafTjZD3flWqBbjmlWeOD6FpBLVdnU
9cDfxYiV7lC8T3XSBaJb02/1o2MwYTALBgNVHQ8EBAMCB4AwHQYDVR0OBBYEFKtN
kQ9VyucaIV7zyv46zEW17sFUMBMGA1UdJQQMMAoGCCsGAQUFBwMeMB4GCCsGAQUF
BwEIAQH/BA8wDaAHMAUCAwD78KECBQAwCgYIKoZIzj0EAwIDRwAwRAIgB7e0al+k
8cxoNjkDpIPsfIAC0vYInUay7Cp75pKzb7ECIACRBUqh9bAYnSck6LQi/dEc8D2x
OCRdZCk1KI3uDDgp
-----END CERTIFICATE-----
Keys of AS(65536):
==================
ski: 47F23BF1AB2F8A9D26864EBBD8DF2711C74406EC
private key:
x = 6CB2E931B112F24554BCDCAAFD9553A9
519A9AF33C023B60846A21FC95583172
public key:
Ux = 28FC5FE9AFCF5F4CAB3F5F85CB212FC1
E9D0E0DBEAEE425BD2F0D3175AA0E989
Uy = EA9B603E38F35FB329DF495641F2BA04
0F1C3AC6138307F257CBA6B8B588F41F
Router Key Certificate example using OpenSSL 1.0.1e-fips 11 Feb 2013
--------------------------------------------------------------------
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 3752143940 (0xdfa52c44)
Signature Algorithm: ecdsa-with-SHA256
Issuer: CN=ROUTER-00010000
Validity
Not Before: Jan 1 05:00:00 2017 GMT
Not After : Jul 1 05:00:00 2018 GMT
Subject: CN=ROUTER-00010000
Subject Public Key Info:
Public Key Algorithm: id-ecPublicKey
Public-Key: (256 bit)
pub:
04:28:fc:5f:e9:af:cf:5f:4c:ab:3f:5f:85:cb:21:
2f:c1:e9:d0:e0:db:ea:ee:42:5b:d2:f0:d3:17:5a:
a0:e9:89:ea:9b:60:3e:38:f3:5f:b3:29:df:49:56:
41:f2:ba:04:0f:1c:3a:c6:13:83:07:f2:57:cb:a6:
b8:b5:88:f4:1f
ASN1 OID: prime256v1
<span class="grey">Turner & Borchert Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
X509v3 extensions:
X509v3 Key Usage:
Digital Signature
X509v3 Subject Key Identifier:
47:F2:3B:F1:AB:2F:8A:9D:26:86:
4E:BB:D8:DF:27:11:C7:44:06:EC
X509v3 Extended Key Usage:
1.3.6.1.5.5.7.3.30
sbgp-autonomousSysNum: critical
Autonomous System Numbers:
65536
Routing Domain Identifiers:
inherit
Signature Algorithm: ecdsa-with-SHA256
30:45:02:21:00:8c:d9:f8:12:96:88:82:74:03:a1:82:82:18:
c5:31:00:ee:35:38:e8:fa:ae:72:09:fe:98:67:01:78:69:77:
8c:02:20:5f:ee:3a:bf:10:66:be:28:d3:b3:16:a1:6b:db:66:
21:99:ed:a6:e4:ad:64:3c:ba:bf:44:fb:cb:b7:50:91:74
-----BEGIN CERTIFICATE-----
MIIBijCCATCgAwIBAgIFAN+lLEQwCgYIKoZIzj0EAwIwGjEYMBYGA1UEAwwPUk9V
VEVSLTAwMDEwMDAwMB4XDTE3MDEwMTA1MDAwMFoXDTE4MDcwMTA1MDAwMFowGjEY
MBYGA1UEAwwPUk9VVEVSLTAwMDEwMDAwMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcD
QgAEKPxf6a/PX0yrP1+FyyEvwenQ4Nvq7kJb0vDTF1qg6Ynqm2A+OPNfsynfSVZB
8roEDxw6xhODB/JXy6a4tYj0H6NjMGEwCwYDVR0PBAQDAgeAMB0GA1UdDgQWBBRH
8jvxqy+KnSaGTrvY3ycRx0QG7DATBgNVHSUEDDAKBggrBgEFBQcDHjAeBggrBgEF
BQcBCAEB/wQPMA2gBzAFAgMBAAChAgUAMAoGCCqGSM49BAMCA0gAMEUCIQCM2fgS
loiCdAOhgoIYxTEA7jU46Pqucgn+mGcBeGl3jAIgX+46vxBmvijTsxaha9tmIZnt
puStZDy6v0T7y7dQkXQ=
-----END CERTIFICATE-----
<span class="grey">Turner & Borchert Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. BGPsec IPv4</span>
BGPsec IPv4 UPDATE from AS(65536) to AS(65537):
===============================================
Binary Form of BGPsec UPDATE (TCP-DUMP):
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
01 03 02 00 00 00 EC 40 01 01 02 80 04 04 00 00
00 00 80 0E 0D 00 01 01 04 C6 33 64 64 00 18 C0
00 02 90 1E 00 CD 00 0E 01 00 00 01 00 00 01 00
00 00 FB F0 00 BF 01 47 F2 3B F1 AB 2F 8A 9D 26
86 4E BB D8 DF 27 11 C7 44 06 EC 00 48 30 46 02
21 00 EF D4 8B 2A AC B6 A8 FD 11 40 DD 9C D4 5E
81 D6 9D 2C 87 7B 56 AA F9 91 C3 4D 0E A8 4E AF
37 16 02 21 00 90 F2 C1 29 AB B2 F3 9B 6A 07 96
3B D5 55 A8 7A B2 B7 33 3B 7B 91 F1 66 8F D8 61
8C 83 FA C3 F1 AB 4D 91 0F 55 CA E7 1A 21 5E F3
CA FE 3A CC 45 B5 EE C1 54 00 48 30 46 02 21 00
EF D4 8B 2A AC B6 A8 FD 11 40 DD 9C D4 5E 81 D6
9D 2C 87 7B 56 AA F9 91 C3 4D 0E A8 4E AF 37 16
02 21 00 8E 21 F6 0E 44 C6 06 6C 8B 8A 95 A3 C0
9D 3A D4 37 95 85 A2 D7 28 EE AD 07 A1 7E D7 AA
05 5E CA
Signature from AS(64496) to AS(65536):
--------------------------------------
Digest: 21 33 E5 CA A0 26 BE 07 3D 9C 1B 4E FE B9 B9 77
9F 20 F8 F5 DE 29 FA 98 40 00 9F 60 47 D0 81 54
Signature: 30 46 02 21 00 EF D4 8B 2A AC B6 A8 FD 11 40 DD
9C D4 5E 81 D6 9D 2C 87 7B 56 AA F9 91 C3 4D 0E
A8 4E AF 37 16 02 21 00 8E 21 F6 0E 44 C6 06 6C
8B 8A 95 A3 C0 9D 3A D4 37 95 85 A2 D7 28 EE AD
07 A1 7E D7 AA 05 5E CA
Signature from AS(65536) to AS(65537):
--------------------------------------
Digest: 01 4F 24 DA E2 A5 21 90 B0 80 5C 60 5D B0 63 54
22 3E 93 BA 41 1D 3D 82 A3 EC 26 36 52 0C 5F 84
Signature: 30 46 02 21 00 EF D4 8B 2A AC B6 A8 FD 11 40 DD
9C D4 5E 81 D6 9D 2C 87 7B 56 AA F9 91 C3 4D 0E
A8 4E AF 37 16 02 21 00 90 F2 C1 29 AB B2 F3 9B
6A 07 96 3B D5 55 A8 7A B2 B7 33 3B 7B 91 F1 66
8F D8 61 8C 83 FA C3 F1
The human-readable output is produced using bgpsec-io, a BGPsec
traffic generator that uses a Wireshark-like printout.
<span class="grey">Turner & Borchert Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
Send UPDATE Message
+--marker: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+--length: 259
+--type: 2 (UPDATE)
+--withdrawn_routes_length: 0
+--total_path_attr_length: 236
+--ORIGIN: INCOMPLETE (4 bytes)
| +--Flags: 0x40 (Well-Known, Transitive, Complete)
| +--Type Code: ORIGIN (1)
| +--Length: 1 byte
| +--Origin: INCOMPLETE (1)
+--MULTI_EXIT_DISC (7 bytes)
| +--Flags: 0x80 (Optional, Non-transitive, Complete)
| +--Type Code: MULTI_EXIT_DISC (4)
| +--Length: 4 bytes
| +--data: 00 00 00 00
+--MP_REACH_NLRI (16 bytes)
| +--Flags: 0x80 (Optional, Non-transitive, Complete)
| +--Type Code: MP_REACH_NLRI (14)
| +--Length: 13 bytes
| +--Address family: IPv4 (1)
| +--Subsequent address family identifier: Unicast (1)
| +--Next hop network address: (4 bytes)
| | +--Next hop: 198.51.100.100
| +--Subnetwork points of attachment: 0
| +--Network layer reachability information: (4 bytes)
| +--192.0.2.0/24
| +--MP Reach NLRI prefix length: 24
| +--MP Reach NLRI IPv4 prefix: 192.0.2.0
+--BGPSEC Path Attribute (209 bytes)
+--Flags: 0x90 (Optional, Complete, Extended Length)
+--Type Code: BGPSEC Path Attribute (30)
+--Length: 205 bytes
+--Secure Path (14 bytes)
| +--Length: 14 bytes
| +--Secure Path Segment: (6 bytes)
| | +--pCount: 1
| | +--Flags: 0
| | +--AS number: 65536 (1.0)
| +--Secure Path Segment: (6 bytes)
| +--pCount: 1
| +--Flags: 0
| +--AS number: 64496 (0.64496)
+--Signature Block (191 bytes)
+--Length: 191 bytes
+--Algo ID: 1
<span class="grey">Turner & Borchert Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
+--Signature Segment: (94 bytes)
| +--SKI: 47F23BF1AB2F8A9D26864EBBD8DF2711C74406EC
| +--Length: 72 bytes
| +--Signature: 3046022100EFD48B 2AACB6A8FD1140DD
| 9CD45E81D69D2C87 7B56AAF991C34D0E
| A84EAF3716022100 90F2C129ABB2F39B
| 6A07963BD555A87A B2B7333B7B91F166
| 8FD8618C83FAC3F1
+--Signature Segment: (94 bytes)
+--SKI: AB4D910F55CAE71A215EF3CAFE3ACC45B5EEC154
+--Length: 72 bytes
+--Signature: 3046022100EFD48B 2AACB6A8FD1140DD
9CD45E81D69D2C87 7B56AAF991C34D0E
A84EAF3716022100 8E21F60E44C6066C
8B8A95A3C09D3AD4 379585A2D728EEAD
07A17ED7AA055ECA
<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>. BGPsec IPv6</span>
BGPsec IPv6 UPDATE from AS(65536) to AS(65537):
===============================================
Binary Form of BGP/BGPsec UPDATE (TCP-DUMP):
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
01 10 02 00 00 00 F9 40 01 01 02 80 04 04 00 00
00 00 80 0E 1A 00 02 01 10 FD 00 00 00 00 00 00
00 00 00 00 00 C6 33 64 64 00 20 20 01 0D B8 90
1E 00 CD 00 0E 01 00 00 01 00 00 01 00 00 00 FB
F0 00 BF 01 47 F2 3B F1 AB 2F 8A 9D 26 86 4E BB
D8 DF 27 11 C7 44 06 EC 00 48 30 46 02 21 00 EF
D4 8B 2A AC B6 A8 FD 11 40 DD 9C D4 5E 81 D6 9D
2C 87 7B 56 AA F9 91 C3 4D 0E A8 4E AF 37 16 02
21 00 D1 B9 4F 62 51 04 6D 21 36 A1 05 B0 F4 72
7C C5 BC D6 74 D9 7D 28 E6 1B 8F 43 BD DE 91 C3
06 26 AB 4D 91 0F 55 CA E7 1A 21 5E F3 CA FE 3A
CC 45 B5 EE C1 54 00 48 30 46 02 21 00 EF D4 8B
2A AC B6 A8 FD 11 40 DD 9C D4 5E 81 D6 9D 2C 87
7B 56 AA F9 91 C3 4D 0E A8 4E AF 37 16 02 21 00
E2 A0 2C 68 FE 53 CB 96 93 4C 78 1F 5A 14 A2 97
19 79 20 0C 91 56 ED F8 55 05 8E 80 53 F4 AC D3
<span class="grey">Turner & Borchert Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
Signature from AS(64496) to AS(65536):
--------------------------------------
Digest: 8A 0C D3 E9 8E 55 10 45 82 1D 80 46 01 D6 55 FC
52 11 89 DF 4D B0 28 7D 84 AC FC 77 55 6D 06 C7
Signature: 30 46 02 21 00 EF D4 8B 2A AC B6 A8 FD 11 40 DD
9C D4 5E 81 D6 9D 2C 87 7B 56 AA F9 91 C3 4D 0E
A8 4E AF 37 16 02 21 00 E2 A0 2C 68 FE 53 CB 96
93 4C 78 1F 5A 14 A2 97 19 79 20 0C 91 56 ED F8
55 05 8E 80 53 F4 AC D3
Signature from AS(65536) to AS(65537):
--------------------------------------
Digest: 44 49 EC 70 8D EC 5C 85 00 C2 17 8C 72 FE 4C 79
FF A9 3C 95 31 61 01 2D EE 7E EE 05 46 AF 5F D0
Signature: 30 46 02 21 00 EF D4 8B 2A AC B6 A8 FD 11 40 DD
9C D4 5E 81 D6 9D 2C 87 7B 56 AA F9 91 C3 4D 0E
A8 4E AF 37 16 02 21 00 D1 B9 4F 62 51 04 6D 21
36 A1 05 B0 F4 72 7C C5 BC D6 74 D9 7D 28 E6 1B
8F 43 BD DE 91 C3 06 26
The human-readable output is produced using bgpsec-io, a BGPsec
traffic generator that uses a Wireshark-like printout.
Send UPDATE Message
+--marker: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+--length: 272
+--type: 2 (UPDATE)
+--withdrawn_routes_length: 0
+--total_path_attr_length: 249
+--ORIGIN: INCOMPLETE (4 bytes)
| +--Flags: 0x40 (Well-Known, Transitive, Complete)
| +--Type Code: ORIGIN (1)
| +--Length: 1 byte
| +--Origin: INCOMPLETE (1)
+--MULTI_EXIT_DISC (7 bytes)
| +--Flags: 0x80 (Optional, Non-transitive, Complete)
| +--Type Code: MULTI_EXIT_DISC (4)
| +--Length: 4 bytes
| +--data: 00 00 00 00
+--MP_REACH_NLRI (29 bytes)
| +--Flags: 0x80 (Optional, Non-transitive, Complete)
| +--Type Code: MP_REACH_NLRI (14)
| +--Length: 26 bytes
| +--Address family: IPv6 (2)
| +--Subsequent address family identifier: Unicast (1)
| +--Next hop network address: (16 bytes)
| | +--Next hop: fd00:0000:0000:0000:0000:0000:c633:6464
| +--Subnetwork points of attachment: 0
<span class="grey">Turner & Borchert Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
| +--Network layer reachability information: (5 bytes)
| +--2001:db8::/32
| +--MP Reach NLRI prefix length: 32
| +--MP Reach NLRI IPv6 prefix: 2001:db8::
+--BGPSEC Path Attribute (209 bytes)
+--Flags: 0x90 (Optional, Complete, Extended Length)
+--Type Code: BGPSEC Path Attribute (30)
+--Length: 205 bytes
+--Secure Path (14 bytes)
| +--Length: 14 bytes
| +--Secure Path Segment: (6 bytes)
| | +--pCount: 1
| | +--Flags: 0
| | +--AS number: 65536 (1.0)
| +--Secure Path Segment: (6 bytes)
| +--pCount: 1
| +--Flags: 0
| +--AS number: 64496 (0.64496)
+--Signature Block (191 bytes)
+--Length: 191 bytes
+--Algo ID: 1
+--Signature Segment: (94 bytes)
| +--SKI: 47F23BF1AB2F8A9D26864EBBD8DF2711C74406EC
| +--Length: 72 bytes
| +--Signature: 3046022100EFD48B 2AACB6A8FD1140DD
| 9CD45E81D69D2C87 7B56AAF991C34D0E
| A84EAF3716022100 D1B94F6251046D21
| 36A105B0F4727CC5 BCD674D97D28E61B
| 8F43BDDE91C30626
+--Signature Segment: (94 bytes)
+--SKI: AB4D910F55CAE71A215EF3CAFE3ACC45B5EEC154
+--Length: 72 bytes
+--Signature: 3046022100EFD48B 2AACB6A8FD1140DD
9CD45E81D69D2C87 7B56AAF991C34D0E
A84EAF3716022100 E2A02C68FE53CB96
934C781F5A14A297 1979200C9156EDF8
55058E8053F4ACD3
<span class="grey">Turner & Borchert Standards Track [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc8608">RFC 8608</a> BGPsec Algs, Key & Signature Formats June 2019</span>
Acknowledgements
The authors wish to thank Geoff Huston and George Michaelson for
producing [<a href="./rfc7935" title=""The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure"">RFC7935</a>], which this document is entirely based on. The
authors would also like to thank Roque Gagliano, David Mandelberg,
Tom Petch, Sam Weiler, and Stephen Kent for their reviews and
comments. Mehmet Adalier, Kotikalapudi Sriram, and Doug Montgomery
were instrumental in developing the test vectors found in <a href="#appendix-A">Appendix A</a>.
Additionally, we want to thank Geoff Huston, author of [<a href="./rfc5398" title=""Autonomous System (AS) Number Reservation for Documentation Use"">RFC5398</a>] from
which we borrowed wording for <a href="#section-2.1">Section 2.1</a> of this document.
Authors' Addresses
Sean Turner
sn3rd
Email: sean@sn3rd.com
Oliver Borchert
NIST
100 Bureau Drive
Gaithersburg, MD 20899
United States of America
Email: oliver.borchert@nist.gov
Turner & Borchert Standards Track [Page 21]
</pre>
|
