Skip to main content

IPv6 Security Problem Statement
draft-vives-v6ops-ipv6-security-ps-03

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author 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

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. The deployment of IPv6 enabled devices and networks bring some issues, which must be addressed by security administrators in order to guarantee at least the same level of security that is obtained nowadays with IPv4 and network-based (including perimetral-based) security schemes, allowing at the same time all the IPv6 advantages.

Authors

Alvaro Vives

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)