Carrier and user use of ENUM and DNS

RFC 5526 proposed an “Infrastructure ENUM” parallel to the e164.arpa namespace to allow “carriers to provision DNS records for telephone numbers independently of those provisioned by end users (number assignees)”[RFC 5526].

The need for such an infrastructure ENUM are described in RFC 5067. RFC 5527 describes how the infrastructure ENUM could be combined in the e164.arpa namespace.

For a discussion of the need for including the source SIP URI in an ENUM query see the Internet Draft: “Routing SIP Requests with ENUM” [Kaplan 2011].

Slide Notes

Livingood, P. Pfautz, and R. Stastny, “The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM”, Internet Request for Comments, RFC Editor, RFC 5526 (Informational), ISSN 2070-1721, April 2009 http://www.rfc-editor.org/rfc/rfc5526.txt Links to an external site.

M. Haberler, O. Lendl, and R. Stastny, “Combined User and Infrastructure ENUM in the arpa Tree”, Internet Request for Comments, RFC Editor, RFC 5527 (Informational), ISSN 2070-1721, May 2009 http://www.rfc-editor.org/rfc/rfc5527.txt Links to an external site.

S. Lind and P. Pfautz, “Infrastructure ENUM Requirements”, Internet Request for Comments, RFC Editor, RFC 5067 (Informational), ISSN 2070-1721, November 2007, http://www.rfc-editor.org/rfc/rfc5067.txt Links to an external site.

H. Kaplan, C. Pons, and P. Gorman, Routing SIP Requests with ENUM, IETF Network Working Group, Internet Draft, October 24, 2011, Expired: April 24, 2012, draft-kaplan-enum-sip-routing-04, http://tools.ietf.org/html/draft-kaplan-enum-sip-routing-04 Links to an external site.

Transcript

[slide232] There are a bunch of carriers that use iNum.