1 / 24

Internet and Intranet Fundamentals

Internet and Intranet Fundamentals. Class 5 Session A. Topics. Telnet FTP SMTP NNTP. Telnet Topics. Overview History Terminology, Model Commands. Telnet Overview. General, bi-directional, byte-oriented communications facility remote login

gina
Télécharger la présentation

Internet and Intranet Fundamentals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internet and Intranet Fundamentals Class 5 Session A

  2. Topics • Telnet • FTP • SMTP • NNTP

  3. TelnetTopics • Overview • History • Terminology, Model • Commands

  4. TelnetOverview • General, bi-directional, byte-oriented communications facility • remote login • Interfaces terminal devices and terminal-oriented processes • could also be used for process-process or terminal-terminal communication • TCP Application

  5. TelnetHistory • Very early beginning: 1971 • 1983: Standard • RFC 854 (Postel & Reynolds) • http://info.internet.isi.edu:80/in-notes/rfc/files/rfc854.txt

  6. TelnetTerminology, Model • NVT = Network Virtual Terminal • Negotiated Options • Symmetric Treatment of Terminals and Processes

  7. TelnetTerminology, Model • NVT • Network Virtual Terminal • standard, intermediate representation of canonical terminal • each end assumed to originate and terminate • user host is host with physical terminal • but could just be the host that initiated the communication

  8. TelnetTerminology, Model • Principle of Negotiated Options • DO, DONT, WILL, WONT • allows user and server to agree on set of conventions for the Telnet session • conventions such as character set, echoing, etc. • either party can initiate a request that some option take effect • other party can accept or reject • may refuse to enable; must never refuse to disable

  9. TelnetTerminology, Model • Two-Byte or Three-Byte Command Structure • IAC = interpret as command • followed by command code • followed optionally by argument / option • Examples: • AYT, AO, GA, WILL, WONT, etc.

  10. TelnetCommands NAME CODE MEANING SE 240 End of subnegotiation parameters. NOP 241 No operation. Data Mark 242 The data stream portion of a Synch. This should always be accompanied by a TCP Urgent notification. Break 243 NVT character BRK. Interrupt Process 244 The function IP. Abort output 245 The function AO. Are You There 246 The function AYT. Erase character 247 The function EC. Erase Line 248 The function EL. Go ahead 249 The GA signal. SB 250 Indicates that what follows is subnegotiation of the indicated option.

  11. TelnetCommands WILL (option code) 251 Indicates the desire to begin performing, or confirmation that you are now performing, the indicated option. WON'T (option code) 252 Indicates the refusal to perform, or continue performing, the indicated option. DO (option code) 253 Indicates the request that the other party perform, or confirmation that you are expecting the other party to perform, the indicated option. DON'T (option code) 254 Indicates the demand that the other party stop performing, or confirmation that you are no longer expecting the other party to perform, the indicated option. IAC 255 Data Byte 255.

  12. FTPFile Transfer Protocol • Objectives • History • Terminology, Model • Commands • Process • Relation to Other Application Protocols

  13. Objectives of FTP • Promote … file sharing • Encourage … indirect / implicit use of remote computers • Shield … user from file system variations • Facilitate … reliable and efficient data transfer

  14. Objectives of FTP “FTP, though usable directly by a user at a terminal, is designed mainly for use by programs.” -- Postel, Reynolds, RFC 959, October 1985

  15. FTPHistory • MIT 1971 (NCP) • RFC 114 • RFC 141 • 1972 (NCP) • RFC 354 • 1980 (TCP) • RFC 765

  16. FTPTerminology • data connection • A simplex connection over which data is transferred, in a specified mode and type. • DTP • data transfer process server-DTP, user-DTP • active and passive states • PI • protocol interpreterserver-PI, user-PI

  17. FTP Model

  18. FTP Model • Connections • do not need to exist all of the time • bi-directional • User-PI initiates TELNET connection • FTP commands sent to server via TELNET • control the data connection • Replies sent from server-PI to user-PI via TELNET

  19. FTPModel • User-DTP listens (like a server) on data port • Data port does not need to be on same host as sender of FTP commands • Can transfer data between two remote hosts

  20. FTPCommands • Access Control Commands • user • password • quit • Transfer Parameter Commands • PORT h1,h2,h3,h4,p1,p2 • data port = p1 * 256 + p2 • PASV (passive) • order server-DTP to listen • ordinarily, server-DTP initiates a connection request

  21. FTPCommands • RETR • STOR • APPE • DELE • CWD • LIST

  22. SMTP • Simple Mail Transport Protocol • Model • at user request, two-way comm channel set up between sender-SMTP and receiver-SMTP • receiver may be ultimate or intermediate • commands are send and replies are received • use Telnet to port 25 • try help to see commands

  23. SMTP • Receiver-SMTP writes (appends) to file • typically a mailbox file • Receiver-SMTP sends replies back to sender-SMTP

  24. SMTPCommands • HELO • MAIL TO: • RCPT FROM: • DATA • QUIT

More Related