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.
CASE FILE
A Data Manifest Cannot Account for the Datapoints That Never Arrived
A network chart contains a clean sixty-second blank. The points before it have a platform, subscription and collection context; so do the points after it. The empty interval has none. A manifest can make received telemetry intelligible, but it cannot, from inside the same…
Story
ARIN's Retired Origin AS Field Recorded a Possibility, Not a Live Route
Old registration exports can preserve an `Origin AS` value long after ARIN removed the field. The label looks authoritative, but ARIN defined it as an optional holder-supplied list of ASNs from which a block might originate. It was neither a cryptographic authorization nor a…
IETF
Deletion Is the Hard Test as DNSOP’s Integration Draft Reaches Its Last Call Deadline
A DNS name can be easy to attach to an application and surprisingly hard to detach. As DNSOP’s integration draft reaches its scheduled Working Group Last Call deadline, its most consequential test is not whether a user can prove control once. It is whether the application can…
CASE FILE
SCONE Can Carry a Rate, Not the Policy That Chose It
SCONE makes a network's throughput advice visible to a QUIC application. What crosses the path is a number. The subscriber plan, traffic classification, load decision, responsible operator and correction route that produced it do not travel with the signal. That is a sound…
Story
LACNIC Whois created Dates the Registry Record, Not the Network's Launch
A timestamp precise to the second can look like a birth certificate. In LACNIC registration data, however, `created` dates the record for an address block. It does not reveal when the holder was founded, when engineers switched on a network, when the addresses were first used, or…
Story
AFRINIC Whois org-type Classifies a Registry Relationship, Not Legal Corporate Form
AFRINIC’s `org-type` field looks deceptively familiar: a short label attached to an organisation record. Its proper use is narrower. It helps describe how that record sits inside the registry’s resource and membership system; it does not answer the legal, ownership or operational…
IETF
CSR Attestation Reaches Last Call, but the Certificate Is Not the Evidence Record
A certificate can be perfectly valid and still say nothing about the private evidence that persuaded its issuer. The CSR-attestation draft now in IETF Last Call makes that boundary unusually clear: a CA may appraise extra device evidence or discard it, while publishing the…
IETF
An Authorized MPLS Neighbor Is Still Outside the Trust Boundary
An inter-provider link can be legitimate, authenticated and operationally necessary without making either provider part of the other's trusted core. RFC 5920 makes that distinction explicit. The leadership problem is not whether to trust or distrust the peer in the abstract; it…
CASE FILE
A Key Transparency Tombstone Does Not Retire the Old Log
The migration model in the KEYTRANS architecture gives an old log a precise job: point each label toward its newer home without letting an outage revive stale data. That marker solves lookup order. It does not prove that offline clients have finished monitoring the old history…
Story
RIPE Database mnt-ref Authorises an Organisation Reference, Not Corporate Control
An accepted `org:` link in the RIPE Database has passed a meaningful authorisation test. That makes it evidence of an approved database reference—not a shortcut to proving ownership, group membership or control of the network behind the record.
IETF
An In-Band Management Channel Reuses the Transport Path Without Inheriting Its Authority
An MPLS-TP node without native IP delivery or a separate out-of-fiber network can still be managed across the transport fabric. RFC 5718 makes that possible through the Generic Associated Channel, but the channel supplies only a delivery path: it neither identifies the sender nor…
Story
APNIC’s NIR RDAP Redirect Finds a More-Specific Record, Not a Network Operator
A redirect from APNIC to an NIR-specific RDAP host is an evidence trail about where registration data is served. It can lead to a narrower record without proving who currently routes, owns or operates the network.
IETF
GAAP-23 fixes its address ranges but leaves convergence after partitions open
The latest Group Address Allocation Protocol draft removes one source of disagreement: independently written implementations now have fixed IPv4 and IPv6 ranges. In the same revision, it records a harder limit. Two sides of a partition can choose different fallback addresses for…
Story
ARIN’s Whois Retirement Proposal Is a Protocol Transition, Not the End of Directory Data
Three dates in ARIN’s latest consultation can look like shutdown deadlines. They are not. The registry is asking how to retire three older access protocols in favour of RDAP, with separate dependencies and earliest dates for each path. The proposal changes how registration data…
IETF
A Discovered Ethernet Address Identifies the Next Hop Without Owning the Link Policy
The moment a peer tells you its MAC address, two different facts arrive: where to send the next frame, and what the link is allowed to become. RFC 7213 supplies the first, not the second. It makes Ethernet parameters discoverable for non-IP MPLS-TP links while leaving topology…
IETF
IETF’s PROBE Revision Admits Its Ping Analogy Misled Both Code and Eyes
A new deployment appendix records an unusually candid standards lesson: a familiar analogy can become an undocumented instruction, first for implementers and then for operators reading the result.
Story
LACNIC Whois routing-c Can Register Routing Policy, Not Prove Who Operates BGP
LACNIC Whois routing-c Can Register Routing Policy, Not Prove Who Operates BGP 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 G-ACh Advertisement Shares Peer State Without Delegating Local Configuration Authority
A peer can truthfully advertise a capability and still have no authority to decide what the receiving node should do with it. RFC 7212 makes that distinction operational: advertisements cross the link, but authorization, interpretation, freshness and the consequences of a local…
IETF
JOSE Sends Two Algorithms Toward Deprecation Without a Clock for Local Exceptions
The JOSE Working Group has asked the IESG to publish a draft that would deprecate `none` and `RSA1_5`. The document draws a sensible line between a safer common default and narrowly retained local choice. The unresolved operating question is how a permitted exception stops…
IETF
A Dynamic MPLS-TP Control Plane Does Not Own Every LSP
A green signaling adjacency can coexist with a broken data path, while a working static LSP can exist without any control plane at all. RFC 6373 therefore treats automation as a governed operating choice, not as automatic ownership of the transport network.