Repurpose spares2 Field for Volume Lock Timestamp in nvldbentry and uvldbentry
draft-barbosa-afs3-vldb-locktimestamp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marcio Brito Barbosa | ||
| Last updated | 2024-02-25 (Latest revision 2023-08-24) | ||
| Replaces | draft-barbosa-afs3-vlcapabilities-lock | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)