Re: [e2md] Problem statement, Requirements and Use Cases

[Tony Rutkowski <[e-mail]>]

On 5/19/2010 12:45 PM, PFAUTZ, PENN L (ATTCORP) wrote:
> This is an area that will need more discussion which I hope will ensue,
> if not necessarily under e2md then in the IETF, ITU, i3 and national
> SDOs. At least some bodies are looking for a single integer (SPN), e.g.
> the value under the OID 1.3.6.1.4 arc, for AT&T 74. There have also been
> some requests to support hierarchy subtending an SPN.
>    

Agreed.

Another international carrier identifier choice is
ITU-ICCs pursuant to the M.1400 standard.  However,
their six alphanumeric character structure doesn't
scale, and the uptake has been minimal.

Almost every country has one or more national
identifiers for carriers, but those differ structurally
and are not global by definition.

Then there is the new NeuStar proposal for a five digit
number issued by either the ITU equivalent of IANA (the
TSB) or by national telephone managers like NeuStar.
However, these don't scale, would have significant
regulatory burdens and costs, and seem unlikely to be
accepted as a new global SPID.

OIDs on the other hand were created in the 1980s as a
universal, simple, extensible identifier for all
entities, explicitly including service providers.  They
are hierarchical and can be recursively resolved.  They
are widely used as SPIDs.  The assignment identity
proofing and maintenance leaves something to be
improved, but this is being addressed with the use of
X.509 or EVcerts or other assurance overlays.

Anyhow, those seem like the SPID alternatives.

--tony