draft-ietf-dhc-client-id-03.txt   draft-ietf-dhc-client-id-04.txt 
DHC Working Group N. Swamy DHC Working Group N. Swamy
Internet-Draft Nokia Internet-Draft Nokia
Updates: 2131 (if approved) G. Halwasia Updates: 2131 (if approved) G. Halwasia
Intended status: Standards Track P. Jhingran Intended status: Standards Track P. Jhingran
Expires: January 11, 2013 Cisco Systems Expires: January 12, 2013 Cisco Systems
July 10, 2012 July 11, 2012
Client Identifier Option in DHCP Server Replies Client Identifier Option in DHCP Server Replies
draft-ietf-dhc-client-id-03 draft-ietf-dhc-client-id-04
Abstract Abstract
This document updates RFC2131 [RFC2131]. The changes to [RFC2131] This document updates RFC2131 [RFC2131]. The changes to [RFC2131]
defined in this draft clarifies the use of 'client identifier' option defined in this draft clarifies the use of 'client identifier' option
by the DHCP servers. The clarification addresses the issues arising by the DHCP servers. The clarification addresses the issues arising
out of the point specified by [RFC2131] that the server 'MUST NOT' out of the point specified by [RFC2131] that the server 'MUST NOT'
return client identifier' option to the client. return client identifier' option to the client.
Requirements Requirements
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 January 11, 2013. This Internet-Draft will expire on January 12, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 32 skipping to change at page 4, line 32
relevant fields are modified accordingly to overcome the problems relevant fields are modified accordingly to overcome the problems
mentioned in this document. mentioned in this document.
Option DHCPOFFER DHCPACK DHCPNAK Option DHCPOFFER DHCPACK DHCPNAK
------ --------- ------- ------- ------ --------- ------- -------
Client identifier (if MUST MUST MUST Client identifier (if MUST MUST MUST
sent by client) sent by client)
Client identifier (if MUST NOT MUST NOT MUST NOT Client identifier (if MUST NOT MUST NOT MUST NOT
not sent by client) not sent by client)
Client MAY use 'client identifier' or 'chaddr' received from server When a client receives a DHCP message containing a 'client
along with 'xid' to map the response to request. This will guarantee identifier' option, the client MUST compare that client identifier to
that a particular response from the server is meant for the the one it is configured to send. If the two client identifiers do
particular client. not match, the client MUST silently discard the message.
4. IANA Considerations 4. IANA Considerations
This memo asks the IANA for no new parameters. This memo asks the IANA for no new parameters.
5. Security Considerations 5. Security Considerations
No known security considerations. No known security considerations.
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Bernie Volz, Ted Lemon, Barr Hibbs The authors would like to thank Bernie Volz, Ted Lemon, Barr Hibbs,
for their insightful discussions on the previous version of this Richard Johnson for their insightful discussions on the previous
document. version of this document.
7. Normative References 7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
 End of changes. 5 change blocks. 
11 lines changed or deleted 11 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/