One document matched: draft-farrell-dtnrg-km-00.xml
<?xml version="1.0" encoding="utf-8"?>
<?rfc toc="yes"?>
<?rfc tocdepth="2"?>
<?rfc comments="yes"?>
<?rfc sortrefs="yes"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<rfc ipr="full3978" category="info" docName="draft-farrell-dtnrg-km-00">
<front>
<title abbrev="DTN Key Management Requirements"> DTN Key Management Requirements</title>
<author initials="S." surname="Farrell" fullname="Stephen Farrell">
<organization>Trinity College Dublin</organization>
<address>
<postal>
<street>Distributed Systems Group</street>
<street>Department of Computer Science</street>
<street>Trinity College </street>
<city>Dublin</city>
<code>2</code>
<country>Ireland</country>
</postal>
<phone>+353-1-608-1539</phone>
<email>stephen.farrell@cs.tcd.ie</email>
</address>
</author>
<date year="2007"/>
<area>Security</area>
<workgroup>DTN Research Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>DTN</keyword>
<keyword>Delay-Tolerant Networking</keyword>
<keyword>Disruption-Tolerant Networking</keyword>
<abstract>
<t>This short document outlines requirements for DTN key management. It may or may not
grow to specify some DTN key management schemes. </t>
</abstract>
</front>
<middle>
<section title="Introduction" toc="default">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
are to be interpreted as described in <xref target="refs.RFC2119"
format="default" pageno="false"/>.</t>
<t>This document lists a set of putative requirements for key managment
for DTN protocols, in particular the bundle protocol <xref
target="refs.DTNBP" format="default" pageno="false"/>
with the aim of assisting in the development of workable key mangement
schemes for
the bundle security protocol
<xref target="refs.DTNBPsec" format="default" pageno="false"/>. </t>
<t>Readers should also consult the DTN Architecure RFC <xref target="RFC4838" format="default" pageno="false"/>
and the DTN Security Overview and Motivations document <xref
target="refs.DTNsecOver" format="default" pageno="false"/> which contains an overview
of the current work on DTN security.</t>
<t>Depending on what happens, this document might grow to include the specification
of some key management schemes.</t>
</section>
<section title="Key Management Requirements">
<list style="numbers">
<t>No single KM scheme will work for all DTNs therefore a set of schemes, or a framework, is REQUIRED.</t>
<t>All schemes MUST support some well-defined BSP ciphersuite(s).</t>
<t>At least one scheme SHOULD be defined for each of:</t>
<list style="numbers">
<t>Manual keying, i.e. pre-shared secrets or pre-installed public keys; </t>
<t>Key transport & key agreement options. </t>
</list>
<t>Schemes SHOULD be able to use extension blocks to piggy-back KM information
with application-data handling bundles.</t>
<t>Schemes MAY involve use of specific bundle payloads.</t>
<t>Some schemes MUST be defined using standard, well-known techniques (e.g. RSA key transport).</t>
<t>DTN node connectivity, computation and storage capabilities vary enormously, so some
scheme for highly challenged nodes SHOULD be defined.</t>
</list>
</section>
<section title="Security Considerations">
<t>This memo is entirely about security requirements. See above.</t>
</section>
<section title="IANA Considerations">
<t>For now, there are none. If specific DTN key managmenet schemes are defined
that meet these requirements, then an IANA registry, or entries in an IANA
registry, MAY be required.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="refs.RFC2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="Scott Bradner">
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass. Ave.</street>
<city>Cambridge</city>
<region>MA</region>
<code>02138</code>
<country>US</country>
</postal>
<phone>+1 617 495 3864</phone>
<email>sob@harvard.edu</email>
</address>
</author>
<author initials="J." surname="Reynolds" fullname="Joyce K. Reynolds">
<organization abbrev="ISI">USC/Information Sciences Institute</organization>
<address>
<postal>
<street>4676 Admiralty Way</street>
<city>Marina del Rey</city>
<region>CA</region>
<code>90292</code>
<country>US</country>
</postal>
<phone>+1 310 822 1511</phone>
<facsimile>+1 310 823 6714</facsimile>
<email>jkrey@isi.edu</email>
</address>
</author>
<date month="October" year="1997"/>
</front>
<seriesInfo name="RFC" value="2119"/>
</reference>
</references>
<references title="Informative References">
<reference anchor="refs.DTNsecOver">
<front>
<title>Delay-Tolerant Network Security Overview</title>
<author initials="S." surname="Farrell" fullname="Stephen Farrell">
<organization/>
</author>
<author initials="S." surname="Symington" fullname="Susan Symington">
<organization>The MITRE Corporation</organization>
<address>
<postal>
<street>7515 Colshire Drive</street>
<city>McLean</city>
<region>VA</region>
<code>22102</code>
<country>US</country>
</postal>
<phone>+1 703-983-7209</phone>
<email>susan@mitre.org</email>
</address>
</author>
<author initials="H." surname="Weiss" fullname="Howard Weiss">
<organization/>
</author>
<date month="October" year="2006"/>
</front>
<seriesInfo name="draft-irtf-dtnrg-sec-overview-02.txt" value=""/>
</reference>
<reference anchor="refs.DTNBPsec">
<front>
<title>Bundle Security Protocol Specification</title>
<author initials="S." surname="Symington" fullname="Susan Symington">
<organization>The MITRE Corporation</organization>
<address>
<postal>
<street>7515 Colshire Drive</street>
<city>McLean</city>
<region>VA</region>
<code>22102</code>
<country>US</country>
</postal>
<phone>+1 703-983-7209</phone>
<email>susan@mitre.org</email>
</address>
</author>
<author initials="S." surname="Farrell" fullname="Stephen Farrell">
<organization>Trinity College Dublin</organization>
<address>
<postal>
<street>Distributed Systems Group</street>
<street>Department of Computer Science</street>
<street>Trinity College </street>
<city>Dublin</city>
<code>2</code>
<country>Ireland</country>
</postal>
<phone>+353-1-896-1761</phone>
<email>stephen.farrell@cs.tcd.ie</email>
</address>
</author>
</front>
</reference>
<reference anchor="refs.DTNBP">
<front>
<title>Bundle Protocol Specification</title>
<author initials="K." surname="Scott" fullname="Dr. Keith L. Scott">
</author>
<author initials="S." surname="Burleigh" fullname="Scott Burleigh">
</author>
<date month="April" year="2007"/>
</front>
<seriesInfo name="draft-irtf-dtnrg-bundle-spec-09.txt" value=""/>
</reference>
<reference anchor="RFC4838">
<front>
<title>Delay-Tolerant Networking Architecture</title>
<author initials="V." surname="Cerf" fullname="Vint Cerf"/>
<author initials="S." surname="Burleigh" fullname="Scott Burleigh"/>
<author initials="A." surname="Hooke" fullname="Adrian Hooke"/>
<author initials="L." surname="Torgerson" fullname="Leigh Torgerson"/>
<author initials="R." surname="Durst" fullname="Robert Durst"/>
<author initials="K." surname="Scott" fullname="Keith Scott"/>
<author initials="K." surname="Fall" fullname="Kevin Fall"/>
<author initials="H." surname="Weiss" fullname="Howard Weiss"/>
<date month="April" year="2007"/>
</front>
<seriesInfo name="RFC 4838" value=""/>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 03:33:47 |