[e2md] E2MD and Indirection -- a new problem statement
Dean Willis <dean.willis@softarmor.com> Fri, 14 May 2010 16:25 UTC
Return-Path: <dean.willis@softarmor.com>
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 65E743A6B6C for <e2md@core3.amsl.com>; Fri, 14 May 2010 09:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.669
X-Spam-Level:
X-Spam-Status: No, score=-0.669 tagged_above=-999 required=5 tests=[AWL=-0.670, BAYES_50=0.001]
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 he87jSlhz6Cp for <e2md@core3.amsl.com>; Fri, 14 May 2010 09:25:32 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id EF1A23A6B27 for <e2md@ietf.org>; Fri, 14 May 2010 09:24:50 -0700 (PDT)
Received: from [192.168.2.109] (cpe-66-25-30-183.tx.res.rr.com [66.25.30.183]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o4EGOekb028932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <e2md@ietf.org>; Fri, 14 May 2010 11:24:41 -0500
Message-ID: <4BED7940.20405@softarmor.com>
Date: Fri, 14 May 2010 11:24:32 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [e2md] E2MD and Indirection -- a new 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 16:25:33 -0000
I've heard Ray and Richard say that indirection might be appropriate in some cases. If we're willing to factor that into the work, we might have an opportunity. If we amended our problem statement to say that we would analyze the initial use cases, determine which cases need to be "in the database" and which need to be indirectly referenced, show how to indirectly reference where needed, and provide guidance for future users on how to make this determination and provide future guidance on dereferencing, then I predict our problem statement would be MUCH more palatable to the opposition. Let's try a re-write of my proxy-shill version and see if it gets friendlier looking. This one's a bit rough, but it should convey the basics: Goal of the E2MD Work --------------------- An easily extensible framework for using the DNS to discover data that is related to an E.164 number also resolvable in the DNS. The framework's organizational model is expected to be based as closely as possible on the existing ENUM framework. The framework is expected to provide for a multiplicity of different data types and provide for a semantic definition of each data type as well as define its relationship with the aforementioned E.164 number. The framework is expected to provide for storing some data types directly in the DNS, and in other cases to store a reference to the data in the DNS, with that determination based on the nature of the data type and its use cases. The framework is NOT expected to provide a selective query mechanism; rather, a DNS query for framework data associated with an E.164 number is expected to return all such data and data references known by the DNS to the querying node. The framework's expected query mechanism is expected to be straight-up DNS, and as such will make no considerations for authentication, authorization, or selective response based on the identity of the querying node. Further, the framework's query mechanism is expected to make no considerations for network congestion, reliability, integrity, privacy, or overly-large response sets beyond the inherent mechanisms of the DNS. Where such considerations are significant, the framework is expected to provide guidance on the use of other protocols that will be used to retrieve the framework data referenced from the DNS, and such other protocols are expected to provide needed considerations for authentication, authorization, selective response based on the identity of the querying node, network congestion, reliability, integrity, privacy, and large responses. The framework is expected to provide for standardization and IANA registration of new data types without a requirement for IETF consensus on each new data type, using the existing ENUM service registration model.
- [e2md] E2MD and Indirection -- a new problem stat… Dean Willis
- Re: [e2md] E2MD and Indirection -- a new problem … Richard Shockey
- Re: [e2md] E2MD and Indirection -- a new problem … Dean Willis
- Re: [e2md] [Enum] E2MD and Indirection -- a new p… Tony Rutkowski
- Re: [e2md] [Enum] E2MD and Indirection -- a new p… bmanning