54th IETF Meeting - Telephone Number Mapping WG (enum)
agenda@ietf.org Thu, 11 July 2002 16:50 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25112; Thu, 11 Jul 2002 12:50:16 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id MAA24596 for ietf-123-outbound.10@ietf.org; Thu, 11 Jul 2002 12:45:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id LAA23439 for <all-ietf@loki.ietf.org>; Thu, 11 Jul 2002 11:12:07 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20445 for <all-ietf>; Thu, 11 Jul 2002 11:11:12 -0400 (EDT)
Message-Id: <200207111511.LAA20445@ietf.org>
To: IETF-Announce:;
From: agenda@ietf.org
Subject: 54th IETF Meeting - Telephone Number Mapping WG (enum)
Date: Thu, 11 Jul 2002 11:11:12 -0400
Sender: dinaras@cnri.reston.va.us
Telephone Number Mapping WG (enum) Monday, July 15 at 1300-1500 ============================= CHAIRS: Patrik Faltstrom <paf@cisco.com> Richard Shockey <rich.shockey@neustar.biz> Mailing Lists: General Discussion:enum@ietf.org To Subscribe: enum-request@ietf.org In Body: subscribe Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/ AGENDA BASHING (5 min) Scribe Introduction \005 Jay Hilton 1. RFC2916bis -01 REV - Faltstrom/Mealing (45 Min) The goal here should be to give the document authors definitive direction on the draft so that it can begin to move forward with all deliberate speed. The 01 revision is in the ho pper so we should see it shortly. ############### 2. The ENUMSERVICE's documents 45 Min [Stastny/Conroy/Brandner] It should be clear from the list that these documents have generated the most discussion a nd I want the meeting in Yokohama to come to some reasonable consensus on the next steps f or these documents. I think there we are close to agreement on several points but we have several proposals o n what is the proper ABNF syntax to use and the exact terms and definitions to be used in describing the data elements. For instance it is still disagreement on URI scheme vs a more expanded 'protocol' element for the mandatory portion of the enumservice field. Presenters should be prepared to precisely define their proposals and the rationale for th em. Scenarios for ENUM and ENUM-like Systems http://www.ietf.org/internet-drafts/draft-stastny-enum-scenarios-00.txt Analysis of the Usage of ENUM and ENUM Services http://www.ietf.org/internet-drafts/draft-stastny-enum-services-analysis-00.txt Categorical enumservices http://www.ietf.org/internet-drafts/draft-brandner-enum-categorical-enumservices-00.txt ################ 3. The 'enum' URI 10 M http://www.ietf.org/internet-drafts/draft-brandner-enum-uri-00.txt OPTIONAL IF there is any time left The tel URI... http://www.ietf.org/internet-drafts/draft-brandner-tel-svc-00.txt