Implement draft-ietf-6man-rfc4941bis
Subsystems (4)
PATCH 1/1 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
This reduces stress on network elements, among other things
* 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.txt | 2 +- include/net/addrconf.h | 2 +- include/net/if_inet6.h | 1 - net/ipv6/addrconf.c | 85 +++++++++++--------------- 4 files changed, 38 insertions(+), 52 deletions(-)
Documentation/networking/ip-sysctl.txt +1 -1
@@ -1807,7 +1807,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/addrconf.h +1 -1
@@ -8,7 +8,7 @@#define MIN_VALID_LIFETIME (2*3600)/* 2 hours */ -#define TEMP_VALID_LIFETIME (7*86400) +#define TEMP_VALID_LIFETIME (2 * 86400)#define TEMP_PREFERRED_LIFETIME (86400)#define REGEN_MAX_RETRY (3)#define MAX_DESYNC_FACTOR (600)
include/net/if_inet6.h +0 -1
@@ -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 +36 -49
154 lines not on this page · raw message
Signature · 1 line
2.26.0
Jakub Kicinski
maintainerQuoted 6 lines · On Wed, 8 Apr 2020 07:44:58 -0300 Fernando Gont wrote:
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
This reduces stress on network elements, among other things
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" anywhereSigned-off-by Fernando Gont <[email protected]>
net-next is currently closed:
https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html#q-how-often-do-changes-from-these-trees-make-it-to-the-mainline-linus-tree
http://vger.kernel.org/~davem/net-next.html
You'll have to resend your change when it opens back up.
Thanks!
Quoted 26 lines · On Wed, 8 Apr 2020 07:44:58 -0300 Fernando Gont <[email protected]> wrote:
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
This reduces stress on network elements, among other things* 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" anywhereSigned-off-by Fernando Gont <[email protected]>--- Documentation/networking/ip-sysctl.txt | 2 +- include/net/addrconf.h | 2 +- include/net/if_inet6.h | 1 - net/ipv6/addrconf.c | 85 +++++++++++--------------- 4 files changed, 38 insertions(+), 52 deletions(-)Documentation/networking/ip-sysctl.txt +0
-0
Documentation/networking/ip-sysctl.txt use_tempaddr - INTEGER · line 1810
Quoted 5 lines
Documentation/networking/ip-sysctl.txt +1
-1@@ -1807,7 +1807,7 @@ use_tempaddr - INTEGER temp_valid_lft - INTEGER valid lifetime (in seconds) for temporary addresses. - Default: 604800 (7 days) + Default: 172800 (2 days)
You can't change defaults for existing users without a really good argument.
Quoted 6 lines · Stephen Hemminger
Quoted 3 lines · On Wed, 8 Apr 2020 07:44:58 -0300 Fernando Gont <[email protected]> wrote:
Implement the upcoming rev of RFC4941 (IPv6 temporary addresses):
https://tools.ietf.org/html/draft-ietf-6man-rfc4941bis-09
[...]
Quoted 8 lines
Documentation/networking/ip-sysctl.txt use_tempaddr - INTEGER · line 1810
Quoted 5 lines
temp_valid_lft- INTEGER
valid lifetime (in seconds) for temporary addresses.Documentation/networking/ip-sysctl.txt +1
-1- Default: 604800 (7 days) + Default: 172800 (2 days)You can't change defaults for existing users without a really good argument.
The number of extra addresses you get when the Valid Lifetime is 7 days tends to exacerbate the stress caused on network elements/devices. There are references in the I-D.
Additionally, the motivation of temporary addresses is indeed privacy and reduced exposure. With a default VL of 7 days, and address that becomes revealed is reachable for one whole week. That's not very "temporary" as the name would imply.
The only use case for a VL 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 probably shouldn't be using a temporary address.
And even more in the era of mobile devices, I'd argue that general applications should be prepared and robust to address changes (nodes swaps wifi <-> 4G, etc.)
This is, of the top of my head, the reason why we decided to modify the default valid lifetime in the upcoming revision of the standard.
Thoughts?
Thanks,
Signature · 4 lines
Fernando Gont SI6 Networks e-mail: [email protected] PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492