netdev - Re: [PATCH net-next] net: ipv6: add tokenized interface identifier support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130408.165758.621291267677314731.davem@davemloft.net>
Date:	Mon, 08 Apr 2013 16:57:58 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	dborkman@...hat.com
Cc:	netdev@...r.kernel.org, hannes@...essinduktion.org,
	yoshfuji@...ux-ipv6.org, tgraf@...g.ch
Subject: Re: [PATCH net-next] net: ipv6: add tokenized interface identifier
 support

From: Daniel Borkmann <dborkman@...hat.com>
Date: Mon,  8 Apr 2013 16:01:30 +0200

> This patch adds support for IPv6 tokenized IIDs, that allow
> for administrators to assign well-known host-part addresses
> to nodes whilst still obtaining global network prefix from
> Router Advertisements. It is currently in draft status.
> 
>   The primary target for such support is server platforms
>   where addresses are usually manually configured, rather
>   than using DHCPv6 or SLAAC. By using tokenised identifiers,
>   hosts can still determine their network prefix by use of
>   SLAAC, but more readily be automatically renumbered should
>   their network prefix change. [...]
> 
>   The disadvantage with static addresses is that they are
>   likely to require manual editing should the network prefix
>   in use change.  If instead there were a method to only
>   manually configure the static identifier part of the IPv6
>   address, then the address could be automatically updated
>   when a new prefix was introduced, as described in [RFC4192]
>   for example.  In such cases a DNS server might be
>   configured with such a tokenised interface identifier of
>   ::53, and SLAAC would use the token in constructing the
>   interface address, using the advertised prefix. [...]
> 
>   http://tools.ietf.org/html/draft-chown-6man-tokenised-ipv6-identifiers-02
> 
> The implementation is partially based on top of Mark K.
> Thompson's proof of concept. However, it uses the Netlink
> interface for configuration resp. data retrival, so that
> it can be easily extended in future. Successfully tested
> by myself.
> 
> Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>
> Cc: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
> Cc: Thomas Graf <tgraf@...g.ch>
> Signed-off-by: Daniel Borkmann <dborkman@...hat.com>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html