This tracks byte volume, rather than packet count, for the external, recursively-resolved, non-recursive-accounting bucket associated with this prefix. This lets an admin gauge actual bandwidth consumed by recursively-resolved traffic to this prefix specifically, which is useful when trying to determine how much of a link's load is attributable to indirectly-resolved routes versus directly-resolved ones. A sharp rise in this counter without a corresponding rise in the internal-bucket byte counter would indicate growth specifically in traffic requiring recursive route resolution to reach this prefix.