@@ -627,7 +627,7 @@ contain the following information about its OCM API:
627627* REQUIRED: enabled (boolean) - Whether the OCM service is enabled at
628628 this endpoint
629629* REQUIRED: apiVersion (string) - The OCM API version this endpoint
630- supports. Example : ` "1.4 .0"`
630+ supports. Example : ` "1.5 .0"`
631631* REQUIRED: endPoint (string) - The URI of the OCM API available at
632632 this endpoint. Example : ` "https://cloud.example.org/ocm"`
633633* OPTIONAL: provider (string) - A friendly branding name of this
@@ -2888,9 +2888,9 @@ The complete changelog is updated in the OCM-API GitHub repository.
28882888* Clarified that `created` bounds the lifetime of a captured
28892889 signature but does not by itself detect replay within that window
28902890 (see Section 7.2.2 of [RFC9421]).
2891- * `jwksUri` and `{tokenEndPoint}` transport: https remains mandatory,
2891+ * `jwksUri` and `{tokenEndPoint}` transport: HTTPS remains mandatory,
28922892 with the same HTTP fallback allowance for testing setups that the
2893- Discovery Process has; dropped the https -only schema pattern from
2893+ Discovery Process has; dropped the HTTPS -only schema pattern from
28942894 spec.yaml accordingly.
28952895* Appendix B now defers the missing-`jwksUri` case to [Decision to
28962896 Discard](#decision-to-discard) instead of stating a stronger
@@ -2907,6 +2907,9 @@ The complete changelog is updated in the OCM-API GitHub repository.
29072907 Notification") endpoint and payload, and adaptation of the IANA
29082908 registries. The core notifications have now been fully spelled
29092909 out, clarifying their scope.
2910+ * Introduced an `encryption` optional object in the Share Creation
2911+ Notification payload, and defined a corresponding Encryption Schemes
2912+ OCM IANA Registry.
29102913
29112914# # Version 06
29122915* Introduced IANA Registries for resource types, protocols, share
0 commit comments