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

bmanning@isi.edu Wed, 04 January 1995 19:09 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06894; 4 Jan 95 14:09 EST
Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa06890; 4 Jan 95 14:09 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa05685; 4 Jan 95 14:09 EST
Received: from zed.isi.edu by venera.isi.edu (5.65c/5.61+local-20) id <AA08289>; Wed, 4 Jan 1995 10:34:48 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: bmanning@isi.edu
Posted-Date: Wed, 4 Jan 1995 10:34:29 -0800 (PST)
Message-Id: <199501041834.AA10101@zed.isi.edu>
Received: by zed.isi.edu (5.65c/4.0.3-4) id <AA10101>; Wed, 4 Jan 1995 10:34:30 -0800
Subject: Re: ftp://ftp.cisco.com/fred/rreq-03.txt
To: barns@cove.mitre.org
Date: Wed, 4 Jan 1995 10:34:29 -0800 (PST)
Cc: louie@alter.net, rreq@isi.edu
In-Reply-To: <9501041813.AA02338@cove.mitre.org.mitre.org> from "barns@cove.mitre.org" at Jan 4, 95 01:13:49 pm
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1095

> 
> > I think that the transition issue is just so much smoke and mirrors.
> 
> word.  I thought the real transition issue was of allowing manager x to
> 
>    1) bilingual routers during manager transition
>    2) bilingual managers during router transition
>    3) bilingual everything for some long period of time, then reconsider
>    4) maybe some managers can't see some routers during transition
> 
> I thought #4 was deemed a bad thing but if people think it's OK, then
> you're completely right.
> 
> > I suspect that the new RREQ RFC will achive "standard" status after
> > the SNMPv2 RFC does, right?
> 
> Hadn't thought about that.  I can't figure out whether RFC 1602 mandates
> 6 month and 4 month delays for advancement of RREQ (in the event that it
> only references full standards, that is).  Good point.
> 

With the NM-AD giving some "hints", I expect that the prudent thing to
do is to drop references to SNMPv2 in the current RREQ doc and let it stand
as is.  A snapshot of requirements for IPv4 routers in 1994.

Future generations can work transition issues.

-- 
--bill