Best Current Practice for Filtering ICMPv6 Messages in Firewalls
draft-ietf-v6ops-icmpv6-filtering-bcp-01
| Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Elwyn B. Davies , János Mohácsi | ||
| Last updated | 2006-07-20 (Latest revision 2006-03-09) | ||
| Replaced by | RFC 4890 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-icmpv6-filtering-recs | |
| Consensus boilerplate | Unknown | ||
| 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
In networks supporting IPv6 the Internet Control Message Protocol version 6 (ICMPv6) plays a fundamental role with a large number of functions, and a correspondingly large number of message types and options. A number of security risks are associated with uncontrolled forwarding of ICMPv6 messages. On the other hand, compared with IPv4 and the corresponding protocol ICMP, ICMPv6 is essential to the functioning of IPv6 rather than a useful auxiliary. This document provides some recommendations for ICMPv6 firewall filter configuration that will allow propagation of ICMPv6 messages that are needed to maintain the functioning of the network but drop messages which are potential security risks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)