Elliptic Curve Cryptography Subject Public Key Information

Abstract

Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

BGPsec Algorithms, Key Formats, and Signature Formats

“…The algorithms used to compute signatures on CA certificates, BGPsec Router Certificates, and Certificate Revocation Lists (CRLs) are as specified in o algorithm (an AlgorithmIdentifier type): The id-ecPublicKey OID MUST be used in the algorithm field, as specified in Section 2.1.1 of [RFC5480]. The value for the associated parameters MUST be secp256r1, as specified in Section 2.1.1.1 of [RFC5480].…”

“…The value for the associated parameters MUST be secp256r1, as specified in Section 2.1.1.1 of [RFC5480].…”

“…o subjectPublicKey: ECPoint MUST be used to encode the certificate's subjectPublicKey field, as specified in Section 2.2 of [RFC5480].…”

Use of Static-Static Elliptic Curve Diffie-Hellman Key Agreement in Cryptographic Message Syntax

“…o that both certificates (the recipient's certificate and its own) contain public-key values with the same curve parameters, and o that both of these public-key values are marked as appropriate for ECDH (that is, marked with algorithm identifiers id-ecPublicKey or id-ecDH [RFC5480]). …”

“…In order to encourage interoperability, implementations SHOULD use the elliptic curve domain parameters specified by [RFC5480].…”