Security Implications of IPv6 on IPv4 Networks
draft-ietf-opsec-ipv6-implications-on-ipv4-nets-07

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: RFC Editor <rfc-editor@rfc-editor.org>,
    opsec mailing list <opsec@ietf.org>,
    opsec chair <opsec-chairs@tools.ietf.org>
Subject: Document Action: 'Security Implications of IPv6 on IPv4 Networks' to Informational RFC (draft-ietf-opsec-ipv6-implications-on-ipv4-nets-07.txt)

The IESG has approved the following document:
- 'Security Implications of IPv6 on IPv4 Networks'
  (draft-ietf-opsec-ipv6-implications-on-ipv4-nets-07.txt) as
Informational RFC

This document is the product of the Operational Security Capabilities for
IP Network Infrastructure Working Group.

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-opsec-ipv6-implications-on-ipv4-nets/

Ballot Text

Technical Summary

This document discusses the security implications (and provides possible mitigations) of native IPv6 support and IPv6 transition/co-existence technologies on "IPv4-only" networks.

It details a number of operational security concerns, and provides mitigations for many of them. In many cases operators of IPv4 only networks have not considered the security implications of an attacker (or an automatic tunneling mechanism) enabling IPv6 on their network / hosts.

Working Group Summary

There was no drama in the WG on this topic.

Document Quality

This document does not describe any protocol/ specifications, and so there are no existing implementations / things to implement.

The document is of good quality. It is easily read and clear.

Personnel


Warren Kumari is the Document Shepherd. Joel Jaeggli is the responsible AD.

RFC Editor Note