From bernie@ietf.hoeneisen.ch Thu Feb 4 01:17:02 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 142543A6A91; Thu, 4 Feb 2010 01:17:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.255 X-Spam-Level: X-Spam-Status: No, score=-2.255 tagged_above=-999 required=5 tests=[AWL=0.344, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KROBdAa90J5U; Thu, 4 Feb 2010 01:17:01 -0800 (PST) Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id 1F9893A6A8F; Thu, 4 Feb 2010 01:17:00 -0800 (PST) Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from ) id 1NcxqK-0006i5-G5; Thu, 04 Feb 2010 10:17:44 +0100 Date: Thu, 4 Feb 2010 10:17:44 +0100 (CET) From: Bernie Hoeneisen X-X-Sender: bhoeneis@softronics.hoeneisen.ch To: IETF DISPATCH list , IETF ENUM list , dnsop@ietf.org, dnsext@ietf.org, EPP Provreg Message-ID: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false Subject: [Enum] BOF / New Mailing List E2MD (E.164 To MetaData) DDDS application X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2010 09:17:02 -0000 Dear DNS, ENUM and RAI experts, Please be informed that a new mailing list has been created for discussion related to a proposed DDDS application 'E.164 to MetaData' (E2MD). If you are interested in this topic, please subscribe to the new Mailing List via: https://www.ietf.org/mailman/listinfo/e2md E2MD is proposed to hold E.164-related information that does not fit the normal use cases for E2U. Known use cases include information that describes the structure of the E.164 numbering plan, and records which do not represent end-user communication URIs. A BOF about E2MD has been proposed for the upcoming IETF in Anaheim: http://trac.tools.ietf.org/bof/trac/#RAI Note: E2MD has been formerly known as E2M (a naming conflict with a legacy SIP WG item required a change of the acronym for this BOF) cheers, Bernie From richard@shockey.us Sat Feb 20 11:55:37 2010 Return-Path: X-Original-To: enum@core3.amsl.com Delivered-To: enum@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 662793A797A for ; Sat, 20 Feb 2010 11:55:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.378 X-Spam-Level: X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USr8Sv35wRCx for ; Sat, 20 Feb 2010 11:55:36 -0800 (PST) Received: from outbound-mail-359.bluehost.com (outbound-mail-359.bluehost.com [66.147.249.253]) by core3.amsl.com (Postfix) with SMTP id 527C53A7656 for ; Sat, 20 Feb 2010 11:55:36 -0800 (PST) Received: (qmail 17903 invoked by uid 0); 20 Feb 2010 19:57:28 -0000 Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy1.bluehost.com.bluehost.com with SMTP; 20 Feb 2010 19:57:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=nD7MrP0TWAWrzWqbVPcorbocM4cbVLnp7GlK8ZMCJL2Sz40VHtoPyTUt7nDtbDFxSEFCNTyzpsopN/U7Uo+SVk8DcJckmtqvR5mnaIZbrNrAglaKMkARyEB2klNkgAZ1; Received: from pool-96-241-62-33.washdc.fios.verizon.net ([96.241.62.33] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from ) id 1NivSB-0007tq-Ph; Sat, 20 Feb 2010 12:57:28 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" , "'E.164 To MetaData BOF discussion list'" References: In-Reply-To: Date: Sat, 20 Feb 2010 14:57:24 -0500 Message-ID: <003c01cab266$ec61c840$c52558c0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcqyTSgwGF/4l9DBSwa4B6TEfGzp+QAFhDuw Content-Language: en-us X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.241.62.33 authed with richard@shockey.us} Cc: drinks@ietf.org, enum@ietf.org Subject: Re: [Enum] [e2md] Summary of Use Cases X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Feb 2010 19:55:37 -0000 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: e2md-bounces@ietf.org [mailto:e2md-bounces@ietf.org] 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 e2md@ietf.org https://www.ietf.org/mailman/listinfo/e2md