NANC 214

Conflict Functionality with Due Date = Today

Origination Date :04/24/1998



When a subscription version is created with a due date equal to the day it was created, regardless of the status of the T1 and T2 timers, per requirements RR5-42.1 through RR5-42.4, the old SP cannot put the subscription version into conflict after 12:00 on the day before the due date.  It has been suggested that the subscription version be allowed to be put into conflict prior to the expiration of the T2 timer.


A clarification made to the requirements that basically states  "The timeframe in which the Old SP would have the ability to put an SV into conflict, would be the greater of 12:00 noon the date before the due date OR the expiration of the T2 timer...".


In essence, a New SP that doesn't abide by the three day rule, doesn’t restrict the Old SP from setting to conflict; however, an Old SP that waits to respond to the new SP create until the due date would still have to contend with the expiration of the T2 timer (and may not be able to set to conflict).

The conflict restriction process is shown below, with comments to indicate the desired behavior of the requirements):


1.  NPAC SMS shall provide a Conflict Restriction Window that restricts an Old Service Provider from putting a Subscription Version into Conflict.
(New requirement.  This means that a Conflict Restriction Window exists, and this is when an Old SP is NOT allowed to put an SV into conflict.)


2.  RR5‑42.2  Conflict Subscription Version – Conflict Restriction Window, would remain the same.
NPAC SMS shall provide a Conflict Restriction Window Tunable which is defined as the time on the business day prior to the New Service Provider due date that a pending Subscription Version can no longer be placed into a conflict state by the old Service Provider.
(Current restriction requirement.  This means that the restriction tunable exists, which is a time of day value [e.g., 13:00], and defines the time of day, ON THE DAY PRIOR TO THE DUE DATE, that an Old SP is NOT allowed to put an SV into conflict.)

3.  NPAC SMS shall restrict a Subscription Version from being placed into Conflict by the Old Service Provider, when the Conflict Restriction Window Tunable Time is reached AND the Final Concurrence Timer (T2) has expired.
(New requirement.  This means that the restriction for placing an SV into conflict starts when BOTH the tunable time is reached [on the day prior to the due date] AND the Final Concurrence Timer [T2] has expired.)

Final Resolution:

It was noted that the old SP could issue a cancel.  This change order is seen as one that should be implemented prior to release 2 or earlier by some service providers.  GTE and Ameritech support implementation of this change order as soon as possible.


Service Providers should be prepared to finalize the proposed wording for RR5-42.1 through RR5-42.4 at the June T&O meeting in Denver.


During the August T&O meeting, it was agreed that the description for this change order is satisfactory.


There was a request to add a statement relating to a discrepancy between this change order and NANC 201.  Specifically, requirement #3 of NANC 214 shall supercede the "N/A" listed in the conflict restriction window for short timer default values in the table for NANC 201 that describes timer default values for each of the six applicable timers.


Moved to future release closed list, already submitted to LLCs, awaiting prioritization.


This is in Release 2 (SOW 9).

Related Release:


Status: Implemented