-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2005-01-14, at 11.50, Brian E Carpenter wrote:
John C Klensin wrote:
... but I note that we are still turning over rocks from
which new issues crawl.
And the first year of operation will certainly reveal
other issues, which may move faster than a crawl.
I am deeply convinced we will be revising this BCP after
a year's experience. So I think we will very soon have to
agree to leave some known issues open.
(fyi, the average lifetime of the first two versions of
the IETF standards process and of the Nomcom procedures
was 24 months... it seems to take us a couple of iterations
and ~4 years to get a process BCP right.)
I would like to voice support for Brian's statement. I think that we
need to realise that we can't foresee all issues and our anticipation's
of them are best guesses. There is nothing like real-life experience
and at some point we need start getting that instead of arguing.
- - kurtis -
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1
iQA/AwUBQefksaarNKXTPFCVEQIGHwCg3ubaU2mF7r+1z8evNZ0PUiiP+PoAnA2p
raE6Pf0VPgCk9i38WUebmTX4
=Jx0a
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf