[Enum] RFC 5067 on Infrastructure ENUM Requirements
rfc-editor@rfc-editor.org Tue, 20 November 2007 01:49 UTC
Return-path: <enum-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuIEv-0000p1-De; Mon, 19 Nov 2007 20:49:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuIEu-0000om-3S; Mon, 19 Nov 2007 20:49:24 -0500
Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuIEq-0002r0-MV; Mon, 19 Nov 2007 20:49:24 -0500
Received: by bosco.isi.edu (Postfix, from userid 70) id 59C99F5C4A; Mon, 19 Nov 2007 17:49:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20071120014920.59C99F5C4A@bosco.isi.edu>
Date: Mon, 19 Nov 2007 17:49:20 -0800
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: enum@ietf.org, rfc-editor@rfc-editor.org
Subject: [Enum] RFC 5067 on Infrastructure ENUM Requirements
X-BeenThere: enum@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enum Discussion List <enum.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:enum@ietf.org>
List-Help: <mailto:enum-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/enum>, <mailto:enum-request@ietf.org?subject=subscribe>
Errors-To: enum-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5067
Title: Infrastructure ENUM Requirements
Author: S. Lind, P. Pfautz
Status: Informational
Date: November 2007
Mailbox: sdlind@att.com,
ppfautz@att.com
Pages: 7
Characters: 14311
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-enum-infrastructure-enum-reqs-04.txt
URL: http://www.rfc-editor.org/rfc/rfc5067.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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum