RIP-II MD5 Authentication
draft-ietf-ripv2-md5-auth-00
| Document | Type | Expired Internet-Draft (ripv2 WG) | |
|---|---|---|---|
| Last updated | 1997-03-07 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-ripv2-md5-auth-00.txt
Abstract
Growth in the Internet has made us aware of the need for improved authentication of routing information. RIP-II provides for unauthenticated service (as in classical RIP), or password authentication. Both are vulnerable to passive attacks currently widespread in the Internet. Well-understood security issues exist in routing protocols [4]. Clear text passwords, currently specified for use with RIP-II, are no longer considered sufficient [5].
Authors
Fred Baker
(fred.baker@cisco.com)
Randall Atkinson
(rja@extremenetworks.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)