DC-to-DC links: link mode, diverse paths, third-party circuits #12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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 router is already topology-agnostic: import the duct/manhole network (or the metro fibre ring) and
A->B is routed along it, because
engine/street.jsonly knows about a graph. What is missing for asite-to-site circuit is the contract, not the routing.
Ask
A design mode for a point-to-point link between two sites, with protection.
is a circuit: A -> B, routed length, joints, splices, optical budget, verdict, and what to buy.
Minimum-cost edge-disjoint routing (Suurballe) over the same graph, with a diversity report: the
two paths, their lengths, and every segment they share with the metres ("diverse except 180 m at
the building entry"), because "diverse until the last duct" is the real answer and must be stated.
carries a provider, a stated length and a cost, contributes its loss to the budget, and is excluded
from the cable BOM.
Acceptance
POST /api/design/link(orsynthesisewithmode: "link"): two sites, a network, optics; returnsthe path(s), per-leg budget verdicts, and a BOM that contains cable only for owned segments.
paths[0]andpaths[1]are edge-disjoint on the true ringand share 0 m; with a graph where diversity is impossible, the result says which segment is shared
and how many metres.
length — same rule as
budget.pointToPointtoday.Not in this issue
Amplifiers, regenerators, CWDM/DWDM multi-wavelength budgets, and duct capacity per segment — each is
its own model and its own decision.
Today
street.buildGraph+routePath) on any imported geometry;budget.pointToPoint), including reach and overload — a short duct run on a ZX opticfails on overload and needs an attenuator;
as customer service, and only ever produces one path.