Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
TCP/IP Ch 5- 7 Terms
Terms for TCP/IP Chapter 5, 6, and 7
| Question | Answer |
|---|---|
| Two Transport layer protocols | UDP and TCP |
| UDP | User Datagram Protocol |
| TCP | Transmission Control Protocol |
| Connectionless Transport layer protocol | UDP |
| Connection-oriented Transport layer protocol | TCP |
| Used by TCP to track the transfer of data and ensure sucessful delivery | acknowledgments and sequence numbers |
| Range of addresses for well-known ports | 0-1023 |
| Range of addresses that corresponds to registered port numbers | 1024-49151 |
| Range of addresses that correspond to dynamic port numbers | 49152 - 65535 |
| characteristics of a connection-oriented protocol like TCP | delivery quarantee, connection handling, segmentation and reassembly, message-level checksum in header, eplicit transmission acknowledgments |
| TCP process used to maintain an active connection between hosts | keep-alive |
| Number of steps in the TCP handshake process | three |
| Steps of the TCP handshake | SYN, SYN ACK, ACK |
| Notification of successful receipt of data | acknowledgment |
| The amount of data that a receiver states that it can handle in its TCP buffer space. | advertised window |
| Measurement of the amount of information that can cross the network | bandwidth |
| Condition of overload on a network or receiver | congestion |
| Attack that causes a system to refuse services because its busy handling attack requests. | DoS (Denial of Service attack) |
| Tempory port number used for one communication process. Are cleared after the connection is closed and a four-minute wait time | dynamic port numbers |
| Procedure for retransmitting missing or damaged data. Examples: drop in current window size | error recovery |
| TCP connection not completed with a final ack. Indication of a Dos attack. | half-open connection |
| process of setting up virtual connection between TCP peers. Consists of 3 packets. | handshake process |
| Time value that determines whan a TCP host retransmits a packet after it was lost. | RTO (retransmission timeout) |
| TCP windowing problem caused by an application removing only small amounts of data from a full TCP receive buffer, causing the peer to advertise a very small window size. | SWS (Silly Window Syndrome) |
| Queuing area used to hold incoming and outgoing TCP packets | TCP buffer |
| Process of acknowledging multiple packets with a single ack | windowing |
| Situation when a TCP peer advertises a window value of 0. TCP host cannot continue to send to TCP peer that advertises a window size of 0. | zero-window state |
| UDP | No reliability, No delivery guarantees, no connection handling, does identify the application layer protocol used by use of port numbers, no buffering, and no segmentation. Up to 40% faster that TCP because no overhead. |
| Port numbers assigned to key or core services used by the system | well-known ports |
| Port numbers assigned to industry applications and processes | registered port numbers |
| TFTP port number and transport layer protocol | UDP port 69 |
| DHCP port number and transport layer protocol | UDP port 67 and 68 |
| DNS port number and transport layer protocol | UDP/TCP port 53 |
| FTP port number and transport layer protocol | TCP port 21 |
| Telnet port number and transport layer protocol | TCP port 23 |
| HTTP port number and transport layer protocol | TCP port 80 |
| POP3 port number and transport layer protocol | TCP port 110 |
| TCP Connection Termination | FIN ACK, ACK, FIN ACK, ACK |
| byte stream | A continuous stream of data that contains no boundaries. |
| congestion | A condition of overload on a network or at a receiver. When the network is congested, senders cannot continue to send TCP packets. To avoid congesting a receiver, the receiver advertises a window size of zero. |
| connectionless | protocolA protocol that simply sends datagrams without establishing, managing, or otherwise handling a connection between sender and receiver; UDP is a connectionless Transport layer protocol. |
| core services | Primary and key services used in TCP/IP networking. FTP, DNS, and DHCP are considered core services. These services are assigned the well-known ports 0 - 1023 |
| current window | The actual window size being used at the time. A sender determines the current window size by using the receiver’s advertised window and the network congestion window (what the network can handle). |
| Denial of Service (DoS | An attack that causes a system to refuse services because it is busy handling attack requests. |
| dynamic port number | A temporary port number used just for one communication process. These port numbers are cleared after the connection is closed and a four minute wait time. |
| half open connections | A TCP connection that is not completed with a final acknowledgment. These half |
| handshake process | The process of setting up a virtual connection between TCP peers. The handshake process consists of three packets used to set up the starting sequence number that each TCP peer will use for communications. |
| keep alive process | The procedure of maintaining an idle connection. TCP connections can be kept alive through TCP keep |
| Maximum Segment Size (MSS) | The maximum amount of data that can fit in a TCP packet after the TCP header. Each TCP peer shares the MSS during the handshake process. |
| retransmission timeout (RTO) | The time value that determines when a TCP host retransmits a packet after it was lost. The RTO value is exponentially increased after an apparent connection loss. |
| sliding window | A set of data that is sent along a sliding timeline. As transmitted data is acknowledged, the window moves over to send more data to the TCP peer. |
| TCP buffer area | A queuing area used to hold incoming and outgoing TCP packets. If a TCP packet has the Push flag set, the packet should not be held in either the incoming or outgoing TCP buffer area. |
| temporary port | A port that is used for the duration of the connection. The port numbers assigned to temporary ports also are called dynamic port numbers or ephemeral port numbers. |
| windowing | The process of acknowledging multiple packets with a single acknowledgment. |
| bot | Short for robot or sometimes Web robot, a specially programmed Web program that interacts with Web sites without requiring a human to steer or control its activities. |
| client/server | A type of relationship between two computer hosts in which one host takes on the role of requesting services (the client) and the other the role of responding to service requests (the server) |
| Finger | Short for Finger User Information Protocol, Finger provides information about individual users or hosts on the Internet. |
| load balancing | A method of distributing the processing load for service requests by directing individual requests for service to multiple machines in a way that causes the numbers of such requests per machine to be as nearly equal (or balanced) as possible. |
| MSN Messenger | A proprietary protocol specification that provides an asynchronous communications framework for establishing Internet presence and real time instant messaging. Though it primarily serves as a basic ASCII |
| presence | Information about whether a client is offline, available, or online but unavailable (used in both instant messaging and Voice over IP applications to help users decide if they can or should initiate communications with specific parties). |
| pull | A method of replicating server data in which the receiver initiates the transfer, thereby pulling that data from its original source. |
| push | A method of replicating server data in which the sender initiates the transfer, thereby pushing that data to the receiver. |
| Quote of the Day (QOD) | A basic TCP/IP service that delivers a short stream of text (usually a joke or an epigram) in response to a request for service. |
| Secure Sockets Layer (SSL) | A standard programming interface that encrypts outgoing data before passing it to the Transport layer and decrypts incoming data before passing it to the Application layer. SSL provides a handy way to improve the security of networked communications. |
| Secure Telnet (Stelnet) | A special implementation of Telnet that uses SSL, or a secure shell, to encrypt outgoing traffic and decrypt incoming traffic to prevent such traffic from being snooped en route between sender and receiver. |
| Trivial File Transfer Protocol (TFTP) | A basic TCP/IP Application layer service that supports lightweight file transfer from a local host to a remote host (especially in the context of a local user who’s logged on to the remote host). Uses UDP! |
| Uniform Resource Identifier (URI) | A generic term for all types of names and addresses that refer to objects on the Web. A URL is one kind of URI. |
| Voice over Internet Protocol (VoIP) | VoIP is a method for routing real time voice communication and multiplexing videoconference streams for transmission across a packet switched network. |
| Whois | A client utility used to access a remote server database of domain or IP address registries. Because many domain names are not registered in the databases that Whois searches. |
| address (A) record | A DNS resource record that maps domain names to IP addresses. |
| address request | A DNS service request for an IP address that matches a domain name. |
| authoritative response | A reply to a query from the name server that’s authoritative for the zone in which the requested name or address resides. |
| authoritative server | The DNS server that’s responsible for one or more particular zones in the DNS database environment. |
| available | The quality of quickly responding to user requests for service. |
| BIND (Berkeley Internet Name Domain) | The most popular implementation of DNS server software on the Internet today. |
| caching | Storing remote information locally once obtained, so if it is needed again, it may be accessed much more quickly. Both DNS resolvers (clients) and DNS servers cache DNS data to lower the odds that a remote query will have to be resolved. |
| caching server | A DNS server that stores valid name and address pairs already looked up, along with invalid names and addresses already detected. Any DNS server can cache data, including primary, secondary, and caching |
| caching only server | A DNS server that does not have primary or secondary zone database responsibilities, this type of server is used only to cache already |
| canonical name (CNAME) record | The DNS RR used to define database aliases, primarily to make it quicker and easier to edit and manage DNS zone files. |
| delegation of authority | The principle whereby one name server designates another name server to handle some or all of the zone files for the domain or subdomains under its purview. |
| distributed database technology | A database that’s managed by multiple database servers, each of which has responsibility for some distinct portion of a global database. |
| DNS database segment | A distinct and autonomous subset of data from the DNS name and address hierarchy. A DNS database segment usually corresponds to a DNS database zone and is stored in a collection of interrelated zone files. See also zone and zone file. |
| DNS round robin | A method of managing server congestion in which a DNS server keeps track of which IP addresses it has provided most recently for a specific translation and rotates them within the pool or list of addresses available. |
| domain name hierarchy | The entire global namespace for the domain names that DNS manages on the Internet. This space includes all registered and active domain names. |
| domain name resolution | The process whereby DNS translates a domain name into a corresponding numeric IP address. |
| fully qualified domain name (FQDN) | A special form of a domain name that ends with a period to indicate the root of the domain name hierarchy. You must use FQDNs in DNS A and PTR resource records. |
| host information (HINFO) record | A DNS resource record that provides information about some specific host, as specified by its domain name. |
| HOSTS | A special text file that lists known domain names and corresponding IP addresses, thereby defining a static method for domain name resolution. |
| incremental zone transfer | A type of DNS query that limits updates from a primary DNS server to one or more secondary DNS servers only to data that has changed on the primary server. |
| inverse DNS query | A DNS query that supplies an IP address for conversion to a corresponding domain name. Inverse DNS queries are often used to double check user identities to make sure that the domain names they present match the IP addresses in their packet headers. |
| IP spoofing | A technique where a programmer constructs an IP packet that presents domain name credentials that differ from the IP address in the packet header. IP spoofing is often used in illicit network break in attempts, or to impersonate users or packet source |
| iterative query | A DNS query that targets one specific DNS server and terminates with whatever response may be forthcoming, whether that response is a definite answer, an error message, a null (no information) reply, or a pointer to another name server. |
| mail exchange (MX) record | A DNS resource record that’s used to identify the domain name for the email server that handles any particular domain or subdomain, or that’s used to route e |
| multihomed | Containing multiple network interfaces capable of attaching to multiple subnets. |
| name query | An inverse DNS query that seeks to obtain a domain name for a corresponding numeric IP address. |
| name resolver | A client side software component, usually part of a TCP/IP stack implementation, that’s responsible for issuing DNS queries for applications, and relaying whatever responses come back to those applications. |
| name server (NS) record | The DNS resource record that identifies name servers that are authoritative for some particular domain or subdomain. Often used as a mechanism to delegate authority for DNS subdomains downward in the domain name hierarchy. |
| negative caching | A technique for storing error messages in a local cache so that repeating a query that previously produced an error message can be satisfied more quickly than if that query was forwarded to some other DNS name server. |
| non-authoritative response | Name, address, or RR information from a DNS server that’s not authoritative for the DNS zone being queried (such responses originate from caches on such servers). |
| NSLOOKUP | A widely implemented command line program that supports DNS lookup and reporting capabilities. The “NS” in this command name stands for “name server,” so it’s reasonable to think of this as a general |
| pointer (PTR) record | The DNS resource record that’s used for inverse lookups to map numeric IP addresses to domain names. |
| primary DNS server | The name server that’s authoritative for some particular domain or subdomain and has primary custody over the DNS database segment (and related zone files) for that A type of DNS query that continues until a answer is returned. |
| recursive query | address translation, contents of the requested resource record(s), or an error message of some kind. |
| resource record (RR) | One of a series of pre-defined record types in a DNS database or a DNS zone file. |
| robust | The condition of being ready for use under almost any circumstances; DNS allows multiple name servers to respond to queries about the same database zone to improve the odds that at least one such server will be able to respond to such queries. |
| root | The highest level in the domain name hierarchy, the root is symbolized by a final period in a fully qualified domain name. |
| secondary DNS server | A DNS server that contains a copy of a domain or subdomain database, along with copies of the related zone files, but which must synchronize its database and related files with whatever server is primary for that domain or subdomain. |
| Start of Authority (SOA) record | The DNS resource record that’s mandatory in every DNS zone file, the SOA record identifies the server or servers that are authoritative for the domain or subdomain to which the zone files or database correspond. |
| subdomain | A named element within a specific domain name, denoted by adding an additional name and period before the parent domain name. Thus, clearlake.ibm.com is a subdomain of the ibm.com domain. |
| text (TXT) record | A DNS resource record that can accommodate arbitrary ASCII text data, often used to describe a DNS database segment, the hosts it contains, and so forth. |
| tree structure | The domain name hierarchy adheres to an inverted tree structure because the root usually appears at the top of diagrams drawn to represent it. |
| zone | A portion of the domain name hierarchy that corresponds to the database segment managed by some particular name server, or collection of name servers. |
| zone data file | Any of several specific files used to capture DNS database information for static storage when a DNS server is shut down, or when a secondary DNS server requests synchronization with its primary DNS server’s database. |
| zone transfer | The DNS mechanism in which a secondary DNS server gets its data for the zone from the master server for that zone. |
Created by:
Leisac
Popular Computers sets