SSC-3: Filemarks/Setmarks and Encryption

Rose, Roger Rrose at
Tue Nov 14 10:45:05 PST 2006

* From the T10 Reflector (t10 at, posted by:
* "Rose, Roger" <Rrose at>
As long as this is being addressed for filemarks and setmarks,
End-of-Data should be included.  Space to EOD, then back a few filemarks
is a common operation.
-roger rose
 Exabyte Corp
> -----Original Message-----
> From: owner-t10 at [mailto:owner-t10 at] On Behalf 
> Of Kevin D Butt
> Sent: Monday, November 13, 2006 4:27 PM
> To: t10 at
> Subject: SSC-3: Filemarks/Setmarks and Encryption
> Tapeheads, 
> I believe that we need to better clarify that Filemarks are 
> "encryption neutral".  SSC-3r3b does state in 4.20.2 
> "Filemarks shall not be encrypted" but that is the only 
> statement about filemarks and encryption.  Additionally there 
> is no statement about setmarks and encryption. 
> I think we should add the following: 
> 1) In 4.20.2 where it says "Filemarks shall not be encrypted" 
> should be changed to "Filemarks and Setmarks shall not be 
> encrypted and are considered encryption neutral". 
> 2) In section Reading encrypted data on the medium, 
> the following paragraph: 
> Filemarks and Setmarks are considered encryption neutral.  
> Reading into a Filemark or setmark shall not cause a change 
> of encryption state and shall not cause an encryption 
> additional sense code to be returned. 
> Comments? 
> Thanks, 
> Kevin D. Butt
> SCSI & Fibre Channel Architect, Tape Firmware
> MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
> Tel: 520-799-2869 / 520-799-5280
> Fax: 520-799-2723 (T/L:321)
> Email address: kdbutt at
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at

More information about the T10 mailing list