From Fedora Project Wiki
No edit summary
No edit summary
Line 25: Line 25:
== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
DHCP client and server should use [https://tools.ietf.org/html/rfc6355 RFC 6355] DUID UUID for DHCPv6 operations


== Owner ==
== Owner ==
Line 59: Line 60:


<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Currently DUID LL(T) is used for IPv6 address assignment and prefix delegation. This lead to  issues with devices which don't have hardware address assigned (like PPP) or devices which are not constantly assigned to the "server" (like wireless/usb devices
etc).  There are two main issues caused by this:
# Posible violation of [https://tools.ietf.org/html/rfc3315#section-9.4 RFC 3315]
# DUID cannot be assembled due to lack of hardware address which leads dhclient to exit with error and manual intervention is required. [https://bugzilla.redhat.com/show_bug.cgi?id=626514 Bug#626514]
# DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages [https://bugzilla.redhat.com/show_bug.cgi?id=1163379 Bug#1163379]


== Benefit to Fedora ==
== Benefit to Fedora ==

Revision as of 12:17, 16 March 2018


WIP! dhclient switch to DUID-UUID

Summary

DHCP client and server should use RFC 6355 DUID UUID for DHCPv6 operations

Owner

  • Name: Pavel Zhukov
  • Email: <landgraf@fedoraproject.org>
  • Release notes owner:

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: 2018-03-16
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Currently DUID LL(T) is used for IPv6 address assignment and prefix delegation. This lead to issues with devices which don't have hardware address assigned (like PPP) or devices which are not constantly assigned to the "server" (like wireless/usb devices etc). There are two main issues caused by this:

  1. Posible violation of RFC 3315
  2. DUID cannot be assembled due to lack of hardware address which leads dhclient to exit with error and manual intervention is required. Bug#626514
  3. DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages Bug#1163379

Benefit to Fedora

Currently DUID LL(T) is used for IPv6 address assignment and prefix delegation. This lead to issues with devices which don't have hardware address assigned (like PPP devices) or devices which are not constantly assigned to the "server" (like wireless/usb devices etc). There are two main issues caused by this:

  1. DUID cannot be assembled due to lack of hardware address which leads dhclient to exit with error and manual intervention is required. Bug#626514
  2. DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages Bug#1163379

Changing default to DUID UUID should solve mentioned issue and bring consistency within the distribution (NetworkManager uses DUID UUID from the beginning). As this change depends on systemd feature (machineid) it may be hard to get patches merged upstream


Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

This impact all installation which use dhclient to obtain ipv6 address or prefix. During the upgrade default duid changes from duid-ll to duid-uuid. Manual intervention is needed to protect old duid (or to update) is not decided yet.

How To Test

DHCP DUID is

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes

Insert non-formatted text here