Time Horizon
NEAR TERM
Within the Time Horizon facet, NEAR TERM time-horizon intelligence organises articles by the period over which a signal is expected to matter. The page helps readers distinguish immediate operational changes from longer-cycle governance, investment, standards, and infrastructure shifts that may unfold across quarters or years. It connects timing assumptions with public evidence, related actors, market context, customer exposure, policy pressure, and infrastructure planning so readers can judge whether a development is urgent, strategic, or still waiting on confirming evidence. The page also explains how time horizon changes the meaning of a signal, which organisations may be exposed, and which infrastructure decisions require short-term action or long-cycle monitoring.
IETF
An RSVP-TE Hop Attribute Targets One Route Step Without Granting It Path-Wide Authority
An RSVP-TE Path message reaches the route step named immediately before an ERO Hop Attributes subobject. That adjacency fixes which hop the request addresses; the R bit then selects required or optional processing. It does not give the ingress path-wide authority.
IETF
The Fast Path Is a Recovery Graph: RFC 9912 Moves Wireless Reliability Into the Network Plane
Wireless conditions can change faster than a controller can install a new route, so RAW preinstalls a finite recovery graph and lets a Point of Local Repair select protection paths locally. That is the architectural move: reliability becomes a network-plane control problem, not a…
IETF
An RSVP-TE Required Attribute Can Reject an LSP Without Making Every Attribute Mandatory
A Path message reaches a legacy transit LSR carrying an attribute it does not recognize. Whether the LSP continues or fails is decided by the carrying entity’s enforcement class and the attribute’s defining RFC—not by a general rule that every attribute must be understood.
IETF
The Namespace Stayed Put: RFC 9911 Makes Common YANG Types a Migration Surface
A server can import the same `ietf-yang-types` namespace yet validate a timestamp differently when the common module revision changes. RFC 9911 keeps the familiar module identity while revising accepted values, canonical forms, and descriptions—turning a shared typedef library…
IETF
The Link Is a Snapshot: RFC 9910 Makes RIR Hierarchies Searchable
A single-result RDAP search link may become a lookup URL, but registry state can change before a client follows it. The link is therefore a time-bound snapshot of a registry view, not a timeless statement about a resource.
IETF
An RSVP-TE Exclude Route Forbids Resources Without Choosing the Remaining Path
An RSVP-TE Exclude Route Forbids Resources Without Choosing the Remaining Path intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
IETF
The Server Writes the Blank Form: RFC 9908 Makes EST CSR Attributes Operational
An EST server can now send a partially filled CSR form: it fixes the values it requires while leaving explicit blanks for the client to complete.
IETF
The Review Is the Interface: RFC 9907 Turns YANG Documents into Operational Controls
A YANG module may parse cleanly yet still create incompatible operations when its specification leaves lifecycle, datastore, or registry authority ambiguous. RFC 9907 makes authoring and review discipline part of the control surface for management specifications.
IETF
RSVP-TE Fast Reroute Lets a Local Node Bypass Failure Without Rewriting the End-to-End LSP
One protected hop fails, and the nearest Point of Local Repair (PLR) changes its local label operation to use a pre-established detour or facility bypass before the head-end can learn of the failure and recompute the end-to-end LSP. That is the speed proposition of RSVP-TE Fast…
IETF
Every Cell Says Stop: RFC 9906 Completes ECC-GOST’s DNSSEC Retirement
Every affected ECC-GOST registry cell now says **MUST NOT**: RFC 9906 closes both the production and validation lanes, unlike RFC 9905’s SHA-1 compatibility transition. The result is not merely a recommendation to stop signing; it is a coordinated retirement covering signing…
IETF
Stop Signing, Keep Reading: RFC 9905 Makes SHA-1 Retirement Asymmetric
RFC 9905 changes the DNSSEC operating rule at the algorithm-row level: the affected SHA-1 algorithms MUST NOT be used to create new material, while validator implementations MUST continue to support validation during the remaining installed-base transition. The result is…
IETF
MPLS Linear Protection Coordinates the Switch—but Priority Rules Decide Which Request Wins
A protection-domain endpoint receives local and remote requests, orders them by explicit priority, and moves selectors between a pre-provisioned working path and protection path. The leadership decision is therefore not whether PSC can invent a recovery route: it is whether both…
IETF
Four Cells, One Trust Chain: RFC 9904 Moves DNSSEC Algorithm Policy into the Registry
A DNSSEC algorithm number has four separately governed recommendation cells: validator implementation, signer implementation, validation use, and signing use. RFC 9904 changes where that guidance is maintained, not the recommendation status inherited on day one.
Global Cloud Services Trends
Ambarella’s US$91.4m RPO Is Not a Semiconductor-Demand Map
Ambarella’s July filing offers a useful corrective to the way chip-demand stories are often assembled. It reports US$91.4 million of transaction price allocated to certain unsatisfied product-order and engineering obligations. It also reports that two distributors represented…
IETF
MPLS Loss and Delay Measurements Expose Performance Without Taking Control of the Path
MPLS performance measurement turns forwarding evidence into operational evidence: loss measurement derives deltas from packet or octet counters, while delay measurement derives one-way and two-way values from timestamps carried in LM/DM query-response exchanges over G-ACh. It…
IETF
One Intent, Two Link-State Languages: RFC 9903 and the OSPF SR-MPLS Control Boundary
A single SR intent can be managed through a common YANG surface, while OSPFv2 exposes it through Opaque LSAs and OSPFv3 through Extended LSAs and distinct TLVs. That is a shared management contract, not identical wire encoding.
IETF
The MPLS Generic Associated Channel Carries Maintenance Without Turning Its Label into Forwarding Authority
MPLS label value 13 acts as the Generic Associated Channel Label, identifying a G-ACh packet and indicating that an Associated Channel Header follows the bottom of the label stack. The ACH Channel Type then selects a registered processing context. This is an in-band maintenance…
Global Institutional Trends
MarketAxess kept a 33% premium while its cash offer fell US$8
Intercontinental Exchange's first proposal and signed MarketAxess deal carry almost the same headline premium. They do not carry the same cheque. The merger proxy shows how a moving share-price denominator, a lower bid, two standalone forecasts and buyer-only synergies can…
IETF
An MPLS Extension Label Expands a Scarce Namespace Without Letting the Sender Assign Meaning
An MPLS LSR sees Base Special-Purpose Label 15 as the Extension Label (XL), then interprets the immediately following label under the Extended Special-Purpose Label (eSPL) registry. That two-entry mechanism expands a tightly constrained namespace without allowing a packet author…
IETF
The Model Behind the Label Stack: RFC 9902 and the Operational Contract for IS-IS Segment Routing
One enable leaf can start advertising IS-IS Segment Routing extensions, but safe activation depends on the protocol-independent SR label resources already configured beneath it. RFC 9902 makes that seam visible: the switch belongs to IS-IS, while the resources it invokes belong…