Using SRTP transport format with HIP
draft-tschofenig-hiprg-hip-srtp-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Hannes Tschofenig | ||
| Last updated | 2006-10-25 | ||
| 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
The Host Identity Protocol (HIP) is a signaling protocol which adds a new layer between the traditional Transport and the Network layer. HIP is an end-to-end authentication and key exchange protocol, which supports security and mobility in a commendable manner. The HIP base specification is generalized and purported to support different key exchange mechanisms in order to provide confidentiality protection for the subsequent user data traffic. This draft explains a mechanism to establish Secure Real Time Protocol associations, to protect the user data packets, by using HIP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)