Re: [e2md] E2MD and Indirection -- a new problem statement
"Richard Shockey" <richard@shockey.us> Fri, 14 May 2010 17:34 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 4676B3A6BFD for <e2md@core3.amsl.com>; Fri, 14 May 2010 10:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.47
X-Spam-Level:
X-Spam-Status: No, score=-0.47 tagged_above=-999 required=5 tests=[AWL=-0.805, BAYES_50=0.001, 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 d83UMsEEbFOv for <e2md@core3.amsl.com>; Fri, 14 May 2010 10:34:16 -0700 (PDT)
Received: from oproxy2-pub.bluehost.com (oproxy2-pub.bluehost.com [67.222.39.60]) by core3.amsl.com (Postfix) with SMTP id E85583A68C3 for <e2md@ietf.org>; Fri, 14 May 2010 10:33:31 -0700 (PDT)
Received: (qmail 10545 invoked by uid 0); 14 May 2010 17:33:22 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 14 May 2010 17:33:22 -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=GgTtgtnDx/yvJSTo+0/64GzHZxfUzyzMfiwoPmpjouPEY6A1e4Byc1kkgCmTqHmAPNhIWEYQQejqN2rAG/aREcLOMaBcxyFoB30AJLzWnhvgdwTbsINC3ISTsxC72qV1;
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 1OCylG-0000Ma-HG; Fri, 14 May 2010 11:33:22 -0600
From: Richard Shockey <richard@shockey.us>
To: 'Dean Willis' <dean.willis@softarmor.com>, "'E.164 To MetaData BOF discussion list'" <e2md@ietf.org>
References: <4BED7940.20405@softarmor.com>
In-Reply-To: <4BED7940.20405@softarmor.com>
Date: Fri, 14 May 2010 13:33:16 -0400
Message-ID: <00aa01caf38b$89ffd910$9dff8b30$@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: Acrzg5M97ghUoucvR5a/pFhdlAk3zwABX9qw
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: 'IETF ENUM list' <enum@ietf.org>
Subject: Re: [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 17:34:16 -0000
DNS technology Dean !!! ..stop this "It's the DNS" thing. Its not about the DNS it never was. You are perpetuating the problem once again. If you note the ENUM charter we never ever used the word DNS. That was deliberate and calculated when I wrote it. Delete the word DNS from your text and it closer to the reality here. Now of course the solution is really the two variants of 3761 in deployment the public trees and the private closed ones. The use cases would reflect that matrix of options. Indirection is NOT needed in closed systems its simply interjects a redundant look up into the system that causes delay is session set up. Goal of the E2MD Work (see how much better it reads when you don't talk about the DNS :-) --------------------- An easily extensible framework for using the DNS to discover data that is related to an E.164 number. The framework's organizational model is expected to be based as closely as possible on the existing ENUM [RFC 3761 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, and in other cases to store a reference to the data, 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 query for framework data associated with an E.164 number is expected to return all such data and data. The framework's query mechanism will make no considerations for authentication, authorization, or selective response based on the identity of the querying node. Further, the framework's mechanism is expected to make no considerations for network congestion, reliability, integrity, privacy, or overly-large response sets. 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 , 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. -----Original Message----- From: e2md-bounces@ietf.org [mailto:e2md-bounces@ietf.org] On Behalf Of Dean Willis Sent: Friday, May 14, 2010 12:25 PM To: E.164 To MetaData BOF discussion list Subject: [e2md] E2MD and Indirection -- a new problem statement 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 mailing list e2md@ietf.org https://www.ietf.org/mailman/listinfo/e2md
- [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