Repository navigation
dtls: prepare shared packet interception and IPv6 prerequisites (1/18) - #1469
Draft
mgonzalezlopezudc wants to merge 3 commits into
Draft
mgonzalezlopezudc wants to merge 3 commits into
mgonzalezlopezudc wants to merge 3 commits into
Conversation
The original DTLS implementation and extensions need bounded review units that preserve their final behavior and evidence. Define the complete 41-commit, 18-PR sequence, source allocation, independently tested preparations and publication dependencies before reconstructing code. Keep the original branches and local edits intact. Separate historical input results from reconstructed verification, require focused commit checks and combined PR-tip/final acceptance, and retain the original statistical baseline with its causal example commit. Plan: plan/pending/dtls-publication-plan.md Change: plan | behavior.add | - | dtls-publication
Interleaved UDP datagrams need interception by typed packet content as well as an expression. Evaluate both filters before occurrence counting, so nonmatching payloads do not consume the second-match drop. The fixture requires every other matching and nonmatching datagram to arrive. Protocol scenarios: TypedTapPredicate. Their companion reviewer documents specify topology, faults, required observations and limits. Immediate-parent comparison is source-based unless the linked publication execution record identifies an actual compatible run. Missing capability is not a runtime defect observation. The immediate-parent comparison for these scenarios is source-based unless the associated comparison record documents execution. New exchanges depend on the endpoint transition described above. Scenarios retaining earlier outcomes serve as controls. Exact-parent behavior is otherwise unverified. - TypedTapPredicate: Typed tap predicates combine with expressions before occurrence counting. Interleaved 100-byte and 200-byte UDP datagrams share a destination. An extra 200-byte datagram uses another destination port and must also pass. Only the second matching 200-byte datagram is dropped; all four 100-byte datagrams and the other two 200-byte datagrams must arrive. This proves nonmatching typed packets do not advance nth(2). Plan: plan/pending/dtls-publication-plan.md Change: tests | behavior.add | test | dtls-publication
An IPv6 application can request an unfragmented datagram, but source fragmentation previously ignored that request. Honor the packet request on immediate and delayed output, report an oversized packet through the existing drop path, and retain ordinary source fragmentation when no prohibition is supplied. Protocol scenarios: Ipv6DontFragmentRequest, Ipv6DontFragmentRequestDelayed, Rfc8200SourceFragmentation. Their companion reviewer documents specify topology, faults, required observations and limits. Immediate-parent comparison is source-based unless the linked publication execution record identifies an actual compatible run. Missing capability is not a runtime defect observation. The immediate-parent comparison for these scenarios is source-based unless the associated comparison record documents execution. New exchanges depend on the endpoint transition described above. Scenarios retaining earlier outcomes serve as controls. Exact-parent behavior is otherwise unverified. - Ipv6DontFragmentRequest: IPv6 source fragmentation honors the existing FragmentationReq tag. One oversized forbidden UDP datagram drops; one small tagged datagram and one untagged oversized datagram deliver. Neighbor-resolution without an injected delay preserves the tag through its queue. - Ipv6DontFragmentRequestDelayed: IPv6 source fragmentation honors the existing FragmentationReq tag. One oversized forbidden UDP datagram drops; one small tagged datagram and one untagged oversized datagram deliver. Neighbor-resolution delay preserves the tag through its queue. - Rfc8200SourceFragmentation: RFC 8200 — a source fragments a 1500-octet packet for a 1280-octet link, the router forwards the fragments untouched, and the destination reassembles them. Checks RFC8200-FRAG-3 (must), FRAG-4, FRAG-5 (description; their structure, without the payload length), FRAG-6 (must not), EXT-1, REASM-1, REASM-2 (description) and MTU-4 (must) from doc/project/evidence/standard/rfc8200/catalog.md; also covers HDR-3. The payload length of the fragments is Rfc8200FragmentPayloadLength.test, kept apart so that one wrong field does not hide the reassembly verdicts. The English procedure, the mockup and the size arithmetic are in doc/project/evidence/protocol/ipv6/checks/fragmentation.md#source- fragmentation-and-reassembly; the program steps below map one to one onto its expected observations. Host A's interface to link 1 has MTU 1280; a 1500-octet packet (1452 octets of data) splits into pieces of 1232 and 228 octets, ... Plan: plan/pending/dtls-publication-plan.md Change: src.networklayer.ipv6 | behavior.add | test whatsnew | dtls-extensions
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DTLS needs packet-level fault injection and an IPv6 path that honors requests to keep datagrams unfragmented. Typed packet-tap predicates now select actual contents before counting matching packets, and IPv6 drops an oversized datagram carrying a dontFragment request. Ordinary source fragmentation remains covered by controls.
This is series unit 01 of 18, from the approved 53-commit reconstruction. Its base is the pinned upstream master.
All 18 review branches are published. Units 02–18 will be opened incrementally after their predecessors land, unless maintainers provide upstream base refs. The paired statistics PR belongs to unit 06 and preserves the original baseline files and values. Existing PRs #1459 and #1465 remain unchanged.
Exact incremental comparison. Base
476ab0f2fa019c0bcf36d23d9f99ec884ee9393c, headd7f55fbeeea4e5bc99b461b8143336b2850da2db.flowchart LR P[Packet at tap] --> M{Expression and typed predicate match} M -->|No| F[Pass without advancing count] M -->|Yes| C[Advance occurrence count] C --> N{Selected occurrence} N -->|Yes| D[Apply requested packet fault] N -->|No| FCommits
Protocol scenarios and parent comparison
The fixtures and companion reviewer documents describe their real UDP/IP topology, fixed-seed stimulus, observations and limits. The comparison with the immediate parent is source-based unless the record identifies an executed comparison. A missing capability or API is reported as unavailable coverage, and is never counted as an observed parent runtime failure. Existing outcomes retained by a later fixture are controls.
Verification
Both-mode builds and the assigned PR-tip test union passed. Executed fixture counts: protocol / debug: 7, protocol / release: 7. The combined publication evidence and verification record retain exact commands, source/library identities, selectors, seeds, counts, input corrections and execution limits. input and history identity proof maps message-only reconstruction to the exact tested trees.
The identical IPv6 fixtures on the immediate parent produce two behavior failures and one passing ordinary-fragmentation control. The new typed-tap API is absent on its parent, so no runtime failure is claimed there.
Exact PR-tip commands
The record names the working directory, matching library hashes and raw artifact paths. A reused result is explicitly identified with its input-identity proof.
Baselines and protection
This unit changes no statistical, chart or fingerprint baseline values or pins.
Sealed packet-core sources remain unchanged. The DTLS/TLS/contract/adapter architecture, NED/MSG naming and interface scopes pass. Their global findings are inherited and match the pinned upstream target. The C++ gate retains 49 distinct hand-authored candidates and generated/framework findings, with zero compiler errors; its assessment is in the publication evidence. No global warning-free result or new seal is claimed.
Model limits and delivery
The series models protocol state, retained protected content, sizes and configured processing cost. It does not implement real cryptographic security or establish unrestricted interoperability. This unit provides the capability described above; later units introduce their own dependent behavior.
The original #1459 and #1465 branches and PRs remain unchanged. Upstream submission uses one landing at a time: PR01 targets master, and each later incremental PR follows its predecessor landing or an upstream-maintained base ref. Fork comparison branches do not supply upstream base branches.
Series roadmap