Updated UAFX SKS Push Facet with the decisions from the attached Word doc.
Modified Profile reporting tool with the same changes.

Changes agreed to in the 9/2/22 AWG meeting

Reopened to add more details

The attached document describes several reasons why the initial definition of the UAFX SKS Push Facet was incoherent. The following decisions were made to correct this:

We tried to make SKS PubSub Key Management mandatory, but it relied on SecurityGroupType which was not pulled in due to PubSub Model SKS being optional. It was determined that exposing the key management interface was not necessary for an MVS.
DECISION: pubSub Key Management should be made optional.

The SecurityGroupType type does not need to be exposed, but the controller (on the SKS side) must have the implementation.
DECISION: The functionality of SecurityGroupType must be supported, but the type does not need to be exposed in the information model.
Decided in the 8/31/22 AWG meeting.

The team agreed that we did not want a controller to be forced to serve as general purpose SKS for the whole network. PubSub Model SKS Push was made mandatory in the facet, but that CU required support of the AddPushTarget and RemovePushTarget methods via support for PubSubPushTargetFolderType. Exposing these methods would effectively make controllers a general purpose SKS. We decided to write a new CU for UAFX without requiring support for PubSubPushTargetFolderType. That CU will say, "The SKS pushes security keys to targets by invoking the SetSecurityKeys Method on the target."
DECISION: We will create a new CU, make it mandatory, and make PubSub Model SKS Push optional.

The last issue in the attached issues document was determined to be a non-issue. The target side is adequately covered with PubSub Publisher SetSecurityKeys and PubSub Subscriber SetSecurityKeys.

Resolutions agreed in 9/7/22 AWG meeting.