NANC 164

Duplicate NPA-NXX's and LRN's

Origination Date :09/25/1997

Originator:Perot

Description:

It was indicated that in some rare cases, there could be multiple owners of an NPA-NXX... (through sub-leasing etc).  The Perot implementation does not validate duplicate NPA-NXX’s.  The Lockheed implementation prevents this from happening due to port to original processing.

It has been requested that a clarifying statement be documented for both NPA-NXX and LRN duplication validation.

The following requirements should be added:

RR4-5  Duplicate NPA-NXX Validation

NPAC SMS shall validate upon request to add an NPA-NXX for a service provider that the NPA-NXX does not exist for any service provider in the region.

RR4-6  Duplicate NPA-NXX Validation – Error Processing

NPAC SMS shall upon finding that an NPA-NXX already exists for a service provider in a region will reject a request to add  NPA-NXX for a service provider and report an error to the user.

RR4-7  Duplicate LRN Validation

NPAC SMS shall validate that upon request to add an LRN added for a service provider that the LRN does not exist for any service provider in the region.

RR4-8  Duplicate LRN Validation – Error Processing

NPAC SMS shall upon finding that an LRN already exists for a service provider in a region will reject a request to add LRN for a service provider and report an error to the user.

Final Resolution:

Functionality stated for the vendors’ needs to be validated and desired behavior needs to be discussed.

Only one use of an NPA-NXX in a region is allowed. 

Only one LRN in a region is allowed. (LRN and NPA-NXX duplicates are not allowed.)

Lockheed does prevent duplicate LRN’s for a service provider. Perot does not.

Closed 11/7/97.

Related Release:

1.7

Status: Implemented