[netconf] draft-ietf-netconf-transaction-id-05

[Reshad Rahman <[e-mail]>]

Hi Jan,
Some basic questions on this document (apologies, I haven't followed recent discussions/changes). 
Very well-written and clear!
In the following paragraph in section 3.3, why use strings as opposed to monotonically increasing integers as in the example?
   In principle, txid values are opaque strings that uniquely identify a
   particular configuration state.  Servers are expected to know which
   txid values it has used in the recent past, and in which order they
   were assigned to configuration change transactions.  This information
   is known as the server's Txid History.

In the following paragraph in section 3.3, any consideration to having that number either configurable or retrievable from oper state?

   How many historical txid values to track is up to each server
   implementor to decide, and a server MAY decide not to store any
   historical txid values at all.  The more txid values in the server's
   Txid History, the more efficient the client synchronization may be,
   as described in the coming sections.
Section 3 nit: implememnting -> implementing
Section 6.1, 2 mechanisms are mentioned in the feature below, 1 is a MUST and the other MAY.How is support for the last-modified txid mechanism indicated?
     feature last-modified {
       description "Servers implementing this module MUST support the
         etag txid mechanism.  Servers MAY also support the
         last-modified txid mechanism.  Support is shown by announcing
         this feature.";
     }
Section 6.1, for etag-t, should there be a reference? Also, an explanation for what the special meaning of '?', '!' and '=' are, e.g a reference to last-modified-t?
Section 6.1 nit: should be "relative to the running datastore".               relative the running datastore, but not yet received

Regards,Reshad.