NANC 363

Lockheed-to-NeuStar private enterprise number: Change to NeuStar registration number.

Origination Date :06/14/2002

Originator:Neustar

Description:

Business Need:

The current ASN.1 uses the Lockheed Martin private enterprise number.  This needs to be changed to the NeuStar registration number, as was provided by IANA (Internet Assigned Number Authority).

The following three areas in the ASN.1 will be changed:

LNP-OIDS

  {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

  lockheedMartin(103) cis(7) npac(0) iis(0) oids(0)}

lnp-npac OBJECT IDENTIFIER ::=

  {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

  lockheedMartin(103) cis(7) npac(0)}

-- LNP General ASN.1 Definitions

LNP-ASN1

  {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

  lockheed(103) cis(7) npac(0) iis(0) asn1(1)}

Final Resolution:

Func Backwards Compatible:  NO

Change the current ASN.1 definition from lockheedMartin (103) to NeuStar (13568).

Jan ’03 LNPAWG, approved, move to accepted category.  Need to get SOA/LSMS vendor feedback during Feb ’03 LNPAWG meeting.

Feb ’03 LNPAWG, SOA/LSMS vendor feedback.  Colleen Collard (Tekelec), more than a recompile, but LOE is low.  Logistical implementation an issue since non-backwards compatible (for vendors with single platform and different regions with different implementation dates).  Need to consider efficiency of roll-out.  To alleviate this problem would need all regions upgraded at same time.  Burden will be somewhere for someone to support both (either NPAC or vendor side).  This change should be incorporated at the next regular release, and not during it’s own release.

NPAC LOE is TBD since NPAC may support both old and new number. Would set short sunset.

SOA/LSMS LOE is low/low.

Moved to Cancel-Pending status at December 06 LNPAWG meeting.

Related Release:

N/A

Status: Closed