NANC 147

Version ID Rollover Strategy

Origination Date :08/27/1997

Originator:AT&T

Description:

Business Need:

Currently there is no strategy defined for rollover if the maximum value for any of the id fields (sv id, lrn id, or npa-nxx id) is reached.  One should be defined so that the vendor implementations are in sync.  Currently the max value used by Lockheed is a 4 byte-signed integer and for Perot it is a 4 byte-unsigned integer.

Refer to the attached document for more detailed information:

Final Resolution:

Functional Backward Compatible:  YES

The NPAC SMS shall implement a strategy whereby the version ID is incremented until the maximum ([2**31] –1) is achieved, then start over at minus [2**31]), and use all available numbers at that point in time when a new version ID needs to be assigned (e.g., new SV-ID for a TN).

This affects Audit ID, Action ID, Subscription Version ID, LRN ID, NPA-NXX ID, NPA-NXX-X ID, and Number Pool Block ID.

Implemented in FRS 3.4.0a 3/19/10.

Implemented in IIS 3.4.0a 3/19/10.

Related Release:

Implemented in FRS 3.4.0a 3/19/10.

Implemented in IIS 3.4.0a 3/19/10.

Status: Implemented