Concluded WG Routing Information Protocol (rip)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Routing Information Protocol | |
|---|---|---|---|
| Acronym | rip | ||
| Area | Routing Area (rtg) | ||
| State | Concluded | ||
| Charter | charter-ietf-rip-01 Approved | ||
| Document dependencies | |||
| Personnel | Chair | Gary S. Malkin | |
| Mailing list | Address | rip@ietf.org | |
| To subscribe | rip-request@ietf.org | ||
| Archive | https://mailarchive.ietf.org/arch/browse/rip |
Final Charter for 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.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Apr 1997 | 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. |
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| 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. | |
| Done | Submit RIPng Internet-Draft for consideration as a Proposed Standard. Submission MUST be accompanied by a suitably restrictive Applicability Statement. | |
| 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 Internet-Draft of MD5 Proposal. | |
| Done | Submit MD5 document to IESG for consideration as a Proposed Standard. | |
| Done | Submit RIPng as an Internet-Draft. | |
| Done | Meet at San Jose IETF to discuss MD5 document. |