1ods-timing(5) OpenDNSSEC timinig ods-timing(5)
2
3
4
6 ods-timing - OpenDNSSEC timing specification
7
9 /etc/opendnssec/conf.xml
10 /etc/opendnssec/kasp.xml
11 /etc/opendnssec/zonelist.xml
12
14 The configuration files of OpenDNSSEC need to have timing descriptions,
15 notably for periods. These descriptions follow ISO 8601 with excep‐
16 tions for the duration of a month and a year, as these periods would be
17 allowed to vary if ISO 8601 were strictly adhered to.
18
19 Durations are represented by the format P[n]Y[n]M[n]DT[n]H[n]M[n]S. In
20 these representations, the [n] is replaced by the value for each of the
21 date and time elements that follow the [n]. Leading zeros are not
22 required. The capital letters P, Y, M, W, D, T, H, M and S are designa‐
23 tors for each of the date and time elements and are not replaced
24
25 P is the duration designator (historically called "period") placed
26 at the start of the duration representation.
27
28 Y is the year designator that follows the value for the number of
29 years.
30
31 M is the month designator that follows the value for the number of
32 months.
33
34 W is the week designator that follows the value for the number of
35 weeks.
36
37 D is the day designator that follows the value for the number of
38 days.
39
40 T is the time designator that precedes the time components of the
41 representation.
42
43 H is the hour designator that follows the value for the number of
44 hours.
45
46 M is the minute designator that follows the value for the number
47 of minutes.
48
49 S is the second designator that follows the value for the number
50 of seconds.
51
52 For example, P3Y6M4DT12H30M5S represents a duration of "three years,
53 six months, four days, twelve hours, thirty minutes, and five seconds".
54 Date and time elements including their designator may be omitted if
55 their value is zero, and lower order elements may also be omitted for
56 reduced precision. For example, P23DT23H and P4Y are both acceptable
57 duration representations.
58
60 A year or month vary in duration depending on the current date. For
61 OpenDNSSEC, we assume fixed values.
62
63 One month
64 is assumed to be 31 days.
65
66 One year
67 is assumed to be 365 days.
68
69 This exception may or may not change in future releases of OpenDNSSEC.
70 The reason for making this exception is to avoid complicating this
71 software in a way that may not meet any practical need.
72
74 ods-control(8), ods-enforcerd(8), ods-enforcer(8), ods-signerd(8),
75 ods-signer(8), ods-kasp(5), ods-kaspcheck(1), ods-timing(5), ods-hsm‐
76 speed(1), ods-hsmutil(1), opendnssec(7), ISO 8601,
77 http://www.opendnssec.org/
78
80 OpenDNSSEC was made by the OpenDNSSEC project, to be found on
81 http://www.opendnssec.org/
82
83
84
85OpenDNSSEC February 2010 ods-timing(5)