Skip to content

Abstract: separate provisioning from resolution - #32

Closed
remcovanmook wants to merge 1 commit into
normative/sentinel-placeholderfrom
abstract/provisioning-step
Closed

remcovanmook wants to merge 1 commit into
normative/sentinel-placeholderfrom
abstract/provisioning-step

Conversation

@remcovanmook

Copy link
Copy Markdown
Owner

The abstract implied the provisioning step rather than stating it - "Hosts that receive 192.0.0.11/32 as their IPv4 default gateway address resolve..." leaves the reader to work out whether new DHCPv4 machinery is involved.

Now the two steps are separate and explicit:

  1. Provisioning is unchanged - the host obtains its IPv4 address and default gateway through ordinary, unmodified DHCPv4, or by static configuration. Static config is named, since it is in scope.
  2. Only the gateway value changes - when that value is the sentinel, next-hop resolution comes from the IPv6 neighbor cache instead of ARP, and nothing else about IPv4 operation is altered.

From article review (H. Kramselund).

Closes #30

🤖 Generated with Claude Code

The abstract implied provisioning with "Hosts that receive...",
leaving a reader to guess whether new DHCPv4 machinery is needed.
State the two steps separately: provisioning happens through
ordinary unmodified DHCPv4 or static configuration, and the
sentinel value changes only the next-hop resolution step.

Closes #30

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@remcovanmook

remcovanmook commented Sep 23, 2026 •

Copy link
Copy Markdown
Owner Author

Superseded by #42.

@remcovanmook
remcovanmook deleted the abstract/provisioning-step branch September 23, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants