Print
NANC 228
Maximum ID Value
Origination Date :08/10/1998
Originator:AT&T
Description:
With the increase in porting activity, AT&T feels that we need to start addressing the NPAC's maximum ID value for SVs, LRNs, NPA-NXXs, etc.
Final Resolution:
Discussed during 8/12/98 face-to-face T&O meeting (Detroit).
Jim stated that the NPAC allows a value up to 2(32) , which equates to 2.14B (signed 32-bit integer).
Sep LNPAWG (Seattle), the issue is that the NPAC (2.14B, signed 32-bit integer) and SPs (16M, un-signed 32-bit integer) that use version 1 of the DSET Toolkit have a different maximum value. At some point in time, this will become an issue, since the NPAC and the SP could be out of sync on the max value (so NPAC could send an ID that is greater than what a local SP can support).
This change order will update the IIS to state the current limitations, so that SP technical staff will be aware of this situation, and be able to plan accordingly.
Oct LNPAWG (Kansas City), it was requested that Jim and John get together to provide words for this. The proposed text is shown below.
In the IIS, section 2.3 and 2.4, the following text should be added as a new paragraph at the end of the section, prior to sub-sections 2.3.1 and 2.4.1.
"The NPAC SMS currently uses a 32-bit signed integer for the Naming ID Value. The maximum value is ([2**32] – 1) or 2.14B. It is anticipated that all Service Providers will be able to successfully handle Naming ID Values up to this maximum".
In the GDMO/ASN.1, it has been requested that the behavior state that the NPAC is using a 32-bit signed integer.
This will undergo approval during the Nov LNPAWG meeting.
Nov LNPAWG (Dallas), this has been approved by the group. This change order now moves to future release, and will be included in the next release of the documentation.
Mar LNPAWG (Denver), possibly put into section 5.2.1.7 (sequencing numbering is discussed), instead of 2.3 and 2.4. Leave up to CMA to determine best place for new paragraph.
Related Release:
2.0.1
Status: Implemented