RFC 6104 on Rogue IPv6 Router Advertisement Problem Statement

rfc-editor@rfc-editor.org Thu, 24 February 2011 00:59 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E10D83A6960; Wed, 23 Feb 2011 16:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level:
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IKKA27eSgn4y; Wed, 23 Feb 2011 16:59:01 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id D33933A691B; Wed, 23 Feb 2011 16:59:01 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6C4FEE06EE; Wed, 23 Feb 2011 16:59:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6104 on Rogue IPv6 Router Advertisement Problem Statement
From: rfc-editor@rfc-editor.org
Message-Id: <20110224005950.6C4FEE06EE@rfc-editor.org>
Date: Wed, 23 Feb 2011 16:59:50 -0800
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 00:59:03 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6104

        Title:      Rogue IPv6 Router Advertisement Problem 
                    Statement 
        Author:     T. Chown, S. Venaas
        Status:     Informational
        Stream:     IETF
        Date:       February 2011
        Mailbox:    tjc@ecs.soton.ac.uk, 
                    stig@cisco.com
        Pages:      16
        Characters: 36518
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-rogue-ra-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6104.txt

When deploying IPv6, whether IPv6-only or dual-stack, routers are
configured to send IPv6 Router Advertisements (RAs) 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 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 document, 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.  This document 
is not an Internet Standards Track specification; it is
published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC