Category: Network

Traffic Control

Posted on by lechuck park

This image shows a network traffic control system architecture. Here’s a detailed breakdown:

  1. At the top, several key technologies are listed:
  • P4 (Programming Protocol-Independent Packet Processors)
  • eBPF (Extended Berkeley Packet Filter)
  • SDN (Software-Defined Networking)
  • DPI (Deep Packet Inspection)
  • NetFlow/sFlow/IPFIX
  • AI/ML-Based Traffic Analysis
  1. The system architecture is divided into main sections:
  • Traffic flow through IN PORT and OUT PORT
  • Routing based on Destination IP address
  • Inside TCP/IP and over TCP/IP sections
  • Security-Related Conditions
  • Analysis
  • AI/ML-Based Traffic Analysis
  1. Detailed features:
  • Inside TCP/IP: TCP/UDP Flags, IP TOS (Type of Service), VLAN Tags, MPLS Labels
  • Over TCP/IP: HTTP/HTTPS Headers, DNS Queries, TLS/SSL Information, API Endpoints
  • Security-Related: Malicious Traffic Patterns, Encryption Status
  • Analysis: Time-Based Conditions, Traffic Patterns, Network State Information
  1. The AI/ML-Based Traffic Analysis section shows:
  • AI/ML technologies learn traffic patterns
  • Detection of anomalies
  • Traffic control based on specific conditions

This diagram represents a comprehensive approach to modern network monitoring and control, integrating traditional networking technologies with advanced AI/ML capabilities. The system shows a complete flow from packet ingress to analysis, incorporating various layers of inspection and control mechanisms.

with Claude

TIMELY

Posted on by lechuck park

With Claude
TIMELY (Transport Informed by MEasurement of LatencY)

  1. System Architecture
  • Cloud/Data Center to External Network Connection
  • TIMELY Module Process at Kernel Level
  • Bidirectional Operation Support
  • TCP Protocol Based
  1. RTT-based Traffic Control Components
  • RTT Monitoring
    • 5-tuple monitoring (Src/Dst IP, Src/Dst Port, Protocol)
    • Real-time latency measurement
  • Congestion Detection
    • Network congestion detection through RTT increases
  • Congestion Window Adjustment
    • Control of send buffer size
  • MSS-based Adjustments
    • Congestion window adjustments in MSS units
  1. Related RTT-based Technologies
  • TCP BBR
  • TCP Vegas
  • CUBIC TCP
  1. Advantages of RTT-based Control
  • Proactive congestion detection before packet loss
  • Real-time network state awareness
  • Efficient buffer management
  • Lower latency in data transmission
  • Effective bandwidth utilization
  • Better performance in high-speed networks
  1. Disadvantages of RTT-based Control
  • RTT measurement accuracy dependency
  • Complex implementation at kernel level
  • Potential overhead in RTT monitoring
  • Need for continuous RTT measurement
  • Sensitivity to network jitter
  • May require adjustments for different network environments

The TIMELY system demonstrates an efficient approach to network congestion control using RTT measurements, particularly suitable for cloud and data center environments where latency and efficient data transmission are critical. The system’s kernel-level implementation and MSS-based adjustments provide fine-grained control over network traffic, though success heavily depends on accurate RTT measurements and proper environment calibration.

DAS / NAS / SAN

Posted on by lechuck park

With a Claude
This image is a diagram comparing three major storage systems – DAS (Direct Access Storage), NAS (Network Access Storage), and SAN (Storage Network Array).

Let’s examine each system in detail:

  1. DAS (Direct Access Storage):
  • Direct storage system connected to the CPU
  • Shows direct connections between RAM and disk drives
  • Most basic storage architecture
  • Connected directly to the computer system
  1. NAS (Network Access Storage):
  • Storage accessible through the network
  • Marked with “Over The Network” indicating network connectivity
  • Consists of standalone storage units
  • Provides shared storage access through network
  1. SAN (Storage Network Array):
  • Most sophisticated and complex storage system
  • Features shown include:
    • High Speed Dedicated Network
    • Centralization Control
    • Block Storage
    • HA with RAID (High Availability with RAID)
    • Scale-out capabilities

The diagram effectively illustrates the evolution and increasing complexity of storage systems. It shows the progression from the simple direct-attached storage (DAS) through network-attached storage (NAS) to the more complex storage area network (SAN), with each iteration adding more sophisticated features and capabilities.

The layout of the diagram moves from left to right, demonstrating how each storage solution becomes more complex but also more capable, with SAN offering the most advanced features for enterprise-level storage needs.

Fast Copy over network

Posted on by lechuck park

With a Claude
This image illustrates a system architecture diagram for “Fast Copy over network”. Here’s a detailed breakdown:

  1. Main Sections:
  • Fast Copy over network
  • Minimize Copy stacks
  • Minimize Computing
  • API optimization for read/write
  1. System Components:
  • Basic computing layer including OS (Operating System) and CPU
  • RAM (memory) layer
  • Hardware device layer
  1. Key Features:
  • The purple area on the left focuses on minimizing Count & Copy with API
  • The blue center area represents minimized computing works (Program Code)
  • The orange area on the right shows programmable API implementation
  1. Data Flow:
  • Arrows indicating bi-directional communication between systems
  • Vertical data flow from OS to RAM to hardware
  • Horizontal data exchange between systems

The architecture demonstrates a design aimed at optimizing data copying operations over networks while efficiently utilizing system resources.

Web Socket

Posted on by lechuck park

with a Claude’s help
The image is a diagram that explains the differences between HTTP (Hypertext Transfer Protocol) and WebSocket communication. Let me summarize the key points:

  1. HTTP REQ/RES (Request/Response):
    • The request is sent from the client (laptop icon) to the server (globe icon).
    • The response is sent back from the server to the client.
    • The <Req> and <Res> are separate connections, and the communication is bi-directional (one connection only).
    • All data is transferred via the HTTP protocol payload.
  2. WebSocket:
    • The WebSocket is established between the client (laptop icon) and server (globe icon).
    • The <Req> and <Res> are working in one connection, which is bi-directional.
    • Data Transferring is working on a socket (not HTTP Req/Res).
    • A TCP socket is commonly used for WebSocket data transfer.
    • WebSocket data transfer is described as “light & fast Transmission (more real time)”.

Overall, the diagram illustrates the differences between the traditional HTTP request-response model and the WebSocket communication, which provides a more efficient, real-time data transfer mechanism.

RON ( Routed Optical Networking )

Posted on by lechuck park

From Claude with some prompting
This image provides an overview of Routed Optical Networking (RON), which is a networking technology that combines IP routing and MPLS with wavelength multiplexing to enable very long distance data transmission.

The key features highlighted in the image are:

  1. Network simplification: RON reduces the complex hierarchy of routers and transmission equipment traditionally used in optical networks.
  2. Cost-effectiveness: RON eliminates the need for separate transmission equipment, reducing hardware and maintenance costs.
  3. Reduced latency: Data is processed within a single device, rather than going through multiple devices, reducing latency.
  4. Operational efficiency: Routing and transport functions are consolidated, allowing the network to be managed from a single management platform.

The image also shows the main components of a RON system, including IP routing + MPLS, wavelength multiplexing, L3 layer, physical layer, router, and DWDM (Dense Wavelength Division Multiplexing). It also lists some specific technologies used, such as IP over Dense, Wavelength Division Multiplexing (Juniper) and Photonic Service Engine (Nokia).

Overall, this diagram illustrates how RON simplifies optical networking by combining multiple networking functions into a more efficient and cost-effective architecture.Copy

MPLS

Posted on by lechuck park

From Claude with some prompting
Let me explain this MPLS (Multiprotocol Label Switching) diagram:

  1. Left Section – Network Stack:
  • Application layer
  • TCP/UDP layer
  • IP layer
  • Ethernet layer
  1. Middle Section – MPLS Label Structure:
  • Label (20 bits): Used for routing
  • Experimental (3 bits): For QoS (Quality of Service) priority
  • Bottom of Stack (1 bit): Indicates if it’s the last label (Not Bottom: 0)
  • TTL (8 bits): Time to Live, prevents looping
  1. Right Section – MPLS Network Operation:
  • Label Edge Router (LER): Adds/removes labels at network boundaries
  • Label Switching Router (LSR): Performs label-based switching
  • Packets expire when TTL reaches 0
  • Routing based on priority using Experimental (QoS) bits

Operational Flow:

  1. Add Label Header: When packets enter MPLS network
  2. Routing by Label: Packet forwarding based on labels with Priority by Exp(QoS)
  3. Remove Label Header: When packets exit MPLS network

Key Benefits of MPLS:

  • Fast packet forwarding (label-based switching)
  • QoS support
  • Efficient traffic engineering
  • Support for multiple network protocols

The diagram shows how MPLS creates a more efficient and manageable network by using label-based forwarding instead of traditional IP routing. Labels can be stacked (Label Stack-able) for more complex routing scenarios, and the TTL field helps prevent infinite routing loops.