<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3688 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY RFC6020 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml">
<!ENTITY RFC6991 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6991.xml">
<!ENTITY RFC7950 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml">
<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
<!ENTITY RFC8341 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml">
<!ENTITY RFC8639 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8639.xml">
<!ENTITY RFC8791 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8791.xml">
<!ENTITY RFC9196 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9196.xml">
<!ENTITY RFC7951 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7951.xml">
<!ENTITY RFC8641 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8641.xml">
<!ENTITY I-D.ietf-netconf-notif-envelope SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-notif-envelope.xml">
<!ENTITY I-D.ietf-netconf-yang-push-2 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-netconf-yang-push-2.xml">
<!ENTITY I-D.dikshit-nmop-telemetry-identifier-scoping SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.dikshit-nmop-telemetry-identifier-scoping.xml">
<!ENTITY I-D.dikshit-netmod-comparability-scope-extension SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.dikshit-netmod-comparability-scope-extension.xml">
]>
<rfc submissionType="IETF" docName="draft-dikshit-netconf-yang-push-causal-ordering-02" category="std" ipr="trust200902">
  <?rfc strict="yes"?>
  <?rfc compact="yes"?>
  <?rfc subcompact="no"?>
  <?rfc symrefs="yes"?>
  <?rfc sortrefs="yes"?>
  <?rfc text-list-symbols="*o+-"?>
  <?rfc toc="yes"?>
  <front>
  <title abbrev="YANG-Push Causal Ordering">Cross-Publisher Causal Ordering for YANG-Push Datastore Telemetry</title>
  <author initials="S." surname="Dikshit" fullname="Saumya Dikshit">
  <organization>Hewlett Packard Enterprise</organization>
  <address><postal>
  <street>Mahadevpura</street>
  <city>Bangalore</city>
  <region>Karnataka</region>
  <code>560 048</code>
  <country>India</country>
  </postal>
  <email>saumya.dikshit@hpe.com</email>
  </address>
  </author>

  <date year="2026" month="November" day="20"/>
  <abstract><t>
  In YANG-Push version 2, each publisher numbers its own notifications,
  and the numbers of two publishers are not comparable. When a single
  subscription is served by several publishers, for example on a
  multi-line-card router or a disaggregated routing stack, a collector
  cannot order updates across those publishers from the sequence numbers
  alone. This document defines an opt-in, coordination-free mechanism
  that carries a Comparability Scope, a coarse Causal-Epoch, and a
  per-publisher Local-Sequence-Number in the notification envelope.
  Publishers stay lock-free on the export fast path, and a collector
  reconstructs cross-publisher order within a bounded reordering window.
  A companion YANG module adds the subscription controls, the envelope
  metadata, and the capability discovery. The mechanism does not require
  synchronized clocks across publishers.</t>
  </abstract>
  </front>

  <middle>
  <section title="Introduction" anchor="sect-1"><t>
  YANG-Push version 2 <xref target="I-D.ietf-netconf-yang-push-2"/> gives
  every notification a sequence number that is counted separately for
  each publisher within a subscription. Section 13 of that document
  states that sequence numbers from different publishers do not establish
  an ordering between their notifications, and it allows data to move from
  one publisher to another at a collection boundary.</t>

  <t>
  In a distributed network element, a single subscription can be served
  at the same time by several publishers, for example one per line card
  or per routing process. When their notifications arrive interleaved at
  a collector, the per-publisher sequence numbers alone cannot place the
  updates in one order across publishers.</t>

  <t>
  This document defines an opt-in, coordination-free mechanism for
  cross-publisher ordering. Publishers stay lock-free on the export fast
  path and carry three small metadata elements in the notification
  envelope: a Comparability Scope that bounds which notifications are
  compared, a coarse Causal-Epoch that advances only when causal state is
  handed off across publishers, and a per-publisher Local-Sequence-Number.
  A collector reconstructs order within a Comparability Scope using a
  bounded reordering window. The mechanism does not require synchronized
  clocks across publishers. A companion YANG module (<xref target="sect-5"/>)
  adds the subscription opt-in, the envelope metadata, and capability
  discovery.</t>

  <section title="Requirements Language" anchor="sect-1.1"><t>
  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
  "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
  "OPTIONAL" in this document are to be interpreted as described in
  BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only
  when, they appear in all capitals, as shown here.</t>
  </section>

  <section title="Terminology" anchor="sect-1.2"><t><list style="symbols">
  <t>Comparability Scope: a set of publishers and notifications whose
     updates are compared for cross-publisher ordering, identified by a
     Comparability Scope identifier. The scope aligns with
     <xref target="I-D.dikshit-nmop-telemetry-identifier-scoping"/> and
     <xref target="I-D.dikshit-netmod-comparability-scope-extension"/>.</t>
  <t>Causal-Epoch: a coarse logical counter shared across publishers
     within a Comparability Scope. It advances only when causal state is
     handed off across a publisher boundary.</t>
  <t>Local-Sequence-Number (Local-Seq): the strictly monotonic
     per-publisher counter used to detect loss and duplicates within a
     given publisher and Causal-Epoch.</t>
  <t>Publisher: as defined in
     <xref target="I-D.ietf-netconf-yang-push-2"/>.</t>
  <t>Collector: the receiver that consumes notifications and reconstructs
     order.</t>
  </list>
  </t>
  </section>
  </section>

  <section title="Problem Statement and Comparability Scope" anchor="sect-2"><t>
  In distributed network elements, such as multi-line-card routers,
  disaggregated routing stacks, or replicated telemetry exporters, a
  single YANG-Push subscription may be served concurrently by multiple
  independent publishers. Existing notification sequence numbers are
  strictly local to each individual publisher process or transport
  session.</t>

  <t>
  When notifications from multiple publishers arrive interleaved at a
  collector, per-publisher sequence numbers cannot:</t>

  <t><list style="numbers">
  <t>Establish causal or cross-publisher ordering across datastore
     updates.</t>
  <t>Distinguish out-of-order delivery across publishers from genuine
     packet loss within a single publisher stream.</t>
  </list>
  </t>

  <t>
  To avoid imposing cross-publisher ordering overhead on unrelated
  telemetry, causal ordering is bounded to an explicit Comparability
  Scope, aligned with
  <xref target="I-D.dikshit-nmop-telemetry-identifier-scoping"/> and
  <xref target="I-D.dikshit-netmod-comparability-scope-extension"/>. Only
  notifications sharing the same Comparability Scope identifier are
  evaluated for cross-publisher causal ordering.</t>
  </section>

  <section title="High-Level Architecture" anchor="sect-3"><t>
  Enforcing a single globally incremented sequence number across
  distributed publishers would require synchronous inter-process locking
  or strict wall-clock synchronization on the telemetry export fast path,
  degrading throughput under high churn.</t>

  <t>
  Instead, this architecture decouples per-publisher loss detection from
  cross-publisher causal ordering by keeping publishers coordination-free
  on the fast path and offloading bounded reordering to the collector:</t>

  <figure><artwork><![CDATA[
  Lock-free fast path (publishers)        Collector engine
  ================================        ================

  +---------------------------------+
  | Publisher P1 (e.g. LC1 / RIBd)  |
  | emits {Scope=S1,Epoch=12,Seq=1} |---+
  +---------------------------------+   |   +------------------------+
                                        +-->| 1. group by Scope (S1) |
   causal state hand-off                |   | 2. order by (Epoch,    |
   advances Epoch 12 -> 13              |   |    Local-Seq)          |
            |                           |   | 3. bounded watermark   |
            v                           |   |    reordering window   |
  +---------------------------------+   |   +------------------------+
  | Publisher P2 (e.g. LC2 / BGPd)  |---+
  | emits {Scope=S1,Epoch=13,Seq=1} |
  +---------------------------------+
]]></artwork>
  </figure>

  <t>
  Key design properties:</t>

  <t><list style="symbols">
  <t>Zero per-notification cross-publisher locks: each publisher
     maintains its own local monotonic Local-Seq counter in O(1) without
     inter-process communication or atomic contention across line cards
     or processes.</t>
  <t>Coarse Causal-Epoch propagation: publishers share a Causal-Epoch
     counter that advances only when a causal state dependency crosses
     publisher boundaries, for example a RIB state installation that
     triggers a BGP update. The epoch piggybacks on existing
     control-plane state hand-offs rather than introducing per-packet
     coordination.</t>
  <t>Two-tier ordering at the collector: the Causal-Epoch establishes a
     partial, causal ordering across distinct publishers within the same
     Comparability Scope, while the Local-Seq preserves exact
     per-publisher gap and duplicate detection within any given
     (Publisher, Causal-Epoch) pair.</t>
  </list>
  </t>
  </section>

  <section title="Notification Metadata Model" anchor="sect-4"><t>
  When cross-publisher causal ordering is negotiated or configured for a
  subscription, each exported YANG-Push notification carries three
  metadata elements within its notification envelope, extending
  <xref target="I-D.ietf-netconf-notif-envelope"/>:</t>

  <figure><artwork><![CDATA[
  +------------------------------------------------------------+
  | YANG-Push notification envelope (ietf-yp-notification)     |
  +------------------------------------------------------------+
  | comparability-scope-id  (multi-publisher group identifier) |
  | causal-epoch            (uint64; cross-publisher fence)    |
  | local-sequence-number   (uint64; per-publisher monotonic)  |
  +------------------------------------------------------------+
  | notification payload (datastore-changes / push-update)     |
  +------------------------------------------------------------+
]]></artwork>
  </figure>

  <t>
  Subscription-level opt-in: support for causal ordering MUST be disabled
  by default and enabled explicitly per subscription via a boolean leaf
  (enable-causal-ordering), ensuring zero wire or CPU overhead for
  single-publisher subscriptions.</t>

  <t>
  The following example shows a push-change-update notification
  <xref target="RFC8641"/> carried in the envelope with the causal
  ordering metadata, using the JSON encoding of
  <xref target="RFC7951"/>:</t>

  <figure><artwork><![CDATA[
{
  "ietf-yp-notification:envelope": {
    "event-time": "2026-11-20T09:30:00.12Z",
    "ietf-yp-notification:hostname": "pe-router-01",
    "ietf-yp-notification:sequence-number": 405,
    "ietf-yang-push-causal-ordering:causal-ordering": {
      "comparability-scope-id": "rib-vrf-red",
      "causal-epoch": "12",
      "local-sequence-number": "405"
    },
    "contents": {
      "ietf-yang-push:push-change-update": {
        "id": 1011
      }
    }
  }
}
]]></artwork>
  </figure>
  </section>

  <section title="YANG Module" anchor="sect-5"><t>
  This document defines the YANG 1.1 <xref target="RFC7950"/> module
  ietf-yang-push-causal-ordering. It imports common types from
  <xref target="RFC6991"/>. It augments ietf-subscribed-notifications
  <xref target="RFC8639"/> with the subscription opt-in controls, augments
  the YANG-Push notification envelope
  <xref target="I-D.ietf-netconf-notif-envelope"/> with the causal
  ordering metadata using the structure extension of
  <xref target="RFC8791"/>, and augments the system and notification
  capabilities of <xref target="RFC9196"/> so that a client can discover
  support.</t>

  <figure><artwork><![CDATA[
<CODE BEGINS> file "ietf-yang-push-causal-ordering@2026-11-20.yang"

module ietf-yang-push-causal-ordering {
  yang-version 1.1;
  namespace
    "urn:ietf:params:xml:ns:yang:ietf-yang-push-causal-ordering";
  prefix yp-co;

  import ietf-yang-types {
    prefix yang;
    reference
      "RFC 6991: Common YANG Data Types";
  }

  import ietf-subscribed-notifications {
    prefix sn;
    reference
      "RFC 8639: Subscription to YANG Notifications";
  }

  import ietf-yang-structure-ext {
    prefix sx;
    reference
      "RFC 8791: YANG Data Structure Extensions";
  }

  import ietf-system-capabilities {
    prefix sysc;
    reference
      "RFC 9196: YANG Modules Describing Capabilities for Systems
       and Behavioral Change Management";
  }

  import ietf-notification-capabilities {
    prefix notc;
    reference
      "RFC 9196: YANG Modules Describing Capabilities for Systems
       and Behavioral Change Management";
  }

  import ietf-yp-notification {
    prefix ypn;
    reference
      "I-D.ietf-netconf-notif-envelope: Extensible YANG Model for
       YANG-Push Notifications";
  }

  organization
    "IETF NETCONF (Network Configuration) Working Group";
  contact
    "WG Web:   <https://ietf.org>
     WG List:  <mailto:netconf@ietf.org>

     Author:   Saumya Dikshit
               <mailto:saumya.dikshit@hpe.com>";
  description
    "This module defines YANG extensions for opt-in cross-publisher
     causal ordering in YANG-Push datastore telemetry without
     requiring synchronous locking across distributed publishers.

     Copyright (c) 2026 IETF Trust and the persons identified as
     authors of the code.  All rights reserved.

     Redistribution and use in source and binary forms, with or
     without modification, is permitted pursuant to, and subject to
     the license terms contained in, the Revised BSD License set
     forth in Section 4.c of the IETF Trust's Legal Provisions
     Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC XXXX
     (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
     for full legal notices.";

  revision 2026-11-20 {
    description
      "Initial revision adding opt-in subscription causal ordering
       configuration and lock-free notification envelope metadata.";
    reference
      "draft-dikshit-netconf-yang-push-causal-ordering-02";
  }

  feature causal-ordering {
    description
      "Indicates that the publisher supports opt-in cross-publisher
       causal ordering metadata on YANG-Push notifications.";
  }

  grouping causal-ordering-subscription-config {
    description
      "Subscription-level opt-in parameters for cross-publisher
       causal ordering.";
    leaf enable-causal-ordering {
      if-feature "causal-ordering";
      type boolean;
      default "false";
      description
        "When set to 'true', publishers serving this subscription
         include cross-publisher causal ordering metadata in
         emitted notification envelopes.  Disabled by default to
         incur zero overhead on single-publisher subscriptions.";
    }
    leaf comparability-scope-id {
      when "../enable-causal-ordering = 'true'";
      if-feature "causal-ordering";
      type string {
        length "1..64";
      }
      description
        "Identifier defining the multi-publisher comparability
         group.  Notifications sharing the same scope identifier
         can be causally ordered by a collector.";
    }
    leaf max-skew-window {
      when "../enable-causal-ordering = 'true'";
      if-feature "causal-ordering";
      type uint32;
      units "milliseconds";
      default "50";
      description
        "Recommended bounded reordering window hint for collectors
         processing interleaved streams within this comparability
         scope.";
    }
  }

  grouping causal-ordering-envelope-metadata {
    description
      "Lightweight, coordination-free metadata carried in the
       YANG-Push notification envelope when causal ordering is
       enabled.";
    leaf comparability-scope-id {
      type string {
        length "1..64";
      }
      mandatory true;
      description
        "The comparability scope identifier shared by all
         publishers participating in the same causal ordering
         domain.";
    }
    leaf causal-epoch {
      type yang:counter64;
      mandatory true;
      description
        "Coarse logical epoch shared across publishers within the
         comparability scope.  Increments only upon causal state
         hand-off across publishers, avoiding per-message locks.";
    }
    leaf local-sequence-number {
      type yang:counter64;
      mandatory true;
      description
        "Strictly monotonic per-publisher sequence counter used to
         detect packet loss and duplicates within a given
         (publisher, causal-epoch) tuple.";
    }
  }

  augment "/sn:subscriptions/sn:subscription" {
    description
      "Adds opt-in cross-publisher causal ordering controls to
       configured and dynamic subscriptions.";
    uses causal-ordering-subscription-config;
  }

  augment "/sn:establish-subscription/sn:input" {
    description
      "Allows dynamic subscription RPC requests to opt into
       cross-publisher causal ordering.";
    uses causal-ordering-subscription-config;
  }

  augment "/sn:modify-subscription/sn:input" {
    description
      "Allows dynamic subscription modifications to update
       causal ordering parameters.";
    uses causal-ordering-subscription-config;
  }

  sx:augment-structure "/ypn:envelope" {
    description
      "Augments the extensible YANG-Push notification envelope with
       coordination-free cross-publisher causal ordering metadata
       when enabled for the subscription.";
    container causal-ordering {
      if-feature "causal-ordering";
      presence
        "Present when cross-publisher causal ordering is enabled
         for the subscription.";
      description
        "Cross-publisher causal ordering metadata carried alongside
         event-time in the notification header.";
      uses causal-ordering-envelope-metadata;
    }
  }

  augment "/sysc:system-capabilities/notc:subscription-capabilities"
        + "/ypn:notification-metadata/ypn:metadata" {
    if-feature "causal-ordering";
    description
      "Allows a client to discover whether the publisher supports
       cross-publisher causal ordering metadata in the notification
       envelope.";
    leaf causal-ordering-supported {
      type boolean;
      default "false";
      description
        "Indicates whether the publisher supports emitting
         cross-publisher causal ordering metadata in the
         ietf-yp-notification envelope.";
    }
  }
}

<CODE ENDS>
]]></artwork>
  </figure>
  </section>

  <section title="Operational and Performance Considerations" anchor="sect-6"><t>
  To ensure deterministic performance on resource-constrained network
  elements, deployments SHOULD apply the following operational
  controls:</t>

  <t><list style="symbols">
  <t>Selective subscription enablement: operators SHOULD enable
     cross-publisher causal ordering only on subscriptions monitoring
     causally coupled distributed state, for example cross-line-card
     RIB and FIB or protocol state transitions, leaving high-volume
     interface counters in standard unordered mode.</t>
  <t>Bounded collector reordering window: collectors MUST bound memory
     and reordering latency using a configurable watermark timer
     (max-skew-window). Notifications arriving past the watermark MAY be
     flagged as late rather than stalling downstream datastore ingestion
     indefinitely.</t>
  <t>Clock independence: because ordering relies on logical causal epochs
     (Causal-Epoch) and local monotonic counters (Local-Seq),
     implementations do not require sub-millisecond PTP or NTP
     synchronization across publishers to guarantee causal
     consistency.</t>
  </list>
  </t>
  </section>

  <section title="Security Considerations" anchor="sect-7"><t>
  The YANG module defined in this document augments
  ietf-subscribed-notifications <xref target="RFC8639"/> with configurable
  subscription nodes (enable-causal-ordering, comparability-scope-id, and
  max-skew-window). These nodes are writable through configuration or
  through the dynamic subscription RPCs. The access control model of
  <xref target="RFC8341"/> SHOULD be used to restrict which clients can
  change them, because enabling or changing causal ordering affects the
  notifications a subscription emits.</t>

  <t>
  The causal ordering metadata is asserted by the publishers. A publisher
  that reports an incorrect Causal-Epoch or Local-Sequence-Number can
  cause a collector to order notifications incorrectly within a
  Comparability Scope. This relies on the same trust in the publisher as
  the existing per-publisher sequence number in
  <xref target="I-D.ietf-netconf-yang-push-2"/>, and it does not affect
  notifications outside the Comparability Scope.</t>

  <t>
  A collector MUST bound the reordering window (max-skew-window) so that
  interleaved or delayed notifications cannot cause unbounded buffering.
  Notifications arriving after the window MAY be flagged as late rather
  than held.</t>

  <t>
  The transport and authentication considerations of
  <xref target="I-D.ietf-netconf-yang-push-2"/> and
  <xref target="RFC8639"/> apply unchanged.</t>
  </section>

  <section title="IANA Considerations" anchor="sect-8"><t>
  This document requests IANA to register the following URI in the "ns"
  subregistry within the "IETF XML Registry" <xref target="RFC3688"/>:</t>

  <figure><artwork><![CDATA[
URI: urn:ietf:params:xml:ns:yang:ietf-yang-push-causal-ordering
Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace.
]]></artwork>
  </figure>

  <t>
  This document requests IANA to register the following YANG module in
  the "YANG Module Names" registry <xref target="RFC6020"/>:</t>

  <figure><artwork><![CDATA[
Name: ietf-yang-push-causal-ordering
Namespace: urn:ietf:params:xml:ns:yang:ietf-yang-push-causal-ordering
Prefix: yp-co
Reference: RFC XXXX
]]></artwork>
  </figure>
  </section>
  </middle>

  <back>
  <references title="Normative References">
  &RFC2119;
  &RFC3688;
  &RFC6020;
  &RFC6991;
  &RFC7950;
  &RFC8174;
  &RFC8341;
  &RFC8639;
  &RFC8791;
  &RFC9196;
  &I-D.ietf-netconf-notif-envelope;
  &I-D.ietf-netconf-yang-push-2;
  </references>
  <references title="Informative References">
  &RFC7951;
  &RFC8641;
  &I-D.dikshit-nmop-telemetry-identifier-scoping;
  &I-D.dikshit-netmod-comparability-scope-extension;
  <reference anchor="Kulkarni2014">
    <front>
    <title>Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases</title>
    <author initials="S." surname="Kulkarni"/>
    <author initials="M." surname="Demirbas"/>
    <author initials="D." surname="Madappa"/>
    <author initials="B." surname="Avva"/>
    <author initials="M." surname="Leone"/>
    <date year="2014"/>
    </front>
  </reference>
  <reference anchor="Fidge1988">
    <front>
    <title>Timestamps in Message-Passing Systems That Preserve the Partial Ordering</title>
    <author initials="C." surname="Fidge"/>
    <date year="1988"/>
    </front>
  </reference>
  <reference anchor="Mattern1989">
    <front>
    <title>Virtual Time and Global States of Distributed Systems</title>
    <author initials="F." surname="Mattern"/>
    <date year="1989"/>
    </front>
  </reference>
  </references>

  <section title="Alternative Approaches Considered" anchor="app-a"><t>
  Several primitives can order notifications across publishers. The table
  summarizes the trade-offs; n is the number of publishers in a
  Comparability Scope.</t>

  <figure><artwork><![CDATA[
 Approach                 State     Cross-pub order    Clock dep.
 ----------------------   -------   ----------------   ----------
 Per-publisher counter    O(1)      none               none
 (YANG-Push)
 Vector clock             O(n)      exact causality    none
 Hybrid Logical Clock     O(1)      total, within      loose sync
                                    clock offset
 Causal-Epoch +           O(1)/ep   partial, within    none
 Local-Seq (this doc)               a scope
]]></artwork>
  </figure>

  <t>
  The per-publisher counter is kept for per-publisher loss detection. A
  vector clock <xref target="Fidge1988"/> <xref target="Mattern1989"/>
  gives exact causality, but its size grows with the number of
  publishers. A Hybrid Logical Clock <xref target="Kulkarni2014"/> is
  fixed in size but needs loosely synchronized clocks. The mechanism in
  this document keeps constant per-epoch state and needs no synchronized
  clocks, at the cost of ordering only within a Comparability Scope and
  only as fine as the Causal-Epoch hand-offs.</t>
  </section>

  <section title="Changes Between Revisions" anchor="app-b"><t>
  This section is to be removed before publishing as an RFC.</t>

  <t>
  From -01 to -02:</t>

  <t><list style="symbols">
  <t>Replaced the Hybrid Logical Clock proposal with an opt-in,
     coordination-free model using a Comparability Scope, a Causal-Epoch,
     and a per-publisher Local-Sequence-Number.</t>
  <t>Added a high-level architecture that keeps publishers lock-free on
     the fast path and moves bounded reordering to the collector
     (<xref target="sect-3"/>).</t>
  <t>Added the notification envelope metadata model and a wire-encoded
     JSON example (<xref target="sect-4"/>).</t>
  <t>Added the YANG module ietf-yang-push-causal-ordering, with the
     subscription opt-in, the envelope metadata, and the capability
     discovery of <xref target="RFC9196"/> (<xref target="sect-5"/>).</t>
  <t>Added Operational and Performance Considerations
     (<xref target="sect-6"/>).</t>
  <t>Changed the intended status to Standards Track and updated the
     Security and IANA Considerations.</t>
  <t>Moved the comparison of ordering primitives to
     <xref target="app-a"/>.</t>
  <t>Updated the author affiliation to Hewlett Packard Enterprise.</t>
  </list>
  </t>

  <t>
  From -00 to -01:</t>

  <t><list style="symbols">
  <t>Rebased on draft-ietf-netconf-yang-push-2, restated the problem
     around a hand-over example, and added the comparison of ordering
     primitives.</t>
  </list>
  </t>
  </section>
  </back>
  </rfc>
