1. IETF 64 – ENUM WG IANA Registration for an Enumservice Containing PSTN Signaling Information <draft-ietf-enum-pstn-00> 8 November Co-Authors: Jason Livingood Richard Shockey

2. History of This Enumservice I-D
“draft-livingood-shockey-enum-npd-00” was first presented at IETF 63 in Paris.
Formally adopted as a WG item at IETF 63.
Now renamed “draft-ietf-enum-pstn-00” for consideration at IETF 64.
IPTEL WG now working on a general IANA registry of TEL parameters.

3. Changes From Previous I-D
Changed Enumservice type from “npd” to “pstn.”
The data is more general than simply Number Portability Data, so PSTN is more appropriate.
Can add CNAM in the future IANA TEL registration
Goal single URI for PSTN parameters
Added SIP URIs:
As a URI type for the Enumservice.
In the examples section.
Added Section 3 on Distribution of Data.
Per WG feedback at IETF 63.
Records distributed on a private basis, not in e164.arpa.

4. Changes From Previous I-D
Added Section 4 on Record Conflict Resolution.
What to do if both an “on-net” and “off-net” ENUM NAPTR is found.
Added Section 7 on Implementation Recommendations
Feedback from DNS vendors regarding implementation / BCP.
Added Section 8 for an Example Call Process with E2U+PSTN.
Updated References:
Updated Yu draft I-D # from IPTEL WG.
Added reference to RFC 3261 (SIP).
Added reference to RFC 3764 (Enumservice registration for SIP AoRs).

5. Vendor Implementations of I-D
To become a standard, must have multiple working implementations.
Working with DNS vendors to gather feedback and develop test implementations:
NetNumber, Nominum, Incognito, UltraDNS
Working with PSTN data provider to test DNS integration:
NeuStar
</presentation>