Infrastructure ENUM Requirements
RFC 5067, “Infrastructure ENUM Requirements”, is an Informational document published in November 2007 by S. Lind, P. Pfautz. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5067 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5066 Ethernet in the First Mile Copper Interfaces MIB
- RFC 5068 Email Submission Operations: Access and Accountability Requirements
- RFC 5065 Autonomous System Confederations for BGP
- RFC 5064 The Archived-At Message Header Field
- RFC 5070 The Incident Object Description Exchange Format
- RFC 5063 Extensions to GMPLS Resource Reservation Protocol Graceful Restart
- RFC 5071 Dynamic Host Configuration Protocol Options Used by PXELINUX
- RFC 5062 Security Attacks Found Against the Stream Control Transmission Protocol and Current Countermeasures