BACP: Bandwidth Allocation Control Protocol
The Bandwidth Allocation Control Protocol (BACP) is the associated control protocol for Bandwidth Allocation Protocol. BACP provides Multilink PPP peers with the ability to govern link utilization. Once peers have successfully negotiated using BACP, they can use the Bandwidth Allocation Protocol (BAP) to negotiate bandwidth allocation.
Standard Organization: IETF
Reference Document: RFC 2125
Banyan VINES Protocols
Banyan Virtual Integrated Network Service (VINES) is a protocol stack defined by Banyan Company, derived from the Xerox Network Systems (XNS) protocols. VINES is based on the UNIX operating system and uses a client/server architecture. The Banyan suite includes the following protocols: VARP (VINES Address Resolution Protocol); VIP (VINES Internet Protocol); ICP (Internet Control Protocol); RTP (Routing Update Protocol); IPC (InterProcess Communications Protocol); SPP (Sequenced Packet Protocol); NetRPC (NetRemote Procedure Call); SteetTalk.
In October 1999 Banyan became ePresence, an internet service provider. At the same time, it announced the obsolescence of VINES and other Banyan products.
Standard Organization: Banyan
BAP: Bandwidth Allocation Protocol
The Bandwidth Allocation Protocol (BAP) can be used to manage the number of links in a multi-link bundle. BAP defines datagrams to coordinate adding and removing individual links in a multi-link bundle, as well as specifying which peer is responsible for various decisions regarding managing bandwidth during a multi-link connection. BAP provides a set of rules governing dynamic bandwidth allocation through call control. Bandwidth Allocation Control Protocol (BACP) is the associated control protocol for BAP to connect two peers. After BACP reaches the opened state, either peer MAY request another link be added to the bundle by sending a BAP Call- or Callback-Request packet. A Call-Request packet is sent if the implementation wishes to originate the call for the new link, and a Callback-Request packet is sent if the implementation wishes its peer to originate the call for the new link. The implementation receiving a Call- or Callback-Request MUST respond with a Call- or Callback-Response with a valid Response Code. The removal of a link is controlled by a link drop message in BAP.
Standard Organization: IETF
Reference Document: RFC 2125
Basic NAT: Basic Network Address Translation
Basic Network Address Translation (Basic NAT) is a method by which IP addresses are mapped from one group to another, transparent to end users. Network Address Port Translation, or NAPT, is a method by which many network addresses and their TCP/UDP ports are translated into a single network address and its TCP/UDP ports. Together, these two operations, referred to as traditional NAT, provide a mechanism to connect a realm with private addresses to an external realm with globally unique registered addresses.
Standard Organization: IETF
Reference Document: RFC 3022
BCAST: Broadcast Protocol
Broadcast Protocol (BCAST), a Novell protocol in the NetWare suite, deals with announcements from the network running Netware to inform the user when receiving a message.
Standard Organization: Novell
BCP: Bridging Control Protocol
The Bridging Control Protocol (BCP), a protocol in the Point-Point Protocol (PPP) suite, is responsible for configuring the bridging protocol parameters on both ends of the point-to-point link. BCP uses the same packet exchange mechanism as the Link Control Protocol. BCP packets cannot be exchanged until PPP has reached the Network-Layer Protocol phase. BCP packets received before this phase is reached are discarded.
Standard Organization: IETF
Reference Document: RFC 3518
BEEP: Blocks Extensible Exchange Protocol
Blocks Extensible Exchange Protocol(BEEP) is a framework for creating network application protocols, that is intended to abstract out the common features that have traditionally been duplicated in each protocol implementation. BEEP is a generic application protocol kernel for connection-oriented, asynchronous interactions. BEEP permits simultaneous and independent exchanges within the context of a single application user-identity, supporting both textual and binary messages.
Standard Organization: IETF
Reference Document: RFC 3080
BFD: Bidirectional Forwarding Detection
Bidirectional Forwarding Detection (BFD) is a network protocol used to detect faults between two forwarding engines. BFD provides low-overhead, low-latency detection of faults even on physical media that don't support failure detection of any kind, such as ethernet, virtual circuits, tunnels and MPLS LSPs. BFD establishes a session between two endpoints over a particular link. If more than one link exists between two systems, multiple BFD sessions may be established to monitor each one of them. The session is established with a three-way handshake, and is torn down the same way.
Standard Organization: IETF
BGMP: Border Gateway Multicast Protocol
Border Gateway Multicast Protocol (BGMP) is a protocol for inter-domain multicast routing. BGMP natively supports "source-specific multicast" (SSM). To also support "any-source multicast" (ASM), BGMP builds shared trees for active multicast groups and allows domains to build source-specific, inter-domain distribution branches where needed. Building upon concepts from PIM-SM and CBT, BGMP requires that each global multicast group be associated with a single root. However, in BGMP, the root is an entire exchange or domain, rather than a single router.
Standard Organization: IETF
Reference Document: RFC 3913
BGP: Border Gateway Protocol
The Border Gateway Protocol (BGP) runs over TCP and is an inter-Autonomous System routing protocol. BGP is the only protocol that is designed to deal with a network of the Internet's size and the only protocol that can deal well with having multiple connections to unrelated routing domains. It is built on experience gained with EGP. The primary function of a BGP system is to exchange network reachability information with other BGP systems.
Standard Organization: IETF
Reference Document: RFC 1771
BGP-4: Border Gateway Protocol version 4
The Border Gateway Protocol (BGP) is the routing protocol used to exchange routing information across networks. BGP runs over TCP and is an inter-Autonomous System routing protocol. Border Gateway Protocol version 4 (BGP-4), the current version of BGP, provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms which allow aggregation of routes, including aggregation of AS paths.
Standard Organization: IETF
Reference Document: RFC 4271
BIC: Broadband Inter Carrier
Broadband Inter-Carrier (BIC), also known as Broadband Inter-Carrier Interface (BICI) or BISDN Inter-Carrier Interface, is an ITU-T standard that defines the protocols and procedures needed for establishing, maintaining, and terminating broadband switched virtual connections between public networks.
Standard Organization: ITU-T
BICC: Bearer Independent Call Control
Bearer Independent Call Control (BICC) is a signaling protocol based on N-ISUP that is used to support narrowband ISDN service over a broadband backbone network without interfering with interfaces to the existing network and end-to-end services. BICC was designed to be fully compatible with existing networks and any system capable of carrying voice messages.
Standard Organization: ITU-T
Reference Document: Q.1901
B-ICI: BISDN Inter Carrier Interface
BISDN Inter Carrier Interface (B-ICI), also known as Broadband Inter-Carrier Interface (BCI), is based on Broadband ISDN User Part (B-ISUP) signaling messages and parameters. BICI is an interface connecting two different ATM based public network providers or carriers. B-ICI is used to facilitate end-to-end national and international ATM/BISDN services. The B-ICI specification also includes service specific functions above the ATM layer required to transport, operate and manage a variety of intercarrier services across the B-ICI.
Standard Organization: ITU-T
BIDIR-PIM: Bi-directional PIM
Bi-directional PIM (BIDIR-PIM) is one of the Protocol Independent Multicast (PIM) protocols based on PIM-SM. The main difference of BIDIR-PIM from PIM-SM is in the method used to send data from a source to the RP. Whereas in PIM-SM data is sent using either encapsulation or a source-based tree, in BIDIR-PIM the data flows to the RP along the shared tree, which is bi-directional. The main advantage of BIDIR-PIM is that it scales very well when there are many sources for each group. However, the lack of source-based trees means that traffic is forced to remain on the possibly inefficient shared tree. BIDIR-PIM is not used often in real world.
Standard Organization: IETF
BISDN: Broadband Integrated Services Digital Network
Broadband Integrated Services Digital Network (BISDN or Broadband ISDN) is designed to handle high-bandwidth applications. BISDN currently uses ATM technology over SONET-based transmission circuits to provide data rates from 155 to 622 Mbps and beyond, in contrast with the traditional narrowband ISDN (or N-ISDN), which is only 64 kps basically and up to 2 Mbps maximum.
Standard Organization: ITU-T
BISUP: Broadband ISDN User Part
Broadband ISDN User Part (BISUP) is a protocol intended to support services such as high-definition television (HDTV), multilingual TV, voice and image storage and retrieval, video conferencing, high-speed LANs and multimedia. Since BISDN is not deployed widely so far, so is not the BISUP.
Standard Organization: ITU-T
Reference Document: Q.2763
BISYNC
BISYNC, also known as Binary Synchronous Communication (BSC), is an old IBM protocol that was originally designed for batch transmissions between the IBM S/360 mainframe family and IBM 2780 and 3780 terminals. BISYNC establishes rules for transmitting binary-coded data between a terminal and a host computer's BISYNC port. While BISYNC is a half-duplex protocol, it will synchronize in both directions on a full-duplex channel. BISYNC supports both point-to-point (over leased or dial-up lines) and multipoint transmissions. BISYNC was replaced by SDLC (Synchronous Data Link Control).
Standard Organization: IBM
Bluetooth
Bluetooth, defined in IEEE 802.15, is for wireless personal area networks (WPANs), which has characters such as short-range, low power, low cost, small networks and communication of devices within a Personal Operating Space. Bluetooth is for wireless transmission between a wide variety of devices such as PCs, cordless phone, headsets and PDAs within 10 meter range.
Standard Organization: IEEE
Reference Document: IEEE 802.15.1
BMP: Burst Mode Protocol
The Burst Mode Protocol (BMP), a protocol in the Novell NetWare suite, was designed to allow multiple responses to a single request for file reads and writes. Burst Mode increases the efficiency of client/server communications by allowing workstations to submit a single file read or write request and receive up to 64 kilobytes of data without submitting another request. BMP is actually a type of NetWare Core Protocol (NCP) packet (Request type = 7777H).
Standard Organization: Novell
BOOTP: Bootstrap Protocol
The Bootstrap Protocol (BOOTP) is an UDP/IP-based protocol which allows a booting host to configure itself dynamically and without user supervision. BOOTP provides a means to notify a host of its assigned IP address, the IP address of a boot server host and the name of a file to be loaded into memory and executed. Other configuration information, such as the local subnet mask, the local time offset, the addresses of default routers and the addresses of various Internet servers, can also be communicated to a host using BOOTP.
Standard Organization: IETF
Reference Document: RFC 951
BPDU: Bridge Protocol Data Unit
Bridge Protocol Data Unit (BPDU), a protocol in the PPP suite, refers to some of "hello packets" of the spanning tree protocol sent out at intervals to exchange information among bridges in the network. BPDUs help describe and identify attributes of a switch port and allow for switches to obtain information about each other.
Standard Organization: IETF
BPON: Broadband Passive Optical Network
Broadband Passive Optical Network (BPON) is renamed from the ATM PON (APON) which is defined by the Full Service Access Network (FSAN) group. Since using of the term APON led users to believe that only ATM services could be provided to end-users, the FSAN decided to broaden the name to Broadband PON (BPON). BPON systems offer numerous broadband services including Ethernet access and video distribution.
Standard Organization: ITU-T
BSC: Binary Synchronous Communication
Binary Synchronous Communication (BSC), also known as bisync, is an old IBM protocol that was originally designed for batch transmissions between the IBM S/360 mainframe family and IBM 2780 and 3780 terminals. BISYNC establishes rules for transmitting binary-coded data between a terminal and a host computer's BISYNC port. While BISYNC is a half-duplex protocol, it will synchronize in both directions on a full-duplex channel. BISYNC supports both point-to-point (over leased or dial-up lines) and multipoint transmissions. BISYNC was replaced by SDLC (Synchronous Data Link Control).
Standard Organization: IBM
BVCP: Banyan VINES Control Protocol
Banyan VINES Control Protocol(BVCP), as defined in IETF RFC 1763, is responsible for configuring, enabling, and disabling the VINES protocol modules on both ends of the point-to-point (PPP) link. In order to establish communications over a point-to-point link, each end of the PPP link must first send LCP packets to configure and test the data link. After the link has been established and optional facilities have been negotiated as needed by the LCP, PPP must send BVCP packets to choose and configure the VINES network-layer protocol. Once BVCP has reached the Opened state, VINES datagrams can be sent over the link. The link will remain configured for communications until explicit LCP or BVCP packets close the link down, or until some external event occurs (an inactivity timer expires or network administrator intervention).
Standard Organization: IETF
Reference Document: RFC 1763