RFC 2385: Protection of BGP Sessions via the TCP MD5 Signature Option
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5925.
Current version: RFC 5925 — The TCP Authentication Option
In plain English — editorial summary, not part of the RFC
This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2385
- Published
- August 1998
- Authors
- A. Heffernan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2988Computing TCP's Retransmission TimerObsoleted
November 2000
- RFC 2439BGP Route Flap DampingCurrent
November 1998
- RFC 2202Test Cases for HMAC-MD5 and HMAC-SHA-1Current
September 1997
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 2918Route Refresh Capability for BGP-4Updated
September 2000
- RFC 1810Report on MD5 PerformanceCurrent
June 1995
- RFC 3107Carrying Label Information in BGP-4Obsoleted
May 2001
- RFC 3392Capabilities Advertisement with BGP-4Obsoleted
November 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?