Update the OPI security API to use CRUD operations and to use more non-implementation specific types. The v1 API messages were very specifc to a strongSwan implementation. This version updates the API to align with the more generic types from the IETF yang model described in RFC 9061.
Using an API version tag of v2alpha1 as the API is not backwards compatible with the v1 IPsec APIs.
Adpoting protobuf naming conventions for all messages and services.
BREAKING-CHANGE: Breaks compatiblity with the existing OPI security API definition.
artek-koltun
commented
2 weeks ago
Resolves issue #446 and #104
Update the OPI security API to use CRUD operations and to use more non-implementation specific types. The v1 API messages were very specifc to a strongSwan implementation. This version updates the API to align with the more generic types from the IETF yang model described in RFC 9061.
Using an API version tag of v2alpha1 as the API is not backwards compatible with the v1 IPsec APIs.
Adpoting protobuf naming conventions for all messages and services.
BREAKING-CHANGE: Breaks compatiblity with the existing OPI security API definition.