[Netconf] subscription-id management across applications

[Andy Bierman <[e-mail]>]

Hi,

The configured subscriptions use a uint32 subscription-id.
There is text in 5.2 about splitting the range for dynamic and configured
subscriptions:

   To support deployments including both configured and dynamic
   subscriptions, it is recommended to split subscription identifiers
   into static and dynamic halves.  That way it eliminates the
   possibility of collisions if the configured subscriptions attempt to
   set a subscription-id which might have already been dynamically
   allocated.  A best practice is to use lower half the "identifier"
   object's integer space when that "identifier" is assigned by an
   external entity (such as with a configured subscription).  This
   leaves the upper half of subscription identifiers available to be
   dynamically assigned by the publisher.


The draft does not say anything about how multiple independent applications
pick uint32 values that are not likely to collide with other applications.

Since configured subscriptions are expected to be usable by the client
the instant the NETCONF session is active, the app must be fairly sure
the hard-coded subscription-id values are really set correctly, and not
the IDs picked (and overwritten) by another application.


Andy