Security Requirements for UDT
draft-d-sec-udt-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Danilo Valeros Bernardo | ||
| Last updated | 2009-09-29 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
UDT does not have its specific security mechanism. It depends on the application to provide authentication and lower layer to provide security mechanisms[GG07]. However, UDT implementations should check each arrived packets are from the expected source, since UDP is connectionless. This document proposes evaluation of security requirements for UDT, or UDP based Data Transfer considered as an alternative data transfer protocol for the situation when TCP does not work well.The objective is to achieve a wide class of security methods used on existing mature protocols such as UDP and TCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)