Protocol Action: RIP Version 2 to Draft Standard

IESG Secretary <iesg-secretary@CNRI.Reston.VA.US> Thu, 08 September 1994 19:40 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08798; 8 Sep 94 15:40 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa13812; 8 Sep 94 15:40 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08771; 8 Sep 94 15:39 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08673; 8 Sep 94 15:36 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa13716; 8 Sep 94 15:36 EDT
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa08666; 8 Sep 94 15:36 EDT
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ietf-rip@xylogics.com
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: RIP Version 2 to Draft Standard
Date: Thu, 08 Sep 94 15:36:20 -0400
X-Orig-Sender: jstewart@CNRI.Reston.VA.US
Message-ID: <9409081536.aa08666@IETF.CNRI.Reston.VA.US>

  The IESG has approved the Internet-Drafts:
  
    o "RIP Version 2 Carrying Additional Information"
      <draft-ietf-ripv2-protocol-01.txt>

    o "RIP Version 2 MIB Extension"
      <draft-ietf-ripv2-mibext2-02.txt>

    o "RIP Version 2 Protocol Applicability Statement"
      <draft-ietf-ripv2-protocol-applic-01.txt>

  as Draft Standards.  The IESG also recommends to the RFC Editor
  that:

    o "RIP Version 2 Protocol Analysis"
      <draft-ietf-ripv2-protocol-analysis-01.txt>

  be published as an Informational RFC.
  
  These documents are the product of the RIP Version II Working
  Group.  The IESG contact person is Joel Halpern.
 
 
Technical Summary

  RIP Version 2 is an extension to the existing RIP routing protocol.
  While preserving the simple operation and distance vector model of
  RIP, RIPv2 adds support for Subnet Masks (including Supernetting),
  Next-Hop advertisement, and Authentication.

  The Next-Hop capability increases the useability of this protocol
  as a method to notify hosts of the best routes off of networks.  It
  also interacts well with demand-circuit routing, saving the need to
  setup extra circuits for routing exchange.

  The Authentication definition includes only passwords.  But the
  form of the field allows for any authentication which fits into
  16 bytes.

Working Group Summary

  There was no significant dissent within the working group.

Protocol Quality

  The protocol has been reviewed by the working group, and by the
  Routing Area Director.  It is a technically sound extension to a
  simple distance-vector routing protocol.

  As indicated in the Protocol Analysis, there are multiple
  interoperating implementations.