Re: comments on draft-ietf-idpr-specv1-02.txt
Mills@udel.edu Tue, 16 March 1993 01:02 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26405; 15 Mar 93 20:02 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa26401; 15 Mar 93 20:01 EST
Received: from PIZZA.BBN.COM by CNRI.Reston.VA.US id aa03773; 15 Mar 93 20:02 EST
Received: from pizza by PIZZA.BBN.COM id aa04692; 15 Mar 93 19:57 EST
Received: from BBN.COM by PIZZA.BBN.COM id aa04688; 15 Mar 93 19:56 EST
Received: from huey.udel.edu by BBN.COM id aa28456; 15 Mar 93 19:58 EST
Date: Mon, 15 Mar 1993 19:56:34 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mills@udel.edu
To: kasten@ftp.com
cc: jnc@ginger.lcs.mit.edu, idpr-wg@bbn.com, mccurley@cs.sandia.gov
Subject: Re: comments on draft-ietf-idpr-specv1-02.txt
Message-ID: <9303151956.aa08941@huey.udel.edu>
Frank, Geeze, you trust the timestamps? NTP uses either DES or MD5 in much the same way. For the latter, the garb was more pipe and tweed jacket. Keeping track of keys is becoming a major headache and SDNS is not much help. Dave
- comments on draft-ietf-idpr-specv1-02.txt Kevin S. McCurley
- Re: comments on draft-ietf-idpr-specv1-02.txt Noel Chiappa
- Re: comments on draft-ietf-idpr-specv1-02.txt Frank Kastenholz
- Re: comments on draft-ietf-idpr-specv1-02.txt Mills