White Paper

The Dynamic Address Layer (dal): Enabling Identity-Based Networking for the Dynamic Internet

appleby nexus | v1.0 | 2025


Abstract

The internet’s core addressing model is fundamentally static — IP addresses are tied to networks, devices, or topologies. Yet the digital world is no longer static: people, devices, services, and applications are mobile, multi-network, and constantly shifting contexts.

This creates a critical limitation for the emerging Internet of Things (IoT), edge computing, AR/VR, autonomous vehicles, and decentralised enterprise architectures. Without flexible, identity-based addressing, seamless connectivity, mobility, and dynamic orchestration are compromised.

This white paper introduces dal — the dynamic address layer — a framework for implementing identity-first, context-aware addressing on top of existing IPv6 and DNS systems. dal enables addresses that follow the user, service, or application, regardless of physical location, device, or network attachment.


1. Introduction: The Addressing Problem

1.1 The Static Nature of IP

IP addressing (even in IPv6) is inherently hierarchical and tied to:

This model works for traditional, centralised systems. But for modern architectures — mobile devices, IoT, virtual identities, autonomous services — it introduces:

1.2 The Mobility Gap

As applications shift toward:


2. The Dynamic Address Layer (dal)

2.1 Concept Overview

dal introduces an identity-linked, dynamic addressing layer, operating in parallel with and augmenting IP:

sql
| Application |
| dal |Identity-aware, dynamic address resolution
| IPv6 / IP | ← Underlying transport
| Link layer |

A dal address is bound to an identity (person, organisation, device group, service) — not a fixed network endpoint. It can be resolved and routed dynamically based on context:

2.2 Architecture

dal consists of:

2.3 Address Model

A dal address looks like:

graphql
alice@appleby.dal
fleet42@vehicles.appleby.dal
cam15@site12.security.appleby.dal
vruser12@ar.app.dal

It can resolve to:

2.4 Resolution Process

1️⃣ Application makes a request to dal resolver
2️⃣ Resolver evaluates:


3. Key Capabilities

3.1 Identity Mobility

A person, service, or device group can maintain a stable dal address — even as devices, networks, and locations change.

Example:
An autonomous drone fleet can publish telemetry and receive commands under one dal identity, even as they roam between LTE, satellite, and mesh links.

3.2 Session Continuity

dal supports application-layer handoff, avoiding broken sessions when IP changes occur (network switch, roaming, failover).

3.3 Fine-Grained Policy

dal policies control:

3.4 Integration with Zero-Trust

dal is designed to complement zero-trust networking:


4. Implementation Considerations

4.1 Protocol Integration

dal is designed to integrate with:

4.2 Compatibility with IPv6

dal does not replace IP. It augments IPv6-based transport by providing a dynamic, semantic resolution layer.

4.3 Deployment Models


5. Use Cases

5.1 IoT Fleets

5.2 Smart Mobility & Transport

5.3 AR / Wearables

5.4 Remote Work & Personal Networking


6. Benefits

Traditional IP Model dal Model
Device-based addressing Identity-based addressing
Static or NAT’d IP Dynamic, context-aware resolution
Fragile mobility Seamless mobility & session continuity
Complex overlays needed Native overlay support
Poor fit for IoT & AR Designed for IoT, AR, dynamic edge
Network-centric User- and service-centric

7. Roadmap

appleby nexus is actively developing:


8. Conclusion

The internet is becoming dynamic — yet addressing remains static. To enable the next generation of IoT, immersive applications, mobile work, and decentralised services, we must move beyond traditional IP-based addressing alone.

The dynamic address layer (dal) provides a practical, forward-compatible architecture for doing so — layered on current standards, but designed for the needs of the dynamic internet.

appleby nexus invites partners, enterprises, and innovators to collaborate on building this future.