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

Invalid v1.0 format connection request #150

Open
sajith opened this issue Sep 5, 2024 · 0 comments · May be fixed by #149
Open

Invalid v1.0 format connection request #150

sajith opened this issue Sep 5, 2024 · 0 comments · May be fixed by #149
Assignees

Comments

@sajith
Copy link
Member

sajith commented Sep 5, 2024

This one is less useful because it (1) asks for a VLAN that is not present on the ingress port, and (2) asks for a range on the egress port while not asking for a matching range on the ingress port.

"endpoints": [
{
"port_id": "urn:sdx:port:amlight.net:A1:3",
"vlan": "777"
},
{
"port_id": "urn:sdx:port:zaoxi:B2:1",
"vlan": "55:90"
}

Note that the label range available on "urn:sdx:port:amlight.net:A1:3" is "100-200" and "1000":

"id": "urn:sdx:port:amlight.net:A1:3",
"label_range": [
"100-200",
"1000"
],

Service Provisioning Data Model 1.0 specification says this: "If one endpoint has the VLAN range or option “all”, all endpoints must have the same value."

@sajith sajith self-assigned this Sep 5, 2024
@sajith sajith linked a pull request Sep 13, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant