Re: [e2md] Dean's Proxy-Shill Version of the Problem statement

"Richard Shockey" <richard@shockey.us> Fri, 14 May 2010 13:51 UTC

Return-Path: <richard@shockey.us>
X-Original-To: e2md@core3.amsl.com
Delivered-To: e2md@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 799413A68CF for <e2md@core3.amsl.com>; Fri, 14 May 2010 06:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.744
X-Spam-Level:
X-Spam-Status: No, score=-1.744 tagged_above=-999 required=5 tests=[AWL=0.521, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 VeJECmBYMmiA for <e2md@core3.amsl.com>; Fri, 14 May 2010 06:51:10 -0700 (PDT)
Received: from oproxy2-pub.bluehost.com (oproxy2-pub.bluehost.com [67.222.39.60]) by core3.amsl.com (Postfix) with SMTP id 45C0E3A6903 for <e2md@ietf.org>; Fri, 14 May 2010 06:51:10 -0700 (PDT)
Received: (qmail 14594 invoked by uid 0); 14 May 2010 13:51:01 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 14 May 2010 13:51:01 -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=RLwov4AL/XpPbkEgdzfV2om1SNsOiLJW//iL9Kj0tXtNLVkkFNc2NNanDJ6rA7Mild41RH8mYOo3tO4nJbI4vi3csIoQNgUFHSL3ao1iPxvc0P/3bm6jxpKYKJGJLzrO;
Received: from pool-96-231-199-72.washdc.fios.verizon.net ([96.231.199.72] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1OCvI4-0000XE-NG; Fri, 14 May 2010 07:51:01 -0600
From: Richard Shockey <richard@shockey.us>
To: 'Ray Bellis' <Ray.Bellis@nominet.org.uk>, 'Dean Willis' <dean.willis@softarmor.com>
References: <4BED0591.9070608@softarmor.com> <C812C78B.5214%ray.bellis@nominet.org.uk>
In-Reply-To: <C812C78B.5214%ray.bellis@nominet.org.uk>
Date: Fri, 14 May 2010 09:50:54 -0400
Message-ID: <006401caf36c$79b716a0$6d2543e0$@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: AQHK8sHDwrL8HcNm+EebiyZ93zdBepJPzxeAgAAUBoCAADL/AIAAad8AgAADtICAABTVgIAAWmPA
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 96.231.199.72 authed with richard@shockey.us}
Cc: "'E.164 To MetaData BOF discussion list'" <e2md@ietf.org>
Subject: Re: [e2md] Dean's Proxy-Shill Version of the Problem statement
X-BeenThere: e2md@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "E.164 To MetaData \(E2MD\) BOF discussion list" <e2md.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/e2md>
List-Post: <mailto:e2md@ietf.org>
List-Help: <mailto:e2md-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/e2md>, <mailto:e2md-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 13:51:11 -0000

CNAM is either way .. if the data is going to be used in a public DNS tree
yes there probably should be pointer that requires authentication. For all
the infrastructure EWNUM systems no..its just a look up function in a closed
trusted tree. 

-----Original Message-----
From: e2md-bounces@ietf.org [mailto:e2md-bounces@ietf.org] On Behalf Of Ray
Bellis
Sent: Friday, May 14, 2010 4:26 AM
To: Dean Willis
Cc: E.164 To MetaData BOF discussion list
Subject: Re: [e2md] Dean's Proxy-Shill Version of the Problem statement


> Just how far away from that approach would we be willing to explore?
> Might we, for example, consider a model where the data is held somewhere
> outside of ENUM, and ENUM just contains a pointer to the data?

That depends on the data.

For Send-N, absolutely not.  The data is trivially small, and getting it
returned as quickly as possible in response to a query for an incomplete
number is a specific design goal.

For the example given during the BOF of a record describing a ring tone,
absolutely!  That should clearly take the form of a *reference* to the
ring-tone data, and not the data itself.

For unused, maybe a hybrid approach - a small amount of data might be
necessary in the actual record (i.e. a "reason code", combined with a
reference to more detailed information).

Ray

_______________________________________________
e2md mailing list
e2md@ietf.org
https://www.ietf.org/mailman/listinfo/e2md