Skip to main content

Request to Move RFC 1745 to Historic Status
draft-meyer-rfc1745-historic-00

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3167.
Authors David Meyer , John Scudder
Last updated 2013-03-02 (Latest revision 2001-02-09)
RFC stream Legacy stream
Intended RFC status Informational
Formats
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3167 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-meyer-rfc1745-historic-00
A new Request for Comments is now available in online RFC libraries.

        RFC 3167

        Title:      Request to Move RFC 1745 to Historic Status
        Author(s):  D. Meyer, J. Scudder
        Status:     Informational
        Date:       August 2001
        Mailbox:    dmm@sprint.net, jgs@cisco.com
        Pages:      3
        Characters: 3825
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-meyer-rfc1745-historic-00.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3167.txt

RFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes
technology which was never deployed in the public internet.  This
document requests that RFC 1745 be moved to Historic status.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.