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

[Tony Rutkowski <[e-mail]>]

On 5/19/2010 11:03 AM, PFAUTZ, PENN L (ATTCORP) wrote:
> Use RFC 3761 technology provide for the Carrier of Record for an E.164
> number (as defined in RFC 5067) to publish the mapping of
> that E.164 to a globally defined identifier, specifically an IANA
> Enterprise Number as defined in RFC 2578.
>    

Hi Penn,

Good choice.  However, the text needs tweaking to read:

   Use RFC 3761 technology to provide for the Carrier of
   Record for an E.164 number (as defined in RFC 5067) to
   publish the mapping of that E.164 number using an assigned
   Carrier of Record Object Identifier (OID)) such as an IANA
   Enterprise Number as defined in RFC 2578.  Ref. Rec.
   ITU-T Recs. X.660 and X.680.

The changes clarify what identifier is being specified and
includes reference to the authoritative OID standard.  It
also allows for the possibility of using other assigned OIDs
for a Carrier of Record.  Although more than 35,000 Enterprise
Numbers have been registered with IANA, there are many
carriers who have OIDs that were registered with national
authorities for Carrier of Record purposes.  As long as there
is a valid, globally unique OID, some flexibility should exist.

For example, ATT has the OID 1.3.6.1.4.74 from IANA's
OID block, but it also has 0.7.7223 that it uses for some
services in Argentina.

best,
tony