draft-ietf-dhc-dhcp4o6-saddr-opt-02.txt   draft-ietf-dhc-dhcp4o6-saddr-opt-03.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: September 18, 2018 L. Sun Expires: September 28, 2018 L. Sun
Tsinghua University Tsinghua University
March 17, 2018 March 27, 2018
DHCPv4 over DHCPv6 Source Address Option Softwire Provisioning using DHCPv4 Over DHCPv6
draft-ietf-dhc-dhcp4o6-saddr-opt-02 draft-ietf-dhc-dhcp4o6-saddr-opt-03
Abstract Abstract
DHCPv4 over DHCPv6 is a mechanism for dynamically configuring IPv4 DHCPv4 over DHCPv6 is a mechanism for dynamically configuring IPv4
over an IPv6-only network. For DHCPv4 over DHCPv6 to function with over an IPv6-only network. For DHCPv4 over DHCPv6 to function with
some IPv4-over-IPv6 softwire mechanisms and deployment scenarios, the some IPv4-over-IPv6 softwire mechanisms and deployment scenarios, the
operator needs to know the IPv6 address that the client will use as operator needs to know the IPv6 address that the client will use as
the source of IPv4-in-IPv6 softwire tunnel. This address, in the source of IPv4-in-IPv6 softwire tunnel. This address, in
conjunction with the client's IPv4 address and (in some deployments), conjunction with the client's IPv4 address and (in some deployments),
the Port Set ID are used to create a binding table entry in the the Port Set ID are used to create a binding table entry in the
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 September 18, 2018. This Internet-Draft will expire on September 28, 2018.
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 2, line 50 skipping to change at page 2, line 50
7.3. Releasing the IPv4 Address Lease and Softwire 7.3. Releasing the IPv4 Address Lease and Softwire
Source Address . . . . . . . . . . . . . . . . . . . . . 10 Source Address . . . . . . . . . . . . . . . . . . . . . 10
7.4. OPTION_S46_BIND_IPV6_PREFIX Validation Behavior . . . . . 10 7.4. OPTION_S46_BIND_IPV6_PREFIX Validation Behavior . . . . . 10
7.5. Client and Server Softwire Source Address Mismatch . . . 11 7.5. Client and Server Softwire Source Address Mismatch . . . 11
7.6. Use With Dynamic, Shared IPv4 Addresses . . . . . . . . . 11 7.6. Use With Dynamic, Shared IPv4 Addresses . . . . . . . . . 11
8. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 11 8. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Changing the Bound IPv6 Source Address . . . . . . . . . 11 8.1. Changing the Bound IPv6 Source Address . . . . . . . . . 11
9. Security Considerations . . . . . . . . . . . . . . . . . . . 12 9. Security Considerations . . . . . . . . . . . . . . . . . . . 12
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
12.1. Normative References . . . . . . . . . . . . . . . . . . 12 12.1. Normative References . . . . . . . . . . . . . . . . . . 13
12.2. Informative References . . . . . . . . . . . . . . . . . 12 12.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
Deterministic IPv4-over-IPv6 transition technologies require that Deterministic IPv4-over-IPv6 transition technologies require that
elements are pre-configured with binding rules for routing traffic to elements are pre-configured with binding rules for routing traffic to
clients. This places a constraint on the choice of address used as clients. This places a constraint on the choice of address used as
the client's softwire source address: it must use a pre-determined the client's softwire source address: it must use a pre-determined
prefix which is usually configured on the home gateway device. prefix which is usually configured on the home gateway device.
[RFC7597] describes a DHCPv6 based mechanism for provisioning such [RFC7597] describes a DHCPv6 based mechanism for provisioning such
skipping to change at page 12, line 24 skipping to change at page 12, line 24
10. IANA Considerations 10. IANA Considerations
IANA is requested to assign the OPTION_DHCP4O6_S46_SADDR option code IANA is requested to assign the OPTION_DHCP4O6_S46_SADDR option code
from the "BOOTP Vendor Extensions and DHCP Options" registry from the "BOOTP Vendor Extensions and DHCP Options" registry
maintained at http://www.iana.org/assignments/bootp-dhcp-parameters. maintained at http://www.iana.org/assignments/bootp-dhcp-parameters.
IANA is requested to assign the OPTION_S46_BIND_IPV6_PREFIX option IANA is requested to assign the OPTION_S46_BIND_IPV6_PREFIX option
code from the DHCPv6 "Option Codes" registry maintained at 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 update the entry for DHCPv6 Option S46_BR (90)
in the table at https://www.iana.org/assignments/dhcpv6-parameters as
follows:
Old entry:
| 90 | S46_BR | No | No |
New entry:
| 90 | S46_BR | Yes | No |
IANA is also requested to make a new entry for
OPTION_S46_BIND_IPV6_PREFIX TBD1) in the table at
https://www.iana.org/assignments/dhcpv6-parameters:
| TBD1 |OPTION_S46_BIND_IPV6_PREFIX| Yes | Yes |
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Ted Lemon, Lishan Li, Tatuya Jinmei, The authors would like to thank Ted Lemon, Lishan Li, Tatuya Jinmei,
Jonas Gorski and Razvan Becheriu for their contributions and Jonas Gorski and Razvan Becheriu for their contributions and
comments. comments.
12. References 12. References
12.1. Normative References 12.1. Normative References
 End of changes. 6 change blocks. 
8 lines changed or deleted 26 lines changed or added

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