Skip to contentSkip to conversation

ipv6: Implement draft-ietf-6man-rfc4941bis

PATCH Applied Fernando Gont 2 participants 2 messages May 1, 2020 – May 7, 2020

Subsystems (4)
lore
Share & tools
lore
#0 lore raw

PATCH v3 1/1 ipv6: Implement draft-ietf-6man-rfc4941bis

Implement the upcoming rev of RFC4941 (IPv6 temporary addresses):
https://tools.ietf.org/html/draft-ietf-6man-rfc4941bis-09

* Reduces the default Valid Lifetime to 2 days
The number of extra addresses employed when Valid Lifetime was 7 days exacerbated the stress caused on network elements/devices. Additionally, the motivation for temporary addresses is indeed privacy and reduced exposure. With a default Valid Lifetime of 7 days, an address that becomes revealed by active communication is reachable and exposed for one whole week. The only use case for a Valid Lifetime of 7 days could be some application that is expecting to have long lived connections. But if you want to have a long lived connections, you shouldn't be using a temporary address in the first place. Additionally, in the era of mobile devices, general applications should nevertheless be prepared and robust to address changes (e.g. nodes swap wifi <-> 4G, etc.)

* Employs different IIDs for different prefixes
To avoid network activity correlation among addresses configured for different prefixes

* Uses a simpler algorithm for IID generation
No need to store "history" anywhere

---
 Documentation/networking/ip-sysctl.rst |  2 +-
 include/net/if_inet6.h                 |  1 -
 net/ipv6/addrconf.c                    | 91 +++++++++++---------------
 3 files changed, 40 insertions(+), 54 deletions(-)
Documentation/networking/ip-sysctl.rst +1 -1
index 50b440d29a13..b72f89d5694c 100644
@@ -2065,7 +2065,7 @@ use_tempaddr - INTEGER
 temp_valid_lft - INTEGER
 	valid lifetime (in seconds) for temporary addresses.
 
-	Default: 604800 (7 days)
+	Default: 172800 (2 days)
 
 temp_prefered_lft - INTEGER
 	Preferred lifetime (in seconds) for temporary addresses.
include/net/if_inet6.h +0 -1
index a01981d7108f..212eb278bda6 100644
@@ -190,7 +190,6 @@ struct inet6_dev {
 	int			dead;
 
 	u32			desync_factor;
-	u8			rndid[8];
 	struct list_head	tempaddr_list;
 
 	struct in6_addr		token;
net/ipv6/addrconf.c +39 -52

160 lines not on this page · raw message

Signature · 1 line
2.26.0
maintainer Applied
#1 lore raw

From: Fernando Gont <[email protected]>
Date: Fri, 1 May 2020 00:51:47 -0300

Quoted 18 lines

Implement the upcoming rev of RFC4941 (IPv6 temporary addresses):
https://tools.ietf.org/html/draft-ietf-6man-rfc4941bis-09

* Reduces the default Valid Lifetime to 2 days
The number of extra addresses employed when Valid Lifetime was 7 days exacerbated the stress caused on network elements/devices. Additionally, the motivation for temporary addresses is indeed privacy and reduced exposure. With a default Valid Lifetime of 7 days, an address that becomes revealed by active communication is reachable and exposed for one whole week. The only use case for a Valid Lifetime of 7 days could be some application that is expecting to have long lived connections. But if you want to have a long lived connections, you shouldn't be using a temporary address in the first place. Additionally, in the era of mobile devices, general applications should nevertheless be prepared and robust to address changes (e.g. nodes swap wifi <-> 4G, etc.)

Quoted 8 lines

* Employs different IIDs for different prefixes
To avoid network activity correlation among addresses configured for different prefixes

* Uses a simpler algorithm for IID generation
No need to store "history" anywhere

Applied, thanks.