Provides a mechanism for keeping synchronized clocks.
OTHER REFERENCES:
DEPENDENCIES: Internet Control Message Protocol
CONTACT: Mills@USC-ISID.ARPA
SUPDUP Protocol ------------------------------------------- (SUPDUP)
STATUS: Elective
SPECIFICATION: RFC734 (in APH)
COMMENTS:
A special Telnet like protocol for display terminals.
OTHER REFERENCES:
DEPENDENCIES: Transmission Control Protocol
CONTACT: Crispin@SU-SCORE.ARPA
Official ARPA-Internet Protocols RFC944
Internet Message Protocol ------------------------------------ (MPM)
STATUS: Experimental
SPECIFICATION: RFC759
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:
RFC767 - Structured Document Formats
DEPENDENCIES: Transmission Control Protocol
CONTACT: Postel@USC-ISIF.ARPA
Post Office Protocol - Version 2 ---------------------------- (POP2)
STATUS: Experimental
SPECIFICATION: RFC937
COMMENTS:
The intent of the Post Office Protocol - Version 2 (POP2) 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).
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES: Obsoletes RFC918
DEPENDENCIES: Transmission Control Protocol
CONTACT: JKReynolds@USC-ISIF.ARPA
Official ARPA-Internet Protocols RFC944
Network Standard Text Editor ------------------------------- (NETED)
STATUS: Elective
SPECIFICATION: RFC569
COMMENTS:
Describes a simple line editor which could be provided by every
Internet host.
OTHER REFERENCES:
DEPENDENCIES:
CONTACT: Postel@USC-ISIF.ARPA
Authentication Service -------------------------------------- (AUTH)
STATUS: Experimental
SPECIFICATION: RFC931
COMMENTS:
This server provides a means to determine the identity of a
user of a particular TCP connection. Given a TCP port number
pair, it returns a character string which identifies the owner
of that connection on the server's system.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES: Supercedes RFC912
DEPENDENCIES: Transmission Control Protocol
CONTACT: StJohns@MIT-Multics.ARPA
Official ARPA-Internet Protocols RFC944
APPENDICES
Assigned Numbers ---------------------------------------------------
STATUS: None
SPECIFICATION: RFC943
COMMENTS:
Describes the fields of various protocols that are assigned
specific values for actual use, and lists the currently
assigned values.
Issued April 1985, replaces RFC923, RFC790 in IPTW, and
RFC900.
OTHER REFERENCES:
CONTACT: JKReynolds@USC-ISIF.ARPA
Pre-emption --------------------------------------------------------
STATUS: Elective
SPECIFICATION: RFC794 (in IPTW)
COMMENTS:
Describes how to do pre-emption of TCP connections.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Official ARPA-Internet Protocols RFC944
Service Mappings ---------------------------------------------------
STATUS: None
SPECIFICATION: RFC795 (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: RFC796 (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: RFC678
COMMENTS:
Describes standard format rules for several types of documents.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Official ARPA-Internet Protocols RFC944
Bitmap Formats -----------------------------------------------------
STATUS: None
SPECIFICATION: RFC797
COMMENTS:
Describes a standard format for bitmap data.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Facsimile Formats --------------------------------------------------
STATUS: None
SPECIFICATION: RFC804
COMMENTS:
Describes a standard format for facsimile data.
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Host-Front End Protocol ------------------------------------- (HFEP)
STATUS: Experimental
SPECIFICATION: RFC929
COMMENTS:
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES: RFC928
DEPENDENCIES:
CONTACT: Padlipsky@USC-ISI.ARPA
Official ARPA-Internet Protocols RFC944
Internet Protocol on X.25 Networks ------------------------ (IP-X25)
STATUS: Recommended
SPECIFICATION: RFC877
COMMENTS:
Describes a standard for the transmission of IP Datagrams over
Public Data Networks.
OTHER REFERENCES:
CONTACT: jtk@PURDUE.ARPA
Internet Protocol on DC Networks --------------------------- (IP-DC)
STATUS: Elective
SPECIFICATION: RFC891
COMMENTS:
OTHER REFERENCES:
RFC778 - DCNET Internet Clock Service
CONTACT: Mills@USC-ISID.ARPA
Internet Protocol on Ethernet Networks ---------------------- (IP-E)
STATUS: Recommended
SPECIFICATION: RFC894
COMMENTS:
OTHER REFERENCES: RFC893
CONTACT: Postel@USC-ISIF.ARPA
Official ARPA-Internet Protocols RFC944
Internet Protocol on Experimental Ethernet Networks -------- (IP-EE)
STATUS: Recommended
SPECIFICATION: RFC895
COMMENTS:
OTHER REFERENCES:
CONTACT: Postel@USC-ISIF.ARPA
Internet Subnets Protocol --------------------------------- (IP-SUB)
STATUS: Experimental
SPECIFICATION: RFC940
COMMENTS:
Discussion of the various problems and potential solutions of
"explicit subnets" in a multi-LAN environment.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES: RFC917, RFC925, RFC932, RFC936, RFC922
DEPENDENCIES:
CONTACT: Mills@USC-ISID.ARPA
Broadcasting Internet Datagrams ------------------------- (IP-BROAD)
STATUS: Experimental
SPECIFICATION: RFC919
COMMENTS:
A proposed protocol of simple rules for broadcasting Internet
datagrams on local networks that support broadcast, for
addressing broadcasts, and for how gateways should handle them.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES: RFC922
Official ARPA-Internet Protocols RFC944
DEPENDENCIES:
CONTACT: Mogul@SU-SCORE.ARPA
Address Resolution Protocol ---------------------------------- (ARP)
STATUS: Recommended
SPECIFICATION: RFC826
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: RFC903
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
Multi-LAN Address Resolution Protocol ----------------------- (MARP)
STATUS: Experimental
SPECIFICATION: RFC925
COMMENTS:
Discussion of the various problems and potential solutions of
"transparent subnets" in a multi-LAN environment.
Please discuss any plans for implementation or use of this
protocol with the contact.
Official ARPA-Internet Protocols RFC944
OTHER REFERENCES: RFC917, RFC826
DEPENDENCIES:
CONTACT: Postel@USC-ISIF.ARPA
Broadcasting Internet Datagrams with Subnets --------- (IP-SUB-BROAD)
STATUS: Experimental
SPECIFICATION: RFC922
COMMENTS:
A proposed protocol of simple rules for broadcasting Internet
datagrams on local networks that support broadcast, for
addressing broadcasts, and for how gateways should handle them.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES:
DEPENDENCIES:
CONTACT: Mogul@SU-SCORE.ARPA
Host Access Protocol ----------------------------------------- (HAP)
STATUS: Recommended
SPECIFICATION: RFC907
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:
DEPENDENCIES:
CONTACT: Schoen@BBN-UNIX.ARPA
Official ARPA-Internet Protocols RFC944
Reliable Asynchronous Transfer Protocol --------------------- (RATP)
STATUS: Experimental
SPECIFICATION: RFC916
COMMENTS:
This paper specifies a protocol which allows two programs to
reliably communicate over a communication link. It ensures
that the data entering one end of the link if received arrives
at the other end intact and unaltered. This proposed protocol
is designed to operate over a full duplex point-to-point
connection. It contains some features which tailor it to the
RS-232 links now in current use.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES:
DEPENDENCIES: Transmission Control Protocol
CONTACT: Finn@USC-ISIF.ARPA
Thinwire Protocol --------------------------------------- (THINWIRE)
STATUS: Experimental
SPECIFICATION: RFC914
COMMENTS:
This paper discusses a Thinwire Protocol for connecting
personal computers to the ARPA-Internet. It primarily focuses
on the particular problems in the ARPA-Internet of low speed
network interconnection with personal computers, and possible
methods of solution.
Please discuss any plans for implementation or use of this
protocol with the contact.
OTHER REFERENCES:
DEPENDENCIES:
CONTACT: Farber@ROCHESTER.ARPA