IETF Logo Mail Archive

Re: ftp://ftp.cisco.com/fred/rreq-03.txt

David Waitzman <djw@bbn.com> Wed, 04 January 1995 16:29 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04173; 4 Jan 95 11:29 EST
Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa04167; 4 Jan 95 11:29 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa01515; 4 Jan 95 11:29 EST
Received: from MORPHEUS.BBN.COM by venera.isi.edu (5.65c/5.61+local-20) id <AA00518>; Wed, 4 Jan 1995 07:23:22 -0800
Message-Id: <199501041523.AA00518@venera.isi.edu>
To: kasten@ftp.com
Cc: rreq@isi.edu
Subject: Re: ftp://ftp.cisco.com/fred/rreq-03.txt
In-Reply-To: Your message of Wed, 04 Jan 95 08:23:10 -0500. <9501041323.AA03592@mailserv-D.ftp.com>
Date: Wed, 04 Jan 1995 10:21:32 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: David Waitzman <djw@bbn.com>

> i do not believe that it is appropriate to make a requirement
> 'temporally conditional' in this manner. at this point in time,
> either v2 is ready to be required in r.r. or it is not. if it is
> ready and if we think it is the right thing to do then we should
> mandate it. if it is not ready then it is not ready and we should
> wait for it to be ready.

V2's security features address a critical need for securely managing
routers.  Some routers are already shipping with proposed-standard v2
(ex. cisco version 10.2).  I think that this is a case where having
r.r. conditionally leading a bit will help make it more applicable in
the long term.

Are you worried about what happened with CMOT standardization?

-david

v2.23.0 | Report a Bug | By Email