Telephone Number Mapping (ENUM) Service Registration for H.323
updated by
- rfc-6118 — Update of Legacy IANA Registrations of Enumservices
Extracted elements (7)
If an H.323 URL matching local policies and capabilities is retrieved from the ENUM DNS lookup, the procedure defined in H.323 Annex O section O.8.1 'Locating H.323 Destination' SHOULD be performed.
The H.323 entity MUST fully comply with the procedures defined in RFC 3761 for both record retrieval and processing by the DNS client.
The H.323 related ENUM record MUST be populated with a standard H.323 URL as defined in ITU-T H.323.
The H.323 URL in the ENUM record MAY include parameters specifying the specific protocols and transport means the H.323 entity supports.
The 'E2U+H323' service is defined for use in the 'service' sub-field of the 'enumservice' as specified in RFC 3761, mapping E.164 telephone numbers to H.323 URLs.
Registers the 'E2U+H323' ENUM service with IANA, using the 'h323:' URI scheme, with intended usage COMMON, per RFC 3761 guidelines.
H.323 URL information published in DNS via ENUM becomes publicly accessible; security for H.323 destinations can be achieved using H.235, which provides integrity, authentication, non-repudiation, and encryption. Threats from ENUM's dependence on DNS and DNSSEC applicability are analyzed in RFC 3761.