idnits 2.17.1 draft-ietf-enum-h323-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 245 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 8 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([2], [3]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2003) is 7621 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '2' on line 96 looks like a reference -- Missing reference section? '3' on line 130 looks like a reference -- Missing reference section? '5' on line 105 looks like a reference -- Missing reference section? '1' on line 113 looks like a reference -- Missing reference section? '4' on line 123 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ENUM O. Levin 3 Internet Draft RADVISION 4 Document: draft-ietf-enum-h323-01.txt 6 Expires: December 2003 June 2003 8 ENUM Service Registration for H.323 URL 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months and may be updated, replaced, or obsoleted by other documents 22 at any time. It is inappropriate to use Internet-Drafts as 23 reference material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Abstract 32 The H.323 specification [2] defines a means for building multimedia 33 communication services over an arbitrary Packet Based Network, 34 including the Internet. This document registers an ENUM service for 35 H.323 according to specifications and guidelines in RFC2916bis [3]. 37 O. Levin Expires: December 2003 1 39 ENUM Service Registration for H.323 URL 41 Table of Contents 43 1. INTRODUCTION..........................................................3 45 2. ENUM SERVICE REGISTRATION..............................................3 47 3. THE E2U+H323 ENUM SERVICE..............................................3 49 4. CONVENTIONS USED IN THIS DOCUMENT......................................3 51 5. SECURITY CONSIDERATIONS................................................4 53 6. IANA CONSIDERATIONS...................................................4 55 7. AUTHOR'S ADDRESSES.....................................................4 57 REFERENCES................................................................4 59 O. Levin Expires: December 2003 2 61 ENUM Service Registration for H.323 URL 63 1. Introduction 65 The H.323 specification [2] defines a means for building multimedia 66 communication services over an arbitrary Packet Based Network, 67 including the Internet. When H.323 is used in the context of the 68 Internet, it would be useful to take advantages of such services as 69 domain name system (DNS) and ENUM in order to help facilitate the 70 completion of multimedia calls. 72 This document registers an ENUM service for H.323 according to 73 specifications and guidelines in RFC2916bis [3]. 75 2. ENUM Service Registration 77 As defined in [3], the following is a template covering information 78 needed for the registration of the enumservice specified in this 79 document. 81 - Service Name: "E2U+H323" 82 - URI Scheme(s): "h323:" 83 - Functional Specification: see section "3. The E2U+H323 ENUM 84 Service" 85 - Security considerations: see section "5. Security Considerations" 86 - Intended usage: COMMON 87 - Author: Orit Levin 88 - Any other information that the author deems interesting: None 90 3. The E2U+H323 ENUM Service 92 This document defines the "E2U+H323" service to be used in the 93 "service" sub-field of the "enumservice" as defined in [3]. 95 The H.323 related ENUM record MUST be populated with a standard 96 H.323 URL as defined in [2]. This URL MAY include parameters 97 specifying the specific protocols and the transport means the H.323 98 entity supports. 100 The H.323 entity MUST fully comply with the procedures defined in 101 [3] for both record retrieval and processing by the DNS client. 103 If, as a result of the ENUM DNS lookup, an H.323 URL matching local 104 policies and capabilities is retrieved, the procedure defined in 105 section O.8.1 "Locating H.323 Destination" of [5] SHOULD be 106 performed. 108 4. Conventions used in this document 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 112 this document are to be interpreted as described in RFC-2119 [1]. 114 O. Levin Expires: December 2003 3 116 ENUM Service Registration for H.323 URL 118 5. Security Considerations 120 The h323-URL information, once populated in the DNS, effectively 121 becomes publicly accessible. The access to the H.323 destinations 122 (published using ENUM) can be secured by techniques and procedures 123 defined in H.235 [4] - the security framework for H.323. The 124 framework defines means for achieving integrity, authentication, 125 non-repudiation, encryption, etc. for H.323 calls. 127 6. IANA Considerations 129 This document registers the �E2U+H323� ENUM service according to 130 specifications and guidelines in RFC2916bis [3] and the definitions 131 in this document. 133 7. Author's Addresses 135 Orit Levin 136 RADVISION 137 266 Harristown Road Phone: +1-201-689-6330 138 Glen Rock, NJ USA Email: orit@radvision.com 140 References 142 1 RFC 2119 Bradner, S., "Key words for use in RFCs to Indicate 143 Requirement Levels", BCP 14, RFC 2119, March 1997. 144 2 "Packet-based multimedia communications systems", ITU-T 145 Recommendation H.323, 2003. 146 3 Faltstrom, P. and M. Mealling, "The E.164 to URI DDDS 147 Application", draft-ietf-enum-rfc2916bis-06 (under IESG review), 148 May 2003. 149 4 "Security and encryption for H-Series(H.323 and other H.245- 150 based) multimedia terminals", ITU-T Recommendation H.235, 2003. 151 5 "Usage of URLs and DNS", ITU-T Recommendation H.323 Annex O, 152 2003. 154 O. Levin Expires: December 2003 4