Re: [e2md] Doodle poll: Next Conf-Call on Requirements
Lawrence Conroy <lconroy@insensate.co.uk> Tue, 18 May 2010 22:52 UTC
Return-Path: <lconroy@insensate.co.uk>
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 D6EE83A69DB for <e2md@core3.amsl.com>; Tue, 18 May 2010 15:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.402
X-Spam-Level:
X-Spam-Status: No, score=0.402 tagged_above=-999 required=5 tests=[AWL=-0.839, BAYES_50=0.001, SARE_LWSHORTT=1.24]
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 YhG2yAdV8NU7 for <e2md@core3.amsl.com>; Tue, 18 May 2010 15:52:26 -0700 (PDT)
Received: from insensate.co.uk (ghost.insensate.co.uk [213.152.49.121]) by core3.amsl.com (Postfix) with ESMTP id 929963A6A08 for <e2md@ietf.org>; Tue, 18 May 2010 15:52:25 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 0C4E813B1EC; Tue, 18 May 2010 23:52:15 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="iso-8859-1"
From: Lawrence Conroy <lconroy@insensate.co.uk>
In-Reply-To: <alpine.DEB.2.00.1005182049100.7965@softronics.hoeneisen.ch>
Date: Tue, 18 May 2010 23:52:17 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB37DD33-DEBC-4FD0-80BC-EA9AACFE8494@insensate.co.uk>
References: <alpine.DEB.2.00.1005182049100.7965@softronics.hoeneisen.ch>
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-Mailer: Apple Mail (2.1078)
Cc: "E.164 To MetaData BOF discussion list" <e2md@ietf.org>
Subject: Re: [e2md] Doodle poll: Next Conf-Call on Requirements
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: Tue, 18 May 2010 22:52:27 -0000
Hi Bernie, folks, I am slightly confused. The Dean & Rich show does that :)p This looks rather like a Bait 'n' Switch deal. AFAICT, there is an idea to revive the ENUM WG and to work on *some* of the items in that. I agree++ with that -- ENUM Vivax! In fact, on list everyone has agreed with that and our friendly channeled demons don't seem to have raised a complaint yet :). For ENUM (as opposed to any other WG) ... First Step: I'd guess that revival could work on Send-N and Unused. [Assuming we can roll back some of the more arcane restrictions in section 1.2 of rfc3761bis and the bit moved into the second paragraph of the intro of section 2]. These **should** be short term work items. Even CNAM and SPID could be done in the existing ENUM WG as well, I suspect. Heck -- we have number portability already, so why not? Second step: In the past the IESG appear to have resisted URIs that do not act as "direct" session initiators to Internet services. I remember the protracted pain of pushing against that resistance (that initially included use of telephone numbers, video telephony service, and even SMS §-/ So ... ISTM that it might be useful to re-charter ENUM to extend its remit to either unwind these alleged but unwritten rules (or write them in stone so at last we know what the limits ARE). ----- SO ... what is the other stuff that you are asking for requirements, and some seem to be thinking of other RR types, use of other protocols, indirection, ... ? It sure isn't ENUM. I seem to have lost track. Clarification required. all the best, Lawrence On 18 May 2010, at 19:54, Bernie Hoeneisen wrote: > Hi, > > As decided at the last conf call, we will have a dedicated conf call on requirements / use cases. > > Please indicate your availabilities on Doodle: > > http://www.doodle.com/3hqunikiwxzkrez5 > > > Goals: > > * Get a common understanding on the set of requirements and use cases > we are going to address > > > Topics: > > * List of Requirements (draft version) > http://trac.tools.ietf.org/bof/e2md/trac/wiki/RequirementsList > > * Use Cases (under construction) > http://trac.tools.ietf.org/bof/e2md/trac/wiki/UseCases > > Note: No other topics are discussed during this call. > > Looking forward to you Doodle responses! > > cheers, > Bernie > _______________________________________________ > e2md mailing list > e2md@ietf.org > https://www.ietf.org/mailman/listinfo/e2md
- [e2md] Doodle poll: Next Conf-Call on Requirements Bernie Hoeneisen
- Re: [e2md] Doodle poll: Next Conf-Call on Require… Lawrence Conroy
- Re: [e2md] Doodle poll: Next Conf-Call on Require… Bernie Hoeneisen