draft-ietf-dhc-relay-port-03.txt   draft-ietf-dhc-relay-port-04.txt 
Networking Working Group N. Shen Networking Working Group N. Shen
Internet-Draft E. Chen Internet-Draft E. Chen
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: October 13, 2017 April 11, 2017 Expires: October 20, 2017 April 18, 2017
Generalized UDP Source Port for DHCP Relay Generalized UDP Source Port for DHCP Relay
draft-ietf-dhc-relay-port-03 draft-ietf-dhc-relay-port-04
Abstract Abstract
This document proposes an extension to the DHCP and DHCPv6 protocols This document proposes an extension to the DHCP and DHCPv6 protocols
that allows any valid number to be used as the relay agent's UDP that allows any valid number to be used as the relay agent's UDP
source port for DHCP packets. source port for DHCP packets.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 October 13, 2017. This Internet-Draft will expire on October 20, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 2, line 25 skipping to change at page 2, line 25
4.2. Relay Source Port Option for DHCPv6 . . . . . . . . . . . 5 4.2. Relay Source Port Option for DHCPv6 . . . . . . . . . . . 5
5. Relay Agent and Server Behavior . . . . . . . . . . . . . . . 6 5. Relay Agent and Server Behavior . . . . . . . . . . . . . . . 6
5.1. DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. DHCPv6 . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. DHCPv6 . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.3. Compatibility . . . . . . . . . . . . . . . . . . . . . . 7 5.3. Compatibility . . . . . . . . . . . . . . . . . . . . . . 7
6. A DHCPv6 Cascaded Relay Example . . . . . . . . . . . . . . . 7 6. A DHCPv6 Cascaded Relay Example . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
10. Document Change Log . . . . . . . . . . . . . . . . . . . . . 9 10. Document Change Log . . . . . . . . . . . . . . . . . . . . . 9
10.1. Changes to draft-ietf-dhc-relay-port-03 . . . . . . . . 9 10.1. Changes to draft-ietf-dhc-relay-port-04 . . . . . . . . 9
10.2. Changes to draft-ietf-dhc-relay-port-02 . . . . . . . . 9 10.2. Changes to draft-ietf-dhc-relay-port-03 . . . . . . . . 9
10.3. Changes to draft-ietf-dhc-relay-port-01 . . . . . . . . 9 10.3. Changes to draft-ietf-dhc-relay-port-02 . . . . . . . . 9
10.4. Changes to draft-ietf-dhc-relay-port-00 . . . . . . . . 9 10.4. Changes to draft-ietf-dhc-relay-port-01 . . . . . . . . 9
10.5. Changes to draft-ietf-dhc-relay-port-00 . . . . . . . . 9
11. Normative References . . . . . . . . . . . . . . . . . . . . 9 11. Normative References . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
RFC 2131 [RFC2131] and RFC 3315 [RFC3315] specify the use of UDP as RFC 2131 [RFC2131] and RFC 3315 [RFC3315] specify the use of UDP as
the transport protocol for DHCP and DHCPv6. They also define both the transport protocol for DHCP and DHCPv6. They also define both
the server side and client side port numbers. The DHCP server port the server side and client side port numbers. The DHCP server port
is UDP number (67) and the client port is UDP number (68); for DHCPv6 is UDP number (67) and the client port is UDP number (68); for DHCPv6
the server port is (546) and the client port is (547). the server port is (546) and the client port is (547).
skipping to change at page 7, line 16 skipping to change at page 7, line 16
message in replying to the relay agent. message in replying to the relay agent.
When a relay agent receives a Relay-reply message with the "Relay When a relay agent receives a Relay-reply message with the "Relay
Source Port Option" from a server or from an upstream relay agent, if Source Port Option" from a server or from an upstream relay agent, if
the "Downstream Source Port" field in the option is non-zero, it MUST the "Downstream Source Port" field in the option is non-zero, it MUST
use this UDP port number to forward the Relay-reply message to the use this UDP port number to forward the Relay-reply message to the
downstream relay agent. downstream relay agent.
5.3. Compatibility 5.3. Compatibility
With this source port generalization, the DHCP and DHCPv6 server MUST Sites that need for relay agents to specify a source port will need
be upgraded to support the extension specified in this document to install new DHCP server and DHCP relay agent software with this
before the extension is used by a relay agent. feature. If a site installs only DHCP relay agent software with this
feature, there is no possibility that the DHCP server will be able to
communicate to the relay agent.
The implementation is advised to allow configuration for relay agent The implementation is advised to allow configuration for relay agent
specifying a DHCP relay port number. It can be used to allow the specifying a DHCP relay port number. It can be used to allow the
relay agent either using a normal DHCP UDP port or non-DHCP UDP port. relay agent either using a normal DHCP UDP port or non-DHCP UDP port.
6. A DHCPv6 Cascaded Relay Example 6. A DHCPv6 Cascaded Relay Example
An example of DHCPv6 cascaded relay agents with the "Relay Source An example of DHCPv6 cascaded relay agents with the "Relay Source
Port Option" is shown below. Port Option" is shown below.
skipping to change at page 9, line 7 skipping to change at page 9, line 7
comments of this document. comments of this document.
The authors would like to thank Bernie Volz for discussions that led The authors would like to thank Bernie Volz for discussions that led
to the definition of The Relay Source Port sub-option and DHCPv6 to the definition of The Relay Source Port sub-option and DHCPv6
Relay Source Port Option. Relay Source Port Option.
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
10. Document Change Log 10. Document Change Log
10.1. Changes to draft-ietf-dhc-relay-port-03 10.1. Changes to draft-ietf-dhc-relay-port-04
o Posted the draft in April 2017.
o Rephrased the relay agent and server requirement with this relay
port feature.
10.2. Changes to draft-ietf-dhc-relay-port-03
o Posted the draft in April 2017. o Posted the draft in April 2017.
o Added the "Relay Agent and Server Behavior" section. o Added the "Relay Agent and Server Behavior" section.
10.2. Changes to draft-ietf-dhc-relay-port-02 10.3. Changes to draft-ietf-dhc-relay-port-02
o Posted the draft in February 2017. o Posted the draft in February 2017.
o Added the Terminology section. o Added the Terminology section.
o Defined the Sub-option and Option names for DHCP and DHCPv6. o Defined the Sub-option and Option names for DHCP and DHCPv6.
o Added the DHCPv6 cascaded relay agents example. o Added the DHCPv6 cascaded relay agents example.
10.3. Changes to draft-ietf-dhc-relay-port-01 10.4. Changes to draft-ietf-dhc-relay-port-01
o Posted the draft in January 2017. o Posted the draft in January 2017.
o Change the DHCPv6 Relay Source Port Option, UDP Source Port field o Change the DHCPv6 Relay Source Port Option, UDP Source Port field
to Downstream Source Port. Add the option handling mechanism for to Downstream Source Port. Add the option handling mechanism for
DHCPv6 server and relay agents. DHCPv6 server and relay agents.
10.4. Changes to draft-ietf-dhc-relay-port-00 10.5. Changes to draft-ietf-dhc-relay-port-00
o Posted first version of working group draft in October 2016. o Posted first version of working group draft in October 2016.
o This draft was renamed from draft-shen-dhc-client-port-03.txt. o This draft was renamed from draft-shen-dhc-client-port-03.txt.
11. Normative References 11. 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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
 End of changes. 9 change blocks. 
14 lines changed or deleted 24 lines changed or added

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