DHCPv6-Shield: Protecting Against Rogue DHCPv6 Servers
draft-gont-opsec-dhcpv6-shield-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-05-17
Replaced by draft-ietf-opsec-dhcpv6-shield, rfc7610
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Operational Security Capabilities for                            F. Gont
IP Network Infrastructure (opsec)                 SI6 Networks / UTN-FRH
Internet-Draft                                              May 18, 2012
Intended status: BCP
Expires: November 19, 2012

         DHCPv6-Shield: Protecting Against Rogue DHCPv6 Servers
                   draft-gont-opsec-dhcpv6-shield-00

Abstract

   This document specifies a mechanism for protecting hosts connected to
   a broadcast network against rogue DHCPv6 servers.  The aforementioned
   mechanism is based on DHCPv6 packet-filtering at the layer-2 device
   on which the packets are received.  The aforementioned mechanism has
   been widely deployed in IPv4 networks ('DHCP snooping'), and hence it
   is desirable that similar functionality be provided for IPv6
   networks.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.  This document may not be modified,
   and derivative works of it may not be created, and it may not be
   published except as an Internet-Draft.

   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 November 19, 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

Gont                    Expires November 19, 2012               [Page 1]
Internet-Draft                DHCPv6-Shield                     May 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
   2.  DHCPv6-Shield Configuration  . . . . . . . . . . . . . . . . .  4
   3.  DHCPv6-Shield Implementation Advice  . . . . . . . . . . . . .  5
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12

Gont                    Expires November 19, 2012               [Page 2]
Internet-Draft                DHCPv6-Shield                     May 2012

1.  Introduction

   This document specifies a mechanism for protecting hosts connected to
   a broadcast network against rogue DHCPv6 servers.  This mechanism is
   analogous to the RA-Guard mechanism [RFC6104] [RFC6105]
   [I-D.ietf-v6ops-ra-guard-implementation] intended for protection
   against rogue Router Advertisement messages.

   The basic concept behind DHCPv6-Shield is that a layer-2 device
   filters DHCPv6 messages meant to DHCPv6 clients, according to a
   number of different criteria.  The most basic filtering criterion
   being that the aforementioned DHCPv6 messages are discarded by the
   layer-2 device unless they are received on a specified port of the
   layer-2 device.

   Before the DCHPv6-Shield device is deployed, the administrator
   specifies the layer-2 port(s) on which DHCPv6 packets meant for
   DHCPv6 clients are allowed.  Only those ports to which a DHCPv6
   server is to be connected should be specified as such.  Once
   deployed, the DHCPv6-Shield device inspects received packets, and
   allows (i.e. passes) DHCPv6 messages meant for DHCPv6 clients only if
   they are received on layer-2 ports that have been explicitly
   configured for such purpose.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Gont                    Expires November 19, 2012               [Page 3]
Show full document text