ods-timing(5) OpenDNSSEC timinig ods-timing(5)NAMEods-timing - OpenDNSSEC timing specification
SYNOPSIS
/usr/local/etc/opendnssec/conf.xml
/usr/local/etc/opendnssec/kasp.xml
/usr/local/etc/opendnssec/zonelist.xml
DESCRIPTION
The configuration files of OpenDNSSEC need to have timing descriptions,
notably for periods. These descriptions follow ISO 8601 with excep‐
tions 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 designa‐
tors for each of the date and time elements and are not replaced
P is the duration designator (historically called "period") placed
at the start of the duration representation.
Y is the year designator that follows the value for the number of
years.
M is the month designator that follows the value for the number of
months.
W is the week designator that follows the value for the number of
weeks.
D is the day designator that follows the value for the number of
days.
T is the time designator that precedes the time components of the
representation.
H is the hour designator that follows the value for the number of
hours.
M is the minute designator that follows the value for the number
of minutes.
S is the second designator that follows the value for the number
of seconds.
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.
EXCEPTION
A year or month vary in duration depending on the current date. For
OpenDNSSEC, we assume fixed values
One month
is assumed to be 31 days.
One year
is assumed to be 365 days.
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.
SEE ALSOods-control(8), ods-enforcerd(8), ods-hsmspeed(1), ods-hsmutil(1),
ods-kaspcheck(1), ods-ksmutil(1), ods-signer(8), ods-signerd(8),
opendnssec(7), ISO 8601, http://www.opendnssec.org/
AUTHORS
OpenDNSSEC was made by the OpenDNSSEC project, to be found on
http://www.opendnssec.org/
OpenDNSSEC February 2010 ods-timing(5)
