RIP-2 MD5 Authentication
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 12
- Abstract
- Growth in the Internet has made us aware of the need for improved authentication of routing information. RIP-2 provides for unauthenticated service (as in classical RIP), or password authentication. [STANDARDS-TRACK]
- Publication Date
- 1997-01-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2082- Link
- https://doi.org/10.17487/RFC2082
- Author(s)
- Fred BakerRan Atkinson
- Keyword(s)
- RIP2-MD5, Routing, Protocol, Encryption
Latest version of IETF RFC 2082
Document Versions — IETF RFC 2082
-
▶ IETF RFC 2082 (1997-01-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- S. Bellovin, "Security Problems in the TCP/IP Protocol Suite", ACM Computer Communications Review, Volume 19, Number 2, pp.32-48, April 1989. EXTERNAL
- IETF RFC 1321 [Active*]
- IETF RFC 1388 [Superseded*]
- IETF RFC 1389 [Superseded*]
- IETF RFC 1636 [Active*]
- IETF RFC 1704 [Active*]
- IETF RFC 1826 [Superseded*]
- IETF RFC 1827 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2082.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2082, RIP-2 MD5 Authentication. Available at https://doi.org/10.17487/RFC2082
Snippet:
IETF RFC 2082, RIP-2 MD5 Authentication. Available at https://doi.org/10.17487/RFC2082
HTML (ISO 690 compliant)
Preview:
IETF RFC 2082, RIP-2 MD5 Authentication. Available at https://doi.org/10.17487/RFC2082
Snippet:
<span class="citation"><cite>IETF RFC 2082</cite>, RIP-2 MD5 Authentication. Available at <a href="https://doi.org/10.17487/RFC2082" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2082</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc2082">IETF RFC 2082</cite>, RIP-2 MD5 Authentication <span class="doi">10.17487/RFC2082</span> </li>
Referenced By
- IETF RFC 2367 [Active*]
- IETF RFC 2453 [Active*]
- IETF RFC 4822 [Active*]