Fact-checked by Grok 2 weeks ago

Unicast

Unicast is a fundamental communication method in computer networking where data packets are transmitted from a single source to a single specific destination, establishing a point-to-point between sender and receiver. This one-to-one model relies on unique network addresses, such as addresses, to identify the endpoints and ensure targeted delivery. Unicast forms the backbone of most Internet traffic, supporting applications like web browsing, , and remote file access, where efficiency in direct transmission is prioritized over group distribution. In contrast to (one-to-many delivery to a group of recipients) and broadcast (one-to-all transmission across a ), unicast minimizes usage by avoiding redundant packet replication at the source. This approach is the default for IP-based networks, with unicast routing protocols like (Open Shortest Path First) and (Border Gateway Protocol) directing traffic through optimal paths based on destination addresses. Unicast addressing varies by protocol version: in IPv4, unicast addresses comprise 32-bit identifiers from classes A, B, and C (or CIDR blocks), excluding ranges starting with 1110 in binary. In , unicast addresses are 128-bit values that identify a single interface, including subtypes like global unicast (routable worldwide), link-local (for single-link communication), and unique local (site-internal). These addresses support aggregatable hierarchies for scalable routing, with interface identifiers often derived from MAC addresses using methods like Modified EUI-64.

Fundamentals

Definition

Unicast is a fundamental communication paradigm in computer networking that involves the transmission of data packets from a single sender to a single specific receiver. This method ensures that data is directed exclusively to the intended destination, identified by a unique , enabling precise and targeted delivery across interconnected . In contrast to group-oriented approaches like or broadcast, unicast focuses solely on individual point-to-point exchanges. The origins of unicast trace back to the development of early packet-switched networks in the 1970s, particularly the , which was the first operational packet-switching network designed to connect geographically dispersed computers. Initiated by the U.S. Department of Defense's Advanced Research Projects Agency () in 1969, ARPANET demonstrated the feasibility of breaking data into packets for independent routing to specific destinations, laying the groundwork for unicast as the default mode of communication in such systems. This approach evolved significantly with the standardization of the TCP/IP protocol suite in the late 1970s and early 1980s, following the seminal 1974 paper by Vinton Cerf and Robert Kahn that outlined protocols for inter-network packet communication. TCP/IP formalized unicast transmission as a core element, with its adoption on ARPANET in 1983 marking a pivotal transition to the modern architecture. At its core, the unicast process begins with encapsulating application into discrete packets, each including a header that specifies the source and destination . These packets are then routed through the network based on the destination's unique identifier, such as a 32-bit IPv4 , ensuring to the exact without duplication to unintended parties. This encapsulation and addressing mechanism, defined in the (IP), supports reliable end-to-end communication by allowing intermediate routers to forward packets hop-by-hop toward the specified endpoint.

Characteristics

Unicast transmissions are characterized by their point-to-point nature, where data is sent from a single source to a single designated in a manner, facilitating precise and isolated exchanges in networked environments. In connection-oriented s that utilize unicast, reliability is enhanced through mechanisms such as acknowledgments and retransmissions, allowing the sender to confirm receipt and recover lost packets by resending them as needed. These features provide end-to-end , making unicast suitable for applications requiring guaranteed delivery, though they introduce additional overhead in terms of processing. Unicast's bandwidth usage is notable for allocating a full to each individual receiver, which results in multiplied network traffic when serving multiple recipients, as the sender must replicate and transmit separate streams for each. This approach can lead to higher overall resource consumption in scenarios with many destinations, contrasting with methods that share streams across groups. Central to unicast operation is the use of destination-specific addressing, which enables routers to direct packets along unique paths tailored to the intended receiver's identifier, ensuring accurate and efficient delivery across the network. This addressing scheme underpins unicast's role in networks, where unique identifiers distinguish individual endpoints.

Addressing and Routing

Unicast Addressing

Unicast addressing in relies on 32-bit addresses that identify individual hosts or interfaces, originally structured under a classful system as defined in the specification. Class A addresses range from 1.0.0.0 to 126.255.255.255, supporting large networks with up to 16 million hosts; Class B from 128.0.0.0 to 191.255.255.255 for medium-sized networks with up to 65,000 hosts; and Class C from 192.0.0.0 to 223.255.255.255 for smaller networks with up to 254 hosts. These ranges exclude the block from 224.0.0.0 to 239.255.255.255, reserved for group communications, and broadcast addresses such as 255.255.255.255 or network-specific broadcasts like 10.255.255.255. Private unicast addresses, not routable on the public , include 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, enabling internal network use without global registration. In , unicast addressing uses 128-bit addresses to provide a vastly expanded space, with specific formats for different scopes. Global unicast addresses, routable on the public , begin with the 2000::/3 , allowing hierarchical allocation for worldwide connectivity. Unique local addresses, intended for site-internal communications without routing, use the fc00::/7 , with the eighth bit set to 1 for local assignment. Link-local unicast addresses, used for communication within a single network segment, are prefixed with fe80::/10 and automatically configured on interfaces. Within local networks, unicast IP addresses are resolved to underlying link-layer addresses, such as Ethernet addresses, using protocols like the (). operates by broadcasting requests to discover the associated with a target IPv4 unicast address, enabling direct frame delivery on the local segment. The hierarchical structure of unicast addressing, facilitated by (), divides addresses into network prefixes and host identifiers, allowing route aggregation to support scalable packet forwarding across large networks. This prefix-based hierarchy integrates with routing tables to efficiently direct unicast traffic toward destinations.

Routing Mechanisms

In unicast networking, routers forward packets to a specific destination by consulting tables that store prefixes and associated next-hop information. The forwarding decision relies on the (LPM) algorithm, where the router selects the entry with the most specific prefix that matches the packet's destination , ensuring efficient and hierarchical across IP networks. This mechanism allows routers to handle variable-length masks and aggregate routes, optimizing path selection without exhaustive table scans. Several routing protocols populate these tables for unicast environments, each suited to different scales and topologies. Open Shortest Path First (OSPF) is a link-state protocol that enables routers to construct a complete network topology map using flooding of link-state advertisements, then computes shortest paths via Dijkstra's algorithm for intra-domain routing. Border Gateway Protocol (BGP), a path-vector protocol, manages inter-domain routing by exchanging reachability information between autonomous systems, incorporating policy-based decisions to select paths while avoiding loops through attribute comparisons. Routing Information Protocol (RIP), a distance-vector protocol, propagates routing updates based on hop counts, making it suitable for smaller networks despite its limitations in scalability due to periodic full-table broadcasts. Unicast paths are typically established through hop-by-hop forwarding, where each router independently determines the next hop based on its , progressing the packet toward the destination. Alternatively, source routing permits the originating host to specify the full path in the packet header, though this is rarely used in modern networks due to and concerns. To prevent infinite loops during forwarding, the Time to Live (TTL) field in the is decremented by one at each hop; if it reaches zero, the packet is discarded, limiting its lifetime in the network. Unicast routing integrates with end-to-end control mechanisms, particularly in transport protocols like , which employs a sliding window to dynamically adjust the amount of unacknowledged data in flight based on network feedback. This window size grows during slow start and avoidance phases but shrinks multiplicatively upon detecting loss, preventing router queues from overflowing and maintaining fair resource sharing among unicast flows. Unicast addresses facilitate this process by enabling precise destination lookups in tables.

Comparison to Other Methods

With Multicast

Unicast transmission involves sending separate data from to each individual receiver, resulting in network duplication where, for N receivers, must generate N distinct . This approach leads to higher consumption across the , as the same data is replicated multiple times at the sender level. In contrast, multicast employs a single stream from the source to a group of subscribers, managed through protocols such as (IGMP) for host membership and (PIM) for routing, which significantly reduces overall usage by replicating packets only at branch points in the distribution tree closer to the receivers. This efficiency is particularly evident in scenarios with many recipients, where avoids the redundant transmission inherent in unicast. The divergence in use cases highlights their transmission differences: unicast suits personalized, point-to-point communications like (VoIP) calls, where individualized data delivery is essential. Multicast, however, excels in distributing identical content to multiple participants, such as in video conferences, enabling efficient sharing without per-receiver duplication. Regarding overhead, unicast imposes greater CPU load on the sender due to the need for packet replication for each recipient, potentially straining resources in high-receiver scenarios. shifts this burden to the network infrastructure, introducing complexity in router processing for group management and tree maintenance, though it alleviates sender-side demands.

With Broadcast

Unicast transmission directs data packets to a single specific , thereby minimizing unnecessary traffic by ensuring that only the intended recipient processes the information. In contrast, broadcast transmission sends data to all devices within a , such as a (), where the destination is set to the universal broadcast identifier ff:ff:ff:ff:ff:ff, flooding the segment indiscriminately. This all-encompassing approach is useful for discovery protocols but can lead to inefficiencies, as every device must receive and potentially discard irrelevant packets. One key efficiency challenge with broadcast is the risk of broadcast storms, which occur when loops cause repeated flooding of broadcast , overwhelming the and leading to or . These storms are mitigated by protocols like (STP), which detects loops and blocks redundant paths to maintain a loop-free topology in Layer 2 . Unicast avoids such issues inherently through its point-to-point nature, where are forwarded only along the path to the destination without segment-wide replication. Regarding scope, broadcast communication is inherently limited to a single , typically bounded by routers that do not forward broadcast packets beyond the local segment to prevent global propagation. Unicast, however, supports end-to-end delivery across interconnected networks, including the global , via mechanisms that span multiple domains. For instance, protocols like (ARP) rely on a single broadcast within the local domain to resolve IP-to-MAC mappings for subsequent unicast transmissions.

With Anycast

Unicast communication in networks directs packets from a source to a single, specific destination interface identified by a unique , ensuring one-to-one delivery to that exact . In contrast, employs the same across multiple interfaces, typically on different nodes, where protocols deliver packets to the "nearest" interface among them, based on metrics such as shortest path or lowest cost. This receiver selection in anycast introduces a form of dynamic , differing from unicast's fixed targeting. The core routing distinction lies in destination handling: unicast relies on precise address resolution to route exclusively to the designated host, often using protocols like OSPF or BGP for path computation to that singular target. Anycast, however, leverages the same unicast infrastructure but selects the optimal receiver from the anycast set by evaluating proximity in the , without requiring application-layer awareness of multiple endpoints. For instance, in BGP anycast deployments, the advertises the shared from multiple locations, allowing the network to forward traffic to the topologically closest instance, which enhances efficiency in global services. A prominent example of 's application is in DNS root servers, where instances of servers like F-root and K-root share the same IP address and use BGP to route queries to the nearest , reducing and distributing load across geographically dispersed sites—unlike unicast, which would bind queries to a single . While unicast suits direct connections requiring endpoint specificity, anycast excels in scenarios like load balancing and for replicated services.

Applications

In Internet Protocol Networks

Unicast serves as the primary and default transmission mode in both IPv4 and networks, enabling the delivery of datagrams from a single source address to a single destination address for the vast majority of standard IP traffic. In IPv4, as specified in the original , unicast addresses are 32-bit identifiers that uniquely specify hosts, supporting point-to-point communication across internetworks without inherent support for group addressing in routine operations. builds on this foundation with 128-bit addresses, where unicast types such as global unicast and link-local addresses identify individual interfaces, ensuring scalability and routability in larger networks. All interfaces in must assign at least one link-local unicast address, underscoring its foundational role. At the , unicast is integral to protocols that operate over . provides reliable, ordered unicast delivery by initiating connections via a three-way : the client sends a SYN segment, the responds with SYN-, and the client acknowledges with , synchronizing sequence numbers between the specific endpoints. This process confirms mutual and prevents duplicate connections, making suitable for applications demanding error-free transmission. complements this with connectionless unicast, transmitting datagrams directly to a destination without setup overhead, though designers must implement congestion control—such as limiting rates to one datagram per round-trip time—and enable checksums, especially for , to avoid network overload. Unicast underpins numerous client-server applications in IP networks. For instance, web browsing relies on HTTP, where clients send unicast requests to servers over for resource retrieval, establishing temporary connections for each transaction. File Transfer Protocol (FTP) uses unicast for both control commands and data streams, opening separate connections to transfer files between hosts. Email transmission via Simple Mail Transfer Protocol (SMTP) employs unicast to relay messages sequentially from sender to recipient servers, ensuring point-to-point delivery across the . Similarly, Secure Copy Protocol (SCP) leverages SSH over unicast for encrypted file transfers, maintaining secure, directed sessions between endpoints. IPv6 enhances unicast deployment through stateless address autoconfiguration (SLAAC), allowing hosts to autonomously generate global unicast . Hosts combine a 64-bit prefix from router advertisements with a 64-bit identifier, then perform duplicate detection via neighbor solicitations to verify uniqueness before using the for communication. This process eliminates the need for centralized servers in many scenarios, promoting plug-and-play connectivity in unicast-based environments.

In Other Networking Contexts

In local area networks, Ethernet employs unicast communication by encapsulating data in frames addressed to a specific destination using unique 48-bit Media Access Control () addresses, enabling targeted delivery within the shared medium without flooding the entire segment. This mechanism, defined in the standard, ensures that switches forward unicast frames only to the port associated with the destination , as learned through the (ARP) or dynamic learning processes. In wireless local area networks based on IEEE 802.11 (Wi-Fi), unicast transmission is used for data frames directed to a particular station (STA) via its individual MAC address, allowing reliable point-to-point exchanges such as acknowledgments and retransmissions for error-prone links. In contrast, management frames like beacons are transmitted as multicast to the broadcast address, announcing network parameters to all associated STAs without individual targeting. This distinction optimizes spectrum use by reserving unicast for user-specific traffic while using multicast for common announcements. Asynchronous Transfer Mode (ATM) networks utilize virtual circuits to establish dedicated point-to-point paths, functioning as unicast connections where cells are routed along pre-signaled routes between endpoints using Virtual Path Identifiers (VPIs) and Virtual Channel Identifiers (VCIs). Similarly, (SONET) and its international counterpart Synchronous Digital Hierarchy (SDH) provide unicast-like point-to-point optical transport through fixed-bandwidth circuits multiplexed into synchronous frames, supporting dedicated bidirectional links for high-speed data transfer without shared addressing. These circuit-oriented technologies predate packet-switched paradigms like IP but exemplify unicast principles in circuit-switched environments. In emerging networks, unicast bearers are established as dedicated (PDU) sessions for individual (UE) to enable personalized connectivity, with (QoS) flows within each session handling unicast traffic to specific devices over the . This approach supports per-UE sessions for applications requiring low-latency, individualized delivery, distinct from broadcast or options in the same . While networks represent a primary context for unicast, these layer-2 and specialized transport technologies demonstrate its broader applicability across diverse networking paradigms.

Advantages and Disadvantages

Benefits

Unicast transmission provides high reliability through end-to-end mechanisms that ensure accurate data delivery between sender and receiver. In protocols like , which operates over unicast connections, features such as acknowledgments, retransmissions for lost packets, and sequence numbering enable robust error correction, while flow control prevents receiver overload and congestion avoidance algorithms like those in mitigate network bottlenecks to maintain stable throughput. This reliability is particularly valuable in scenarios requiring guaranteed delivery, as unicast avoids the shared medium issues inherent in broadcast or approaches. Security is another key benefit of unicast, as it facilitates straightforward point-to-point and tailored to individual endpoints, with data accessible only to the intended receiver. Most protocols, including TLS used in applications like , are designed for such point-to-point sessions, avoiding the complexities of group in that can increase exposure to unauthorized access. This targeted approach enhances and without the overhead of coordinating multiple recipients. Unicast's simplicity stems from its lack of need for group management, making it easier to implement in standard networking protocols compared to systems that require membership tracking and trees. Devices and networks are inherently configured for unicast by default, allowing seamless point-to-point communication without additional setup. For in low-receiver environments, such as remote access or individual file transfers, unicast proves efficient by dedicating resources directly to the intended destination, avoiding unnecessary replication while remaining viable when receiver counts are small—unlike scenarios with many users where bandwidth contrast becomes more pronounced.

Limitations

Unicast is inherently bandwidth-inefficient for one-to-many communications, as it necessitates sending a distinct copy of the data to each individual receiver, resulting in traffic volume that scales linearly with the number of recipients. For instance, streaming live video to 1000 concurrent users requires generating and transmitting 1000 separate streams from the source, which can rapidly exhaust available network capacity and increase operational costs. This replication also imposes substantial computational demands on the originating , consuming elevated levels of CPU and to handle the simultaneous encoding, buffering, and of multiple . In environments with high counts, such intensity can lead to bottlenecks, including increased and reduced throughput at the sender. Furthermore, unicast's reliance on independent paths for each exacerbates , as duplicate packets traverse overlapping links, potentially overloading specific segments while underutilizing others, unlike the optimized shared distribution trees employed in protocols. As a result, unicast proves inadequate for large-scale live events, such as real-time broadcasts to mass audiences, where the absence of built-in sharing mechanisms amplifies challenges without external interventions like content delivery networks.

References

  1. [1]
    Group communication - Paul Krzyzanowski
    Oct 3, 2022 · Most of our communication between computers is point-to-point. This is known as unicast. We use unicast to send messages between a client and a ...
  2. [2]
    IP Addresses - CIS 170F: Windows 7 Administration
    unicast: A unicast IP address uniquely identifies a computer or device on the network. An IPv4 unicast address is a four-octet, 32-bit address represented ...
  3. [3]
    [PDF] Data Communications & Networks - Session 12 - IP Multicast - NYU
    Page 4. 4. Cast Definitions. Unicast - send to one destination (198.122.15.20) General Broadcast - send to EVERY local node.
  4. [4]
    Windows NT: Unicast Routing Principles - CS@UCSB
    Unicast routing is the process of forwarding unicasted traffic from a source to a destination on an internetwork. Unicasted traffic is destined for a unique ...
  5. [5]
    RFC 4291 - IP Version 6 Addressing Architecture - IETF Datatracker
    RFC 4291 defines the IPv6 addressing architecture, including unicast, anycast, and multicast addresses, and the addressing model.
  6. [6]
    RFC 791: Internet Protocol
    ### Definition of Unicast in IP Protocol
  7. [7]
    [PDF] Topology Discovery on Unicast Networks: A Hierarchical Approach ...
    In this paper we address the problem of topology discovery in unicast logical tree networks using end- to-end measurements. Without any cooperation from the ...<|control11|><|separator|>
  8. [8]
    ARPANET | DARPA
    In its earliest form, the ARPANET began with four computer nodes, and the first computer-to-computer signal on this nascent network was sent between UCLA and ...
  9. [9]
  10. [10]
    Distributed power control in wireless communication systems
    Wireless networking presents formidable challenges and we consider the problem of unicast or point-to-point (peer-to-peer) communication in wireless networks in ...
  11. [11]
    Bandwidth allocation policies for unicast and multicast flows
    Using multicast delivery to multiple receivers reduces the aggregate bandwidth required from the network compared to using unicast delivery to each receiver.
  12. [12]
    RFC 791: Internet Protocol
    Addressing A distinction is made between names, addresses, and routes [4]. A name indicates what we seek. An address indicates where it is. A route ...
  13. [13]
    RFC 1112 - Host extensions for IP multicasting - IETF Datatracker
    ... addresses range from 224.0.0.0 to 239.255.255.255. The address 224.0.0.0 is ... An IP host group address is mapped to an Ethernet multicast address by ...
  14. [14]
    RFC 1918 - Address Allocation for Private Internets - IETF Datatracker
    This document describes address allocation for private internets. The allocation permits full network layer connectivity among all hosts inside an enterprise.
  15. [15]
    RFC 4193 - Unique Local IPv6 Unicast Addresses - IETF Datatracker
    This document defines an IPv6 unicast address format that is globally unique and is intended for local communications, usually inside of a site.
  16. [16]
    RFC 826 - An Ethernet Address Resolution Protocol - IETF Datatracker
    The purpose of this RFC is to present a method of Converting Protocol Addresses (eg, IP addresses) to Local Network Addresses (eg, Ethernet addresses).
  17. [17]
    RFC 1519 - Classless Inter-Domain Routing (CIDR) - IETF Datatracker
    This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth ...
  18. [18]
    Longest Prefix Match Routing - NetworkLessons.com
    Mar 31, 2022 · Longest prefix match routing is an algorithm where the router prefers the longest prefix in the routing table. In other words, the most specific prefix.
  19. [19]
    Longest Prefix Matching in Routers - GeeksforGeeks
    Jun 15, 2022 · Routers use the Longest Prefix Matching rule. The rule is to find the entry in a table which has the longest prefix matching with the incoming packet's ...
  20. [20]
    Unicast Routing Protocols Guide - Nokia Documentation Center
    Jun 15, 2023 · This guide provides an overview of unicast routing concepts and provides configuration examples for Routing Information Protocol (RIP), Open ...
  21. [21]
    Configuring IP Forwarding Parameters
    Sep 23, 2020 · Forwarding of source-routed packets: A source-routed packet specifies the exact router path for the packet. The packet specifies the path by ...
  22. [22]
    What is Time to Live (TTL) | TTL Best Practices | CDN Guide - Imperva
    TTL stops packets from continuously looping in the network. Routing loops can occur if routers have incorrect routes, or if a temporary instability causes a ...Time To Live (ttl) · How Ttl Works In Different... · Configuring TtlMissing: unicast | Show results with:unicast<|control11|><|separator|>
  23. [23]
    6.3 TCP Congestion Control — Computer Networks
    Recall how TCP's sliding window algorithm works—when a packet is lost, the source eventually reaches a point where it has sent as much data as the ...
  24. [24]
    IP Multicast Technology Overview - Cisco
    IP multicast is a bandwidth-conserving technology that reduces traffic by simultaneously delivering a single stream of information to potentially thousands of ...
  25. [25]
    Unicast vs Multicast: Understanding the Fundamentals of Network ...
    Bandwidth Utilization: Unicast can lead to significant bandwidth consumption when the same data needs to be transmitted to multiple recipients. This issue ...Comparing Unicast And... · Protocols Enabling Multicast... · Key Differences Between...<|separator|>
  26. [26]
    Unicast vs Multicast: Key Differences in Streaming - FastPix
    Oct 23, 2025 · Unicast is ideal for one-to-one streaming, while multicast suits one-to-many, balancing scalability and bandwidth efficiency.What Is Unicast? · What Is Multicast? · Faqs On Unicast And...
  27. [27]
    Unicast Multicast Broadcast Anycast and Incast Traffic Types
    Apr 9, 2022 · In Multicast communication, the sender/source sends the data only 1 time, network devices replicate the traffic, and 3 receivers get the same ...
  28. [28]
    Multicast Group - an overview | ScienceDirect Topics
    IP-based multicast implementations Different from unicast, multicast communication requires routing protocols with higher complexity. It needs advanced routing ...
  29. [29]
    Multicast vs. Broadcast vs. Anycast vs. Unicast - Baeldung
    Mar 26, 2025 · The unicast addressing method indicates that communication through a network involves a unique sender (source) and a single receiver (destination).
  30. [30]
    IPv6 Multicast Configuration - Cisco
    Broadcast packets make use of a broadcast MAC address (FF:FF:FF:FF:FF:FF). For IPv6 multicast addresses, the Ethernet MAC is derived by the four low-order ...
  31. [31]
    STP Status and Global Settings - Cisco
    Spanning Tree Protocol (STP) protects a Layer 2 Broadcast domain from Broadcast storms by selectively setting links to standby mode to prevent loops.<|separator|>
  32. [32]
    Please explain Collision Domain and Broadcast Domain.
    With switches this problems is corrected by everyport being its own collision domain. A broadcast domain includes all devices that would receive the same ...
  33. [33]
    Address resolution protocol (ARP) - WITest
    Sep 12, 2023 · In this experiment, we will examine how ARP is used in IPv4 networks - where a "neighbor" is a network interface on the same IPv4 network.
  34. [34]
  35. [35]
  36. [36]
    RFC 7094 - Architectural Considerations of IP Anycast
    This memo discusses architectural implications of IP anycast and provides some historical analysis of anycast use by various IETF protocols.
  37. [37]
  38. [38]
  39. [39]
  40. [40]
    [PDF] Two Days in the Life of the DNS Anycast Root Servers - CAIDA
    For a DNS root nameserver, anycast provides a service whereby clients send requests to a single address and the network delivers that request to at least one, ...
  41. [41]
  42. [42]
  43. [43]
    RFC 5405 - Unicast UDP Usage Guidelines for Application Designers
    This document provides guidelines on the use of UDP for the designers of unicast applications and upper-layer protocols.
  44. [44]
    RFC 959 - File Transfer Protocol - IETF Datatracker
    RFC 959 is the official specification of the File Transfer Protocol (FTP), designed to promote file sharing and reliable data transfer.
  45. [45]
    RFC 5321 - Simple Mail Transfer Protocol - IETF Datatracker
    This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous ...
  46. [46]
    RFC 4251 - The Secure Shell (SSH) Protocol Architecture
    The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network.Missing: SCP | Show results with:SCP
  47. [47]
    RFC 4862 - IPv6 Stateless Address Autoconfiguration
    This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6.
  48. [48]
    [PDF] ETSI TS 123 501 V17.5.0 (2022-07)
    This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical ...
  49. [49]
    RFC 9293 - Transmission Control Protocol (TCP) - IETF Datatracker
    Mar 19, 2025 · TCP supports unicast delivery of data. There are anycast applications that can successfully use TCP without modifications, though there is ...
  50. [50]
    Unicast - an overview | ScienceDirect Topics
    Implemented primarily through TCP and UDP, unicast ensures data delivery with varying degrees of reliability and overhead. Routing protocols such as RIP, OSPF, ...
  51. [51]
    Difference between Unicast and Broadcast - GeeksforGeeks
    Jul 23, 2025 · Unicast is defined as sending data to only one particular receiver, whereas broadcast is the sending of data to all devices connected to a network.
  52. [52]
  53. [53]
    Unicast and Multicast Networking in Video Surveillance - BCDVideo
    Mar 1, 2019 · Unicasting gives you more control over individual video streams but requires more bandwidth. Multicasting reduces network load and facilitates ...What Is Multicast Networking... · Optimizing Network Load · Unicast Networking Impact
  54. [54]
    Multicast Forwarding and Application State Scalability in the Internet
    IP Multicast increases bandwidth efficiency, because packets destined to multiple receivers travel only once on common parts of the network. It also reduces ...