draft-ietf-dhc-forcerenew-nonce-01.txt   draft-ietf-dhc-forcerenew-nonce-02.txt 
softwire D. Miles softwire D. Miles
Internet-Draft Alcatel-Lucent Internet-Draft Alcatel-Lucent
Intended status: Standards Track W. Dec Intended status: Standards Track W. Dec
Expires: September 11, 2011 Cisco Systems Expires: March 9, 2012 Cisco Systems
J. Bristow J. Bristow
Swisscom Schweiz AG Swisscom Schweiz AG
R. Maglione R. Maglione
Telecom Italia Telecom Italia
March 10, 2011 September 6, 2011
Forcerenew Nonce Authentication Forcerenew Nonce Authentication
draft-ietf-dhc-forcerenew-nonce-01 draft-ietf-dhc-forcerenew-nonce-02
Abstract Abstract
DHCP Forcerenew allows for the reconfiguration of a single host by DHCP Forcerenew allows for the reconfiguration of a single host by
forcing the DHCP client into a Renew state on a trigger from the DHCP forcing the DHCP client into a Renew state on a trigger from the DHCP
server. In Forcerenew Nonce Authentication the server exchanges a server. In Forcerenew Nonce Authentication the server exchanges a
nonce with the client on the initial DHCP ACK that is used for nonce with the client on the initial DHCP ACK that is used for
subsequent validation of a Forcerenew message. subsequent validation of a Forcerenew message.
Status of this Memo Status of this Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 11, 2011. This Internet-Draft will expire on March 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 19 skipping to change at page 4, line 19
by the DHCP server. Its application is currently limited by a by the DHCP server. Its application is currently limited by a
requirement that FORCERENEW message is always authenticated using requirement that FORCERENEW message is always authenticated using
procedures as described in [RFC3118]. Authentication for DHCP procedures as described in [RFC3118]. Authentication for DHCP
[RFC3118] is mandatory for Forcerenew, however as it is currently [RFC3118] is mandatory for Forcerenew, however as it is currently
defined [RFC3118] requires distribution of constant token or shared- defined [RFC3118] requires distribution of constant token or shared-
secret out-of-band to DHCP clients. The mandatory authentication was secret out-of-band to DHCP clients. The mandatory authentication was
originally motivated by a legitimate security concern whereby in some originally motivated by a legitimate security concern whereby in some
network environments a FORCERENEW message can be spoofed. However, network environments a FORCERENEW message can be spoofed. However,
in some networks native security mechanisms already provide in some networks native security mechanisms already provide
sufficient protection against spoofing of DHCP traffic. An example sufficient protection against spoofing of DHCP traffic. An example
of such network is a DSL Forum TR-101 [TR-101] compliant access of such network is a Broadband Forum TR-101 [TR-101i2] compliant
network. In such environments the mandatory coupling between access network. In such environments the mandatory coupling between
FORCERENEW and DHCP Authentication [RFC3118] can be relaxed. This FORCERENEW and DHCP Authentication [RFC3118] can be relaxed. This
document defines extensions to Authentication for DHCP(v4) Messages document defines extensions to Authentication for DHCP(v4) Messages
[RFC3118] to create a new authentication protocol for DHCPv4 [RFC3118] to create a new authentication protocol for DHCPv4
Forcerenew [RFC3203] messages; this method does not require out-of- Forcerenew [RFC3203] messages; this method does not require out-of-
band key distribution to DHCP clients. The Forcerenew Nonce is band key distribution to DHCP clients. The Forcerenew Nonce is
exchanged between server and client on initial DHCP ACK and is used exchanged between server and client on initial DHCP ACK and is used
for verification of any subsequent Forcerenew message. for verification of any subsequent Forcerenew message.
2. Requirements Language 2. Requirements Language
skipping to change at page 11, line 27 skipping to change at page 11, line 27
[RFC3203] T'Joens, Y., Hublet, C., and P. De Schrijver, "DHCP [RFC3203] T'Joens, Y., Hublet, C., and P. De Schrijver, "DHCP
reconfigure extension", RFC 3203, December 2001. reconfigure extension", RFC 3203, December 2001.
7.2. Informative References 7.2. Informative References
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[TR-101] Cohen et al, "Architecture & Transport: "Migration to [TR-101i2]
Ethernet Based DSL Aggregation, DSL Forum TR-101", 2005. Anschutz, T., "Migration to Ethernet-Based Broadband
Aggregation Broadband Forum TR-101 Issue 2", July 2011.
Authors' Addresses Authors' Addresses
David Miles David Miles
Alcatel-Lucent Alcatel-Lucent
L3 / 215 Spring St L3 / 215 Spring St
Melbourne, Victoria 3000, Melbourne, Victoria 3000,
Australia Australia
Phone: +61 3 9664 3308 Phone: +61 3 9664 3308
 End of changes. 6 change blocks. 
8 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/