Why don't we continue to put comments on the e-mail thread and then at the
end of the 2 weeks, post the collection of threads on the wiki with some
conceptual organization. The wiki often seems to be a barrier to free
conversation......but great for capturing overall work.
Karen
On 2/13/12 1:09 PM, "Cory Snavely" <[log in to unmask]> wrote:
>I mention this only because in the past, the group has had useful
>conversations that were not captured in writing, but in retrospect has
>wished that they were. My suggestion was conditional - "if there is a
>desire to capture and do something with it later".
>
>I'd defer to the folks that initiated the discussion on the potential
>value of capturing it in a form other than an email thread.
>
>On 02/13/2012 12:57 PM, John Spencer wrote:
>> I'll be happy to - was that the decision?
>>
>> If so, apologies for filling up everyone's inbox and I'll move my
>>responses over there.
>>
>> John
>>
>> On Feb 13, 2012, at 11:53 AM, Cory Snavely wrote:
>>
>>> Might folks want to consider putting their responses in the wiki, if
>>>there is a desire to capture and do something with it later?
>>>
>>> On 02/13/2012 12:46 PM, John Spencer wrote:
>>>> Andrea,
>>>>
>>>> I'll have a go at it - not going to get too far "in the weeds", but
>>>>maybe this will be of some help. Please see my inserts below in your
>>>>message.
>>>>
>>>> John
>>>>
>>>> John Spencer
>>>> [log in to unmask]
>>>> www.bmschace.com
>>>> office 615.385.1251/ fax 615.385.0153
>>>> mobile 615.714.1199
>>>>
>>>> On Feb 13, 2012, at 11:17 AM, Goethals, Andrea wrote:
>>>>
>>>>> I hope you all don't mind my starting this series off. I think this
>>>>>would work best if we pass the virtual baton around to a different
>>>>>person after each topic. We can queue up a list of topics on the wiki
>>>>>so people know what's coming next.
>>>>>
>>>>> The first topic is encryption in preservation storage. I am thinking
>>>>>about hardware or software or file encryption primarily imposed by
>>>>>the repository (but whether or not you accept content encrypted by
>>>>>others is also interesting). I am thinking less about encrypting for
>>>>>transport (e.g. https). Say what you want about it but I'll pose some
>>>>>questions to get you thinking about it.
>>>>>
>>>>>
>>>>>
>>>>> * Do you have any opinions on it? What are your reasons for
>>>>>your opinions (gut feelings are OK)?
>>>> The majority of the preservation data we deliver to our clients is
>>>>stored on LTO data tapes - without encryption. We do use WORM
>>>>capability if the client is OK with it. Our reasons are mainly based
>>>>on the the assumption that we do not have any control over who can
>>>>access the tape, now or in the future, and staffing changes might
>>>>stifle the client's ability to recover the preservation files ("now
>>>>where did the last person put the list of encryption keys?")
>>>>>
>>>>> * What kinds of problems do you think it might create in the
>>>>>future?
>>>> See above. We're most concerned that staffing issues combined with
>>>>object-based vault management infrastructures in place could lead to
>>>>problems. Certainly not saying that is the best rationale, but it is
>>>>based on current reality.
>>>>>
>>>>> * Do you have any current requirements to do this (laws,
>>>>>policies)? What are the conditions under which you need to encrypt?
>>>>>Do you know of any upcoming requirements for you to do this?
>>>> no
>>>>>
>>>>> * If you do it what technique(s)/strategies do you use? Do
>>>>>you isolate encrypted content from non-encrypted content?
>>>> no answer
>>>>>
>>>>> * Do you know of any relevant studies/papers, etc. about
>>>>>this topic?
>>>> no answer
>>>>>
>>>>> Someone proposed that we keep each topic discussion to around 2
>>>>>weeks so let's see if we've said what we want to by March 2. We can
>>>>>always extend this one since there was no advance notice of the topic.
>>>>>
>>>>> Thanks,
>>>>> Andrea
>>>>>
>>>>> Andrea Goethals
>>>>> Digital Preservation and Repository Services Manager
>>>>> Harvard Library Office for Information Systems
>>>>> [log in to unmask]
>>>>> (617) 495-3724
>>>>>
>>>>>
>>>>> ############################
>>>>>
>>>>> To unsubscribe from the NDSA-INFRASTRUCTURE list:
>>>>> write to:
>>>>>mailto:[log in to unmask]
>>>>>V
>>>>> or click the following link:
>>>>>
>>>>>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA
>>>>>-INFRASTRUCTURE&A=1
>>>>
>>>>
>>>> ############################
>>>>
>>>> To unsubscribe from the NDSA-INFRASTRUCTURE list:
>>>> write to:
>>>>mailto:[log in to unmask]
>>>> or click the following link:
>>>>
>>>>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-
>>>>INFRASTRUCTURE&A=1
>>>
>>> ############################
>>>
>>> To unsubscribe from the NDSA-INFRASTRUCTURE list:
>>> write to:
>>>mailto:[log in to unmask]
>>> or click the following link:
>>>
>>>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-I
>>>NFRASTRUCTURE&A=1
>>
>> ############################
>>
>> To unsubscribe from the NDSA-INFRASTRUCTURE list:
>> write to:
>>mailto:[log in to unmask]
>> or click the following link:
>>
>>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-IN
>>FRASTRUCTURE&A=1
>
>############################
>
>To unsubscribe from the NDSA-INFRASTRUCTURE list:
>write to:
>mailto:[log in to unmask]
>or click the following link:
>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-INF
>RASTRUCTURE&A=1
############################
To unsubscribe from the NDSA-INFRASTRUCTURE list:
write to: mailto:[log in to unmask]
or click the following link:
http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-INFRASTRUCTURE&A=1
