Visual RFC.
ALL RFCs / RFC 7043
Read the RFC ↗
RFC 7043 / DNS LINK-LAYER RECORDS

Follow the private DOCSIS mapping example

05

DOCSIS is a cable-network technology. The RFC’s example separates a cable operator that assigns an IP address from a reseller that already knows a modem’s EUI address.

RFC 7043 · § 5EXAMPLE
4 / 4
Follow the private DOCSIS mapping exampleSeparate requester is not authorized for this private zone. The chosen access policy blocks record disclosure before an EUI answer crosses the boundary. No particular DNS error code is invented here.DOCSIS example: separate operator and resellerother requesterprivate DNSnot authorized: stopPrivate recordsNo EUI answer disclosedChosen owner/IP binding is outside RDATA; no live DNS/DHCP used
04
Stop disclosure to an unauthorized requester

Separate requester is not authorized for this private zone. The chosen access policy blocks record disclosure before an EUI answer crosses the boundary. No particular DNS error code is invented here.

Source for this drawing: RFC 7043 · Read RFC section 5 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Helpful first, if these ideas are unfamiliar

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

The example cable operator has DHCP lease information connecting an EUI-48 address and an assigned IP address; the reseller lacks direct knowledge of those IP assignments.

  • The example cable operator has DHCP lease information connecting an EUI-48 address and an assigned IP address; the reseller lacks direct knowledge of those IP assignments.
  • §5 describes exporting this mapping through DNS zones restricted to the appropriate resellers, with subscriber address data kept out of public DNS. This is the RFC’s documented deployment example, not current legal advice.
  • Our private-view owner lease-42.example.org and its connection to 192.0.2.42 are chosen application fixtures. The RFC does not mandate this owner-name schema, an export transport or a lease-synchronization algorithm.
DETAILS

Fictional offline examples only. EUI records carry supplied address data; they do not authenticate devices, implement IP resolution or authorize tracking. RFC7043 is Informational. The application policies shown are explicitly chosen fixtures.

Read the RFC section ↗

All chapters in RFC 7043

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗