Re: draft-ietf-ipsec-ciph-cbc-02.txt

"Theodore Y. Ts'o" <tytso@MIT.EDU> Tue, 17 March 1998 00:54 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id TAA10966 for ipsec-outgoing; Mon, 16 Mar 1998 19:54:42 -0500 (EST)
Date: Mon, 16 Mar 1998 20:08:26 -0500
Message-Id: <199803170108.UAA24829@dcl.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Paul Koning <pkoning@xedia.com>
Cc: ipsec@tis.com
In-Reply-To: Paul Koning's message of Mon, 16 Mar 1998 16:48:02 -0500, <9803162148.AA07048@kona.>
Subject: Re: draft-ietf-ipsec-ciph-cbc-02.txt
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

   Date: Mon, 16 Mar 1998 16:48:02 -0500
   From: Paul Koning <pkoning@xedia.com>

   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?

The way this is normally done is by publishing an informational RFC
containing the relevant information.  (With pointers to the relevant
papers and research in the bibliography, ideally.)

						- Ted

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