Re: [Netconf] subscription-id management across applications

Hi Rob,

Please see inline.

Tianran

From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Robert Wilton
Sent: Tuesday, July 10, 2018 12:49 AM
To: Andy Bierman <andy@yumaworks.com>; Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>; Netconf <netconf@ietf.org>
Subject: Re: [Netconf] subscription-id management across applications

On 09/07/2018 17:34, Andy Bierman wrote:

On Mon, Jul 9, 2018 at 9:31 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de<mailto:j.schoenwaelder@jacobs-university.de>> wrote:
On Mon, Jul 09, 2018 at 09:12:57AM -0700, Andy Bierman wrote:
> 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.

Why would a server accept a dynamic subscription that clashes with
a configured subscription?

I don't think it would.
The issue is how applications share the range allocated for configured subscriptions.
... which is the reason why I was arguing for string based ids for configured subscriptions.

Humans seemingly find it easier to give unique names to things instead of unique numbers.  And if they want to use the string representation of numbers as unique names, well that also works.

[Tianran] But I did not see how string can help solve the ID conflict for different applications. Do you mean string can have a larger ID space?
On the other hand, we can manage several ID blocks, and map the blocks to related applications for configured subscription.

Perhaps someone need to standardize the equivalent of DNS for subscription ids ;-)

[Tianran] This is a good idea, only a little heavy/complex. ☺

Thanks,
Rob

/js

Andy

--
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

_______________________________________________

Netconf mailing list

Netconf@ietf.org<mailto:Netconf@ietf.org>

https://www.ietf.org/mailman/listinfo/netconf