| Internet-Draft | VLDB_CAPABILITY_LOCKTIMESTAMP | August 2023 |
| Barbosa | Expires 25 February 2024 | [Page] |
This document proposes the repurposing of the currently unused spares2 field within the nvldbentry and uvldbentry structures. The primary objective is to utilize this field for storing the timestamp representing the date and time when a given volume location entry was locked. To make this possible, this memo requests the allocation of a new capability bit, VLDB_CAPABILITY_LOCKTIMESTAMP, to be advertised by the Volume Location Server. When advertised, this bit indicates that the server has the capacity to provide the timestamp in question.¶
Comments regarding this draft are solicited. Please include the AFS-3 protocol standardization mailing list ([email protected]) as a recipient of any comments.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 25 February 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.¶
The Volume Location Server is a critical component in AFS, responsible for providing a lookup service for volumes, identifying the server or set of servers on which volume instances can be found. Currently, there is a lack of standardized mechanisms to convey whether it can provide the date and time when a volume location entry was locked. This memo seeks to address this limitation by repurposing a currently unused volume location entry field and requesting the allocation of a new capability bit.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
Knowing the date and time when a volume location entry was locked can be valuable for various purposes, such as auditing and troubleshooting. It allows administrators and users to track and analyze the history of volume locks, enabling them to understand the sequence of events and take appropriate actions when necessary.¶
If the VLDB_CAPABILITY_LOCKTIMESTAMP bit is advertised, the Volume Location Server should be able to
retrieve and return the lock timestamp for a given volume location entry upon request from clients. The lock
timestamp should represent the date and time when a given entry was locked.
To make this possible, the spares2 field within the nvldbentry and uvldbentry structures has been designated
for the purpose of returning the mentioned timestamp.¶
This memo includes no request to IANA.¶
This memo requests the allocation of a new capability bit to be advertised by the Volume Location Server.¶
This memo does not introduce any new security considerations beyond those already inherent in the underlying protocols it relies on.¶
The author would like to thank Thomas Keiser, as the draft authored by him, titled "AFS-3 Protocol Capabilities Query Mechanism" [I-D.keiser-afs3-capabilities-00], served as a reference throughout the development of this draft.¶