53rd IETF - Telephone Number Mapping WG (enum)

agenda@ietf.org Tue, 12 March 2002 21:07 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07419; Tue, 12 Mar 2002 16:07:51 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA07758 for ietf-123-outbound.10@ietf.org; Tue, 12 Mar 2002 16:05:02 -0500 (EST)
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 PAA16335 for <all-ietf@loki.ietf.org>; Tue, 12 Mar 2002 15:39:35 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06119 for <all-ietf>; Tue, 12 Mar 2002 15:39:32 -0500 (EST)
Message-Id: <200203122039.PAA06119@ietf.org>
To: IETF-Announce:;
From: agenda@ietf.org
Subject: 53rd IETF - Telephone Number Mapping WG (enum)
Date: Tue, 12 Mar 2002 15:39:32 -0500
Sender: dinaras@cnri.reston.va.us

Telephone Number Mapping WG (enum)

Wednesday, March 20 at 0900-1130
=================================

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  < applause >
.
NEW CHARTER REVIEW - Chair\022s (5 Min)

http://www.ietf.org/html.charters/enum-charter.html

Revised Milestones -

SERVICE FIELD DOCUMENTS  ( 1 Hour ??)

ENUM Service Descriptions
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-walter-ranalli-enum-service-01.txt

Issues:
General framework of the problem statement.
What is the goal if any of granularity in service registrations?
What services do we want to register and why?
Should registrations be 1 RFC per protocol?

The Use of ENUM by SIP
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-e164-01.txt

Issues:
Processing of 2 SIP service fields in one ENUM registration?
Order and Preference issues?
Is this a ENUM WG document? Coordination with SIPPING WG?

ENUM Service Resolution
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-zmolek-enum-pointer-00.txt

Issues:
What is this draft meant to do?
Direction on Presence only Service Field
Is Presence different from SIP ??

The ENUM TEL enumservice
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-brandner-enum-tel-00.txt

Issues:
Why?  Is this just for call forwarding or is there carrier specific issues in this ... aka
 LNP?
Is this a ENUM WG document?

CORE DOCUMENT REVIEW  (45 min ??)

2916bis Update -  The E.164 to URI DDDS Application
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-enum-rfc2916bis-00.txt

Issues:
Review of Goals and Objectives for Revision
Status of DDDS
Requirements for Service Registration ..Privacy?  Applicability Statement?

OTHER DOCUMENTS

Extensible Provisioning Protocol and E.164 (10 min +)
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-e164-02.txt

Issues:
Is this the direction the WG wants to go?
Possible transport options?
Tier 1 and or Tier 2 usages?
Relation to PROVREG

ENUM Call Flows (10 min)
draft-lind-enum-callflows-03.txt

Issues:
This document has been around a while but let us clarify what direction this is taking.
What is the goal and purpose of the document?
Is this an accurate picture of possible scenarios?
Should Call Flows descriptions be application specific and included in service registratio
n documentation?

DOCUMENTS OF NOTE [ NOT ON AGENDA ]

US ENUM Forum Overview
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-freilich-overview-enum-forum-00.txt

History and Context of ENUM Operational Decisions
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-iab-itu-enum-notes-00.txt

Should these documents be made Informaitonal RFC's

Number Portability in the PSTN
draft-ietf-enum-e164-gstn-np-03.txt

Issues:
Status to Last Call

OPEN DISCUSSION