Introduce VLDB_CAPABILITY_LOCKTIMESTAMP
draft-barbosa-afs3-vlcapabilities-lock-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Marcio Brito Barbosa | ||
| Last updated | 2023-05-25 | ||
| Replaced by | draft-barbosa-afs3-vldb-locktimestamp | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-barbosa-afs3-vldb-locktimestamp | |
| 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 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 date and time when a given volume location entry was locked. Internet Draft Comments Comments regarding this draft are solicited. Please include the AFS-3 protocol standardization mailing list (afs3-standardization@openafs.org) as a recipient of any comments.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)