research: an OTN line port needs no new port type - four specs already file them as Ethernet cages #1938
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!1938
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1118-0426"
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?
The correction
research/optixtrans-board-census.mdsection 2 concluded that #807, #808 and #810 were blocked on two fields, the second being "a port type that can represent an OTN line port", which it said required an engine change. The measurement in that section is right —engine/media.jshas nootnorwdmtype, andCAGE_MEDIA['sfp+']offers 10G Ethernet media, so a WDM-side wavelength filed asethernetcan be joined to a 10GBASE-LR peer. The conclusion does not hold.Four specs on
mainalready file exactly those ports the same way, and all four passscripts/audit-port-types.jsandtest/hardware-invariants.test.js:devices/huawei/optixtrans-e6616.jsonline*ethernet/cfp2/ 200Gdevices/ciena/waveserver-ai.jsonline*ethernet/qsfp28/ 100Gdevices/adva/fsp-3000.jsonline*ethernet/qsfp28/ 100Gdevices/packetlight/pl-2000m.jsonline*ethernet/qsfp28/ 100GNone of those ports carries Ethernet — a coherent wavelength on an FSP 3000 line card is an OTUk signal, and
optixtrans-e6616is a sibling frame of the queued ones, in the same vendor and the same document family, saying so innotes. So the missing type is an improvement waiting for an engine PR, not a prerequisite for these specs.What is in the diff
research/otn-line-ports-need-no-new-type.md— the convention stated once (cage as built,type: ethernetas the engine's only vocabulary for "framed signal at this rate", the protocol mismatch written intonotes,fabric.excludes: ["line*"]so a line port is not double-counted), the exact sentences each sibling uses to carry the compromise, what anotntype would buy and the mechanical migration if it lands, and the label each queued frame will take once its census arrives.research/optixtrans-board-census.md— a dated correction block under section 2, original text kept for its measurement, and the closing list narrowed from two blocked fields to one.Effect on the queue
The blocker for the three OptiXtrans frames is now singular: one
TNG1N*/TNG1M*client-board chapter that states both its front panel and which subrack accepts it. The frame arithmetic and the eventual labels are already determined; the validity of the board pairing is the part no anonymously readable vendor document states.No issue is answered by this PR and none should change state: the open-request ledger in
research/open-device-requests.jsonis untouched and still accurate.Gates
node scripts/syntax-check.js— 405 files, all OKnode scripts/audit-port-types.js— no port contradicts its declared typenode scripts/check-control-bytes.js— no control bytesnode test/request-queue.test.js— 32 passednode test/apply-research.test.js— 10 passednode test/hardware-invariants.test.js— 26 passednode scripts/regen-registry-doc.js— no diff (2,353 models, 258 vendors)78d2f2638ecba620f374