NANC 344

Doc Only Change Order for GDMO: Update GDMO to more clearly explain information in range notifications.

Origination Date :11/01/2002

Originator:AT&T

Description:

Update the text in section 14.0 Subscriptions Managed Object Class.

The text for subscriptionVersionRangeStatusAttributeValueChange and subscriptionVersionRangeAttributeValueChange notifications currently reads:

When this package is sent, it will include one set of information for the TN range, plus a list of Subscription Version IDs. If the feature data does not apply to all TNs in the original range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN range, and will be sent in separate messages.

Change to read:

When this package is sent, it will include one set of information for the TN range. If the SVIDs are sequential for the TNs then an SVID range will be included. If the SVIDs are not sequential then a paired list of SVIDs and TNs will be sent . If the feature data does not apply to all TNs in the original range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN range, and will be sent in separate messages.

The text for

subscriptionVersionRangeObjectCreation, subscriptionVersionRangeDonorSP-CustomerDisconnectDate, subscriptionVersionRangeCancellationAcknowledge, subscriptionVersionRangeNewSP-CreateRequest, subscriptionVersionRangeOldSP-ConcurrenceRequest, subscriptionVersionRangeOldSP-FinalConcurrenceWindowExpiration, and subscriptionVersionRangeNewSP-FinalCreateWindowExpiration notifications currently reads:

When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations. If the feature data does not apply to all TNs in the original range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN range, and will be sent in separate messages.

Change to read:

When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential.  If the feature data does not apply to all TNs in the original range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN range, and will be sent in separate messages.

Implemented in IIS 3.2.0 and GDMO 3.2.0. 

Final Resolution:

Incorporate into next release of GDMO and IIS

12/12/01 – Reviewed at December 2001 LNPA WG meeting.  Service Providers to verify internally that this change order does not have an impact on their local systems. Leave in “open” status until January 2002 meeting.

01/09/02 – Move to ‘accepted’.

Implemented in IIS 3.2.0 and GDMO 3.2.0.

Related Release:

Implemented in IIS 3.2.0 and GDMO 3.2.0.

Status: Implemented