[cifs-protocol] MS-DNSP errata on timestamp descriptions - TrackingID#2106010040000420
Jeff McCashland
jeffm at microsoft.com
Tue Jul 27 00:02:34 UTC 2021
[-support alias]
Hi Douglas,
We have updated [MS-DNSP] for the next release of the document:
3.1.1.1.1 DNS Server Integer Properties
DsTombstoneInterval:
Every day at 2:00 AM local time the DNS server MUST conduct a search of all zones stored in the directory server for nodes which have the dnsTombstoned attribute set to TRUE and an EntombedTime (section 2.2.2.2.4.23) value greater than DsTombstoneInterval seconds in the past (convert seconds to 100-nanosecond intervals for comparison). Any such nodes MUST be permanently deleted from the directory server <127>
3.1.4.5 R_DnssrvUpdateRecord (Opnum 4)
When processing this call, the server MUST do the following:
§ If pszZoneName points to a primary zone, attempt to perform addition/deletion/update of the record. If the operation is successful, increment the zone serial number using serial number arithmetic [RFC1982]. If the zone is directory server-integrated and the update causes new or modified records to be committed to the directory, the new zone serial number MUST also be written to the Serial field of the dnsRecord attribute (section 2.3.2.2). If the last record at the node is being deleted and the zone is stored in the directory server or is directory server-integrated, the DNS server MUST set the node's dnsTombstoned attribute to TRUE and the node's dnsRecord attribute to contain a DNS_RPC_RECORD_TS record (section 2.2.2.2.4.23) with an EntombedTime value equal to the current time expressed as the number of 100-nanosecond intervals since 12:00 A.M. January 1, 1601 Coordinated Universal Time (UTC).
Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)
Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300
We value your feedback. My manager is Natesha Morrison (namorri), +1 (704) 430-4292
-----Original Message-----
From: Jeff McCashland
Sent: Tuesday, June 1, 2021 3:54 PM
To: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>; cifs-protocol at lists.samba.org
Cc: jeffm at microsoftsupport.com
Subject: RE: MS-DNSP errata on timestamp descriptions - TrackingID#2106010040000420
Hi Douglas,
I have been able to confirm that EntombedTime is actually (and always) in 100-nanosecond increments. Also, "Time Zone Secured" is tracked in full seconds as documented.
The comparison in section 3.1.1.1.1 should perhaps read: "...and an EntombedTime (section 2.2.2.2.4.23) value >>>indicating a time<<< greater than DsTombstoneInterval seconds in the past."
I will file a request to update the document and follow up on it. Let me know if you have any further questions on EntombedTime.
Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada) Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300 We value your feedback. My manager is Natesha Morrison (namorri), +1 (704) 430-4292
-----Original Message-----
From: Jeff McCashland
Sent: Tuesday, June 1, 2021 11:03 AM
To: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>; cifs-protocol at lists.samba.org
Cc: jeffm at microsoftsupport.com
Subject: MS-DNSP errata on timestamp descriptions - TrackingID#2106010040000420
[Sree to BCC, support alias on CC, SR ID on Subject]
Hi Douglas,
I will research your list, and follow up.
Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada) Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300 We value your feedback. My manager is Natesha Morrison (namorri), +1 (704) 430-4292
-----Original Message-----
From: Sreekanth Nadendla <srenaden at microsoft.com>
Sent: Monday, May 31, 2021 8:44 PM
To: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>; cifs-protocol at lists.samba.org
Subject: 2106010040000420 MS-DNSP errata
Hello Douglas, thank you for you question regarding the MS-DNSP specification. We have created incident 2106010040000420 to track the investigation. One of the open specifications team member will contact you shortly.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-----Original Message-----
From: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>
Sent: Monday, May 31, 2021 9:47 PM
To: cifs-protocol at lists.samba.org; Interoperability Documentation Help <dochelp at microsoft.com>
Subject: [EXTERNAL] MS-DNSP errata
hi Dochelp,
In a number of places [MS-DNSP] mentions timestamps in to form of "the number of seconds since 12:00 A.M. January 1, 1601". At least some of these should really speak of the "number of 100-nanosecond intervals" that we are used to dealing with.
In 3.1.4.5, in the paragraph starting "If pszZoneName points to a primary zone", EntombedTime is described as a number of seconds, contrary to descriptions elsewhere (2.2.2.2.4.23).
Same thing in 3.1.1.1.1, under "DsTombstoneInterval", EntombedTime is compared with a number of seconds.
Also in sections 3.1.1 and 3.1.1.2.1 "Time Zone Secured" is described as the number of seconds since 1601. I don't know if that is correct or not.
This is not really a question, unless EntombedTime is really sometimes in seconds and sometimes in 10-millionths of seconds, in which case I will have lots of questions.
Douglas
More information about the cifs-protocol
mailing list