SSC-3: Filemarks/Setmarks and Encryption

Banther, Michael michael.banther at
Mon Nov 20 05:28:22 PST 2006

Formatted message: <A HREF="r0611200_f.htm">HTML-formatted message</A>
Attachment #1: <A HREF="r0611200_banther_michael.vcf">banther_michael.vcf</A>

Hi Kevin,
I agree that better clarification is a good thing.  I'm not happy with
the term 'encryption neutral'.	Is it defined anywhere?  Exactly what
does it mean?  The second sentence that you propose for is more
to my liking as it says how a device server responds when it encounters
a filemark or setmark.
Michael Banther
Hewlett-Packard Ltd.
+44 117 312 9503
From: owner-t10 at [mailto:owner-t10 at] On Behalf Of Kevin D
Sent: 13 November 2006 23:27
To: t10 at
Subject: SSC-3: Filemarks/Setmarks and Encryption
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
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. 
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 

More information about the T10 mailing list