--- oid: "1.3.6.1.4.1.1206.4.2.6.3.7.1" short-description: "maxDaylightSavingEntries OBJECT-TYPE" last-modified: "2025-07-24" parent-oid: "1.3.6.1.4.1.1206.4.2.6.3.7" --- ## OID: `1.3.6.1.4.1.1206.4.2.6.3.7.1` ```asn1 {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 1206 transportation(4) devices(2) global(6) globalTimeManagement(3) daylightSavingNode(7) maxDaylightSavingEntries(1)} ``` ### Description ```asn1 maxDaylightSavingEntries OBJECT-TYPE SYNTAX INTEGER(1..100) ACCESS read-only STATUS mandatory DESCRIPTION " The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2\.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. 1.3.6.1.4.1.1206.4.2.6.3.7.1" ``` **Classification:** MIB object for network management ### Child OIDs No child OID ### Terms of Use [Terms of use](https://oid-base.com/disclaimer.htm.md) **Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.