On Tue, Mar 17, 2009 at 09:47:20AM +0200, Alper Yegin wrote:
> This I-D is not adopted by DSLF.
> It is just one of the candidate solutions.
> DSLF is expecting IETF's evaluation.
> If IETF does not give the green light, this ("damaging") I-D does not get
> adopted by the DSLF.
I'm getting conflicting feedback on this. I suspect you're in a
position to know better than me; but the authors have said that they
currently have "running lab code".
This insight to me is a threat to deploy. There is no other reason to
make that statement other than to say, "It is already in our firmware."
We are in a recession here in the US, and no one wants to hear that
they have spent money building an object they can't sell. They will
deploy it just to pretend they're making money off of it and no one
has to get fired.
So I wonder if DSLF is in any greater position of power to control
release than IETF is...?
I am thinking it is the draft's authors, and neither the IETF nor
DSLF/Broadband Forum about which we should be concerned, and therefore
address.
> If IETF is going to produce any official document on this, it should be
> titled "EAP over DHCP considered harmful" IMHO.
I was rather thinking about the benefits of having the protocol
documented clearly, from the point of view of a draft analyzing it.
--
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
Attachment:
pgpRYPC9IqUBo.pgp
Description: PGP signature