Telephone Number Mapping (ENUM) Service Registration for H.323
draft-ietf-enum-h323-01

ENUM                                                        O. Levin 
   Internet Draft                                             RADVISION 
   Document: draft-ietf-enum-h323-01.txt                                
                                                                        
   Expires: December 2003                                     June 2003 
    
    
                ENUM Service Registration for H.323 URL 
    
    
   Status of this Memo 
    
   This document is an Internet-Draft and is in full conformance with 
   all provisions of Section 10 of RFC2026. 
 
   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF), its areas, and its working groups.  Note that      
   other groups may also distribute working documents as Internet-
   Drafts. 
    
   Internet-Drafts are draft documents valid for a maximum of six 
   months and may be updated, replaced, or obsoleted by other documents 
   at any time.  It is inappropriate to use Internet-Drafts as 
   reference material or to cite them other than as "work in progress." 
    
   The list of current Internet-Drafts can be accessed at 
        http://www.ietf.org/ietf/1id-abstracts.txt 
   The list of Internet-Draft Shadow Directories can be accessed at 
        http://www.ietf.org/shadow.html. 
    
    
   Abstract 
    
   The H.323 specification [2] defines a means for building multimedia 
   communication services over an arbitrary Packet Based Network, 
   including the Internet. This document registers an ENUM service for 
   H.323 according to specifications and guidelines in RFC2916bis [3]. 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     
   O. Levin             Expires: December 2003                       1 

                  ENUM Service Registration for H.323 URL 

Table of Contents 
    
1.  INTRODUCTION..........................................................3 

2. ENUM SERVICE REGISTRATION..............................................3 

3. THE E2U+H323 ENUM SERVICE..............................................3 

4. CONVENTIONS USED IN THIS DOCUMENT......................................3 

5. SECURITY CONSIDERATIONS................................................4 

6.  IANA CONSIDERATIONS...................................................4 

7. AUTHOR'S ADDRESSES.....................................................4 

REFERENCES................................................................4 

     
   O. Levin             Expires: December 2003                       2 

                  ENUM Service Registration for H.323 URL 

1. Introduction 
    
   The H.323 specification [2] defines a means for building multimedia 
   communication services over an arbitrary Packet Based Network, 
   including the Internet. When H.323 is used in the context of the 
   Internet, it would be useful to take advantages of such services as 
   domain name system (DNS) and ENUM in order to help facilitate the 
   completion of multimedia calls. 
    
   This document registers an ENUM service for H.323 according to 
   specifications and guidelines in RFC2916bis [3]. 
    
2. ENUM Service Registration 
    
   As defined in [3], the following is a template covering information 
   needed for the registration of the enumservice specified in this 
   document. 
     
   -  Service Name: "E2U+H323"  
   -  URI Scheme(s): "h323:"  
   -  Functional Specification: see section "3. The E2U+H323 ENUM 
   Service" 
   -  Security considerations: see section "5. Security Considerations"  
   -  Intended usage: COMMON  
   -  Author: Orit Levin  
   -  Any other information that the author deems interesting: None 
     
3. The E2U+H323 ENUM Service 
    
   This document defines the "E2U+H323" service to be used in the 
   "service" sub-field of the "enumservice" as defined in [3]. 
    
   The H.323 related ENUM record MUST be populated with a standard 
   H.323 URL as defined in [2]. This URL MAY include parameters 
   specifying the specific protocols and the transport means the H.323 
   entity supports. 
    
   The H.323 entity MUST fully comply with the procedures defined in 
   [3] for both record retrieval and processing by the DNS client. 
    
   If, as a result of the ENUM DNS lookup, an H.323 URL matching local 
   policies and capabilities is retrieved, the procedure defined in 
   section O.8.1 "Locating H.323 Destination" of [5] SHOULD be 
   performed. 
    
4. Conventions used in this document 
    
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in 
   this document are to be interpreted as described in RFC-2119 [1]. 
    

     
   O. Levin             Expires: December 2003                       3 

                  ENUM Service Registration for H.323 URL 

5. Security Considerations 
 
   The h323-URL information, once populated in the DNS, effectively 
   becomes publicly accessible. The access to the H.323 destinations 
   (published using ENUM) can be secured by techniques and procedures 
   defined in H.235 [4] - the security framework for H.323. The 
   framework defines means for achieving integrity, authentication, 
   non-repudiation, encryption, etc. for H.323 calls. 
    
6. IANA Considerations 
 
   This document registers the ôE2U+H323ö ENUM service according to 
   specifications and guidelines in RFC2916bis [3] and the definitions 
   in this document. 
    
7. Author's Addresses 
    
   Orit Levin 
   RADVISION 
   266 Harristown Road          Phone:  +1-201-689-6330 
   Glen Rock, NJ USA            Email:  orit@radvision.com 
    
References 
    
   1  RFC 2119 Bradner, S., "Key words for use in RFCs to Indicate 
      Requirement Levels", BCP 14, RFC 2119, March 1997. 
   2  "Packet-based multimedia communications systems", ITU-T 
      Recommendation H.323, 2003. 
   3  Faltstrom, P. and M. Mealling, "The E.164 to URI DDDS 
      Application", draft-ietf-enum-rfc2916bis-06 (under IESG review), 
      May 2003. 
   4  "Security and encryption for H-Series(H.323 and other H.245-
      based) multimedia terminals", ITU-T Recommendation H.235, 2003. 
   5  "Usage of URLs and DNS", ITU-T Recommendation H.323 Annex O, 
      2003. 

     
   O. Levin             Expires: December 2003                       4