From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 113: | Line 113: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
# DHCPv4 should continue operating as before '''TBD''': check if client-identifier is affected by this change! | |||
# Prefix Delegation over PPP '''MUST''' work without manual intervention | |||
# DUID '''MUST NOT''' be changed between connections (client runs) | |||
# DUID '''MUST NOT''' be changed as the result of physical device removal/system restart/system upgrade/ | |||
== User Experience == | == User Experience == | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Users which use IPv4 only should not be affected by the change. | |||
Users of IPv6 installations may need to notify their ISP about DUID changes or manually specify old DUID in leases file | |||
== Dependencies == | == Dependencies == | ||
| Line 124: | Line 128: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
None | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Revert back to current DUID. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 138: | Line 142: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
This is Fedora (systemd enabled systems) specific change so the documentation should be written and submitted upstream | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Release Notes == | == Release Notes == | ||
Revision as of 12:26, 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:
- Posible violation of RFC 3315
- DUID cannot be assembled due to lack of hardware address which leads dhclient to exit with error and manual intervention is required. Bug#626514
- 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
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)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: 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
- DHCPv4 should continue operating as before TBD: check if client-identifier is affected by this change!
- Prefix Delegation over PPP MUST work without manual intervention
- DUID MUST NOT be changed between connections (client runs)
- DUID MUST NOT be changed as the result of physical device removal/system restart/system upgrade/
User Experience
Users which use IPv4 only should not be affected by the change. Users of IPv6 installations may need to notify their ISP about DUID changes or manually specify old DUID in leases file
Dependencies
None
Contingency Plan
- Contingency mechanism: Revert back to current DUID.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
This is Fedora (systemd enabled systems) specific change so the documentation should be written and submitted upstream
Release Notes
Insert non-formatted text here