Point-to-Point Protocol (PPP)

RFC1661

WAN protocol that allows interworking with a wide range of third-party routers. PPP is used over leased line circuits where a single channel is used to connect the two locations together. For example, a single channel maybe a 64K channel on a dial-up circuit or a 256K leased line etc.

Link Control Protocol (LCP)

RFC1570

In PPP, LCP establishes, configures and tests data-link Internet connections.

Multi-Link Point-to-Point Protocol (ML-PPP)

RFC1990

Allows additional calls to be made where bandwidth greater than a single channel is required. The maximum number of channels available to data can be set on a service-by-service basis. When the available bandwidth reaches a user defined limit additional channels can be automatically added. Similarly, when traffic falls then the number of channels in use can be automatically reduced. If there is no data traffic on any of the channels in use then all lines can be cleared. Since most carriers have a minimum charge for calls, the period that a channel has to be idle before clearing is configurable. Through these mechanisms call costs can be effectively controlled while ensuring that bandwidth is available as and when it is needed.

Internet Protocol Control Protocol (IPCP)

RFC1332

A Network Control Protocol (NCP) for establishing and configuring IP over a PPP.

Internet Protocol Header Compression (IPHC)

-

Reduces the header size of the data packet to gain bandwidth efficiency over WANs, but adds to transmission latency.

Password Authentication Protocol (PAP)

RFC1334

A method of authenticating the remote end of a connection using unencrypted passwords.

Real-time Transport Protocol (RTP)

Real-time Transport Control Protocol (RTCP)

RFC1889

RTP defines a standardized packet format for delivering audio and video over IP networks.

RTCP works with RTP to send control packets to call participants to provide feedback on the quality of service.

Challenge Handshake Authentication Protocol (CHAP)

RFC1994

Allows an incoming data call to be authenticated using encrypted passwords. The system also provides the option to periodically reaffirm the authenticity of the caller during the data call.

Compression Control Protocol (CCP)

RFC1962

Configures, enables and disables data compression algorithms on both ends of the PPP link. Also used for signal a failure.

Light-weight Directory Access Protocol (LDAP)

RFC4510

Allows the telephone number directory (names and telephone numbers) held in IP Office to be synchronized with the information on an LDAP server (limited to 5000 entries). Although targeted for interoperation with Windows 2000 Server Active Directory, the feature is sufficiently configurable to interoperate with any server that supports LDAP version 2 or higher.

Microsoft Point-to-Point Compression (MPPC)

RFC2118

Data compression method for greater throughput on slow speed WAN links.

Bandwidth Allocation Control Protocol (BACP)

RFC2125

Allows the negotiation with the remote end of the data call to request additional calls to be made to improve aggregate data throughput.

User Datagram Protocol (UDP)

RFC768

A simple connectionless transmission model with a minimum of protocol mechanism used to allow applications to send messages (datagrams) to other hosts on an IP network without prior communications to set up special transmission channels or data paths.

Internet Protocol (IP)

RFC791

A set of rules governing the format of data sent over the Internet or other network.

Transmission Control Protocol (TCP)

RFC793

A connection is established an maintained until the application at each end have finished engaging messages.

Dynamic Host Configuration Protocol (DHCP)

RFC1533

Dynamically distributes network configuration parameters on and IP network such as IP addresses for interfaces and services.

Network Address Translation (NAT)

RFC1631

A mechanism that allows the use of different IP address on a private network behind a router with a public IP Address. When connecting to the Internet, ISPs typically want a customer to use an IP address they have allocated. Using NAT this is easily accommodated, eradicating the need for the customer to change their network numbering scheme and providing additional security to the internal users as their address in hidden to the public.

Typically, a company maps its internal network addresses to a global external IP address and unmaps the global IP address on incoming packets back into internal IP addresses. This helps ensure security since each outgoing or incoming request must go through a translation process. This also offers the opportunity to qualify or authenticate the request or match it to a previous request. NAT also conserves the number of global IP addresses that a company needs.

Bootstrap Protocol (BOOTP)

RFC951

Automatically assigns an IP address to network devices from a configuration server on an IP network.

Trivial File Transfer Protocol (TFTP)

RFC1350

A simple protocol to transfer files implemented on top of the UDP using port number 69.

Network Time Protocol (NTP)

RFC868

Provides clock synchronization between computer systems over packet-switched, variable latency data networks.

Proxy Address Resolution Protocol (ARP)

-

Support for Proxy Address Resolution Protocol allows IP Office to respond on behalf of the IP address of a device connected to it when receiving an ARP request.

Simple Network Managment Protocol (SNMPv1)

RFC1157

RFC1155

RFC1212

RFC1215

Simple Network Management Protocol. (STD15)

Structure and identification of management information for TCP/IP based internets. (STD16)

Concise MIB Definitions. (STD16)

A convention for defining traps for use with SNMP

Managment Information Base (MIB-II)

RFC1213

Management Information base for network management of TCP/IP based internets: MIB-II. (STD17)

ENTITY MIB

RFC2737

Entity MIB (Version 2)

Routing Information Protocol (RIP)

RFC1058

RFC2453

RFC1722

Adistance vector protocol that allows routers to determine the shortest route to a destination network. It does this by measuring the number of intermediary routers that need to be traversed to reach the destination network. If more than one route exists to the same destination the shortest route is used. If a fault occurs on the shortest route it will be remarked as being infinite and any alternative route will become the new shortest route. This behavior can be used to add resilience into a data network. Where a customer has an existing data network comprising of third party routers, IP Office added to the network can provide back up using its routing and dial-up capability. RIP enabled routers share their knowledge of the network with each other by advertising and listening to routing table changes. IP Office Supports both the RIP I and RIP II standards.

Internet Protocol Security (IPSec)

RFC2401

RFC2402

RFC2403

RFC2404

RFC2405

RFC2406

RFC2407

RFC2408

RFC2409

RFC2410

RFC2411

Security Architecture for the Internet Protocol

IP Authentication Header

The Use of HMAC-MD5-96 within ESP and AH

The Use of HMAC-SHA-1-96 within ESP and AH

The ESP DES-CBC Cipher Algorithm with Explicit IV

IP Encapsulation Security Payload. (ESP)

The Internet IP Security Domain of Interpolation for ISAKMP

Internet Security Association and Key Management Protocol

The Internet Key Exchange

The NULL Encryption Algorithm and its Use with IPSec

IP Security Document Roadmap

Layer 2 Tunneling Protocol (L2TP)

RFC2661

RFC3193

PPP authentication using PAP or CHAP takes place between directly connected routers only. When using a public IP Network to connect sites this authentication takes place between the customers router and the service provide router that it is connected to. In some circumstances it is desirable to authenticate between the customer owned routers, jumping over all the intermediary routers of the service provider's network. Layer 2 Tunneling Protocol allow this to happen by facilitating a two stage authentication, firstly with the service provider router then the customer router on the remote network.

IPSec tunnels allow a company to pass data between locations over unsecured IP networks such as the public internet. The company data is secured using 3DES encryption making it unintelligible to other parties that might be 'eaves dropping' on the traffic. Tunneling can be applied to link offices together or provide workers access to the office over the internet. All IP Office systems support up to a total of 256K worth of encrypted traffic to multiple locations. Initially, inter-working is supported only between IP Offices that are connected either directly on a WAN port or via the LAN using a third-party router. IPSec is optional and enabled on IP Office through a License Key.

Differentiated Services (DiffServ)

RFC2474

Networking architecture that specifies a simple, scalable and coarse-grained mechanism for classifying and managing network traffic and providing quality of service (QoS) on IP networks.

Frame Relay Encapsulation

RFC 1490

Multi protocol Interconnect over Frame Relay