DEFERRED

Deferred tracker

This file records every claim that was rephrased or removed to comply with the "no forward-looking promises" rule. Each entry names the feature, where it was mentioned in the wiki, and what the wiki says now. Thomas reviews this and decides whether any of it should land in a private roadmap, in the issue tracker, or nowhere.

Scope of the scrub: removed "planned", "will be", "yet" (when it implied future), "Phase 2", "lands in", "on the roadmap", "stub", "future-proofed", "landing later", and similar language. Kept: factual statements about the current state ("not implemented", "not supported", "decode-only"), and conditional "yet" in user-facing sentences like "if you have not built Ze yet".

Features that were called "planned" or "on the roadmap"

Feature	Where	Action taken
BMP (RFC 7854)	reference/comparison.md, reference/glossary.md, about/status.md	Rewritten as "not implemented". No promise of future work.
MRT dump (RFC 6396)	reference/comparison.md, reference/glossary.md, about/status.md	Same. Reading MRT through ze-analyse is documented separately and remains a current-state capability.
BFD	reference/comparison.md, about/status.md, about/what-is-ze.md	"Not implemented" only. Removed the "planned" and "not on the near-term roadmap" phrasings.
ASPA verification	reference/comparison.md, about/status.md	"Not implemented" only.
Confederation (RFC 5065)	reference/comparison.md, about/status.md, about/why-ze.md	"Not implemented" with a factual pointer to draft-ietf-idr-deprecate-as-set-confed-set. Note: the draft deprecates only the AS_CONFED_SET segment type, not confederation itself. Removed "not on the near-term roadmap".
Prefix list ge/le matching	configuration/bgp/policies.md, reference/comparison.md	"Not implemented" only. Removed "planned". Wiki suggests the external-plugin workaround.
AS-path regex matching	configuration/bgp/policies.md, reference/comparison.md	Same.
Private AS removal	about/why-ze.md, about/status.md	"Route servers cannot strip private ASNs". Removed "yet".
Dynamic neighbors	about/why-ze.md, about/status.md	Unchanged: already factual.
gRPC API	about/why-ze.md, about/status.md, reference/comparison.md	Unchanged: already factual.
AIGP in best-path selection	plugins/capabilities/bgp-aigp.md, configuration/fib.md, plugins/storage/bgp-rib.md, reference/comparison.md	"Not implemented" or "does not use". Removed every "yet".
IGP cost in best-path	configuration/fib.md, plugins/storage/bgp-rib.md	"Not implemented (requires IGP integration)". Removed "yet".
Full ECMP tuning	configuration/fib.md, plugins/infrastructure/fibkernel.md	"Not implemented". Removed "yet".
TCP-AO (RFC 5925)	configuration/bgp/peers.md, about/why-ze.md, reference/glossary.md	"TCP-AO is not implemented". Removed "yet". The "Alternative: nobody has it" cell in the comparison is now -- because the original claim was uncertain (Thomas flagged it: "I believe one may have it, it may be on our project docs/ folder"). Worth verifying.
Route reflector (RFC 4456)	configuration/bgp/route-reflection.md	"Ze does not implement a route reflector". Removed "on the roadmap".
BGP-LS encoding	plugins/address-families/bgp-nlri-ls.md, configuration/bgp/address-families.md	"Encoding is not implemented". Removed "yet". Verified 2026-04-08: in-tree docs/features/bgp-protocol.md and docs/comparison.md both show BGP-LS and BGP-LS VPN as Encode: No, and internal/component/bgp/plugins/nlri/ls/register.go has no encoder. Claim is accurate.
MVPN encoding	plugins/address-families/bgp-nlri-mvpn.md	Same.
RTC encoding	plugins/address-families/bgp-nlri-rtc.md	Same.
DHCPv6 proper Renew	plugins/infrastructure/ifacedhcp.md	Rephrased as "DHCPv6 Renew is not quite correct". Removed "yet". Known issue noted.
OSPF, IS-IS, LDP, PIM, MPLS control plane	about/what-is-ze.md, about/why-ze.md	"Not implemented". Removed "not on the near-term roadmap".
OSPF / IS-IS / static routes as sysrib sources	plugins/infrastructure/sysrib.md	Removed the "future-proofed for" and "Future: will consume" sentences. The plugin still takes inputs from bgp-rib today.
Configuration reference generator	reference/configuration-reference.md, configuration/yang-model.md	Rewritten as a pointer to ze schema show and the in-tree schemas. Removed "the generator is not written yet" and "stub" markers.
Mandatory/default filter visibility in config	configuration/bgp/redistribution.md	Removed "A future extensive view may display them".
FIB-to-kernel at scale	about/why-ze.md, reference/comparison.md	Rephrased as "The FIB story is not on par with FRR or BIRD". Removed "yet" and "planned".
Packaging (Docker, OS packages, binaries)	about/status.md, first-steps/install.md	"No Docker image, no binary releases, no OS packages." Removed "yet".
systemd unit file	first-steps/install.md	Rewritten to point at the "Starting and Stopping" page rather than promising a future sample unit.

Wiki phase language removed

The original Phase 1 build used "Phase 2" as a marker for "coming later". Those markers are all gone.

File	What the old text said	What it says now
Home.md	"A complete worked migration walkthrough lands in Phase 2."	Links to the existing exabgp-migration-walkthrough.md blueprint.
about/index.md	"Two longer pages ... are planned for Phase 2."	Lists why-ze.md and history.md directly.
blueprints/index.md	"Phase 1 of the wiki only ships this index page. The blueprints themselves are written in Phase 2."	Lists the seven blueprints directly.
chaos-testing/index.md	"until it is adapted in Phase 2. The dashboard and property verification pages are stubs for now."	Replaced with pointer to the in-tree architecture doc.
chaos-testing/property-verification.md	"This page is a stub ... will be adapted."	Removed. The page describes the current state.
configuration/index.md	"Phase 1 wiki only ships the entry pages ... until they are adapted into Phase 2."	Replaced with the full Phase 2 page list.
configuration/bgp/index.md	"For Phase 1 only the peer reference is in the wiki."	Replaced with the full BGP subtree page list.
configuration/bgp/route-reflection.md	"[Route server blueprint] when it lands in Phase 2"	Points at the blueprint that exists.
configuration/yang-model.md	"Configuration reference ... (stub)"	Points at the rewritten page without the stub marker.
development/index.md	"Phase 1 of the wiki ships only the entry pages ... until it is adapted in Phase 2."	Replaced with the full development page list.
first-steps/exabgp-migration.md	"A complete worked migration walkthrough lands as a blueprint in Phase 2."	Points at the existing walkthrough.
interfaces/looking-glass.md	"The Public Looking Glass blueprint lands in Phase 2"	Points at the existing blueprint.
operation/index.md	"Phase 1 ... will be adapted into this section in Phase 2."	Replaced with the full operation page list.
operation/monitoring.md	"Logging ... until the wiki page is adapted."	Points at the wiki logging page.
plugin-development/index.md	"The wiki page that adapts it is Phase 2." / "until they are adapted in Phase 2."	Points at the wiki pages directly.
plugin-development/go-plugins.md	"until it is adapted into the wiki"	Replaced with cross-links to the adapted pages.
plugins/index.md	"Phase 1 of this wiki only ships the index. The per-plugin reference pages are stubs until Phase 2."	Removed. The per-plugin pages exist.
reference/comparison.md	"The long-form Why Ze essay lands in Phase 2."	Points at the existing Why Ze page.
reference/index.md	"Phase 1 ships only the entry pages ... until it is adapted in Phase 2."	Replaced with the full reference page list.

Items that describe current state and were kept

A few items read like "yet" statements but describe the current state and were kept unchanged. Flagging them here so the audit is complete.

• about/status.md table "What does not work" lists BFD, BMP, MRT, Confederation, ASPA, Private AS removal, gRPC, and a handful of others as "Not implemented". These are factual statements, not promises.
• reference/comparison.md keeps "No production deployments. Pre-alpha, no releases." and similar factual claims.
• Pre-alpha banners ("Pre-Alpha. This page describes behavior that may change.") appear on every page and describe the current unstable state rather than promising stability at any later time.
• first-steps/quick-start.md and development/contributing.md contain "if you have not X yet" conditionals that are neutral English, not roadmap claims.
• development/rfc-implementation.md contains "no, not yet" inside a quoted example string describing an RFC status value; the quoted content is not a promise.

Items that are missing from the wiki, for any reason

None of these are commitments: they are documentation gaps noted for your attention.

• Auto-generated configuration reference. The spec asked for a per-field reference generated from the YANG schemas. No generator exists. reference/configuration-reference.md points readers at ze schema show and the in-tree schema files instead.
• Per-plugin deep dives. The per-plugin pages under plugins/<category>/ are compact, following the per-plugin template. They describe current behaviour but do not include operational details (specific metrics per plugin, known bugs, performance characteristics). Expand as the operational knowledge accumulates.
• Architecture deep dives beyond about/architecture.md. The in-tree docs/architecture/ directory has ~80 KB of architecture content that is not fully adapted. The wiki's architecture page condenses it to the mental model; the in-tree files remain the authoritative reference.
• Performance benchmarks. The wiki mentions estimated 10-15% CPU overhead vs C/Rust but there are no measured benchmark numbers against another daemon at DFZ scale.

How to use this file

• Before merging or committing the wiki, scan this list and decide whether any of the rephrased statements should be re-added in a different form, deleted from the wiki entirely, or moved to a separate internal roadmap document.
• The "Items Thomas flagged directly for verification" section has the items that need a factual check. Everything else is a rephrasing, not a factual change.
• If you decide the wiki should never promise features, this file can stay in the wiki as an internal audit trail or be moved out.