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.

Sign up for GitHub

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

Jump to bottom

We should distinguish the endpoints for history-based use-cases and real-time ones for topology and capacity #101

Open
Pierre-VF opened this issue Dec 12, 2023 · 0 comments
Open

We should distinguish the endpoints for history-based use-cases and real-time ones for topology and capacity #101

Pierre-VF opened this issue Dec 12, 2023 · 0 comments

Comments

@Pierre-VF
Copy link
Contributor

History-requiring use-cases are still unclear at the moment, while real-time ones drive the current spec.

We should maybe explicitly distinguish these in the spec, and make it clear that we're looking for specific use-cases that would motivate the collection and sharing of historical topology/capacity/availability (most likely around MRV and additionality)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Pierre-VF