IPv6 distributed security requirements
draft-palet-v6ops-ipv6security-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jordi Palet Martinez , Alvaro Vives | ||
| Last updated | 2005-09-21 (Latest revision 2005-02-21) | ||
| Replaced by | draft-vives-distsec-framework | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-vives-distsec-framework | |
| 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 security policies currently applied in Internet with IPv4, doesn’t longer apply for end-to-end security models which IPv6 will enable. Today, each network is often secured by a unique device (i.e. security gateway or firewall), that becomes a bottleneck for the end- to-end security model with IPv6. In addition, users and devices start to be nomadic, moving between different networks that could have different security policies. A distributed and dynamic approach is consequently required, as already described by [1].
Authors
Jordi Palet Martinez
Alvaro Vives
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)