Adding release note for TELCODOCS-1862 REST API v2

Author: aireilly

release_notes/ocp-4-17-release-notes.adoc

@@ -438,6 +438,24 @@ Starting in {product-title} 4.14, Extended Update Support (EUS) is extended to t
 [id="ocp-4-17-networking_{context}"]
 === Networking
 
+
+==== New PTP fast events REST API v2 available
+
+A new PTP fast events O-RAN v3 compliant REST API v2 is available.
+Now, you can develop PTP event consumer applications that receive host hardware PTP events directly from the PTP Operator managed pod via REST API.
+The PTP fast events REST API v1 will be deprecated in a future release.
+
+[NOTE]
+====
+In the link:https://orandownloadsweb.azurewebsites.net/download?id=344[_O-RAN O-Cloud Notification API Specification for Event Consumers 3.0_] specification, the resource is defined as a hierarchical path for the subsystem that will produce the notifications.
+This implies that a subscription to a higher hierarchy path includes subscriptions for all lower hierarchy resources contained in the path.
+
+The PTP events REST API v2 does not support a global events subscription endpoint.
+You subscribe consumer applications to the various available event types separately.
+====
+
+For more information, see xref:../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#ptp-cloud-events-consumer-dev-reference-v2[Developing PTP event consumer applications with the REST API v2].
+
 [id="ocp-4-17-registry"]
 === Registry
 
@@ -945,11 +963,11 @@ BMER was deprecated in {product-title} version 4.15 and 4.16. With this release,
 [id="ocp-4-17-image-registry-bug-fixes_{context}"]
 ==== Image Registry
 
-* In {product-title} 4.14, installing a cluster with Azure AD Workload Identity was made generally available. With that feature, administrators can configure a Microsoft Azure cluster to use Azure AD Workload Identity. With Azure AD Workload Identity, cluster components use temporary security credentials that are managed outside of the cluster. 
+* In {product-title} 4.14, installing a cluster with Azure AD Workload Identity was made generally available. With that feature, administrators can configure a Microsoft Azure cluster to use Azure AD Workload Identity. With Azure AD Workload Identity, cluster components use temporary security credentials that are managed outside of the cluster.
 +
 Previously, when {product-title} was deployed on Azure clusters with Azure AD Workload Identity, storage accounts created for the cluster and the image registry had *Storage Account Key Access* enabled by default, which could pose security risks to the deployment.
 +
-With this update, shared access keys are disabled by default on new installations that use Azure AD Workload Identity, enhancing security by preventing the use of shared access keys. 
+With this update, shared access keys are disabled by default on new installations that use Azure AD Workload Identity, enhancing security by preventing the use of shared access keys.
 +
 [IMPORTANT]
 ====
@@ -1128,6 +1146,11 @@ In the following tables, features are marked with the following statuses:
 |General Availability
 |General Availability
 
+|PTP events REST API v2
+|Not Available
+|Not Available
+|General Availability
+
 |Configure the `br-ex` bridge needed by OVN-Kuberenetes using NMState
 |Not Available
 |Technology Preview