Routing Information Protocol (rip)
----------------------------------
Charter
Last Modified: 2002-04-17
Current Status: Active Working Group
Chair(s):
Gary Malkin <gmalkin@avici.com>
Routing Area Director(s):
Bill Fenner <fenner@research.att.com>
Alex Zinin <zinin@psg.com>
Routing Area Advisor:
Bill Fenner <fenner@research.att.com>
Mailing Lists:
General Discussion:ietf-rip@baynetworks.com
To Subscribe: ietf-rip-request@baynetworks.com
In Body: subscribe ietf-rip <your email address>
Archive: ftp://xylogics.com/pub/users/gmalkin/rip/rip-arc
Description of Working Group:
The RIP Working Group was formed from the RIP Version 2 Working
Group, which was originally chartered to create the RIP-2 standard.
Since several other RIP-related efforts are also occuring within
the IETF, it was decided to create a single working group to handle
them all.
The RIP Working Group is chartered to guide the following proposals
and develop the following projects through the IETF standards track:
- ``RIP Version 2'' (RFC 1723)
- ``RIP Version 2 MIB Extension'' (RFC 1724)
- ``Extensions to RIP to Support Demand Circuits'' (RFC 1582)
- ``RIP-II Cryptographic Authentication'' (Internet-Draft)
Additionally, the RIP Working Group will handle the RIPng protocol
which, in its first incarnation, will contain the minimum modifications
to RIP-2 necessary to handle IPng.
Goals and Milestones:
Done Submit Internet-Draft of MD5 Proposal.
Done Meet at San Jose IETF to discuss MD5 document.
Done Submit RIPng as an Internet-Draft.
Done Submit MD5 document to IESG for consideration as a Proposed
Standard.
Done Meet at Danvers IETF to discuss implementation of all
RIP-related specifications.
Done Submit Demand Circuit RIP document (RFC 1581) to IESG for
consideration as a Draft Standard.
Done Submit RIPng Internet-Draft for consideration as a Proposed
Standard. Submission MUST be accompanied by a suitably
restrictive Applicability Statement.
Done Meet at Stockholm IETF. Review status of MD5 for elevation to
Draft Standard. Review status of RIP-2 and MIB for elevation
to Standard. A suitably restrictive Applicability Statement
for RIP-2 MUST accompany the request for standards level
elevation.
Apr 97 Submit the RIP2 protocol and MIN to the IESG for Standard.
Group will then go into hiatus waiting for other documents to
spend the necessary periods of time at their current standards
level prior to elevation in the standards track.
Internet-Drafts:
No Current Internet-Drafts.
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC1923 I Mar 96 RIPv1 Applicability Statement for Historic Status
RFC2081 I Jan 97 RIPng Protocol Applicability Statement
RFC2080 PS Jan 97 RIPng for IPv6
RFC2092 I Jan 97 Protocol Analysis for Triggered RIP
RFC2091 PS Jan 97 Triggered Extensions to RIP to Support Demand Circuits