Re: I-D Action: draft-ietf-krb-wg-des-die-die-die-02.txt

Sam Hartman <[email protected]>
Newsgroups gmane.ietf.krb-wg
Message-ID <[email protected]>
>>>>> "Tom" == Tom Yu <[email protected]> writes:

    Tom> Simo Sorce <[email protected]> writes:
    >> I am for narrowing the scope to DES and getting this standard out
    >> ASAP.  It has been bounced enough, and adding more discussion to
    >> deprecate other algorithms would only delay it, further.
    >> 
    >> Meanwhile DES is really insecure these days and we ought to
    >> deprecate it officially so that all vendors wake up and start
    >> moving off of it for real.


As a process point, I believe that once we conclude our discussion here
about what if anything to say about RC4, we will not be slowed down
regardless of whether we include RC4.  I think that coming to consensus
to remove RC4 references is likely as difficult as coming to consensus
to keep it.


So, my opinion as someone familiar with IETF process is that we should
do what is right: it will take about the same time either way.

--Sam
_______________________________________________
ietf-krb-wg mailing list
[email protected]
https://lists.anl.gov/mailman/listinfo/ietf-krb-wg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.