IETF Logo Mail Archive

Re: [e2md] Problem statement, Requirements and Use Cases (was RFC 5507 & RFC 5395)

Dean Willis <dean.willis@softarmor.com> Mon, 17 May 2010 21:38 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 B0CCF3A6B9E for <e2md@core3.amsl.com>; Mon, 17 May 2010 14:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.946
X-Spam-Level:
X-Spam-Status: No, score=-1.946 tagged_above=-999 required=5 tests=[AWL=0.653, 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 iw2S7Rhyb2Ij for <e2md@core3.amsl.com>; Mon, 17 May 2010 14:38:21 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 036A53A6B50 for <e2md@ietf.org>; Mon, 17 May 2010 14:38:17 -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 o4HLc4nZ029573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 17 May 2010 16:38:08 -0500
From: Dean Willis <dean.willis@softarmor.com>
To: "PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com>
In-Reply-To: <35FE871E2B085542A35726420E29DA6B03F959AB@gaalpa1msgusr7a.ugd.att.com>
References: <35FE871E2B085542A35726420E29DA6B03F95813@gaalpa1msgusr7a.ugd.att.com> <C8171AA9.52E5%ray.bellis@nominet.org.uk> <35FE871E2B085542A35726420E29DA6B03F959AB@gaalpa1msgusr7a.ugd.att.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 17 May 2010 16:37:57 -0500
Message-ID: <1274132277.2972.4.camel@damnableubu>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 7bit
Cc: "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Subject: Re: [e2md] Problem statement, Requirements and Use Cases (was RFC 5507 & RFC 5395)
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: Mon, 17 May 2010 21:38:22 -0000

On Mon, 2010-05-17 at 13:31 -0400, PFAUTZ, PENN L (ATTCORP) wrote:

> Please sirs, may we have an e2md WG that will analyze proposed use cases guided by RFC 5507 & RFC 5395 and propose appropriate implementations?


That probably would work. I think all we need to do is agree to analyze
the problem(s) and solve each appropriately while respecting the
"rules", rather than insisting on one-size-fits-all hack/slash on ENUM
to define a framework for adding arbitrary metadata into NAPTR records.

--
Dean

v2.23.0 | Report a Bug | By Email