NANC 294

Changing Due Date Edit Functionality in the NPAC SMS for 7PM on Due Date Problems

Origination Date :08/11/1999

Originator:LNPA WG


Service Providers involved in last minute emergency porting situations, cannot create/concur/activate SVs that are created after 7p (eastern standard time) on the due date.  Since those created after 7p EST, equate to after midnight GMT the next day on the NPAC SMS, the old SP cannot concur to the port, and the new SP cannot activate at this point in time since timers have not expired.


Sep LNPAWG (Chicago), after much discussion the group agreed that this problem exists for initial creates as well as concurs, if either one happens after 7p EST.


Option #1 from Portland is a huge effort, and does not resolve the issue (it just narrows the window).  Option #2 from Portland was deemed to be the best solution at this point.  However, the back-dating needs to be limited to ensure this functionality does not open the window for “pamming” (port slamming)


Oct LNPAWG (KC), the back-dating capability allows the SP (local side thinks it’s still the current date) to send a previous day’s date, even though the NPAC has already rolled to the next day.


This back-dating still allows an SP to send up yesterday’s date with zeros in the time portion.  This will accommodate SPs that always sends all zeros in SV create messages (even though this would be more than the 4-10 hour back-dating range).

Final Resolution:

Pure Backwards Compatible:  YES


Aug LNPAWG (Portland), the group talked about two options: 1.) change the NPAC SMS to run and store in central time; 2.) change the NPAC SMS edit to allow a concurrence in the past (i.e., back-dated concurrence).  It was noted that the first option still has a problem with ports in the western region, west coast region, and hawaii, albeit the problem window is smaller.  This will be discussed in more detail next month.


Sep LNPAWG (Chicago), using option #2, a new tunable (“Back-Dating Due Date Differential”) per region would only open the window for back-dating to the largest differential time zone in that region from the NPAC (i.e., from a map perspective, the left most time zone [“prevailing time zone”] in that specific region).  The time zone would be adjusted for standard/daylight, and the tunable would have a valid range of 4-10 hours (4 hours is EDT, 10 hours is Hawaiian standard time).


Oct LNPAWG (KC), the desired functionality may require two tunables per region (to account for both standard time and daylight time).


July 2001: Change Order moved into R3.1 package.


Implemented in FRS 3.1.0, IIS 3.1.0 and GDMO 3.1.0.

Related Release:


Status: Implemented