Protocol Action: Routing Information Protocol to Historic (fwd)

bmanning@isi.edu Mon, 12 February 1996 17:10 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18372; 12 Feb 96 12:10 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18368; 12 Feb 96 12:10 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa10931; 12 Feb 96 12:10 EST
Received: from zed.isi.edu by venera.isi.edu (5.65c/5.61+local-22) id <AA13233>; Mon, 12 Feb 1996 08:37:05 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: bmanning@isi.edu
Posted-Date: Mon, 12 Feb 1996 08:32:35 -0800 (PST)
Message-Id: <199602121632.AA27106@zed.isi.edu>
Received: by zed.isi.edu (5.65c/4.0.3-4) id <AA27106>; Mon, 12 Feb 1996 08:32:36 -0800
Subject: Protocol Action: Routing Information Protocol to Historic (fwd)
To: rreq@isi.edu, pier@isi.edu
Date: Mon, 12 Feb 1996 08:32:35 -0800 (PST)
X-Mailer: ELM [version 2.4 PL25]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 978

> The IESG has reclassified RFC1058 "Routing Information Protocol" as an
> Historic protocol. This document is the product of the Routing Area
> Working Group. The IESG contact person is Joel Halpern.
> 
> The IESG has also approved the publication of RIPv2 Applicability
> Statement <draft-ietf-rip-ripas-00.txt> as an Informational RFC.
> 
> 
> Technical Summary
> 
>   The original version of RIP standarized the behavior of an existing,
>   simple, distance vector protocol.
> 
> Working Group Summary
> 
>   Both the RIPv2 and Router Requirements working groups asked for the
>   move of RIPv1 to Historic.
> 
> Protocol Quality
> 
> 
>   While there is clearly a place for a simple distance vector protocol,
>   it is important that standard IETF protocol be able to support our
>   real environments. RIPv1 is very ill-suited to doing so. In
>   addition, RIPv2 represents a successor protocol which fills this
>   niche in a way suit to our current situation.


-- bill