[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-ietf-ipsec-ciph-cbc-02.txt
Ted,
I like proposal B also.
This does suggest something for consideration... would it be possible
to establish a "registry" for this sort of information? In other
words, a repository for information about things like weak keys, which
is updated by a process less rigorous and time consuming than the
regular IETF document process?
While it clearly is undesirable for mistakes to creep into a listing
of weak keys, the consequences of such mistakes are nowhere near as
serious as messing up protocols or distributed algorithms. And there
is no problem at all with having two ends use different editions of
such a list.
Does the IETF process have this sort of thing at the moment (other
than "Assigned numbers" that is)?
paul
Follow-Ups:
References: