draft-ietf-dhc-dhcpv6-unknown-msg-05.txt   draft-ietf-dhc-dhcpv6-unknown-msg-06.txt 
DHC Working Group Y. Cui DHC Working Group Y. Cui
Internet-Draft Q. Sun Internet-Draft Q. Sun
Updates: 3315 (if approved) Tsinghua University Updates: 3315 (if approved) Tsinghua University
Intended status: Standards Track T. Lemon Intended status: Standards Track T. Lemon
Expires: August 8, 2014 Nominum, Inc. Expires: September 14, 2014 Nominum, Inc.
February 4, 2014 March 13, 2014
Handling Unknown DHCPv6 Messages Handling Unknown DHCPv6 Messages
draft-ietf-dhc-dhcpv6-unknown-msg-05 draft-ietf-dhc-dhcpv6-unknown-msg-06
Abstract Abstract
DHCPv6 is not specific about handling messages with unknown types. DHCPv6 is not specific about handling messages with unknown types.
This memo describes the problems and defines how a DHCPv6 server, This memo describes the problems and defines how a DHCPv6 server,
client or relay agent should behave when receiving unknown DHCPv6 client or relay agent should behave when receiving unknown DHCPv6
messages. This document also provides advice for authors of future messages. This document also provides advice for authors of future
documents defining new messages sent from DHCP servers to DHCP relay documents defining new messages sent from DHCP servers to DHCP relay
agents, and should be read by potential authors of such documents. agents, and should be read by potential authors of such documents.
This document updates RFC3315. This document updates RFC3315.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 August 8, 2014. This Internet-Draft will expire on September 14, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 5, line 26 skipping to change at page 5, line 26
the message as is defined in Section 20.2 of [RFC3315], regardless of the message as is defined in Section 20.2 of [RFC3315], regardless of
the type of the message encapsulated in the Relay Message Option. the type of the message encapsulated in the Relay Message Option.
5. Client and Server Behavior Update 5. Client and Server Behavior Update
A client or server MUST silently discard any received DHCPv6 message A client or server MUST silently discard any received DHCPv6 message
with an unknown message type. with an unknown message type.
6. Security Considerations 6. Security Considerations
This document creates no new security issues that are not already
present in RFC3315. By explicitly documenting the correct handling
of unknown messages, this document, if implemented, reduces any
security exposure that might result from incorrect handling of
unknown messages. The following issues are issues that could already
be present with section 23 of [RFC3315], but we discuss them in
detail here as guidance for implementors.
As the relay agent will forward all unknown types of DHCPv6 messages, As the relay agent will forward all unknown types of DHCPv6 messages,
a malicious attacker can interfere with the relaying function by a malicious attacker can interfere with the relaying function by
constructing fake DHCPv6 messages with arbitrary type code. The same constructing fake DHCPv6 messages with arbitrary type code. The same
problem may happen in current DHCPv4 and DHCPv6 practice where the problem may happen in current DHCPv4 and DHCPv6 practice where the
attacker constructs the fake DHCP message with a known type code. attacker constructs the fake DHCP message with a known type code.
Clients and servers that implement this specification will discard Clients and servers that implement this specification will discard
unknown DHCPv6 messages. Since RFC3315 did not specify either relay unknown DHCPv6 messages. Since RFC3315 did not specify either relay
agent, client or server behavior in the presence of unknown messages, agent, client or server behavior in the presence of unknown messages,
it is possible that some servers or clients that have not been it is possible that some servers or clients that have not been
 End of changes. 4 change blocks. 
4 lines changed or deleted 12 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/