Hello, Teemu. My comments are below. 2008/10/23 <[EMAIL PROTECTED]>: > Hi, > >>-----Original Message----- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >>Behalf Of ext Ted Lemon >>Sent: 16 October, 2008 20:49 >>To: Iljitsch van Beijnum >>Cc: David W. Hankins; [EMAIL PROTECTED]; List Mailing; DHC WG >>Subject: Re: [dhcwg] Brokenness of specs w.r.t. client >>behavior with M&O bits >> >>In order for this to be a valid rejoinder, it would have to be >>the case that the cellular industry was planning to use IPv6 autoconf >>combined with RAs to get IPv6 addresses. It's not my understanding >>that this is the case. In fact, we added the DHCPv6 rapid commit >>option specifically for low-power applications like the cell phones. > > At least latest 3GPP specifications support solely SLAAC and stateless > DHCPv6, so DHCPv6 for stateful address autoconfiguration is currently > not supported per latest 3GPP standard at all (see chapter 5.3.1.1 at > 3GPP 23.401 > http://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-830.zip ): > --cut-- > Both EPS network elements and UE shall support the following mechanisms: > a. IPv4 address allocation via default bearer activation, if IPv4 is > supported. > b. /64 IPv6 prefix allocation via IPv6 Stateless Address > autoconfiguration according to RFC 4862 [18], if IPv6 is supported; > > Furthermore, the Protocol Configuration Options may be used during > bearer activation to configure parameters which are needed for IP > address allocation. > > Both EPS network elements and UE may support the following mechanisms: > a. IPv4 address allocation and IPv4 parameter configuration after the > attach procedure via DHCPv4 according to RFC 2131 [19] and RFC 4039 > [25]; > b. IPv6 parameter configuration via Stateless DHCPv6 according to RFC > 3736 [20]. > --cut-- > > Therefore there's no problem for a host to think how to configure its > IPv6 address - only single way is supported. > > The host to always having guaranteed /64 bit prefix on 3GPP access is > also advantageous for network connection sharing use-cases, as the host > can simply act as a ND proxy. If the host would be using DHCPv6 and get > just a single /128 IPv6 address, how the host could then share the > connection for other devices (like laptop) in LAN behind the host? By > utilizing DHCPv6 Prefix Delegation - but is it guaranteed that a host > using DHCPv6 for address configuration _always_ can ask also for a > prefix from DHCPv6 server with DHCPv6 PD? By acting as bridge - but what > if the hosts in the LAN do not support stateful DHCPv6? > As for your question, I would say that it depends on implementations. AFAIK, there are already several opensources like ISC DHCP which supports IA_NA(maybe IA_TA) as well as IA_PD. And Windows 2008 server also does. Even though details of implementations may be different, site prefixes are derived from delegated prefixes and the LAN interface is configured with addresses from the site prefixes as pre-configured policy. Then, site prefixes are advertised through following RA messages from the LAN interface and hosts have addresses configured via SLAAC. However, I am not sure that ND proxy has been deployed well.
Joseph > Best regards, > > Teemu > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- > -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
