<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.yegin-eap-boot-rfc3118'>
<front>
<title>Bootstrapping RFC3118 Delayed DHCP Authentication Using EAP-based Network  Access Authentication</title>

<author initials='H' surname='Tschofenig' fullname='Hannes Tschofenig'>
    <organization />
</author>

<author initials='A' surname='Yegin' fullname='Alper Yegin'>
    <organization />
</author>

<author initials='D' surname='Forsberg' fullname='Dan Forsberg'>
    <organization />
</author>

<date month='July' day='14' year='2008' />

<abstract><t>The DHCP authentication extension (RFC 3118) cannot be widely deployed due to lack of a key agreement protocol.  This document outlines how EAP-based network access authentication mechanisms can be used to establish bootstrap keying material that can be used to subsequently use RFC 3118 security.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-yegin-eap-boot-rfc3118-03' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-yegin-eap-boot-rfc3118-03.txt' />
</reference>
