RFC 2385 on TCP MD5 Signature Option

[RFC Editor <rfc-ed at ISI.EDU>]

A new Request for Comments is now available in online RFC libraries.


        RFC 2385:

        Title:	    Protection of BGP Sessions via the TCP MD5
		    Signature Option
	Author(s):  A. Heffernan
	Status:     Proposed Standard
	Date:       August 1998
        Mailbox:    ahh at cisco.com
	Pages:      6
        Characters: 12315
        Updates/Obsoletes/See Also: None

        URL:        ftp://ftp.isi.edu/in-notes/rfc2385.txt


This memo describes a TCP extension to enhance security for BGP.  It
defines a new TCP option for carrying an MD5 [RFC1321] digest in a
TCP segment.  This digest acts like a signature for that segment,
incorporating information known only to the connection end points.
Since BGP uses TCP as its transport, using this option in the way
described in this paper significantly reduces the danger from certain
security attacks on BGP.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

<ftp://ftp.isi.edu/in-notes/rfc2385.txt>