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

Inconsistencies in the spec #80

Closed
sfnuser opened this issue Jan 4, 2023 · 2 comments
Closed

Inconsistencies in the spec #80

sfnuser opened this issue Jan 4, 2023 · 2 comments

Comments

@sfnuser
Copy link
Collaborator

sfnuser commented Jan 4, 2023

In CreateSession, 400 error response the following example is provided.

                UePortsRequired:
                  summary: uePorts is required
                  value: 
                    code: INVALID_INPUT
                    message: "Expected property is missing: uePorts"

This meant to say that uePorts is a required param. However, the CreateSession definition mentiones uePorts as optional param.
Which one is correct?

Same way in the below example, it is mentioned port ranges are not allowed for uePorts. However, uePorts is of type PortSpec and there is no restriction on specifying ranges.

                UePortsRangesNotAllowed:
                  summary: Ranges at uePorts are not allowed
                  value: 
                    code: INVALID_INPUT
                    message: "Ranges not allowed: uePorts"

If these examples are not upto date, could we please remove them?

@hdamker
Copy link
Collaborator

hdamker commented Jan 4, 2023

@sfnuser yes, some of the error response examples are not consistent and make no sense within v0.8.0. We had some other examples during the review of the documentation (cf for example #71 (comment)). Luckily they are only examples and need not to be implemented. And yes, we should be more consistent here in the upcoming version.

If I'm not mistaken the two error responses you mentioned are both related to the initial thought that the uePort is needed if a public IPv4 address should to be resolved to identify an UE. In this case the uePort is needed in addition to the IPv4 address and it can't be a range. My current hope is that @eric-murray plans to clean up the error message examples in his planned PR for #34. It should then also be clearer in the spec what is expected from the API caller.

Beyond that: if an operator does not implement a certain parameter or option of the spec, the 501 code "Not Implement" might be more appropriate. As we want to use this error code I will open up a new issue to introduce it into the spec.

@hdamker
Copy link
Collaborator

hdamker commented Jan 28, 2023

Closed as discussed in call on Jan 27th.

@hdamker hdamker closed this as completed Jan 28, 2023
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

2 participants