Subject: RE: SSC-3: Filemarks/Setmarks and Encryption Date: Mon, 20 Nov 2006 13:28:22 -0000 From: "Banther, Michael" <michael.banther@hp.com> To: "Kevin D Butt" <kdbutt@us.ibm.com> Cc: <t10@t10.org> X-Message-Number: 7392 Formatted message: HTML-formatted message Attachment #1: banther_michael.vcf 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 4.2.20.3 is more to my liking as it says how a device server responds when it encounters a filemark or setmark. Regards, Michael Banther Hewlett-Packard Ltd. +44 117 312 9503 ________________________________ From: owner-t10@t10.org [mailto:owner-t10@t10.org] On Behalf Of Kevin D Butt Sent: 13 November 2006 23:27 To: t10@t10.org 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 4.2.20.3 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@us.ibm.com http://www-03.ibm.com/servers/storage/