DHCP Keys via 802.1X
draft-dekok-saag-dhcp-keys-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-24
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)
Network Working Group                                        DeKok, Alan
INTERNET-DRAFT                                       Network RADIUS SARL
Category: Standards Track
<draft-dekok-saag-dhcp-keys-00.txt>
24 October 2016

                          DHCP Keys via 802.1X

Abstract

   While RFC 3118 made provisions for securing DHCP, it made no
   provisions for creating or distributing authentication keys.  This
   specification describes how in some cases, DHCP keys can be
   automatically derived from 802.1X authentication.  The pros and cons
   of this approach are also discussed

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on May 24, 2017.

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

DeKok, Alan                  Standards Track                    [Page 1]
INTERNET-DRAFT            DHCP Keys via 802.1X           24 October 2016

   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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

DeKok, Alan                  Standards Track                    [Page 2]
INTERNET-DRAFT            DHCP Keys via 802.1X           24 October 2016

Table of Contents

1.  Introduction .............................................    4
   1.1.  Problem Statement ...................................    4
   1.2.  Proposed Solution ...................................    4
   1.3.  Requirements Language ...............................    4
2.  Generating Keying Material ...............................    5
   2.1.  Implementation Considerations .......................    6
   2.2.  What does the Signature mean? .......................    6
   2.3.  Open Questions ......................................    6
3.  Security Considerations ..................................    7
4.  IANA Considerations ......................................    7
5.  References ...............................................    8
   5.1.  Normative References ................................    8
   5.2.  Informative References ..............................    8

DeKok, Alan                  Standards Track                    [Page 3]
INTERNET-DRAFT            DHCP Keys via 802.1X           24 October 2016

1.  Introduction

   There has been increased interest in, and awareness of, securing
   basic networking protocols such as DHCP [RFC2131].  While provisions
   were made in [RFC3118] for securing the protocol via secret keys,
   there is little discussion on how the secret keys are created or
   managed.  This specification addresses that issue, for the limited
   case of DHCP which occurs after 802.1X authentication.

1.1.  Problem Statement

   This document addresses the situation where a client machine connects
   to the network via 802.1X / EAP, and where keying material is derived
   as part of the EAP conversation.  Once the client machine
   authenticated to the network, it requests an IP address via DHCP.

   However, there is essentially no communication or interaction between
   the AAA server which authenticates the client machine, and the DHCP
   server which allocates IP addresses.  This lack of communication
   means that it is possible to attack the systems independent.  That
   is, the two systems do not work together to increase security.

1.2.  Proposed Solution

   Have the AAA server derive a shared secret key for signing DHCP
Show full document text