Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-11-03 Thread hyunwook cha
Hello, all. I would like to share my interests on this issue and discuss DHCPv6 based solution more. Solutions suggested by Pekka are below. 1) run DHCPv6 again, with a different DUID or client identifier (could it get more /128's that way, 2) use DHCPv6 IAs to request multiple addresses? Then it

RE: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-11-03 Thread teemu.savolainen
Hi Pekka, >-Original Message- >From: ext Pekka Savola [mailto:[EMAIL PROTECTED] >Sent: 30 October, 2008 09:26 >But, maybe there is an implementable workaround to this >operational issue. Would it be possible for the host to >either 1) run DHCPv6 again, with a different DUID or client

RE: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-11-02 Thread teemu.savolainen
>Pardon my ignorance. Is there a concrete case of this in some access > >network standard? > >(I heard some rumors thereabout) I have heard rumors as well that were in favor of using DHCPv6 for address allocation also in some cellular accesses. By my understanding this is not yet so concrete pr

Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-11-02 Thread Rémi Denis-Courmont
On Mon, 03 Nov 2008 09:59:03 +1300, Brian E Carpenter <[EMAIL PROTECTED]> wrote: >> Failing silently or loudly are no options. You cannot blame the operator >> if you expect him to subsidized your device sale. You cannot fail if your >> competitor "just works" by using NAPT66. > > Agreed, but you

Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-11-02 Thread Brian E Carpenter
On 2008-10-31 21:09, Rémi Denis-Courmont wrote: > On Fri, 31 Oct 2008 15:31:27 +1300, Brian E Carpenter > <[EMAIL PROTECTED]> wrote: >>> Well I'm not completely certain whether involving users here would >>> provide very good experience, >> I see your argument, but failing silently doesn't seem lik

Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-10-31 Thread Rémi Denis-Courmont
On Fri, 31 Oct 2008 15:31:27 +1300, Brian E Carpenter <[EMAIL PROTECTED]> wrote: >> Well I'm not completely certain whether involving users here would >> provide very good experience, > > I see your argument, but failing silently doesn't seem like a > good idea. It is only worse. What will actua

Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-10-30 Thread Brian E Carpenter
Teemu, On 2008-10-30 18:42, [EMAIL PROTECTED] wrote: > Brian, > > (changed topic to be more descriptive) > >>> Consider cellular host case: >>> - host implements e.g. ND proxy and DHCPv6 PD for WAN connection >>> sharing >>> - host attaches to a network where only DHCPv6 happens to be used >>

Re: /128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-10-30 Thread Pekka Savola
On Thu, 30 Oct 2008, [EMAIL PROTECTED] wrote: Consider cellular host case: - host implements e.g. ND proxy and DHCPv6 PD for WAN connection sharing - host attaches to a network where only DHCPv6 happens to be used - host gets single /128 IPv6 address from DHCPv6 - host tries to get some prefixes

/128 address allocation and "localized IPv6 address space exhaustion", was RE: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits

2008-10-29 Thread teemu.savolainen
Brian, (changed topic to be more descriptive) >> Consider cellular host case: >> - host implements e.g. ND proxy and DHCPv6 PD for WAN connection >> sharing >> - host attaches to a network where only DHCPv6 happens to be used >> - host gets single /128 IPv6 address from DHCPv6 >> - host tries