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

Consider "Traffic Levels" #594

Open
stillwaxin opened this issue Nov 4, 2019 · 2 comments
Open

Consider "Traffic Levels" #594

stillwaxin opened this issue Nov 4, 2019 · 2 comments
Milestone

Comments

@stillwaxin
Copy link

@stillwaxin stillwaxin commented Nov 4, 2019

Consider whether the Traffic Levels value for a Network (api/net:"info_traffic") is useful or not. I believe that networks that really care about traffic levels would use a flow tool to really figure out what the traffic levels they actually have for a particular network. I would propose to remove this field entirely.

@grizz

This comment has been minimized.

Copy link
Member

@grizz grizz commented Nov 5, 2019

Removing the field from the API would mean we would need to release a PDB v3.

While I agree with you it's not terribly useful since it's not tied to actual information, having it there doesn't hurt much. Perhaps just noting more clearly that data is network provided?

@peeringdb/pc thoughts?

@shane-kerr

This comment has been minimized.

Copy link

@shane-kerr shane-kerr commented Nov 5, 2019

Agree that we should update documentation to be more clear about the lack of actual meaning.

Possibly we should start a list of things that we want to deprecate, and when it gets long enough decide that it is time for a new major version. Or such a list may already exist?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.