Subject: Re: [Enum] [e2md] Summary of Use Cases

From: "Richard Shockey" <[email-masked]>
Date: Sat, 20 Feb 2010 14:57:24 -0500

SPID and CNAM right now are the poster childs for E2M ..or SPN ( Service
Provider Network ) aka TN to Operator in modern ITU SG2 terms. DRINKS has a
liaison from ITU-T specifically asking that fields for this code be reserved
in any provisioning protocol developed by DRINKS. It's currently the
principal result of LUF in numerous private commercial ENUM applications
though it does not fully address the use case for MVNO's where some form
alt-SPID is required as well to distinguish between the retail service
provider and the underlying network operator.

In ENUM terms this means that the result of the LUF is not the end point
destination or transit network gateway but only the portability corrected
operator of record based on authoritative national numbering databases. The
data associated with the LRF is then presumed to be a private data exchange
between bilateral transit partners and is the result of the E2M translation
is performed by a secondary step.

All of these parameters are used in private closed carrier ENUM applications
for SMS MMS and Voice routing or in SIP location look ups, though how SIP
deals with metadata is IMHO a long standing issue and is another WG in and
of itself.

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of
Bernie Hoeneisen
Sent: Saturday, February 20, 2010 11:53 AM
To: E.164 To MetaData BOF discussion list
Subject: [e2md] Summary of Use Cases

Dear e2md list,

After soliciting input on market need evidence for e2md, I can
provide you with a list of use cases to be considered for e2md:

Legacy use cases:
- cnam
- unused/void
- send-n

Penn Pfautz
- information for routing decisions based on certain characteristics
   associated with a number

Kenneth Cartwright
- Payment Type:  PrePaid | PostPaid
- Network Type:  TDMA | GSM
- Region Code:  A numeric value indicating a region within a country.
- Service Provider Name:  The name of the current service provider.
- SPID:  A string of characters identifying the current service provider.

And some other thoughts that have crossed my mind
(for illustrative purposes only as I have not verified the usefulness of 
the following use cases):
- Charging information (useful for premium rate numbers)
- Assignee address information for premium rate numbers
   (abuse, complaints)
- Number Portability information (partly overlaps with Service
   Provider Name, SPID and an existing Enumservice)
- Service hours for a certain numbers
- Location Information
- PSAP (Public Safety Answering Point) associated with a fixed phone
   number (depending on the content this might be an ENUM use case instead)

These are 15 (potential) use cases!

Did I forget anything?
Please drop a note to this list, in case you know about more use cases.

Thanks a lot to those of you who answered my request!

cheers,
  Bernie
_______________________________________________
e2md mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/e2md