Xblue Networks X-50 - Manual (Page 27)

XBLUE Networks 27
System Specifications
2
TABLE 2.9 Internet Protocol
Protocol Documentation Description
IP Address RFC 950 Defines the standards used to divide Class A, B and C using Subnets.
ARP RFC 826, 3315 Address Resolution Protocol - allows devices to find a “host” device using
the network layer (MAC Address).
RARP RFC 903 Reverse Address Resolution Protocol - allows devices to find a “host”
device using the network layer (MAC Address).
CHAP RFC 1994 Challenge-Handshake Authentication Protocol - Negotiating protocol used
with PPPoE. Also see MSCHAP and PAP
MSCHAP RFC 2433, 2759 Microsoft’s version of CHAP that allows mutual authentication between
peers, by piggybacking challenge and response packets on a successful
packet.
PAP RFC 1334 Simple method for the peer to establish its identity using a 2-way un-
encrypted handshake. Passwords are sent in ASCII format with no
encryption. Also see CHAP, and MSCHAP.
DHCP
Client RFC 2131 - 2132 Dynamic Host Configuration Protocol is used by client devices, to obtain
the correct settings, when joining a network.
DHCP
Server RFC 2132 Dynamic Host Configuration Protocol is used by server devices, to obtain
or assign the correct settings, when joining a network.
DNS RFC 1912 A Domain Name System is the “Phone Book” for the Internet. It translates
“Human Relatable” names such as
www.xbluenetworks.com into the
numeric IP Address. The DNS can be a local or remote server, and it is a
essential part of today’s Internet.
HTTP RFC 2616 Hypertext Transfer Protocol - is one of the communications protocols used
to transfer information over a packet-switched network, such as an
Intranet or the Internet. Typically, HTTP (at default using port 80) initiates
or receives a request/response from a client to/from a server.
ICMP RFC 792 Internet Control Message Protocol is one of the core protocols within
Internet Protocol (IP). This protocol is a reactionary protocol only
responding to error messages that are received.
IP RFC 791 Internet Protocol allows devices to communicate over a package-switched
network. This protocol provides an unreliable network, and makes no
guarantees about sending or receiving a data package; it is a “best Effort”
protocol. Therefore, other protocols such as “TCP” were created to make
data transfer more reliable.
NAT RFC 3022 Network Address Translation allows multiple hosts, on one private
network, to access the Internet using one public IP Address.
NAPT RFC 2663 Network Address Port Translation increases the efficiency of NAT by
translating the “transport identifier”, allowing a private host to multiplex
into the transport identifiers to appear as a single Public IP Address.
PPPoE RFC 2516 Point to Point over Ethernet allows users to “Virtually” create a direct
connection between two devices over an Ethernet network.
SNTP RFC 1305 Simple Network Time Protocol allows devices packet-switched networks to
synchronize their time from a specific location.
NPT RFC 867, 868 Network Time Protocol ensures that the time is synchronized all along the
Packet Switching Network.
TCP RFC 793 Transmission Control Protocol provides the reliability that Internet Protocol
(IP) does not, making it suitable for applications such as File Transfer and
E-mail.