From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...")
 
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 
 
 
<!-- Self Contained or System Wide Change Proposal?
 
<!-- Self Contained or System Wide Change Proposal?
 
Use this guide to determine to which category your proposed change belongs to.
 
Use this guide to determine to which category your proposed change belongs to.
Line 23: Line 21:
  
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= Change Proposal Name <!-- The name of your change proposal --> =
+
= WIP! dhclient switch to DUID-UUID<!-- The name of your change proposal --> =
  
 
== Summary ==
 
== Summary ==
Line 33: Line 31:
 
This should link to your home wiki page so we know who you are.  
 
This should link to your home wiki page so we know who you are.  
 
-->
 
-->
* Name: [[User:FASAcountName| Your Name]]
+
* Name: [[User:Landgraf| Pavel Zhukov]]
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: <landgraf@fedoraproject.org>
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
Line 64: Line 62:
 
== Benefit to Fedora ==
 
== 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:
 +
# DUID cannot be assembled due to lack of hardware address which leads dhclient to exit with error and manual intervention is required.
 +
# DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages
 +
Changing default to DUID UUID should solve mentioned issue and bring consistency within the distribution (NetworkManager uses DUID UUID from the beginning).
 
    
 
    
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
Line 91: Line 93:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
+
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 ==
 
== How To Test ==
Line 109: Line 111:
  
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
+
DHCP DUID is
  
 
== User Experience ==
 
== User Experience ==
Line 151: Line 153:
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
  
<!-- Select proper category, default is Self Contained Change -->
+
[[Category:SystemWideChange]]
[[Category:SelfContainedChange]]
 
<!-- [[Category:SystemWideChange]] -->
 
 
<nowiki>Insert non-formatted text here</nowiki>
 
<nowiki>Insert non-formatted text here</nowiki>

Revision as of 12:06, 16 March 2018


WIP! dhclient switch to DUID-UUID

Summary

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

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.
  2. DUID is changed between dhclient restarts as the result ISP doesn't delegate prefix which cause delays and connection outages

Changing default to DUID UUID should solve mentioned issue and bring consistency within the distribution (NetworkManager uses DUID UUID from the beginning).


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