Add end-to-end SS7 traffic evidence

Author: ammarheidari

.gitattributes

@@ -0,0 +1,3 @@
+*.sh text eol=lf
+*.c text eol=lf
+docs/evidence/** -text

README.md

@@ -15,12 +15,12 @@ Repository: <https://github.com/araditc/sigtran.net>
 SIGTRAN.NET is currently in a **public release-candidate** track. Version
 `1.0.0-rc.1` has been published and restored from NuGet.org.
 
-Native Linux SCTP and external SCTP/M3UA peer evidence are retained and now feed
-the SDK readiness APIs through a common verification catalog. Stateful M3UA,
-M2PA, SCCP, TCAP, and MAP SMS runtimes are available. Full stable-product
-readiness remains gated on end-to-end independent-peer evidence,
-operator-sized performance evidence, trusted signing, and stable release
-execution.
+Native Linux SCTP, external SCTP/M3UA, and cross-implementation full-stack MAP
+SMS traffic evidence are retained. Stateful M3UA, M2PA, SCCP, TCAP, and MAP SMS
+runtimes are available. Full stable-product readiness remains gated on
+operator/vendor profile interoperability, independent M2PA evidence,
+operator-sized performance evidence, production operations, trusted signing,
+and stable release execution.
 
 For release history and governance, see:
 
@@ -53,6 +53,8 @@ The current RC engineering track focuses on:
   reconnect, metrics, and graceful-shutdown evidence.
 - External SCTP/M3UA peer validation with PCAP, SDK trace, peer log, and TShark
   comparison evidence.
+- Cross-implementation MAP SMS traffic through TCAP, SCCP, M3UA, and native SCTP
+  with retained PCAP, traces, field comparison, and digest evidence.
 - Stateful SCCP, TCAP, and MAP SMS service layers.
 - M2PA as a parallel MTP2 path.
 - Byte-level tests and protocol validation.
@@ -69,9 +71,9 @@ The current RC engineering track focuses on:
 | M3UA | Codec, routing, ASP state, long-running `IMtp3Network` runtime, bounded queues, heartbeat supervision, reconnect/failover hooks, diagnostics, and external peer evidence are available. |
 | SCTP | Native Linux SCTP evidence validates stream id, PPID, receive metadata, reconnect, metrics, graceful shutdown, and external peer traffic. |
 | M2PA | RFC 4165 codec and stateful `IMtp2Link` runtime provide alignment, proving, 24-bit sequencing, acknowledgement, retrieval retention, congestion handling, processor-outage recovery, metrics, and transport replacement. Independent peer evidence remains. |
-| SCCP | Stateful `ISccpService` supports UDT/XUDT/LUDT, GT translation, routing, bounded segmentation/reassembly, UDTS return policy, metrics, cancellation, and MTP3 receive ownership. External peer evidence remains. |
-| TCAP | Concurrent `TcapDialogueManager` provides transaction correlation, Begin/Continue/End/Abort, tracked invokes, Result/Error/Reject outcomes, shared timeout scanning, bounded queues, cleanup, snapshots, and metrics. External peer evidence remains. |
-| MAP | Stateful client/server SMS workflows cover SRI-SM, MO/MT ForwardSM, ReportSM-DeliveryStatus, and AlertServiceCentre with operation profiles, result/error correlation, typed dispatch, cancellation, and metrics. Independent peer evidence remains. |
+| SCCP | Stateful `ISccpService` supports UDT/XUDT/LUDT, GT translation, routing, bounded segmentation/reassembly, UDTS return policy, metrics, cancellation, and MTP3 receive ownership. Independent C-peer UDT evidence is retained; operator/vendor profile evidence remains. |
+| TCAP | Concurrent `TcapDialogueManager` provides transaction correlation, Begin/Continue/End/Abort, tracked invokes, Result/Error/Reject outcomes, shared timeout scanning, bounded queues, cleanup, snapshots, and metrics. Independent C-peer transaction evidence is retained; operator/vendor profile evidence remains. |
+| MAP | Stateful client/server SMS workflows cover SRI-SM, MO/MT ForwardSM, ReportSM-DeliveryStatus, and AlertServiceCentre with operation profiles, result/error correlation, typed dispatch, cancellation, and metrics. All five operations have cross-implementation repository-profile evidence; operator/vendor profile evidence remains. |
 | Tooling | Byte-level tests, protocol diagnostics, trace comparison, and interoperability evidence are core project principles. |
 
 ---
@@ -161,6 +163,7 @@ Start here:
 - [Phase 50 TCAP dialogue manager](docs/PHASE50_TCAP_DIALOGUE_MANAGER.md)
 - [MAP SMS service](docs/MAP.md)
 - [Phase 51 MAP SMS service](docs/PHASE51_MAP_SMS_SERVICE.md)
+- [Phase 52 end-to-end SS7 traffic lab](docs/PHASE52_END_TO_END_SS7_TRAFFIC_LAB.md)
 - [Interoperability and tooling](docs/INTEROPERABILITY.md)
 - [Compatibility policy](docs/COMPATIBILITY.md)
 - [Quality and contribution rules](docs/QUALITY.md)
@@ -210,16 +213,16 @@ Stable production support requires:
 - External SIGTRAN peer interoperability evidence.
 - Independent M2PA peer evidence.
 - Stateful SCCP, TCAP, and MAP SMS service validation.
-- End-to-end protocol trace validation.
+- Operator/vendor-profile end-to-end protocol trace validation.
 - Operator-sized capacity and resilience evidence.
 - Trusted package signing and provenance.
 - Stable package publication evidence.
 - Stable API lifecycle validation.
 - Security, release, compliance, and operations review.
 
-The Linux SCTP and external M3UA evidence gates are complete. Until the remaining
-gates are complete, the package should be treated as release-candidate
-infrastructure for controlled integrations.
+The Linux SCTP, external M3UA, and repository-profile full-stack traffic gates
+are complete. Until the remaining gates are complete, the package should be
+treated as release-candidate infrastructure for controlled integrations.
 
 ---
 

docs/COMMERCIAL_READINESS_REPORT.md

@@ -32,20 +32,25 @@ retained manifests instead of stale hard-coded flags.
   reconnect, queue metrics, and graceful shutdown validation. PCAP and SDK trace
   SHA-256 values are retained in
   `docs/evidence/PHASE45_NATIVE_SCTP_20260701T103951Z.json`.
+- Cross-implementation full-stack run `end-to-end-20260724T085858Z` passed on
+  WSL2 Linux with native SCTP. The .NET endpoint sent five MAP SMS operations
+  through TCAP, SCCP, and M3UA; the independent C/lksctp peer parsed five
+  invokes and built five results. The retained PCAP contains 23 SCTP packets
+  and ten M3UA DATA messages. The complete bundle is under
+  `docs/evidence/PHASE52_END_TO_END_20260724T085858Z/`.
 
 ## Remaining Production Blockers
 
 - The current benchmark is real Linux SCTP peer traffic evidence, but it is single-host loopback. Do not use it for broad operator capacity claims until an operator-sized deployment benchmark is retained.
 - Package publication evidence is closed for the public RC prerelease. Stable commercial release gates are foundation-complete, but live stable publication still requires retained stable release evidence, a completed protected stable publication run, and verified stable NuGet publication evidence.
 - Public/stable signing must use the organization's approved trusted certificate in the protected release environment; the current signing evidence is internal self-signed RC evidence.
 - Hosted GitHub provenance/SBOM attestations were skipped for dry-run and prerelease because private repository or organization attestation persistence can require a supported plan or public repository. These runs retained local provenance markers; stable runs keep hosted attestation reserved for the protected stable gate.
-- M3UA and M2PA now provide stateful runtime implementations through
-  `IMtp3Network` and `IMtp2Link`. Independent external M2PA peer evidence remains
-  part of the end-to-end traffic lab gate.
-- SCCP, TCAP, and MAP SMS now provide stateful runtime implementations with
-  routing, reassembly, transaction correlation, typed application operations,
-  Result/Error/Reject outcomes, timeout handling, and cleanup. The complete
-  stack still requires independent end-to-end peer evidence.
+- M3UA and M2PA provide stateful runtime implementations through `IMtp3Network`
+  and `IMtp2Link`. Independent external M2PA peer evidence remains.
+- SCCP, TCAP, and MAP SMS provide stateful runtime implementations and now have
+  cross-implementation traffic evidence for the repository profile. A separate
+  operator or vendor profile run is still required before broad SS7 network
+  interoperability can be claimed.
 - The retained benchmark is not an operator-sized multi-host capacity or soak
   result.
 

docs/INTEROPERABILITY.md

@@ -104,6 +104,24 @@ bool productionReady = report.IsProductionReady;
 
 The foundation gate is complete when trace formatting, conformance vectors, built-in vectors, simulator scripts, MAP SMS flows, transport samples, sample catalog, and CI profile are all present.
 
-Production readiness remains false until external interoperability lab evidence is captured against real peer stacks and packet traces.
+Repository-profile cross-implementation evidence is retained, but production
+readiness remains false until operator/vendor-profile interoperability and the
+remaining release gates are complete.
 
 Phase 7 adds `SigtranInteropEvidenceRegistry` so those lab artifacts can be tracked as stable release evidence instead of free-form notes.
+
+## Full-Stack Traffic Lab
+
+`Sigtran.NET.EndToEndLab` composes the implemented MAP SMS, TCAP, SCCP, M3UA,
+and native SCTP layers. `tools/interop-peer/sigtran_reference_peer.c` is an
+independent C/lksctp peer that parses each layer and constructs response bytes
+without linking to SDK code.
+
+Run `end-to-end-20260724T085858Z` passed with five MAP invokes, five MAP results,
+ten M3UA DATA messages, and 23 SCTP packets. Its PCAP, logs, configuration,
+trace, field export, comparison, report, and digests are retained under
+`docs/evidence/PHASE52_END_TO_END_20260724T085858Z/`.
+
+See [Phase 52](PHASE52_END_TO_END_SS7_TRAFFIC_LAB.md) for execution and evidence
+boundaries. This proves the repository profile across independent
+implementations; it does not replace operator/vendor interoperability.

docs/MAP.md

@@ -240,5 +240,7 @@ extensions, the TCAP facade, operation profiles, correlated client workflows,
 typed server dispatch, and operational controls.
 
 The in-process paired-stack tests exercise all five workflows and MAP error
-mapping. Production readiness remains false until independent end-to-end MAP
-SMS traces and operator-profile validation are retained.
+mapping. Phase 52 adds independent C-peer traffic for all five operations and
+retains PCAP and trace comparison evidence for the repository profile.
+Production readiness remains false until operator-profile validation is
+retained.

docs/PHASE52_END_TO_END_SS7_TRAFFIC_LAB.md

@@ -0,0 +1,93 @@
+# Phase 52 - End-To-End SS7 Traffic Lab
+
+Phase 52 adds an executable cross-implementation lab for carrying MAP SMS
+operations through every implemented layer:
+
+`MAP SMS -> TCAP -> SCCP -> M3UA -> native Linux SCTP`
+
+The SDK endpoint is .NET code. The reference endpoint is an independent C
+program that links only to Linux lksctp and constructs its own response bytes.
+
+## Completed Units
+
+| Unit | Capability | Status |
+| --- | --- | --- |
+| 1 | Executable .NET full-stack lab endpoint | Complete |
+| 2 | Independent C SCTP/M3UA reference peer | Complete |
+| 3 | SCTP stream and PPID receive validation | Complete |
+| 4 | M3UA ASPUP and ASPACTIVE handshake | Complete |
+| 5 | SCCP UDT parsing and response construction | Complete |
+| 6 | TCAP transaction and invoke correlation | Complete |
+| 7 | Five MAP SMS request/result exchanges | Complete |
+| 8 | PCAP, logs, trace, TShark, and comparison capture | Complete |
+| 9 | SHA-256 evidence manifest and retained bundle | Complete |
+| 10 | Runtime shutdown regression, docs, build, test, and pack | Complete |
+
+## Run The Lab
+
+The runner requires Linux kernel SCTP, lksctp headers, GCC, .NET 10,
+`tcpdump`, and `tshark`.
+
+```bash
+SIGTRAN_ARTIFACT_ROOT="$HOME/sigtran-lab/artifacts" \
+bash scripts/run-end-to-end-ss7-lab.sh
+```
+
+When passwordless sudo is unavailable, provide the password only in the process
+environment:
+
+```bash
+SIGTRAN_SUDO_PASSWORD="<runtime-secret>" \
+SIGTRAN_ARTIFACT_ROOT="$HOME/sigtran-lab/artifacts" \
+bash scripts/run-end-to-end-ss7-lab.sh
+```
+
+The script never writes the sudo password to configuration or evidence files.
+
+## Validation Contract
+
+The run passes only when all of the following are true:
+
+- SDK and peer exit successfully.
+- The SDK records five successful MAP outcomes.
+- The peer parses five MAP invokes and emits five MAP results.
+- PCAP contains at least ten M3UA DATA messages.
+- All retained artifacts receive SHA-256 digest coverage.
+
+The validated operations are:
+
+- `sendRoutingInfoForSM`
+- `mo-ForwardSM`
+- `mt-ForwardSM`
+- `reportSM-DeliveryStatus`
+- `alertServiceCentre`
+
+## Passing Evidence
+
+Run `end-to-end-20260724T085858Z` passed on WSL2 kernel
+`6.18.33.2-microsoft-standard-WSL2`.
+
+| Signal | Observed |
+| --- | ---: |
+| SCTP packets | 23 |
+| M3UA DATA messages | 10 |
+| SDK MAP outcomes | 5 |
+| Peer MAP invokes | 5 |
+| Peer MAP results | 5 |
+
+The retained bundle is under
+`docs/evidence/PHASE52_END_TO_END_20260724T085858Z/` and includes the PCAP,
+peer and capture logs, SDK JSONL trace, generated configuration, TShark field
+export, comparison report, summary, and digest manifest.
+
+## Evidence Boundary
+
+This run is independent cross-implementation evidence for the protocol profile
+currently implemented by this repository. The C peer does not share SDK codec
+code and validates every envelope before constructing its response.
+
+It is not evidence of interoperability with an operator STP, SMSC, HLR, vendor
+stack, or a separately maintained standards implementation. Those environments
+can impose profile, addressing, ASN.1, network-management, and operational
+requirements that this local peer does not cover. Stable operator-grade claims
+therefore remain gated on an external operator or vendor profile run.

docs/PHASE52_SUMMARY.md

@@ -0,0 +1,27 @@
+# Phase 52 Summary - End-To-End SS7 Traffic Lab
+
+Phase 52 is complete for repository-profile cross-implementation traffic.
+
+## Delivered
+
+- Added `Sigtran.NET.EndToEndLab`, which composes the public layer contracts from
+  MAP SMS down to native Linux SCTP.
+- Added an independent C peer for SCTP, M3UA, SCCP UDT, TCAP, and the five
+  supported MAP SMS operations.
+- Added a repeatable Linux runner with compilation, packet capture, trace
+  collection, TShark decoding, comparison, reporting, and digest generation.
+- Fixed graceful M3UA shutdown when cancellation occurs during reconnect delay.
+- Added regression coverage for reconnect-delay shutdown and startup
+  cancellation.
+- Retained passing run `end-to-end-20260724T085858Z` with 23 SCTP packets, ten
+  M3UA DATA messages, five MAP invokes, and five MAP results.
+- Updated README, interoperability guidance, protocol docs, roadmap, phase
+  index, and production readiness.
+
+## Readiness Position
+
+The SDK can send and receive real native SCTP traffic through its implemented
+M3UA, SCCP, TCAP, and MAP SMS service layers against an independently compiled
+peer. Operator or vendor interoperability, independent M2PA evidence,
+operator-sized performance, production operations, and stable release identity
+remain separate gates.

docs/PHASE_INDEX.md

@@ -56,7 +56,7 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 | 49 | SCCP stateful service layer | [Phase 49 SCCP Stateful Service](PHASE49_SCCP_STATEFUL_SERVICE.md), [Phase 49 Summary](PHASE49_SUMMARY.md), [SCCP](SCCP.md) | Implementation complete; external peer evidence pending |
 | 50 | TCAP dialogue manager | [Phase 50 TCAP Dialogue Manager](PHASE50_TCAP_DIALOGUE_MANAGER.md), [Phase 50 Summary](PHASE50_SUMMARY.md), [TCAP](TCAP.md) | Implementation complete; external peer evidence pending |
 | 51 | MAP SMS service | [Phase 51 MAP SMS Service](PHASE51_MAP_SMS_SERVICE.md), [Phase 51 Summary](PHASE51_SUMMARY.md), [MAP SMS](MAP.md) | Implementation complete; independent peer evidence pending |
-| 52 | End-to-end SS7 traffic lab | Planned | Pending |
+| 52 | End-to-end SS7 traffic lab | [Phase 52 End-To-End SS7 Traffic Lab](PHASE52_END_TO_END_SS7_TRAFFIC_LAB.md), [Phase 52 Summary](PHASE52_SUMMARY.md), [Interoperability](INTEROPERABILITY.md) | Complete for repository-profile cross-implementation traffic; operator/vendor profile evidence remains |
 | 53 | Operator-sized performance and resilience | Planned | Pending |
 | 54 | Production operations package | Planned | Pending |
 | 55 | Stable release execution | Planned | Pending |
@@ -65,7 +65,8 @@ This index is the complete phase map for Sigtran.NET. It links each phase to the
 
 The retained verification catalog now reports native Linux SCTP, external SCTP
 peer traffic, M3UA interoperability, RC SBOM/provenance/API baseline, and
-prerelease publication evidence. Full product readiness remains blocked on the
-end-to-end M2PA and higher-layer independent peer traffic, operator-sized
-performance, production operations, a
-trusted release identity, and protected stable publication.
+prerelease publication evidence. Phase 52 also retains cross-implementation
+M3UA/SCCP/TCAP/MAP SMS traffic evidence. Full product readiness remains blocked
+on operator/vendor profile validation, independent M2PA peer traffic,
+operator-sized performance, production operations, a trusted release identity,
+and protected stable publication.

docs/SCCP.md

@@ -216,4 +216,6 @@ SccpReadinessSnapshot report = SccpReadiness.GetReport();
 bool foundationReady = report.FoundationReady;
 ```
 
-Production readiness remains false until external SCCP interoperability vectors and network trace validation are added.
+Phase 52 retains independent C-peer SCCP UDT request/response traffic for the
+repository profile. Production readiness remains false until operator/vendor
+SCCP profile and network trace validation is retained.

docs/SDK_ROADMAP.md

@@ -477,15 +477,22 @@ five supported SMS operations through `ITcapComponentDialogues`.
 application contexts, and timeouts. `MapSmsServer` performs typed inbound
 dispatch with Result/Error/Reject responses, cancellation, validation, and
 metrics. Paired-stack tests cover every operation and MAP error mapping.
-Independent end-to-end peer evidence remains in Phase 52.
+Phase 52 adds cross-implementation evidence for all five operations;
+operator/vendor profile validation remains.
 
 ## Phase 52 - End-To-End SS7 Traffic Lab
 
 - Execute MAP over TCAP over SCCP over M3UA over SCTP against an independent peer.
 - Retain PCAP, peer log, SDK trace, configuration, field comparison, report, and
   SHA-256 manifests.
 
-Status: Pending.
+Status: Complete for repository-profile cross-implementation traffic. The .NET
+lab endpoint completed all five supported MAP SMS operations against an
+independently compiled C/lksctp peer. Passing run
+`end-to-end-20260724T085858Z` retained 23 SCTP packets, ten M3UA DATA messages,
+five peer-parsed MAP invokes, five peer-built results, SDK trace, configuration,
+TShark fields, comparison, report, and SHA-256 manifests. Operator/vendor
+profile validation and independent M2PA traffic remain separate gates.
 
 ## Phase 53 - Operator-Sized Performance And Resilience