Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification needed on TAPI Streaming Use Case ST.02 #608

Open
kgkishore opened this issue Feb 4, 2025 · 2 comments
Open

Clarification needed on TAPI Streaming Use Case ST.02 #608

kgkishore opened this issue Feb 4, 2025 · 2 comments

Comments

@kgkishore
Copy link

**ST 0.2:**Discover supported and available streams, then select available streams

Query:
What are the expected streams to be supported or made available for this usecase? Should we have object specific streams made available to end-user? Is it necessary or can there be a single stream to publish all kinds of events?

@roshan-joyce-fujitsu
Copy link

As of now, my understanding is that it is left to the provider. Some texts from TR548 to this effect below:

page 21:

Image

page 25:

Image

@nigel-r-davis , please correct/add.

@nigel-r-davis
Copy link
Collaborator

Hi @kgkishore @roshan-joyce-fujitsu,

Thanks for the question, @kgkishore, @roshan-joyce-fujitsu has identified text in TR-548 that explains the intention. The approach to stream combinations has not been restricted. The assumption is that a client will identify which entities arrive through which streams and then will combine the flows appropriately to build the necessary structures in its repository. Streaming allows for trees to be build (as per YANG) but also allows a flatter more meshy structure to be built.

On a related point, clearly, as with any notification/streaming solution, there is an eventual consistency consideration. Information may be received where that information includes a reference to something that is not yet known. We can go into this in more detail on a call if relevant.

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants