Subject: [6tisch-security] address to use for Join Proxy

From: Michael Richardson <[email-masked]>
Date: Thu, 09 Mar 2017 18:49:12 -0500

One of the constraints about using the IPIP proxy method is that the Join
Proxy has to advertise/coordinate the same IP address.  That is, the JRC
needs to have a LL address configured which the Join Proxy advertises as the
target.  This is so that the UDP/TCP state is correct.

One possible way to deal with this is to use a well-known anycast LL address.
It looks easy to ask IANA to allocate one.

https://bitbucket.org/mcr314/draft-ietf-6tisch-minimal-security/commits/bf3646fa7555dcb620fa8e9e153d9850ec5e75d6

+A pledge finds the layer-2 address of the Join Proxy by looking at the
+EUI64 source address of enhanced beacons it has received that have the
+Network ID extension,  and have the Join Proxy bit set.
+The Layer-3 address is the anycast address TBD1.
+
+The pledge need not do ND for the Join Proxy (which requires an expensive multicast),
+but rather can form the layer-2 address directly from the EUI-64 that was seen.
+
+The pledge uses it's link-local address when speaking to the JRC via the
Join Proxy.
+

https://bitbucket.org/mcr314/draft-ietf-6tisch-minimal-security/commits/af518a119d81ef52d217088ad16d6c91183c3874

+This document allocates the address TBD1 from the
+Internet Protocol Version 6 (IPv6) Anycast Addresses registry.
+
+https://www.iana.org/assignments/ipv6-anycast-addresses/ipv6-anycast-addresses.xhtml

--
Michael Richardson <[email-masked]>, Sandelman Software Works
 -= IPv6 IoT consulting =-