Rogue IPv6 Router Advertisement Problem Statement
RFC 6104

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>,
    v6ops mailing list <v6ops@ietf.org>,
    v6ops chair <v6ops-chairs@tools.ietf.org>
Subject: Document Action: 'Rogue IPv6 Router Advertisement Problem Statement' to Informational RFC

The IESG has approved the following document:
- 'Rogue IPv6 Router Advertisement Problem Statement'
  <draft-ietf-v6ops-rogue-ra-02.txt> as an Informational RFC

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Ron Bonica and Dan Romascanu.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-v6ops-rogue-ra/

Technical Summary
 
When deploying IPv6, whether IPv6-only or dual-stack, routers are
configured to send IPv6 Router Advertisements to convey information to
nodes that enable them to autoconfigure on the network. This information
includes the implied default router address taken from the observed source
address of the Router Advertisement (RA) message, as well as on-link
prefix information. However, unintended misconfigurations by users or
administrators, or possibly malicious attacks on the network, may lead to
bogus RAs being present, which in turn can cause operational problems for
hosts on the network. In this draft we summarise the scenarios in which
rogue RAs may be observed and present a list of possible solutions to the
problem. We focus on the unintended causes of rogue RAs in the text. The
goal of this text is to be Informational, and as such to present a
framework around which solutions can be proposed and discussed.

Working Group Summary 

Working group commentary was quiet but supportive.

Document Quality 

The commentary on the document has stated that it is clear and to the
point.

Personnel

Fred Baker is shepherd for this document.