Category: Network

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.

All are by packets

Posted on by lechuck park

From Claude with some prompting
Let me explain this network diagram which illustrates packet processing and various network devices:

  1. Network Components:
  • Internet: Shows L3-L7 packet flowing
  • Router: Handles L3 routing and packet control
  • Firewall/IPS/IDS: Manages L3/L4 base packet control and L7 packet analysis/control
  • Switching: Performs Ethernet(L2/L3) switching and L2/L3 packet control
  • Server/Client: Handles packet send & receive (L1-L7), packet making and analysis
  1. Key Issues:
  • COST Concerns:
    • ALL operations are packet-based
    • Performs L1-L7 packet collecting/analysis/switching/routing
    • Multiple devices perform many duplicates of the same functions (L2, L3-L4 packet collecting/analysis/switching/routing)
  1. Suggested Improvement:
  • Mentioned in “IF Possible” section:
    • Consider aggregating all packets and manipulating them from central controls
    • This could potentially reduce redundancy and improve efficiency
  1. Key Message:
  • There are many types of packet processing devices on the network
  • Redundancy occurs as each device performs similar functions
  • Need to explore possibility of centralized packet management system

The diagram effectively highlights the complexity and redundancy in modern network architecture while suggesting a potential path toward more efficient packet processing through centralization.

This visualization emphasizes how current network infrastructure might benefit from consolidation of packet processing functions to reduce duplicated efforts and potentially lower costs.

RPKI : Resource Public Key Infrastructure

Posted on by lechuck park

From Claude with some prompting
RPKI (Resource Public Key Infrastructure) Overview

  1. Background of RPKI Need

1.1. Internet requires reliable IP management

1.2. Traditional IP address and routing system vulnerabilities

1.3. Need for secure and verifiable routing infrastructure

  1. Core Components of RPKI Structure

2.1. IANA (Internet Assigned Numbers Authority)

  • Top-level authority for IP resource management
  • Oversees global IP address allocation
  • Delegates authority to regional registries

2.2. RIR (Regional Internet Registry)

  • Manages continental-level resources
  • Key organizations: ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC
  • Handles certification management

2.3. NIR (National Internet Registry)

  • National-level IP resource management
  • Works under RIR guidance
  • Manages local resource allocation
  1. RPKI Operational Process

3.1. Resource Management

  • IP addresses grouped by ASN (Autonomous System Number)
  • Systematic management to prevent chaos
  • Certificate-based validation system

3.2. Technical Implementation

  • Caching servers for RPKI data
  • Router configuration using BGP
  • Real-time validation of routing information
  1. Security Features

4.1. BGP Route Protection

  • Prevents BGP hijacking attempts
  • Validates peer BGP advertisements
  • Ensures routing path integrity

4.2. Validation States

  • OK: Valid route
  • NOT FOUND: No RPKI record
  • INVALID: Failed validation
  1. Benefits of RPKI

5.1. Enhanced routing security

5.2. Prevents unauthorized IP address use

5.3. Provides verifiable trust chain

5.4. Maintains internet routing stability

Summary

This RPKI-centric structure transforms traditional IP management into a robust, secure, and verifiable system for global internet routing infrastructure.

The system essentially creates a chain of trust from IANA through RIRs and NIRs down to individual network operators, ensuring the legitimacy of IP address usage and routing announcements.

Web(HTTP) Service Inside

Posted on by lechuck park

From Claude with some prompting
This image titled “Web Service Inside” illustrates the internal workings of a web service in 8 steps, from the browser to service design:

  1. <Domain> to <IP address>: Converts user-friendly domain names into computer-readable IP addresses. This process utilizes multi-level caching for efficiency and ultimately locates the desired web server.
  2. IP routing: Guides data packets to their destination via optimal paths based on the converted IP address. This ensures accurate and efficient information delivery across the complex network of the internet.
  3. HTTP REQ/RES: Defines the communication rules between clients and servers. It structures how clients make requests and how servers respond, providing a standardized method for exchanging information on the web.
  4. SSL/TLS & HTTP3: Enhances data transmission security and improves performance. It protects information through encryption and enables faster, more efficient communication using the latest protocols.
  5. HTTP Caching & CDN: Increases efficiency for repetitive data requests and delivers content to users faster. This plays a crucial role in reducing server load and improving user experience.
  6. Server Side Works: Involves the actual processing of requests and generation of responses on the server. It covers operating systems, network protocols, and resource management to provide an efficient and stable service foundation.
  7. Service Internal Works: Addresses the internal structure and data processing methods of web services. It covers database management, load balancing, and maintaining high availability to provide reliable service to large-scale user bases.
  8. Service Design: Encompasses the overall architecture and operational strategy of the web service. It involves creating optimal service structures considering user requirements, scalability, and maintainability, as well as establishing continuous improvement and monitoring plans.

Each of these stages is essential in creating a web service that efficiently and securely handles user requests, while building a system that is scalable and easy to maintain at a large scale.

Changes of the network traffic

Posted on by lechuck park

From Claude with some prompting
Here’s an interpretation of the diagram in English, focusing on the major changes in internet traffic types:

  1. Early Internet (Start): The small “Bytecode” circle represents the limited data exchange of the early internet. This period was primarily characterized by simple, text-based information exchange.
  2. Web Era (Web): The larger “bytecode HTTP” circle illustrates the surge in HTTP traffic with the advent of the World Wide Web. This represents increased traffic from web browsing, email, and early online services.
  3. Streaming Age (Streaming): The addition of the “Video Streaming” circle signifies the explosive growth in video streaming traffic, driven by platforms like YouTube and Netflix. This marks a paradigm shift in internet bandwidth usage.
  4. Big Data and AI Era (Big Data IoT / Machine Learning & LLM): The largest circle, “Big Data For AI,” represents the enormous traffic increase due to IoT device proliferation, cloud computing ubiquity, and large-scale data processing for AI and machine learning. This suggests it now constitutes the largest portion of internet traffic.

This diagram effectively shows the evolution of internet traffic from simple data exchange to web-based services, media streaming, and the current data-centric, AI-driven era.

Comments (points to be cautious about):

  1. Accuracy: It’s unclear if the circle sizes accurately reflect actual traffic volumes. This should be understood as a conceptual representation.
  2. Time scale: The time intervals between stages may not be uniform, which is not indicated in the diagram.
  3. Overlap: In reality, these traffic types coexist and are not as distinctly separated as the diagram suggests.
  4. Recent trends: The diagram doesn’t reflect traffic changes due to latest technological trends like 5G or edge computing.
  5. Regional differences: These changes may not have occurred uniformly worldwide, which is not reflected in the diagram.

It’s important to consider these points when interpreting the diagram. Overall, this image effectively conveys the macroscopic trends in the evolution of internet traffic in a concise and impactful manner.