A Discard Prefix for IPv6
draft-ietf-v6ops-ipv6-discard-prefix-03

The information below is for an old version of the document
Document Type Active Internet-Draft (v6ops WG)
Last updated 2012-03-28
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Has enough positions to pass.
Responsible AD Ron Bonica
IESG note Joel Jaeggli, (joelja@bogus.com) v6ops co-chair, is the document shepherd.
Send notices to v6ops-chairs@tools.ietf.org, draft-ietf-v6ops-ipv6-discard-prefix@tools.ietf.org
v6ops Working Group                                          N. Hilliard
Internet-Draft                                                      INEX
Updates: 5156 (if approved)                               March 28, 2012
Intended status: Informational
Expires: September 29, 2012

                       A Discard Prefix for IPv6
                draft-ietf-v6ops-ipv6-discard-prefix-03

Abstract

   Remote triggered black hole filtering describes a method of
   mitigating the effects of denial-of-service attacks by selectively
   discarding traffic based on source or destination address.  Remote
   triggered black hole routing describes a method of selectively re-
   routing traffic into a sinkhole router (for further analysis) based
   on destination address.  This document updates RFC5156 by explaining
   why a unique IPv6 prefix should be formally assigned by IANA for the
   purpose of facilitating IPv6 remote triggered black hole filtering
   and routing.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 29, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Hilliard               Expires September 29, 2012               [Page 1]
Internet-Draft             IPv6 Discard Prefix                March 2012

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . . . 3
   2.  A Discard Prefix for IPv6 . . . . . . . . . . . . . . . . . . . 3
   3.  Operational Implications  . . . . . . . . . . . . . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 5

Hilliard               Expires September 29, 2012               [Page 2]
Internet-Draft             IPv6 Discard Prefix                March 2012

1.  Introduction

   Remote triggered black hole (RTBH) filtering describes a class of
   methods of blocking IP traffic either from a specific source
   ([RFC5635]) or to a specific destination ([RFC3882]) on a network.
   RTBH routing describes a class of methods of re-routing IP traffic
   destined to the attacked/targeted host to a special path (tunnel)
   where a sniffer could capture the traffic for analysis.  Both these
   methods operate by setting the next-hop address of an IP packet with
   a specified source or destination address to be a unicast prefix
   which is connected locally or remotely to a router's discard, null or
   tunnel interface.  Typically, reachability information for this
   prefix is propagated throughout an autonomous system using a dynamic
   routing protocol such as BGP ([RFC3882]).  By deploying RTBH systems
   across a network, traffic to or from specific destinations may be
   selectively black-holed or re-routed to a sinkhole device in a manner
   which is efficient, scalable and straightforward to implement.

   On some networks, operators configure RTBH installations using
   [RFC1918] address space or the address blocks reserved for
   documentation in [RFC5737].  This approach is inadequate because RTBH
   configurations are not documentation, but rather operationally
Show full document text