Re: [Enum] draft-lewis-enum-enumservice-e212-00
Edward Lewis <Ed.Lewis@neustar.biz> Sun, 11 March 2007 13:08 UTC
Return-path: <enum-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQNmL-0006Wx-6i; Sun, 11 Mar 2007 09:08:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQNmK-0006Wn-MQ for enum@ietf.org; Sun, 11 Mar 2007 09:08:00 -0400
Received: from hlid.ogud.com ([66.92.146.160] helo=ogud.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQNmJ-0000fl-BY for enum@ietf.org; Sun, 11 Mar 2007 09:08:00 -0400
Received: from [192.168.1.100] (hlid.ogud.com [66.92.146.160]) by ogud.com (8.13.1/8.13.1) with ESMTP id l2BD7bY5092949; Sun, 11 Mar 2007 08:07:45 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06230903c219ae9a93ac@[192.168.1.100]>
In-Reply-To: <E9D14D48-443D-4A22-8310-F037FD14C453@cisco.com>
References: <E9D14D48-443D-4A22-8310-F037FD14C453@cisco.com>
Date: Sun, 11 Mar 2007 09:07:06 -0400
To: Cullen Jennings <fluffy@cisco.com>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [Enum] draft-lewis-enum-enumservice-e212-00
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: enum@ietf.org
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Errors-To: enum-bounces@ietf.org
At 15:51 -0800 3/10/07, Cullen Jennings wrote: >This draft is pretty hard to understand for someone that does not know what >212, mcc, mnc, MSIN, IMSI etc. I don't think folks will understand what it >is, what it is for, or why the IETF should work on it. I purposefully skimped on this. Part of the reason is that I didn't want to rewrite or copy what is in the ITU publication E.212. That document is short and to the point, clear enough for an IETF'er like me to read and understand in one sitting. (No need to wade though a sea of telephony terms.) I didn't want to put any "tutorial" material in a draft. As far as "why the IETF should work on it" that is something that can be improved in the next round. I plan to add a "use case" to show what the data is good for and also emphasize that this is a use of ENUM, which is an IETF problem domain. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Edward Lewis +1-571-434-5468 NeuStar Sarcasm doesn't scale. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum
- [Enum] draft-lewis-enum-enumservice-e212-00 Cullen Jennings
- Re: [Enum] draft-lewis-enum-enumservice-e212-00 Edward Lewis