Requirements for IPsec Negotiation in the SIP Framework
draft-saito-mmusic-ipsec-negotiation-req-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Makoto Saito , Shingo Fujimoto | ||
| Last updated | 2006-03-10 | ||
| 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
As the Internet grows, it becomes inevitable even for the general users to take measures against the security risks such as tapping, unauthorized access, and so on. For example, we can consider the use case of networked home appliances which cannot have the rich calculation resources and may use the dedicated transport protocol for the media session. In such a case, it is effective to connect such devices securely using IPsec [1] because it does not require the rich resources, and is independent of the upper layer protocol. Also from the viewpoint of implementation, IPsec is not only widespread in IPv4, but also mandatory in IPv6 which is expected in the networked home appliances region(this use case is just the one of examples, and this document does not focus only on home appliances but also on the general applications which use the dedicated media protocols, where IPsec is suitable as the security protocol).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)