Documents Search

ZAC-3 Issues List for ZAC-3r7

1) Marked g25138r6 in the integrated proposals list as New Functionality
2) Integrated g25168r2 - Fixes a couple typos int the interactions with SECURITY ERASE UNIT subclause.
3) Integrated g26116r0 - Adds the ability to report write pointers for read only zones.
4) Fixed a couple typos in 4.8.6 (commas at the end of an A/B list instead of semicolon).
5) Integrated g26112r2 - Adds descriptive material to remove element and \truncate.
6) Integrated g25255r4 - Zone Domains Interactions with Storage Element Depopulation.

April 2026 meeting minutes - F2F held in Dallas, TX

June 2026 T13 Plenary #179 Announcement

End ZAC-3's silence regarding what happens when a ZONE ACTIVATE EXT command processes an OFFLINE zone.

Since nobody can decide whether the Command Duration Limits for writes apply to COALESCING COPY, or is it the limits for reads that apply, eliminate the loose thread before it becomes the means by which the internal-copy house of cards is torn asunder.

Change some wording to clarify changes to zones after a REMOVE ELEMENT AND TRUNCATE command

Summary of project information obtained from INCITS and related TC decisions

Informal Liaison Report of public information

Project proposal for ZAC-4, follow-on to ZAC-3.

Add a FLUSH CACHE EXT SUPPORTED bit to the SATA NCQ Send and Receive log (Log Address 13h)

End ZAC-3's silence regarding what happens when a ZONE ACTIVATE EXT command processes an OFFLINE zone.

SNIA Liaison Report

Bring sanity to the number of passes supported on a Sanitize Overwrite.

Agenda for T13 plenary #178 - April 2026 - Dallas TX

IEEE Security in Storage Working Group (SISWG) Liaison Report to T13

Provide the device with a way to report the most recent known write pointer from the time when the zone condition was changed to READ ONLY.

Agenda for T13 plenary #178 - April 2026 - Dallas TX

Since nobody can decide whether the Command Duration Limits for writes apply to COALESCING COPY, or is it the limits for reads that apply, eliminate the loose thread before it becomes the means by which the internal-copy house of cards is torn asunder.

Change some wording to clarify changes to zones after a REMOVE ELEMENT AND TRUNCATE command

Too much confusion is being generated by the mere mention of the DURABLE/ORDERED WRITE NOTIFICATION subcommand of the NCQ NON-DATA. Since the subcommand definition hasn't been changed in several ACS-x versions and no implementations are clamoring for improvements, the better part of valor here is to obsolete the source of so much disruption.

The aim of this proposal is to clarify the functionality provided by DURABLE/ORDERED WRITE NOTIFICATION, particularly its cache flush capability.

Change some wording to clarify changes to zones after a REMOVE ELEMENT AND TRUNCATE command

Agenda for T13 plenary #178 - April 2026 - Dallas TX

Project proposal for ZAC-4, follow-on to ZAC-3. Updates from February plenary are included.