![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Iljitsch van Beijnum <iljitsch at muada.com> writes: > Sure, trying to implement something brings out bugs in the > specification, but those are usually relatively minor things that > don't go to the design of the protocol. And wide deployment generally > shows that a protocol could have been better in one regard or > another, and that some parts of it don't turn out to be useful in > practice. I don't agree, several IETF protocols that I've implemented while still drafts have had major design changes done them because of an implementation exposed serious flaws in them (secsh-gss, pk-init). There are also specifications that would have been good to have implementations before leaving the WG, because they are not implemented-able as is (spkm). Love
Attachment:
pgp1EjhGqnhHm.pgp
Description: PGP signature
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.