IPv6: Addressing, Header, Transition & Real-World Use

IPv6 Addressing: Beyond 32 Bits

Why IPv6?

IPv4’s 32-bit address space (≈4.3 billion addresses) is exhausted. IPv6 uses 128-bit addresses (≈3.4×10³⁸ addresses), enabling:

• Global uniqueness via hierarchical addressing (ISP → Subnet → Interface).
• No NAT (Network Address Translation) needed, simplifying end-to-end communication.

IPv6 Address Formats

classDiagram
    class IPv6Address {
        +128 bits = 8 hextets (16 bits each)
        +Format: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
        +Types:
        - Global Unicast (2000::/3)
        - Link-Local (fe80::/10)
        - Unique Local (fc00::/7)
        - Multicast (ff00::/8)
    }
    class IPv4Mapped {
        +Format: ::ffff:IPv4_address
        +Used for IPv4/IPv6 transition
    }
    IPv6Address --> IPv4Mapped : "Subset"

Key Address Types (with real-world ties):

Worked Example: Ncell’s 5G IPv6 Allocation Ncell’s ISP allocates /48 blocks to enterprises. For a company with 1000 devices:

• Prefix: 2001:6xx:yyyy::/48
• Subnet ID: zzzz (assigned by Ncell)
• Interface ID: Last 64 bits (EUI-64 or random). Result: Each device gets a unique 2001:6xx:yyyy:0:0:zzzz:abcd:efgh.

A labeled diagram showing the 40-byte IPv6 header with fields: Version (6), Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source/Destination Addresses. (Image: Mro, CC BY-SA 3.0, via Wikimedia Commons)

IPv6 Header: Simpler and More Efficient

IPv4’s header has 12 fields + options. IPv6 reduces this to 8 fixed fields (40 bytes vs. IPv4’s 20–60 bytes), improving speed and predictability.

Key Header Fields

Why This Matters:

• No fragmentation: IPv6 sends "Packet Too Big" (PTB) messages if MTU < payload size. IPv4 fragments at routers.
• Extension Headers: Optional headers (e.g., Authentication, Routing) are placed after the main header, not inline.

Neighbor Discovery Protocol (NDP): Replacing ARP

IPv4 uses ARP to map IP → MAC. IPv6 replaces this with NDP, which handles:

1. Address Resolution: NS (Neighbor Solicitation) → NA (Neighbor Advertisement).
2. Router Discovery: Hosts learn default gateways via RA (Router Advertisement).
3. Parameter Configuration: Hosts get prefix/MTU from routers.
4. Duplicate Address Detection (DAD): Prevents duplicate IPv6 addresses.

NDP Message Exchange (Sequence Diagram)

sequenceDiagram
    participant Host as Host (fe80::1)
    participant Router as Router (2001:db8::1)
    Host->>Router: NS (Who has fe80::1?)
    Router-->>Host: NA (Here I am, fe80::1)
    Router->>Host: RA (Prefix: 2001:db8::/64, MTU: 1500)
    Host->>Router: DAD Check (Is fe80::1 free?)
    Router-->>Host: No response (Address is unique)

Real-World Example: eSewa’s Payment Routing When you pay via eSewa:

1. Your phone (IPv6: fe80::1%wlan0) sends an NS to the local router (NTC’s gateway).
2. The router replies with NA, confirming the link-local address.
3. eSewa’s server (global unicast: 2001:db8:123::1) uses this to route payment requests via NDP-configured paths.

IPv6 Transition Mechanisms: Bridging IPv4 and IPv6

Since IPv4 isn’t disappearing overnight, networks use transition methods:

1. Dual-Stack

• How it works: Devices run both IPv4 and IPv6 stacks simultaneously.
• Example: Google’s DNS (8.8.8.8 for IPv4, 2001:4860:4860::8888 for IPv6).
• Diagram:

  flowchart TD
    A["Host (Dual-Stack)"] -->|"IPv4"| B["IPv4 Router"]
    A -->|"IPv6"| C["IPv6 Router"]
    B --> D["Legacy IPv4 Internet"]
    C --> D

2. Tunneling

• 6to4: Encapsulates IPv6 in IPv4 (uses anycast relay routers).
  • Example: 192.88.99.1 (anycast relay) tunnels IPv6 over IPv4.
• Teredo: For NAT traversal (used by Xbox Live).
• Configured Tunnel: Manual setup (e.g., ISP-provided tunnel endpoints).

3. NAT64/DNS64

• NAT64: Translates IPv6 → IPv4 at the edge (e.g., accessing IPv4-only websites).
• DNS64: Returns IPv6 addresses for IPv4-only services (e.g., http://[2607:f8b0:4009:80e::200e] for google.com).
• Example: Your phone (IPv6-only) uses DNS64 to resolve facebook.com (IPv4) via NAT64.

IPv6 vs. IPv4: Comparison Table

In the Real World

1. Ncell’s 5G Network (Nepal)

   • Uses IPv6 for subscriber IPs (e.g., 2001:6xx::/48 blocks).
   • Why? Supports 1000x more devices than IPv4; enables IoT (e.g., smart meters).
   • NDP in Action: Your phone (IPv6: fe80::1%wwan) discovers the 5G gateway via RA messages.

2. eSewa’s Payment Routing

   • Uses IPv6 multicast (ff02::1) for load balancing across payment servers.
   • Dual-stack: Supports both IPv4 (legacy) and IPv6 (new users).

3. YouTube’s CDN (Global)

   • Anycast DNS: Resolves to the nearest IPv6-enabled server (e.g., 2607:f8b0:4009:80e::200e).
   • Multicast: Reduces bandwidth for live streams (IPv6’s native support).

4. Google’s DNS (8.8.8.8)

   • Dual-stack: 8.8.8.8 (IPv4) and 2001:4860:4860::8888 (IPv6).
   • Transition: Uses NAT64 for IPv6-only devices querying IPv4 sites.

Worked Example: Calculating IPv6 Subnets

Scenario: NTC allocates a /48 block (2001:db8:123::/48) to a university. Subnet for the Computer Science department (needs 500 hosts).

1. Subnet the /48:

   • Split into /64 subnets (standard for interfaces).
   • Subnet ID: 0001 (binary 00000000000000000000000000000001).
   • Resulting Subnet: 2001:db8:123:1::/64.

2. Assign Hosts:

   • Interface ID: Last 64 bits (EUI-64 or random).
   • Example: 2001:db8:123:1::1 (gateway), 2001:db8:123:1::2 to 2001:db8:123:1::1ff.

Visual:

classDiagram
    class /48Block {
        +Prefix: 2001:db8:123::/48
        +Subnets: 65536 (/64 each)
    }
    class /64Subnet {
        +Prefix: 2001:db8:123:1::/64
        +Hosts: 18 quintillion (theoretical)
        +Used by: CS Department
    }
    /48Block --> /64Subnet : "Contains"

Exam Tip

1. Addressing is Critical:

   • Memorize prefixes (e.g., 2000::/3 for global unicast).
   • Practice converting hexadecimal to binary (e.g., 2001:db8::1 → binary).
   • Exam Question: "Given a /64 subnet, write 3 valid host addresses." (Use :: and EUI-64.)

2. Header Fields:

   • Know the 8 fixed fields and their sizes (e.g., Flow Label is 20 bits).
   • Common Mistake: Confusing Traffic Class (QoS) with Flow Label (real-time traffic).

3. Transition Mechanisms:

   • Dual-stack = both protocols running.
   • Tunneling = IPv6 inside IPv4 (e.g., 6to4).
   • NAT64/DNS64 = IPv6 → IPv4 translation.
   • Exam Question: "How would a pure IPv6 host access an IPv4-only website?" (Answer: NAT64 + DNS64.)

4. NDP Over ARP:

   • ARP = IPv4 (IP → MAC).
   • NDP = IPv6 (NS/NA for MAC resolution, RA for router discovery).
   • Exam Question: "What message does a host send to discover its default gateway in IPv6?" (Answer: Router Solicitation → Router Advertisement.)

5. Real-World Scenarios:

   • Ncell 5G: IPv6 /48 allocation, NDP for gateway discovery.
   • eSewa: Dual-stack for backward compatibility.
   • YouTube: Anycast DNS + multicast streaming.
   • Exam Question: "Explain how IPv6 improves traffic routing in Kathmandu’s congested internet." (Answer: No NAT → end-to-end paths; multicast for live streams.)

6. Diagrams:

   • Draw:
     • IPv6 header fields.
     • NDP message exchange (NS/NA/RA).
     • Dual-stack or tunneling topology.
   • Label: Every field/arrow with its purpose.

Pro Tip: For numerical questions (e.g., subnet calculation), always:

1. Write the binary prefix (e.g., /64 = 1111111111111111111111111111111100000000000000000000000000000000).
2. Show one valid host address (e.g., 2001:db8::1).
3. Mention real-world use (e.g., "This subnet serves Pathao’s ride-hailing servers in Lalitpur").