This read-write INTEGER, which always reads back none(1), acts as a transaction control for the BFD admin template tables: writing initialize(2) loads the current operational values into the admin tables and discards any uncommitted edits (acting as both BEGIN- and ABORT-TRANSACTION), while writing commit(3) copies the admin table values into the operational BFD template tables (END-TRANSACTION). Admins use this two-step admin/operational model to stage multiple BFD timer changes and apply them atomically rather than one object at a time. For example, an admin would write initialize(2), edit several tnBfdAdminTemplate* values, then write commit(3) to push all the changes into effect together.