Document Action: 'Security Implications of IPv6 on IPv4 Networks' to Informational RFC (draft-ietf-opsec-ipv6-implications-on-ipv4-nets-07.txt)

The IESG <> Wed, 11 December 2013 23:20 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 500E91A1F72; Wed, 11 Dec 2013 15:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8t3CvvK9tHQT; Wed, 11 Dec 2013 15:19:58 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id E93531AE027; Wed, 11 Dec 2013 15:19:55 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'Security Implications of IPv6 on IPv4 Networks' to Informational RFC (draft-ietf-opsec-ipv6-implications-on-ipv4-nets-07.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Wed, 11 Dec 2013 15:19:55 -0800
Cc: opsec mailing list <>, opsec chair <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Dec 2013 23:20:00 -0000

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:

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.


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