Infrastructure ENUM Requirements
RFC 5067

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: IETF-Announce <>
Cc: Internet Architecture Board <>,
    RFC Editor <>, 
    enum mailing list <>, 
    enum chair <>
Subject: Document Action: 'Infrastructure ENUM Requirements' to 
         Informational RFC 

The IESG has approved the following document:

- 'Infrastructure ENUM Requirements '
   <draft-ietf-enum-infrastructure-enum-reqs-05.txt> as an Informational RFC

This document is the product of the Telephone Number Mapping Working 

The IESG contact persons are Jon Peterson and Cullen Jennings.

A URL of this Internet-Draft is:

Technical Summary
This document provides requirements for "infrastructure" or "carrier" ENUM
(E.164 Number Mapping), defined as the use of RFC 3761 technology to
facilitate interconnection of networks for E.164 number addressed
services, in particular but not restricted to VoIP. Because end user ENUM
as defined in RFC 3761 requires end user opt-in and control of the
location of the NAPTRs, it is not suitable for interconnection needs bu
service providers. The requirements in the document are needed for the WG
to develop a technical solution.
Working Group Summary
The working group reviewed this document in 2005-6 and was document NIT
review preformed by Alexander Mayrhofer <>
Protocol Quality
This document was reviewed for the IESG by Jon Peterson. Gen-ART review
was performed by Gonzalo Camarillo.