Damian Brasher
RHCE BSc (Maths-IT) MBCS - Engineering, research, design, code and author of Internet Draft for IETF. I am a systems administrator on a fixed term contract to OMII-UK at ECS Southampton University. Damian has also begun studying at systems architect grade with Red Hat GLS.
Marisa (wife) MSc-Professional Studies, and many thanks for fantastic support. Marisa works as a skills development leader with Learning Curve.
Myles McClelland MSc-Management FBCS - Part sponsor, involved with early conceptual design, project management advice and valuable technical reasoning as well as physical server maintenance, data storage and transfer tests. Myles is a management consultant with OakLeigh LTD.
Richard Brasher Financial Advice. Richard works for a large multi-national. In his free time he provides accounting templates for small organisations.
Stuart - (BTec Design) DIAP B.Tree Logo.
Stephen Pelc Also Stephen Pelc of MPE Forth for SME deployment context advice and IPR consultancy. Stephen runs and owns MPEForth.
Other individuals Thanks to a number of individuals from various groups for their advice and constructive criticism.

Assets and Intellectual property

Are owned, managed and registered in the name of Interlinux LTD in turn owned by the named partners above apart from Stuart and Stephen and a special licence to OMII-UK has been made available - Trading services can be put in place when necessary. This is a part-time project and will remain so for the foreseeable future. Delivery is and will remain Open Source.

History

1999 - Deployed a single Samba backup server for small charitable organisation. Beowulf experiments as a hobby.
2003 - Merged with larger organisation and took over 12 remote sites, deployed OpenVPN copied files extensively between sites.
2005 - Started experimental home archiving using ftp with help from brother-in-law (no longer operational).
2007 - I Conceived DIAP as a technique and possible protocol, for the rest please read this site.

The original post (since refined) proposing a DIAP RFC was made to HL ML on May 19th 2007:-

"Hi List

I have been working on an experimental archive project for two and a half
years now and now have got to the stage where it looks like a protocol. I
have formulated a generic brief after much deliberation. See draft brief
below. A few Lug members have been testers helping me with understanding
the process.

Now although the work may never turn into and RFC the ideas could, I
think, be worked into an I-D (Internet draft).

Can anyone advise, or has anyone been involved with producing such a
document and if so offer advice? I realise that many are submitted and
many fail.

Here is the protocol name and the brief:

Protocol name:

DIAP - Distributed Internet Archive Protocol. Also see Long-Term Archive
Service Requirements RFC4810 and Long-term Archive Protocol (LTAP) I-D. I
have yet to fully study the above documents but have read some - they are
very detailed so it will take some more time to reference these and other
RFC's and I-D's I have yet to find.

Draft Generic Brief:

By using a number of backup nodes either between sites say between
offices, homes, on a campus or over WAN's, which could be dedicated to
storage or used for existing services, have a round robin synchronisation
of incremental backup pools where the source of data ranges from a
personal laptop to a file store over unused band-width where the data rate
is dynamically controlled according to load and availability. The
incremental data retention tuned to the needs of an organisation so that
some data is always available from any node in the backup pool quickly to
within a certain time frame and tape storage stations strategically places
in various secure locations for older data retention. This system would
avoid using prohibitively expensive packages by reusing resources,
building on Open Source technologies and have a coherent strategy across
many sites increasing the level of redundancy to a high degree. With
layers of indexing, accounting and central management facilities.

Any advice or guidance would be appreciated, even if it to contact third
parties etc.

I may be barking up the wrong tree with parts of this project but there
seems to be evolving a generic Internet archive strategy. Anyway, better
to keep it in the public arena:)

TIA Damian B"

© Site construction: DIAP ® Damian Brasher 2008