[rfc-dist] RFC 5067 on Infrastructure ENUM Requirements
rfc-editor at rfc-editor.org
Mon Nov 19 17:49:20 PST 2007
A new Request for Comments is now available in online RFC libraries.
Title: Infrastructure ENUM Requirements
Author: S. Lind, P. Pfautz
Date: November 2007
Mailbox: sdlind at att.com,
ppfautz at att.com
I-D Tag: draft-ietf-enum-infrastructure-enum-reqs-04.txt
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 (Voice
over IP.) This memo provides information for the Internet community.
This document is a product of the Telephone Number Mapping
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
IETF-Announce mailing list
IETF-Announce at ietf.org
More information about the rfc-dist