plans: the E6616X needs an E1/T1 media family, which the OTN decision does not cover #2261

Merged
jaylouisw merged 1 commit from catalogue/1120-0452 into main 2026-11-20 05:08:38 +00:00
Owner

Refs #803 only - no spec, no engine change, nothing in devices/.

The plan still carries the E6616X in rank 3, "the vendor never published it", beside the E6608T, and its step 6 says an OTN port type is the only engine decision left. Both readings are stale for this request, and between them they tell the next worker to go back to Huawei's document tree:

  • the frame is vendor-sourced (R026 brochure and the chassis chapter: 14 service slots DC / 12 AC, 780 G OTN on TM65UXCL licence, 100 G grey per channel, wavelengths N/A);
  • the only census - 32 E1/T1 on a TMB2DMS, TMB2TPS = 1x DMS + 2x PD1 - exists on reseller reprints and names the X in a 配套 table, so it is evidence of what the artefact would say and not a source for a field;
  • and those ports are 2.048 Mbit/s G.703 (75 ohm BNC / 120 ohm twisted pair) or 1.544 Mbit/s T1. engine/media.js has no cage for either, so an OTN media family - step 6, the one #807/#808/#810 wait on - leaves this request exactly as blocked as it is today.

This PR re-ranks it 2b, adds step 6b with the concrete shape of the media family (three media, two cages, connector-first classifier ahead of the serial fallback at media.js:853, type: serial kept so no view has to learn a new type), and corrects the two sentences that would send a reader back to the vendor tree.

Nothing is modelled from the reprints, per docs/MAINTAINING.md; research/optixtrans-e6616x-port-type-gap.md sections 4-5 carry the measurements this plan now points at.

Gates: node scripts/syntax-check.js (479 files, all OK), node scripts/check-control-bytes.js, node scripts/check-doc-citations.js (359 citations, none judged stale), node scripts/audit-port-types.js (no port contradicts its declared type), node test/hardware-invariants.test.js 26/26, node test/catalogue-hygiene.test.js 25/25, node test/doc-catalog-counts.test.js 43/43. Docs only - no device file, no engine file, registry unchanged.

Refs #803 only - no spec, no engine change, nothing in `devices/`. The plan still carries the E6616X in rank 3, "the vendor never published it", beside the E6608T, and its step 6 says an OTN port type is the only engine decision left. Both readings are stale for this request, and between them they tell the next worker to go back to Huawei's document tree: * the frame is vendor-sourced (R026 brochure and the chassis chapter: 14 service slots DC / 12 AC, 780 G OTN on `TM65UXCL` licence, 100 G grey per channel, wavelengths N/A); * the only census - 32 E1/T1 on a `TMB2DMS`, `TMB2TPS` = 1x DMS + 2x PD1 - exists on reseller reprints and names the X in a 配套 table, so it is evidence of what the artefact would say and not a source for a field; * and those ports are 2.048 Mbit/s G.703 (75 ohm BNC / 120 ohm twisted pair) or 1.544 Mbit/s T1. `engine/media.js` has no cage for either, so an OTN media family - step 6, the one #807/#808/#810 wait on - leaves this request exactly as blocked as it is today. This PR re-ranks it 2b, adds step 6b with the concrete shape of the media family (three media, two cages, connector-first classifier ahead of the `serial` fallback at `media.js:853`, `type: serial` kept so no view has to learn a new type), and corrects the two sentences that would send a reader back to the vendor tree. Nothing is modelled from the reprints, per `docs/MAINTAINING.md`; `research/optixtrans-e6616x-port-type-gap.md` sections 4-5 carry the measurements this plan now points at. Gates: `node scripts/syntax-check.js` (479 files, all OK), `node scripts/check-control-bytes.js`, `node scripts/check-doc-citations.js` (359 citations, none judged stale), `node scripts/audit-port-types.js` (no port contradicts its declared type), `node test/hardware-invariants.test.js` 26/26, `node test/catalogue-hygiene.test.js` 25/25, `node test/doc-catalog-counts.test.js` 43/43. Docs only - no device file, no engine file, registry unchanged.
plans: the E6616X needs an E1/T1 media family, which the OTN decision does not cover
All checks were successful
CI / Classify the change (pull_request) Successful in 42s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 36s
CI / Test (Node 22) (pull_request) Successful in 1m24s
CI / Test (Node 20) (pull_request) Successful in 1m27s
CI / Test (Node 18) (pull_request) Successful in 1m33s
CI / Server smoke and Docker build (pull_request) Successful in 38s
CI / Arm auto-merge (pull_request) Successful in 10s
0d63442114
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 05:01:24 +00:00
jaylouisw deleted branch catalogue/1120-0452 2026-11-20 05:08:40 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!2261
No description provided.