research: EUCC Security Target states the OptiXtrans/OSN 9800 brand join (Refs #810) #1952
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1952
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-0726"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #810 (and #807, #808) - records evidence, adds no spec, closes nothing.
Source (Huawei-authored, vendor-hosted by ENISA): EUCC-3089-2026-004 Security Target, Huawei OptiX OSN 9800 & OptiXtrans E9600 management component software, V100R024C10SPC100 - ST, Issue 0.19, 2026-10-14, 87 pp, 3,009,787 B - https://certification.enisa.europa.eu/document/download/ab9c6a55-bf65-4095-99bb-4e947a28156c_en?filename=EUCC-3089-2026-004%20Security%20Target.pdf
What it states
Why it matters: research/optixtrans-board-chapters-name-m-series.md �2 recorded the enterprise-to-carrier join as an inference. It is now a vendor statement, so a TNG1N/TNG1M chapter naming only the carrier subrack is admissible for #807/#808/#810. The same table also gives the SCC slot positions, which sit outside the service range (24+2 / 13+2 / 5+2 occupied positions per shelf).
What it does not give: no board census - TNG1N 0, TNG1M 0, TNG2 0, TMK1 0 in the 87-page text layer; no port count for TNG4CXP/TME3CTU/TNG1HCXP. The family stays blocked on one vendor copy of an N-series chapter (or EDOC1100163901, or the requester's one-line build).
Routes measured closed this pass (so nobody re-walks them): TNG1N210/206/401/402 filenames inside the TNG2DAP asset folder return S3 AccessDenied (positive control TNG2DAP = 200); the e.huawei.com E9600 product page links no documents at all (only images); every Google-indexed E9600 chapter on e-file is an optical-layer or transceiver chapter.
Gates: syntax-check 407 files OK; audit-port-types no contradiction; hardware-invariants 26/26; request-queue 32/32; check-control-bytes clean; audit-devices no hard defects.
8bddcec10d718573e84b