for the record...
Fred Baker <firstname.lastname@example.org> Tue, 04 April 1995 01:16 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04770;
3 Apr 95 21:16 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04766; 3 Apr 95 21:16 EDT
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa19118; 3 Apr 95 21:16 EDT
Received: from stilton.cisco.com by venera.isi.edu (5.65c/5.61+local-21) id <AA26915>; Mon, 3 Apr 1995 18:04:26 -0700
Received: (fred@localhost) by stilton.cisco.com (8.6.8+c/8.6.5) id SAA26648 for email@example.com; Mon, 3 Apr 1995 18:04:25 -0700
Date: Mon, 3 Apr 1995 18:04:25 -0700
From: Fred Baker <firstname.lastname@example.org>
Subject: for the record...
the following change was accepted in this evening's working group meeting. I will post the document before the end of the week. 9c9 < Document Revision 2.06 --- > Document Revision 2.07 11c11 < draft-ietf-rreq-cidr-02.txt --- > draft-ietf-rreq-cidr-03.txt 14c14 < 3/30/95 --- > 4/3/95 23,24c23,24 < Please also mention the date of this draft (3/30/95) < and the revision level (2.06). --- > Please also mention the date of this draft (4/3/95) > and the revision level (2.07). 7801,7802c7801,7807 < The router SHOULD require a password or other valid authentication before < permitting remote reconfiguration. --- > The router SHOULD require valid authentication before permitting remote reconfiguration. > This authentication procedure SHOULD NOT transmit the authentication secret over the network. > For example, > if telnet is implemented, > the vendor SHOULD IMPLEMENT Kerberos, > S-Key, > or a similar authentication procedure.
- for the record... Fred Baker