IPv8 Packet & DNS

The IPv8 draft defines packet and DNS behavior as part of the core protocol proposal.

Packet Header

The draft includes an IPv8 packet header section. Its purpose is to describe how IPv8 traffic is carried and how the protocol can remain compatible with socket APIs that already expect IPv4-style behavior.

The exact header fields should be checked against the original text in Original Draft -02, because this area is normative protocol material in the draft.

Socket API Compatibility

The proposal aims to preserve application compatibility. It presents IPv8 as compatible with existing IPv4 devices and applications when the routing prefix is zero.

For developers, the important point is that the draft tries to avoid forcing applications to adopt a completely new addressing API before they can participate in an IPv8 network.

DNS A8 Record

The draft defines a DNS A8 record type for IPv8 addresses. It also requests an IANA assignment for that record type in the IANA Considerations section.

The A8 record is part of a broader DNS8 model where outbound traffic validation can depend on a corresponding DNS lookup.

Egress Dependency

In the security model, the draft states that outbound connections are validated at egress. A connection without a corresponding DNS8 lookup is blocked because it has no XLATE8 state table entry.

That DNS dependency is central to the draft’s north-south traffic model.