research(optixtrans): the E6600 hardware description is login-gated, not unpublished (#803) #1976

Merged
jaylouisw merged 2 commits from catalogue/1118-1102 into main 2026-11-18 11:07:04 +00:00
Owner

Evidence for #803 - does not close it. No port count, PoE figure or slot table was read, so no spec is written.

What was wrong with the census

The 2026-11-18 pass counted EDOC ids by fetching /enterprise/<lang>/doc/<ID> and reading a 302 to /view/notFound as "unpublished". A gated document redirects exactly the same way, so the count of "213 of 299 missing" was a count of "not anonymously readable".

/hedex/api/navi/<ID>/first-level-tree answers in three states:

state body means
200 {"status":200,...,"data":[...]} public
401 {"status":401,"message":"NOT LOGIN!","data":{"loginUrl":"https://uniportal.huawei.com/uniportal1/?redirect="}} exists, gated
404 {"status":404,"message":"No doc data found.","data":null} nonexistent

Controls: EDOC9999999999 and EDOC0000000000 -> 404; the public EDOC1100447312 -> 200.

https://support.huawei.com/enterprise/zh/optical-transmission/optixtrans-e6616x-pid-257173887 (200, 437,872 B, crawler UA) links 176 unique EDOC ids: 90 answer 200, 86 answer 401, none 404. The 86 are the technical set, and include:

  • six hardware-description editions: R022C10 EDOC1100303423, R023C00 EDOC1100328735, R023C10 EDOC1100367203, R024C10 EDOC1100456168, R025C00 EDOC1100525984, R025C10 EDOC1100558549;
  • the R026C00 product-documentation bundle EDOC1100625827;
  • OptiXtrans E6616X快速安装指南 02 EDOC1100299473 and the three E6616X release documents EDOC1100376749/50/51;
  • and EDOC1100456166, the English V100R024C10 hardware description the census had counted as absent.

What it changes

#803's blocker is no longer "Huawei does not publish the field" but "an anonymous crawler cannot authenticate". A free Huawei enterprise account reading the hardware description - newest listed edition EDOC1100558549 (zh), EDOC1100456166 (en) - is the remaining step, or the requester stating the build (E6616X DC chassis with 14x <board>).

research/open-device-requests.json and docs/DEVICE_REGISTRY.md are updated to say that, and research/optixtrans-e6616x-docs-gated-not-unpublished.md carries the counts, the controls and the correction. This extends #1973 (merged as 489ceb37), whose census is corrected here.

Gates: syntax-check 413 files OK; audit-port-types clean; test:requests 32/32; test:hardware 26/26; regen-registry-doc --check clean; check:citations and check:bytes pass.

Evidence for #803 - **does not close it**. No port count, PoE figure or slot table was read, so no spec is written. ## What was wrong with the census The 2026-11-18 pass counted EDOC ids by fetching `/enterprise/<lang>/doc/<ID>` and reading a 302 to `/view/notFound` as "unpublished". A *gated* document redirects exactly the same way, so the count of "213 of 299 missing" was a count of "not anonymously readable". `/hedex/api/navi/<ID>/first-level-tree` answers in three states: | state | body | means | |--|--|--| | 200 | `{"status":200,...,"data":[...]}` | public | | 401 | `{"status":401,"message":"NOT LOGIN!","data":{"loginUrl":"https://uniportal.huawei.com/uniportal1/?redirect="}}` | **exists, gated** | | 404 | `{"status":404,"message":"No doc data found.","data":null}` | nonexistent | Controls: `EDOC9999999999` and `EDOC0000000000` -> 404; the public `EDOC1100447312` -> 200. ## What the E6616X's own page links `https://support.huawei.com/enterprise/zh/optical-transmission/optixtrans-e6616x-pid-257173887` (200, 437,872 B, crawler UA) links **176** unique EDOC ids: **90 answer 200, 86 answer 401, none 404**. The 86 are the technical set, and include: - six hardware-description editions: R022C10 `EDOC1100303423`, R023C00 `EDOC1100328735`, R023C10 `EDOC1100367203`, R024C10 `EDOC1100456168`, R025C00 `EDOC1100525984`, R025C10 `EDOC1100558549`; - the R026C00 product-documentation bundle `EDOC1100625827`; - `OptiXtrans E6616X快速安装指南 02` `EDOC1100299473` and the three E6616X release documents `EDOC1100376749/50/51`; - and `EDOC1100456166`, the **English** V100R024C10 hardware description the census had counted as absent. ## What it changes #803's blocker is no longer "Huawei does not publish the field" but "an anonymous crawler cannot authenticate". A free Huawei enterprise account reading the hardware description - newest listed edition `EDOC1100558549` (zh), `EDOC1100456166` (en) - is the remaining step, or the requester stating the build (`E6616X DC chassis with 14x <board>`). `research/open-device-requests.json` and `docs/DEVICE_REGISTRY.md` are updated to say that, and `research/optixtrans-e6616x-docs-gated-not-unpublished.md` carries the counts, the controls and the correction. This extends #1973 (merged as 489ceb37), whose census is corrected here. Gates: syntax-check 413 files OK; audit-port-types clean; test:requests 32/32; test:hardware 26/26; regen-registry-doc --check clean; check:citations and check:bytes pass.
research(optixtrans): the E6600 hardware description is gated, not unpublished (#803)
All checks were successful
CI / Classify the change (pull_request) Successful in 7s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 19s
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 18) (pull_request) Successful in 56s
CI / Test (Node 22) (pull_request) Successful in 53s
CI / Arm auto-merge (pull_request) Successful in 14s
7912ce8dfa
The 2026-11-18 census counted EDOC ids by fetching /enterprise/<lang>/doc/<ID> and
reading a 302 to /view/notFound as "unpublished". That endpoint answers the same way
for a gated document, so the instrument could not tell absent from login-only.

/hedex/api/navi/<ID>/first-level-tree answers in three states: 200 (public), 401
"NOT LOGIN!" (exists, gated) and 404 "No doc data found." (nonexistent). Controls:
EDOC9999999999 and EDOC0000000000 -> 404, the public EDOC1100447312 -> 200.

The E6616X's Chinese product page links 176 EDOC ids: 90 answer 200, 86 answer 401,
none 404. The 86 include six hardware-description editions (R022C10 EDOC1100303423
through R025C10 EDOC1100558549), the R026C00 product-documentation bundle
EDOC1100625827, the E6616X quick installation guide EDOC1100299473 and the three
E6616X release documents - plus the English HD EDOC1100456166 that the census had
counted as absent.

So #803's field is published behind a free Huawei account rather than withheld. No
port count, PoE figure or slot table was read, so no spec is written: the issue stays
open and its registry row now names a login, not a missing publication.
Author
Owner

This branch conflicts with main, so it was not rebased:

docs/DEVICE_REGISTRY.md research/open-device-requests.json research/optixtrans-e6616x-anonymous-doc-census.md research/optixtrans-e6616x-docs-gated-not-unpublished.md 

A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.

This branch conflicts with `main`, so it was not rebased: ``` docs/DEVICE_REGISTRY.md research/open-device-requests.json research/optixtrans-e6616x-anonymous-doc-census.md research/optixtrans-e6616x-docs-gated-not-unpublished.md ``` A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
Merge remote-tracking branch 'origin/main' into catalogue/1118-1102
All checks were successful
CI / Classify the change (pull_request) Successful in 6s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Server smoke test (pull_request) Successful in 6s
CI / Docker build (pull_request) Successful in 20s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Arm auto-merge (pull_request) Successful in 10s
ecae2df9e2
# Conflicts:
#	docs/DEVICE_REGISTRY.md
#	research/open-device-requests.json
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!1976
No description provided.