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
Authenticated Is Not Reachable: RFC 9897 and the MP-DCCP Path-Join Boundary
An authenticated `MP_ADDADDR` advertisement is control data, not permission to send traffic on a new path. That path becomes usable only when `MP_JOIN` binds a new subflow to the original connection and completes the nonce/HMAC reachability handshake.
Story
AFRINIC Whois notify Sends Change Notices, Not Operations Responsibility
AFRINIC Whois notify Sends Change Notices, Not Operations Responsibility 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
A BGP Large Community Carries a Policy Signal Without Granting the Sender Authority
A BGP Large Community can carry an operator’s intent across network boundaries in a form that still fits four-octet ASNs. That portability is useful precisely because it is not command authority. The Global Administrator identifies the namespace whose documentation gives a value…
IETF
Which Marking Wins? RFC 9895 and DLEP's Ethernet Credit Boundary
One packet matches both its Diffserv field and its tagged IEEE 802.1Q fields. Under RFC 9895, Ethernet classification takes precedence, so the Ethernet result determines the credit window against which transmission is accounted.
Story
RIPE Database sponsoring-org Records Administrative Sponsorship, Not Network Operation
The word “sponsor” can sound like ownership, financing or operational command. In the RIPE Database, `sponsoring-org` has a narrower and more useful meaning: it identifies the organisation administratively responsible for sponsoring an independent Internet number resource under…
IETF
A TTL of 255 Proves Network Proximity, Not the Identity of a BGP Peer
A packet can carry the address of a configured BGP neighbor and still be an impostor. RFC 5082 gives the receiving router a cheap test before scarce control-plane resources are consumed: start protected traffic at TTL 255 and distrust packets that arrive from farther away than…
North America Datacenter Trends
Cipher has started the gas link; its 2.5GW power terms remain undisclosed
A buried pipe can become a committed asset before the generator, grid connection or tenant it is meant to serve has public terms. Cipher Digital’s latest expansion plan makes that middle stage—not the headline capacity—the part investors need to price.
IETF
Advertise, Subset or Reset? RFC 9894 and DLEP's Diffserv Credit Boundary
A modem can advertise more DSCP-linked credit windows than a router can realize. The operator therefore has to select a supported subset or reset the session; silently pretending that the two capability shapes match is not a safe operating state.
Story
APNIC Whois mnt-lower Marks Maintainer Hierarchy, Not Routing Hierarchy
The word “lower” invites a network diagram: upstream, downstream, and packets moving between them. In APNIC Whois, `mnt-lower` describes something narrower. It identifies a maintainer in the registry’s update-authorisation structure. That is useful accountability evidence, but it…
IETF
When May the Router Send? RFC 9893 and DLEP's Credit-Window Control Loop
A packet may be ready at the router, but transmission is permitted only after the router finds the matching classifier and FID credit window, confirms enough credits, and counts the packet with its MAC overhead.
Story
ARIN Net Type Records Registration Path, Not a Current Customer Relationship
“Reallocated” and “reassigned” look like labels for a business relationship. In ARIN’s registry, they do something narrower: they describe how an address block entered a downstream registration chain and what the recipient intended to do with it. That history is useful, but it is…
IETF
Who Tells the Router Which Queue? RFC 9892 and DLEP's Traffic-Classification Boundary
A modem can supply a replaceable Traffic Classification Identifier (TID) set to a router. Flow Identifiers (FIDs) then group DSCP or VLAN/PCP matches; when both classifier families match, Ethernet VID/PCP wins. The important boundary is that RFC 9892 describes how classification…
North America Institutional Trends
CONX closed at 75%; EchoStar still has an 80.1% route
CONX now controls HC2 Broadcasting and appoints two of its three directors. Yet the closing did not freeze the cap table: INNOVATE can buy part of the business back, and EchoStar retains a separate route to become the 80.1% owner.
IETF
BGP ADD-PATH Exposes Alternate Routes Without Delegating the Best-Path Decision
A conventional BGP neighbor normally sees one advertised path for a prefix, so a replacement makes the earlier alternative disappear from that relationship. RFC 7911 changes that visibility by attaching a four-octet Path Identifier to each advertised NLRI. The identifier keeps…
IETF
When ACME Crosses a Delayed Network: RFC 9891 and the DTN Node-ID Proof Boundary
ACME authorization material is split between the ordinary ACME channel and delayed Bundle Protocol challenge and response Bundles: the server sends a challenge Bundle to the claimed singleton DTN Node ID, while the client binds the ACME account challenge to receipt of a…
Story
LACNIC WHOIS nslastaa Records the Last Successful Check, Not Current DNS Health
A date in a registry response can look like a present-tense assurance. LACNIC gives `nslastaa` a narrower meaning: it is the last date on which a correct reverse-DNS configuration was observed on a listed server. That historical success is useful evidence, but it is not a promise…
IETF
When a YANG Name Survives Revision: RFC 9890 and the Registry Identity Boundary
A revised YANG module keeps the initial module name and XML namespace. That makes a stable registry identity useful for locating the module, but it does not by itself identify the deployed revision or prove semantic compatibility. The operational question is therefore precise…
IETF
Extended BGP OPEN Removes a 255-Byte Ceiling Without Making Every Peer Ready for More Capabilities
BGP speakers announce capabilities before they exchange routes, but the original OPEN message gives all optional parameters together only one octet of length. RFC 9072 removes that 255-byte aggregate ceiling by defining an extended encoding. The change creates room; it does not…
Story
AFRINIC WHOIS source identifies a database namespace, not a record’s provenance
AFRINIC WHOIS source identifies a database namespace, not a record’s provenance 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
When 5G Slice Intent Reaches the Transport Network: RFC 9889 and the Handoff Control Boundary
An S-NSSAI that the transport domain cannot see must cross a handoff through a VLAN, IP or MPLS identifier before it can be bound to a transport service. That identifier is a translation point, not a complete promise of isolation, quality or capacity.