Following are notes for the discussion of NANC 294 (LNPA Working Group mtg,
Tue afternoon, 11/9), surrounding any implications of "the wireless time
portion" of the due date. As we discussed in KC, wireline providers have a
gentleman's agreement in place to send up all zeros (00:00:00) in the time
portion of the due date timestamp field relating to the port of an SV. In
the wireless world, porting will occur on a more granular level (i.e., at a
specific time on the due date), because wireless providers want the ability
to port numbers within a two-hour interval.

The current proposal on the table for NANC 294 is to allow an SP to do
emergency same day porting in their local time zone, when the NPAC SMS has
already rolled over to the next day (because of the 4-10 hour differential
in GMT and an SP's local time). A current work-around exists whereby the
two involved SPs agree to make the due date one day in the future, by either
sending up a future date (if no previous Create message was sent to the
NPAC), or modifying the current SV that contains the current date to a
future date (in order for the other SP to concur). Once the SV has been
created and concurred with a due date of the next day, the new SP can
activate the SV (since the NPAC has already rolled over to the next day,
which is then considered the current day, and therefore allows the activate
to take place).

This change order would allow an SP to send up a "back-dated" due date (one
day less than the NPAC's current date), within a tunable window period of
time. From the SP's perspective this is still the current date, since their
local time is behind GMT. The tunable would be based on hours and would be
set to the left-most time zone in that specific region. The NPAC may
require two tunables per region to account for both standard and daylight
time, however, this is more an implementation detail.

As an example of the functionality with this change order, an SP needs to do
an emergency port of a customer in New York (Northeast region) on 11/1/99.
The current time in NY is 8:15p. The NPAC has already rolled over to the
next day (11/2/99), but the SP is still on the previous day (11/1/99). The
SP would send the Create message with their current date (11/1/99). The
NPAC would receive this message, and validate the due date. The tunable for
standard time is set to 5 hours. Since it is within the tunable period of
time of the next day on the NPAC (current NPAC time is 01:15 on 11/2/99),
the Create message is accepted as valid (even though the due date has been
back-dated). In order to accommodate wireline providers, the NPAC will
allow a due date of 11/1/99 and a time of 00:00:00 on the Create message.
It should be noted that the NPAC will still validate the time (e.g.,
00:00:00) in the two Create messages match, but will not use the time
portion of the due date when determining if a "back-dated" due date is
within the allowable tunable period of time.

This change order does NOT hinder emergency same day WIRELESS porting.
Since the NPAC is only using the tunable to determine if a back-dated due
date is acceptable, the time portion of the due date timestamp is unaffected
by this change order. In the above example, assuming both SPs were
wireless, the Create message being sent to the NPAC would most likely
contain 11/1/99 and a time of 22:15:00 (10:15p), since the general porting
interval is two hours. Once that time has arrived locally for the SP, an
activate can be sent up to the NPAC (and would be accepted).

In summary, NANC 294 is outside of the functionality of the time portion of
the due date for wireless porting, and therefore the scope of this change
order affects both wireline and wireless porting in the same fashion, and
does not affect one more than the other.