Re: [v6ops] Focused discussion: draft-ietf-v6ops-unique-ipv6-prefix-per-host

["VAN DE VELDE, Gunter (Gunter)" <[e-mail]>]

<>snip<>
I don't understand the text "To accomodate this the WLAN-GW can periodically perform a Subscriber Host Connectivity Verification (i.e. periodically ping each IPv6 UE...)". It seems to me that the the whole point of this approach is that the WLAN-GW doesn't need to know the individual IPv6 addresses formed by the hosts. Also, there's no guarantee that devices will respond to ping. I think better solutions are:

  *
  *   The AP could inform the WLAN-GW of when a subscriber disappeared.
  *   The WLAN-GW could time out any GRE interface that had not received any packets in the last X minutes, or if the customer's /64 prefix had not originated any packets in the last X minutes.

<>end snip<>

Yes, this process is indeed a mistake in added in this text. What is happening in reality is a ND exchange check if the subscriber is still alive. It was only list of corrections to make in the next revision of the text.
With DHCPv6 we have the Address lifetime as additional parameter, but we are not speaking about DHCPv6 in this draft due to lack of support for critical mass of UE's.

The AP is simple device with little control logic… most commonly it is for community Wifi simply bridging from Wireless to a tunnel ( to a GRE) and the Wireless Lan controller does all the smartness of the subscriber management. That way the wireless LAN controller doe not have to rely upon fancy features available on the AP.

G/