NANC 404

Doc Only Change Order: GDMO

Origination Date :07/15/2005

Originator:Neustar

Description:

The current documentation needs to be updated:

1.  Object 19, subscriptionAudit.  The behavior incorrectly states an AVC is sent to the originator.  This text will be removed.

  subscriptionAuditBehavior BEHAVIOR

  DEFINED AS!

  When the subscriptionAuditStatus changes an attribute value change will be emitted to the audit requester

2.  Object 15, serviceProv.  The behavior does not list all applicable attributes.  The text in highlights will be added.

  subscriptionAuditBehavior BEHAVIOR

  DEFINED AS!

  All attributes in this object,

  except serviceProvID, serviceProvType,

  serviceProvDownloadReason, and

  npacCustomerAllowableFunctions can be

3.  Notif 24, applicationLevelHeartbeat.  The behavior does not mention the SP tunables.  The text in highlights will be added.

 applicationLevelHeartbeatBehavior BEHAVIOR

  DEFINED AS!

This notification implements a SOA or LSMS Application Level Heartbeat function.  With this functionality, for SOA/LSMSs that support this functionality, the NPAC SMS will send a periodic Heartbeat message when a quiet period between the SOA/LSMS and the NPAC SMS exceeds the tunable value.  If a SOA/LSMS fails to respond to the Heartbeat message within a timeout period, the association will be aborted by the NPAC SMS.

Optionally, this notification may also be implemented on the SOA or LSMS.  With this functionality, regardless of the setting of the SOA/LSMS support flag, the SOA/LSMS will may send a periodic Heartbeat message when a quiet period between the SOA/LSMS and the NPAC SMS exceeds the tunable value.  If the NPAC SMS fails to respond to the Heartbeat message within a timeout period, the association will be aborted by the SOA/LSMS.

4.  Action 1, lnpDownload, and Action 15, lnpNotificationRecovery.  The behavior does not mention the swim-more-data indicator.  The text in highlights will be added to both Actions.

An action ID is generated by the NPAC and is added in the SWIM response linked replies.  In cases where the last linked reply contains a status of swim-more-data, this indicates that there is more data of the requested type to recover, and the requesting SOA/LSMS should repeat the same action.  For each ACTION response, the requesting SOA/LSMS must respond back with the action ID in the next lnpDownload action.

Final Resolution:

Func Backwards Compatible:  YES

Correct the current documentation.

Implemented in GDMO 3.3.1.

Related Release:

Implemented in GDMO 3.3.1.

Status: Implemented