Re: draft-ietf-ipsec-ciph-cbc-02.txt
Paul Koning <pkoning@xedia.com> Mon, 16 March 1998 21:35 UTC
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id QAA09595 for ipsec-outgoing; Mon, 16 Mar 1998 16:35:36 -0500 (EST)
Date: Mon, 16 Mar 1998 16:48:02 -0500
Message-Id: <9803162148.AA07048@kona.>
From: Paul Koning <pkoning@xedia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: tytso@MIT.EDU
Cc: ipsec@tis.com
Subject: Re: draft-ietf-ipsec-ciph-cbc-02.txt
References: <Pine.HPP.3.96.980316111103.13215K-100000@domus.esat.kuleuven.ac.be> <199803161942.OAA24677@dcl.MIT.EDU>
X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
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
- draft-ietf-ipsec-ciph-cbc-02.txt Roy Pereira
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Bart Preneel
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Theodore Y. Ts'o
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Paul Koning
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Bill Sommerfeld
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Theodore Y. Ts'o
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Theodore Y. Ts'o
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Henry Spencer
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Paul Koning
- Re: draft-ietf-ipsec-ciph-cbc-02.txt Raul Miller