RE: DHCP failures (was RE: Do you want to have more meetings outsi de US ?)

["Tony Hain" <alh-ietf@tndh.net>]

I did not say that DHCP should be deprecated. There are real-world
situations like the ones that took down the IETF DHCP service, that are
clearly operational/implementation/deployment rather than protocol issues.
Just because some organizations run DHCP does not mean everyone else MUST
because the IETF elite refuse to allow an operationally different
alternative to be standardized. 

Tony

> -----Original Message-----
> From: Durand, Alain [mailto:Alain_Durand@cable.comcast.com]
> Sent: Thursday, August 02, 2007 1:26 PM
> To: Jari Arkko; alh-ietf@tndh.net
> Cc: marc.blanchet@viagenie.ca; v6ops@ops.ietf.org
> Subject: RE: DHCP failures (was RE: Do you want to have more meetings
> outsi de US ?)
> 
> I agree. Cable networks have proven that DHCP can be scaled
> to tens of million of leases...
> 
> The fact that something went wrong at IETF is no proof
> that the model is broken.
> 
>   - Alain.
> 
> > -----Original Message-----
> > From: owner-v6ops@ops.ietf.org
> > [mailto:owner-v6ops@ops.ietf.org] On Behalf Of Jari Arkko
> > Sent: Thursday, August 02, 2007 3:53 PM
> > To: alh-ietf@tndh.net
> > Cc: marc.blanchet@viagenie.ca; v6ops@ops.ietf.org
> > Subject: RE: DHCP failures (was RE: Do you want to have more
> > meetings outsi de US ?)
> >
> > I may be missing some context (I'm bandwidth challenged right
> > now and unable to check archives). But its unclear to me
> > where you jumped to the conclusion that DHCP problems in
> > Chicago had something to do with a specific protocol and that
> > this implies we need to deploy an alternate solution in IPv6.
> > If anything, multiple solutions seem to increase the
> > likelihood of interop and configuration problems.
> >
> > Jari
> >
> >
> >