Dear DNS Experts
For the E2MD (E.164 To MetaData) BoF during IETF-77 in Anheim we are
currently discussing the charter proposal. As e2md might have an impact on
DNS, we kindly ask you to review the charter and provide feedback to the
<e...@ietf.org> list by the end of this month (Feb 2010).
Looking forward to a fruitful discussion!
cheers,
Bernie
---------- Forwarded message ----------
Date: Wed, 24 Feb 2010 15:00:46
From: Bernie Hoeneisen <ber...@ietf.hoeneisen.ch>
To: E.164 To MetaData BOF discussion list <e...@ietf.org>
Subject: [e2md] charter discussion kick-off
Hi,
After we have collected the use cases, the e2md work continues with the
charter.
To ensure we have no (unknown) open issues with the charter during the BoF, we
kindly ask you to review the proposal for the e2md charter. The latest version
can be found on:
http://ucom.ch/ietf/e2md-bof/e2md-proposed-charter.txt
For your convenience I attached the current version to this email.
Please send any feedback, issues and other comments concerning the proposed
e2md charter to <e...@ietf.org> by the end of this month (Feb 2010).
cheers,
Bernie
--
http://ucom.ch/
Tech Consulting for Internet Standardization
E.164 to MetaData (E2MD) (proposed charter)
------------------------
Last Modified: 2010-02-24
Additional information is available at tools.ietf.org/wg/e2md
[not yet in use]
Chair(s):
* TBA
Real-time Applications and Infrastructure Area Director(s):
* Robert Sparks <rjspa...@nostrum.com>
* Cullen Jennings <flu...@cisco.com>
Real-time Applications and Infrastructure Area Advisor:
* Cullen Jennings <flu...@cisco.com>
Mailing Lists:
General Discussion: e...@ietf.org
Listinfo: https://www.ietf.org/mailman/listinfo/e2md
To Subscribe: e2md-requ...@ietf.org
In Body: subscribe
Archive: http://www.ietf.org/mail-archive/web/e2md/index.html
Description of Working Group:
Abstract
E.164 to MetaData (E2MD) will use of the Domain Name System (DNS)
for resolving E.164 numbers into metadata to provide information
about E.164 numbers in cases where E.164 Number to URI Mapping
(ENUM) can not be used.
Background
ENUM provides an identifier mapping mechanism to map E.164 numbers
to Uniform Resource Identifiers (URIs) using the DNS.
Thus, ENUM can be used to look up the services associated with an
E.164 number. However, it is controversial whether or not the result
of an ENUM lookup should always be intended to establish a
communications session using the URI found in the corresponding
Naming Authority Pointer (NAPTR) DNS Resource Record (RR).
Problem Statement
Several proposals for Enumservice registrations do not fulfill the
above mentioned interpretation, which suggests that an ENUM lookup
should always be intended to result in a communications session.
These proposals are therefore virtually locked in the process.
Such proposals include (but are not limited to) Enumservices for
'cnam' to provide information about the calling party name,
'unused' to provide a hint that a number is not in use, and
'send-n' to describe the structure of an ENUM tree.
Another issue is that the result of an ENUM (E2U) lookup always
needs to be an URI, which unnecessarily complicates simple mappings.
The authors of such Enumservice proposals tried to circumvent the
issues by introducing the 'data' URI scheme or inventing completely
new URI schemes, with limited success however. The main objection
remained that an ENUM lookup should always result in a URI intended
to establish a communications session.
Proposal
The E2MD Working Group is chartered to develop a new Dynamic
Delegation Discovery System (DDDS) application E2MD, which can be
used with DNS NAPTR RRs for resolving E.164 numbers into metadata.
The resulting metadata can be used (for example) to provide hints
about properties of certain ENUM domains or to provide information
that can be used as attributes of an E.164 number.
E2MD will provide the means for services related to E.164 numbers
that do not fit into the concept of ENUM (E2U), and thus a
way forward for such existing ENUM WG documents in the queue.
Along with the E2MD DDDS application a new IANA registry will be
specified for registration of E2MD services. The registration policy
shall be Expert Review and Specification Required (see RFC 5226),
similarly as specified for Enumservice registrations.
The E2MD specifications shall reuse a much as possible from the ENUM
DDDS and its IANA registry specification.
The E2MD Working Group may take on further proposals for E2MD service
registrations (e.g. send-n) until the IANA registration for E2MD
services is approved by the IESG.
Out-Of-Scope
E2MD shall not be specified as a general purpose lookup nor as bulk
transfer protocol, but rather focus on clear use cases related to
E.164 numbers.
Goals and Milestones:
Aug 2010 Submit Internet Draft(s) for the E2MD DDDS application and
its IANA registry specification
Dec 2010 Submit 'cnam' and 'unused' as E2MD service registrations
(Informational)
XXX 2011 Close the E2MD Working Group (or recharter)
Internet-Drafts:
http://tools.ietf.org/html/draft-hoeneisen-e164-to-metadata-02
http://tools.ietf.org/html/draft-ietf-enum-unused-04
http://tools.ietf.org/html/draft-ietf-enum-cnam-08
(http://tools.ietf.org/html/draft-bellis-enum-send-n-02)
Request For Comments:
None
_______________________________________________
e2md mailing list
e...@ietf.org
https://www.ietf.org/mailman/listinfo/e2md
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
