draft-ietf-dhc-dhcp4o6-saddr-opt-05.txt   draft-ietf-dhc-dhcp4o6-saddr-opt-06.txt 
DHCWG I. Farrer DHCWG I. Farrer
Internet-Draft Deutsche Telekom AG Internet-Draft Deutsche Telekom AG
Updates: 7598 (if approved) Q. Sun Updates: 7598 (if approved) Q. Sun
Intended status: Standards Track Y. Cui Intended status: Standards Track Y. Cui
Expires: April 5, 2019 L. Sun Expires: April 8, 2019 L. Sun
Tsinghua University Tsinghua University
October 2, 2018 October 5, 2018
Softwire Provisioning using DHCPv4 Over DHCPv6 Softwire Provisioning using DHCPv4 Over DHCPv6
draft-ietf-dhc-dhcp4o6-saddr-opt-05 draft-ietf-dhc-dhcp4o6-saddr-opt-06
Abstract Abstract
DHCPv4 over DHCPv6 (RFC7341) is a mechanism for dynamically DHCPv4 over DHCPv6 (RFC7341) is a mechanism for dynamically
configuring IPv4 over an IPv6-only network. For DHCPv4 over DHCPv6 configuring IPv4 over an IPv6-only network. For DHCPv4 over DHCPv6
(DHCP 4o6) to function with some IPv4-over-IPv6 softwire mechanisms (DHCP 4o6) to function with some IPv4-over-IPv6 softwire mechanisms
and deployment scenarios (e.g., RFC7596 or RFC7597), the operator and deployment scenarios (e.g., RFC7596 or RFC7597), the operator
needs to know the IPv6 address that the client will use as the s needs to know the IPv6 address that the client will use as the s
ource of IPv4-in-IPv6 softwire tunnel. This address, in conjunction ource of IPv4-in-IPv6 softwire tunnel. This address, in conjunction
with the client's IPv4 address, and (in some deployments) the Port with the client's IPv4 address, and (in some deployments) the Port
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 April 5, 2019. This Internet-Draft will expire on April 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 11, line 16 skipping to change at page 11, line 16
7.5. Client and Server Softwire Source Address Mismatch 7.5. Client and Server Softwire Source Address Mismatch
If the client receives a DHCPACK message with an If the client receives a DHCPACK message with an
OPTION_DHCP4O6_S46_SADDR containing an IPv6 address which differs OPTION_DHCP4O6_S46_SADDR containing an IPv6 address which differs
from its active softwire source address, the client SHOULD wait for a from its active softwire source address, the client SHOULD wait for a
randomized time interval and then resend the DHCPREQUEST message with randomized time interval and then resend the DHCPREQUEST message with
the correct softwire source address. [RFC2131] Section 4.1 descibes the correct softwire source address. [RFC2131] Section 4.1 descibes
the retransmission backoff interval process. the retransmission backoff interval process.
The default time minimum time for the client to attempt The default minimum time for the client to attempt retransmission is
retransmission is 60 seconds. If, after this time has expired, the 60 seconds. If, after this time has expired, the client has not
client has not received a DHCPACK message with the correct bound IPv6 received a DHCPACK message with the correct bound IPv6 address,
address, client MAY send a DHCPRELEASE message and re-start the client MAY send a DHCPRELEASE message and re-start the process
process described in Section 7. The re-try interval should be described in Section 7. The re-try interval should be configurable
configurable and aligned with any server policy defining the minimum and aligned with any server policy defining the minimum time interval
time interval for client address updates as described in Section 8.1. for client address updates as described in Section 8.1.
7.6. Use With Dynamic, Shared IPv4 Addresses 7.6. Use With Dynamic, Shared IPv4 Addresses
[RFC7618] describes a mechanism for using DHCPv4 to distribute [RFC7618] describes a mechanism for using DHCPv4 to distribute
dynamic, shared IPv4 addresses to clients. The mechanism described dynamic, shared IPv4 addresses to clients. The mechanism described
in this document is compatible with IPv4 address sharing, and can be in this document is compatible with IPv4 address sharing, and can be
enabled by following the process described in Section 6 of [RFC7618]. enabled by following the process described in Section 6 of [RFC7618].
8. Server Behavior 8. Server Behavior
skipping to change at page 13, line 6 skipping to change at page 13, line 6
IANA is requested to assign the OPTION_S46_BIND_IPV6_PREFIX (TBD1) IANA is requested to assign the OPTION_S46_BIND_IPV6_PREFIX (TBD1)
option code from the DHCPv6 "Option Codes" registry maintained at option code from the DHCPv6 "Option Codes" registry maintained at
http://www.iana.org/assignments/dhcpv6-parameters. http://www.iana.org/assignments/dhcpv6-parameters.
IANA is requested to assign the OPTION_DHCP4O6_S46_SADDR (TBD2) IANA is requested to assign the OPTION_DHCP4O6_S46_SADDR (TBD2)
option code from the "BOOTP Vendor Extensions and DHCP Options" option code from the "BOOTP Vendor Extensions and DHCP Options"
registry maintained at http://www.iana.org/assignments/bootp-dhcp- registry maintained at http://www.iana.org/assignments/bootp-dhcp-
parameters. parameters.
IANA is requested to update the entry for DHCPv6 Option S46_BR (90) IANA is requested to update the entry for DHCPv6 Option S46_BR (90)
in the table at https://www.iana.org/assignments/dhcpv6-parameters as in the Option Codes table at https://www.iana.org/assignments/
follows: dhcpv6-parameters as follows:
Old entry: Old entry:
| 90 | S46_BR | No | No | | 90 | S46_BR | No | No |
New entry: New entry:
| 90 | S46_BR | Yes | No | | 90 | S46_BR | Yes | No |
IANA is also requested to make a new entry for IANA is also requested to make a new entry for
 End of changes. 6 change blocks. 
13 lines changed or deleted 13 lines changed or added

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