This documentation has moved

XML API documentation can now be found at developer.openprovider.com. This page will remain available until September 2026, but will no longer be updated.

The XML API itself is not changing. Your existing integration continues to work.

API Format DNSSEC Keys

From Openprovider API documentation

(Difference between revisions)
Jump to: navigation, search
Line 26: Line 26:
*''10'' (RSA/SHA-512)
*''10'' (RSA/SHA-512)
*''12'' (GOST R 34.10-2001)
*''12'' (GOST R 34.10-2001)
 +
|-
 +
|colspan="2" style="background-color:#EEEEEE;"|'''protocol''' (required)
 +
|-
 +
|
 +
:'''Data'''
 +
|The protocol that is used for this key. Currently only one choice, but in the close future this will be expanded.
 +
*''3'' (DNSSEC)
|-
|-
|colspan="2" style="background-color:#EEEEEE;"|'''pubKey''' (required)
|colspan="2" style="background-color:#EEEEEE;"|'''pubKey''' (required)

Revision as of 09:43, 26 October 2015

Format specification > dnssecKeys

Collection of data fields that contains the following members:

Field dnssecKeys
flags (required)
Data
Type of key; the following values (the numbers only) are supported by Openprovider, but the registry might support a limited list
  • 256 (ZSK)
  • 257 (KSK)
alg (required)
Data
Algorithm; the following values (the numbers only) are supported by Openprovider, but the registry might support a limited list
  • 3 (DSA/SHA1)
  • 5 (RSA/SHA1)
  • 6 (DSA-NSEC3-SHA1)
  • 7 (RSASHA1-NSEC3-SHA1)
  • 8 (RSA/SHA-256)
  • 10 (RSA/SHA-512)
  • 12 (GOST R 34.10-2001)
protocol (required)
Data
The protocol that is used for this key. Currently only one choice, but in the close future this will be expanded.
  • 3 (DNSSEC)
pubKey (required)
Data
Public key
Views
Personal tools