Privacy considerations for DHCPv4
draft-ietf-dhc-dhcp-privacy-03

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2016-02-05 (latest revision 2016-01-18)
Replaces draft-jiang-dhc-dhcp-privacy
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestones: Aug 2015 - WG last call on DHCP..., Jan 2016 - Submit DHCP privacy ... )
Document shepherd Bernie Volz
Shepherd write-up Show (last changed 2016-01-12)
IESG IESG state Waiting for Writeup::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Brian Haberman
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
dhc                                                             S. Jiang
Internet-Draft                              Huawei Technologies Co., Ltd
Intended status: Informational                               S. Krishnan
Expires: July 21, 2016                                          Ericsson
                                                            T. Mrugalski
                                                                     ISC
                                                        January 18, 2016

                   Privacy considerations for DHCPv4
                     draft-ietf-dhc-dhcp-privacy-03

Abstract

   DHCP is a protocol that is used to provide addressing and
   configuration information to IPv4 hosts.  This document discusses the
   various identifiers used by DHCP and the potential privacy issues.

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 July 21, 2016.

Copyright Notice

   Copyright (c) 2016 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
   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

Jiang, et al.             Expires July 21, 2016                 [Page 1]
Internet-Draft         DHCP Privacy considerations          January 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language and Terminology . . . . . . . . . . . .   3
   3.  DHCP Options Carrying Identifiers . . . . . . . . . . . . . .   3
     3.1.  Client Identifier Option  . . . . . . . . . . . . . . . .   4
     3.2.  Address Fields & Options  . . . . . . . . . . . . . . . .   4
     3.3.  Client FQDN Option  . . . . . . . . . . . . . . . . . . .   5
     3.4.  Parameter Request List Option . . . . . . . . . . . . . .   5
     3.5.  Vendor Class and Vendor-Identifying Vendor Class Options    5
     3.6.  Civic Location Option . . . . . . . . . . . . . . . . . .   5
     3.7.  Coordinate-Based Location Option  . . . . . . . . . . . .   6
     3.8.  Client System Architecture Type Option  . . . . . . . . .   6
     3.9.  Relay Agent Information Option and Sub-options  . . . . .   6
   4.  Existing Mechanisms That Affect Privacy . . . . . . . . . . .   7
     4.1.  DNS Updates . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Allocation strategies . . . . . . . . . . . . . . . . . .   7
   5.  Attacks . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Device type discovery . . . . . . . . . . . . . . . . . .   8
     5.2.  Operating system discovery  . . . . . . . . . . . . . . .   9
     5.3.  Finding location information  . . . . . . . . . . . . . .   9
     5.4.  Finding previously visited networks . . . . . . . . . . .   9
     5.5.  Finding a stable identity . . . . . . . . . . . . . . . .   9
     5.6.  Pervasive monitoring  . . . . . . . . . . . . . . . . . .   9
     5.7.  Finding client's IP address or hostname . . . . . . . . .  10
     5.8.  Correlation of activities over time . . . . . . . . . . .  10
     5.9.  Location tracking . . . . . . . . . . . . . . . . . . . .  10
     5.10. Leasequery & bulk leasequery  . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Dynamic Host Configuration Protocol (DHCP) [RFC2131] is a protocol
   that is used to provide addressing and configuration information to
Show full document text