<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>DAI WG colleagues: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have been forwarded a link to the IETF’s RFC on their digital preservation approach. This is for preservation of only their RFCs. <o:p></o:p></p><p class=MsoNormal>RFC 8153 <a href="https://www.rfc-editor.org/rfc/rfc8153.html">https://www.rfc-editor.org/rfc/rfc8153.html</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It’s an interesting read, notably: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In section 2.3 they have a discussion of their “metadata”. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In section 2.7 they point to the DPC’s Digital Preservation Handbook (although their reference link is broken… I found it at <a href="https://www.dpconline.org/handbook">https://www.dpconline.org/handbook</a>. It’s now https). <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>An interesting conclusion at the end of section 3 (Conclusions) is: <o:p></o:p></p><pre style='margin-left:.25in'><span style='color:black'>Since the overall model for the<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>digital archive maintained by the RFC Editor follows the OAIS<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>reference model, the associated audit guidelines should also be<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>followed. While the RFC Editor does not seek to be recognized as<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>'OAIS-compliant' at this time, use of the ISO standard "Space data<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>and information transfer systems -- Audit and certification of<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>trustworthy digital repositories" [<a href="https://www.rfc-editor.org/rfc/rfc8153.html#ref-ISO16363" title=""Space data and information transfer systems -- Audit and certification of trustworthy digital repositories"">ISO16363</a>] would provide a solid,<o:p></o:p></span></pre><pre style='margin-left:.25in'><span style='color:black'>accepted method for structuring an audit for this digital archive.<o:p></o:p></span></pre><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The thought that came to me reading this is… why isn’t CCSDS addressing this? What is the CCSDS Secretariat doing to insure long-term access to CCSDS standards such as OAIS? The preservation of the OAIS standards may seem to be self-referential topic, but the question should be asked nonetheless. I recommend that we discuss this and prepare a statement to forward to the CESG/CMC at the end of the next meeting. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Merry Christmas and Happy New Year to all my DAI WG colleagues! <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><a href="https://public.ccsds.org/about/ManagementCouncil/MikeKearney.aspx"><span style='color:#0563C1'>Mike Kearney</span></a><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA<o:p></o:p></span></p><p class=MsoNormal><a href="mailto:KearneySolutions@gmail.com"><span style='color:blue'>KearneySolutions@gmail.com</span></a><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><a href="mailto:MikeK@spacestandards.org"><span style='color:blue'>MikeK@spacestandards.org</span></a><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>+1-256-361-5411 (mobile)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#002060'>Member of Technical Staff<o:p></o:p></span></p><p class=MsoNormal><a href="http://sol.spacenvironment.net/sif/index.html"><span style='color:#0563C1'>Space Infrastructure Foundation</span></a><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>