research: EUCC Security Target states the OptiXtrans/OSN 9800 brand join (Refs #810) #1952

Merged
jaylouisw merged 1 commit from catalogue/1118-0726 into main 2026-11-18 07:35:42 +00:00
Owner

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

  • p.3: 'OptiX OSN 9800 is used by both carriers and enterprise networks, and OptiXtrans E9600 is a new commercial brand for enterprise networks.'
  • Table 1-1 (p.6): one row 'OptiX OSN 9800 M24 / OptiXtrans E9624 - CXP: IU71, IU72 - TNG4CXP'; next row 'OptiX OSN 9800 M12/M05 / OptiXtrans E9612/E9605 - CTU: IU73, IU74 - TME3CTU'; 'OptiXtrans E9624X - HCXP: IU71, IU72 - TNG1HCXP'.

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.

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** - p.3: 'OptiX OSN 9800 is used by both carriers and enterprise networks, and OptiXtrans E9600 is a new commercial brand for enterprise networks.' - Table 1-1 (p.6): one row 'OptiX OSN 9800 M24 / OptiXtrans E9624 - CXP: IU71, IU72 - TNG4CXP'; next row 'OptiX OSN 9800 M12/M05 / OptiXtrans E9612/E9605 - CTU: IU73, IU74 - TME3CTU'; 'OptiXtrans E9624X - HCXP: IU71, IU72 - TNG1HCXP'. **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.
research: EUCC Security Target states the OptiXtrans↔OSN 9800 brand join
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 21s
8bddcec10d
Huawei's own Common Criteria Security Target for OptiX OSN 9800 and
OptiXtrans E9600 (EUCC-3089-2026-004, Issue 0.19, 2026-10-14, 87 pp,
published by ENISA) prints 'OptiX OSN 9800 M24 / OptiXtrans E9624' on one
row of Table 1-1 and 'M12/M05 / E9612/E9605' on the next, with the SCC
boards and their slots (CXP TNG4CXP in IU71,IU72; CTU TME3CTU in
IU73,IU74) and the sentence 'E9600 is a new commercial brand for
enterprise networks'.

That turns the family's 'which enterprise subrack is which carrier
subrack' join from an inference into a vendor statement, so an N-series
chapter that names only the carrier subrack is now sufficient for
#807/#808/#810. The ST still carries no board census: TNG1N 0, TNG1M 0
in all 87 pages. Recorded, not modelled - no spec is added.

Refs #810
jaylouisw force-pushed catalogue/1118-0726 from 8bddcec10d
All checks were successful
CI / Classify the change (pull_request) Successful in 5s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 54s
CI / Arm auto-merge (pull_request) Successful in 21s
to 718573e84b
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 18) (pull_request) Successful in 59s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 9s
2026-11-18 07:33:42 +00:00
Compare
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!1952
No description provided.