Hello, Teemu. Thank you for your clarification.
>>Since DHCPv6 server is also able to assign multiple addresses >>to single client depending on the poliy, the host can activate >>its server with the assigned address except the one used by >>itself if it has >>DHCPv6 server installed. Then, other hosts in LAN can >>configure their addresses through DHCPv6 which might be >>invoked by proxed RA. Yes, this approach shows more >>restriction than SLAAC plus ND proxy apparently. > > Sounds otherwise feasible approach, but that requires the other hosts to > support DHCPv6, which isn't always the case as DHCPv6 support is not > mandatory, right? At least currently not supported by all IPv6 enabled > hosts. > Right. However, you are assuming that provider network is just willing to give /128 through DHCPv6. It seems that there are no feasible ways for hosts w/o DHCPv6 clients except 6to6 NAPT about which I do not want to go further. Besides this point, above suggestion is not a complete solution because of the points below. - DHCPv6 client can not request addresses on behalf of other clients. If it obtains multiple addresses via multiple IA configurations, all addresses are just used for the interface on which the client is running. So, this means that user should remove addresses from the interface manually and also configure DHCPv6 server with these addresses manually. - It is not supported to make both a binding assinged by the remote server in the provider network and a binding assigned by the local server in the gateway(the host) consistent because of different contexts (transactions). Thus, I would like to suggest DHCPv6 proxy concept to address these issues. That is, if the gateway acting as a DHCPv6 proxy receivs a DHCPv6 message from a client on the LAN, it initiates new transaction for exchanging messages on behalf of the client. Through the proxy, clients on the LAN can obtain /128 addresses directly from the server and manage bindings in the server directly while the server sees only the gateway. Joseph since local hosts in the LAN can not 2008/11/3 <[EMAIL PROTECTED]>: > Hi Joseph, > >>Right as long as DHCPv6 server can assign only one address to the host. >>One more thing I would like to know is whether the host is >>allowed to configure multiple arbitrary addresses in the >>scenario of SLAAC plus ND proxy in the service provider's >>view. If other hosts in LAN configure addresses through SLAAC >>plus ND proxy, outbound traffics forwarded by the host acting >>as a gateway have unknown source IPv6 addresses while source >>MAC address is same. Are there any issues on this point? > > The host is allowed to pick whatever IID it wants and also to implement > RFC4941 privacy extensions. > > In 3GPP access the link between host acting as a gateway and access > router is a point-to-point tunneled link, where MAC addresses are not > used. Actually hosts do not necessarily even have MAC address available. > > The access router acts just based on prefixes and thus number of > addresses can be configured into simultaneous use from the /64 prefix > host is allocated with. > >>Since DHCPv6 server is also able to assign multiple addresses >>to single client depending on the poliy, the host can activate >>its server with the assigned address except the one used by >>itself if it has >>DHCPv6 server installed. Then, other hosts in LAN can >>configure their addresses through DHCPv6 which might be >>invoked by proxed RA. Yes, this approach shows more >>restriction than SLAAC plus ND proxy apparently. > > Sounds otherwise feasible approach, but that requires the other hosts to > support DHCPv6, which isn't always the case as DHCPv6 support is not > mandatory, right? At least currently not supported by all IPv6 enabled > hosts. > > Best regards, > > Teemu > -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
