ods-timing(5) | OpenDNSSEC timinig | ods-timing(5) |
ods-timing - OpenDNSSEC timing specification
/etc/opendnssec/conf.xml
/etc/opendnssec/kasp.xml
/etc/opendnssec/zonelist.xml
The configuration files of OpenDNSSEC need to have timing descriptions, notably for periods. These descriptions follow ISO 8601 with exceptions for the duration of a month and a year, as these periods would be allowed to vary if ISO 8601 were strictly adhered to.
Durations are represented by the format P[n]Y[n]M[n]DT[n]H[n]M[n]S. In these representations, the [n] is replaced by the value for each of the date and time elements that follow the [n]. Leading zeros are not required. The capital letters P, Y, M, W, D, T, H, M and S are designators for each of the date and time elements and are not replaced
For example, P3Y6M4DT12H30M5S represents a duration of "three years, six months, four days, twelve hours, thirty minutes, and five seconds". Date and time elements including their designator may be omitted if their value is zero, and lower order elements may also be omitted for reduced precision. For example, P23DT23H and P4Y are both acceptable duration representations.
A year or month vary in duration depending on the current date. For OpenDNSSEC, we assume fixed values.
This exception may or may not change in future releases of OpenDNSSEC. The reason for making this exception is to avoid complicating this software in a way that may not meet any practical need.
ods-control(8), ods-enforcerd(8), ods-enforcer(8), ods-signerd(8), ods-signer(8), ods-kasp(5), ods-kaspcheck(1), ods-timing(5), ods-hsmspeed(1), ods-hsmutil(1), opendnssec(7), ISO 8601, http://www.opendnssec.org/
OpenDNSSEC was made by the OpenDNSSEC project, to be found on http://www.opendnssec.org/
February 2010 | OpenDNSSEC |