| Postel, J. Ed., User Datagram Protocol, RFC768, IETF Network Working Group, Aug. 1980. |
....about a directory that a human browser should understand first about that directory. The conventions for names within a cell s service directory are exactly analogous to the conventions for other protocols: the meanings of the telnet IAC codes [RFC 854] the commands used for file transfer [RFC 959] or SMTP mail transfer [RFC 821] or the names of header fields in Internet text messages [RFC 822] The conventions are necessary for an exactly analogous reason: so that independent AFS cells that wish to cooperate may do so. 2.2. Extensibility Section 3 below enumerates a limited set of known ....
J. Postel and J. Reynolds. File Transfer Protocol (FTP). RFC 959, IETF Network Working Group, October 1985.
....combination of its transport service (e.g. TCP) its well known port number as listed in etc services, and an arbitrary string that has meaning to the service. Since we search for an NFS mountable file system, our RLP request messages contain information such as the NFS transport protocol (UDP [16]) port number (2049) and service specific information such as the name of the root of the file system. 2.3 Amd Amd [15] is a widely used automounter daemon. Its most common use is to demand mount file systems and later unmount them after a period of disuse; however, Amd has many other ....
J. Postel. User Datagram Protocol. RFC 768, IETF Network Working Group, August 1980.
No context found.
Postel, J. Ed., User Datagram Protocol, RFC768, IETF Network Working Group, Aug. 1980.
No context found.
Postel, J. ed., Internet Protocol, RFC 791, IETF Network Working Group, Sept. 1981.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC