Official ARPA-Internet protocols for connecting personal computers to the Internet
RFC 924
Document | Type |
RFC
- Unknown
(October 1984)
Obsoleted by RFC 944
Obsoletes RFC 901
|
|
---|---|---|---|
Authors | |||
Last updated | 2013-03-02 | ||
RFC stream | Legacy stream | ||
Formats | |||
IESG | Responsible AD | (None) | |
Send notices to | (None) |
RFC 924
amp; Postel [Page 27]
Official ARPA-Internet Protocols RFC 924
Internet Message Protocol ------------------------------------ (MPM)
STATUS: Experimental
SPECIFICATION: RFC 759
COMMENTS:
This is an experimental multimedia mail transfer protocol. The
implementation is called a Message Processing Module or MPM.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES:
RFC 767 - Structured Document Formats
DEPENDENCIES: Transmission Control Protocol
CONTACT: Postel@USC-ISIF.ARPA
Post Office Protocol ----------------------------------------- (POP)
STATUS: Experimental
SPECIFICATION: RFC 918
COMMENTS:
The intent of the Post Office Protocol (POP) is to allow a
user's workstation to access mail from a mailbox server. It is
expected that mail will be posted from the workstation to the
mailbox server via the Simple Mail Transfer Protocol (SMTP).
For further information see RFC-821 and RFC-822.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES:
DEPENDENCIES: Transmission Control Protocol
CONTACT: JKReynolds@USC-ISIF.ARPA
Reynolds & Postel [Page 28]
Official ARPA-Internet Protocols RFC 924
Network Standard Text Editor ------------------------------- (NETED)
STATUS: Elective
SPECIFICATION: RFC 569
COMMENTS:
Describes a simple line editor which could be provided by every
Internet host.
OTHER REFERENCES:
DEPENDENCIES:
CONTACT: Postel@USC-ISIF.ARPA
Reynolds & Postel [Page 29]
Official ARPA-Internet Protocols RFC 924
APPENDICES
Assigned Numbers ---------------------------------------------------
STATUS: None
SPECIFICATION: RFC 923
COMMENTS:
Describes the fields of various protocols that are assigned
specific values for actual use, and lists the currently
assigned values.
Issued October 1984, replaces RFC 900, RFC 790 in IPTW, and
RFC 870.
OTHER REFERENCES:
CONTACT: JKReynolds@USC-ISIF.ARPA
Pre-emption --------------------------------------------------------
STATUS: Elective
SPECIFICATION: RFC 794 (in IPTW)
COMMENTS:
Describes how to do pre-emption of TCP connections.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Reynolds & Postel [Page 30]
Official ARPA-Internet Protocols RFC 924
Service Mappings ---------------------------------------------------
STATUS: None
SPECIFICATION: RFC 795 (in IPTW)
COMMENTS:
Describes the mapping of the IP type of service field onto the
parameters of some specific networks.
Out of date, needs revision.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Address Mappings ---------------------------------------------------
STATUS: None
SPECIFICATION: RFC 796 (in IPTW)
COMMENTS:
Describes the mapping between Internet Addresses and the
addresses of some specific networks.
Out of date, needs revision.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Document Formats ---------------------------------------------------
STATUS: None
SPECIFICATION: RFC 678
COMMENTS:
Describes standard format rules for several types of documents.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Reynolds & Postel [Page 31]
Official ARPA-Internet Protocols RFC 924
Bitmap Formats -----------------------------------------------------
STATUS: None
SPECIFICATION: RFC 797
COMMENTS:
Describes a standard format for bitmap data.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Facsimile Formats --------------------------------------------------
STATUS: None
SPECIFICATION: RFC 804
COMMENTS:
Describes a standard format for facsimile data.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Internet Protocol on X.25 Networks ---------------------------------
STATUS: Recommended
SPECIFICATION: RFC 877
COMMENTS:
Describes a standard for the transmission of IP Datagrams over
Public Data Networks.
OTHER REFERENCES:
CONTACT: jtk@PURDUE.ARPA
Reynolds & Postel [Page 32]
Official ARPA-Internet Protocols RFC 924
Internet Protocol on DC Networks -----------------------------------
STATUS: Elective
SPECIFICATION: RFC 891
COMMENTS:
OTHER REFERENCES:
RFC 778 - DCNET Internet Clock Service
CONTACT: Mills@USC-ISID.ARPA
Internet Protocol on Ethernet Networks -----------------------------
STATUS: Recommended
SPECIFICATION: RFC 894
COMMENTS:
OTHER REFERENCES: RFC 893
CONTACT: Postel@USC-ISIF.ARPA
Internet Protocol on Experimental Ethernet Networks ----------------
STATUS: Recommended
SPECIFICATION: RFC 895
COMMENTS:
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Reynolds & Postel [Page 33]
Official ARPA-Internet Protocols RFC 924
Address Resolution Protocol ---------------------------------- (ARP)
STATUS: Recommended
SPECIFICATION: RFC 826
COMMENTS:
This is a procedure for finding the network hardware address
corresponding to an Internet Address.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
A Reverse Address Resolution Protocol ----------------------- (RARP)
STATUS: Elective
SPECIFICATION: RFC 903
COMMENTS:
This is a procedure for workstations to dynamically find their
protocol address (e.g., their Internet Address), when they only
only know their hardware address (e.g., their attached physical
network address).
OTHER REFERENCES:
CONTACT: Mogul@SU-SCORE.ARPA
Host Access Protocol ----------------------------------------- (HAP)
STATUS: Recommended
SPECIFICATION: RFC 907
COMMENTS:
This protocol specifies the network-access level communication
between an arbitrary computer, called a host, and a
packet-switched satellite network, e.g., SATNET or WBNET.
Note: Implementations of HAP should be performed in
coordination with satellite network development and operations
personnel.
OTHER REFERENCES:
Reynolds & Postel [Page 34]
Official ARPA-Internet Protocols RFC 924
DEPENDENCIES:
CONTACT: Schoen@BBN-UNIX.ARPA
Reynolds & Postel [Page 35]