Summary

  • All five active BPM Internet-Drafts are at -00 and carry a Replaces link to an IPPM document.
  • The predecessor records had reached -10, -06, -07, -01 and -03; Datatracker shows the chain but gives no reason for the identifier reset.

A version counter is a poor witness to a project’s age. BPM’s first active docket shows why: five working-group drafts all start at -00, yet every record points back to an IPPM predecessor. One predecessor had already reached -10.

The IETF Datatracker lists three BPM records updated on 30 October 2026 and two on 31 October. All are marked “WG Document” and “I-D Exists.” Their Replaces fields point to IPPM records whose latest versions were -10 for the Alternate Marking Deployment Framework, -06 for its YANG model, -07 for On-Path Telemetry YANG models, -01 for the STAMP residual-bit-error-rate extension and -03 for the STAMP MPLS-header extension.

BPM has five new document records; a -00 suffix does not establish five brand-new lines of work. Replaces keeps the earlier records reachable. The titles cover three Alternate Marking or on-path telemetry documents and two STAMP extensions. Their presence on an active-draft list does not make them RFCs or report deployment results.

The public records give no reason for the BPM identifiers and no side-by-side text comparison or issue-by-issue transfer of review history. That is the evidence needed to judge editorial continuity behind the administrative handoff. Reviewers should follow Replaces before treating each -00 as a clean slate. Count the five active BPM records separately from the 196 results in “Related Internet-Drafts and RFCs”; combining the indexes would produce a false workload figure.

Sources