idnits 2.17.1 draft-levin-enum-h323-00.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard 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 7 instances of too long lines in the document, the longest one being 4 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 (October 2002) is 7864 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 93 looks like a reference -- Missing reference section? '3' on line 125 looks like a reference -- Missing reference section? '5' on line 102 looks like a reference -- Missing reference section? '1' on line 110 looks like a reference -- Missing reference section? '4' on line 118 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft O. Levin 3 Document: draft-levin-enum-h323-00.txt RADVISION 5 Expires: April 2003 October 2002 7 ENUM Service Registration for H.323 URL 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance 12 with all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other documents 21 at any time. It is inappropriate to use Internet-Drafts as 22 reference material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 The H.323 specification [2] defines a means for building multimedia 32 communication services over an arbitrary Packet Based Network, 33 including the Internet. This document registers an ENUM service for 34 H.323 according to specifications and guidelines in RFC2916bis [3]. 36 ENUM Service Registration for H.323 URL 38 Table of Contents 40 STATUS OF THIS MEMO......................................................1 42 ABSTRACT...............................................................1 44 INTRODUCTION...........................................................3 46 ENUM SERVICE REGISTRATION.................................................3 48 THE E2U+H323 ENUM SERVICE..................................................3 50 CONVENTIONS USED IN THIS DOCUMENT..........................................3 52 SECURITY CONSIDERATIONS..................................................3 54 IANA CONSIDERATIONS......................................................4 56 AUTHOR'S ADDRESSES.......................................................4 58 REFERENCES.............................................................4 59 ENUM Service Registration for H.323 URL 61 Introduction 63 The H.323 specification [2] defines a means for building multimedia 64 communication services over an arbitrary Packet Based Network, 65 including the Internet. When H.323 is used in the context of the 66 Internet, it would be useful to take advantages of such services as 67 domain name system (DNS) and ENUM in order to help facilitate the 68 completion of multimedia calls. 70 This document registers an ENUM service for H.323 according to 71 specifications and guidelines in RFC2916bis [3]. 73 ENUM Service Registration 75 As defined in [3], the following is a template covering information 76 needed for the registration of the enumservice specified in this 77 document. 79 - Service Name: "E2U+H323" 80 - URI Scheme(s): "h323:" 81 - Functional Specification: see "The E2U+H323 ENUM Service" section 82 - Security considerations: see "Security Considerations" section 83 - Intended usage: COMMON 84 - Author: Orit Levin 85 - Any other information that the author deems interesting: None 87 The E2U+H323 ENUM Service 89 This document defines the "E2U+H323" service to be used in the 90 "service" sub-field of the "enumservice" as defined in [3]. 92 The H.323 related ENUM record MUST be populated with a standard 93 H.323 URL as defined in [2]. This URL MAY include parameters 94 specifying the specific protocols and the transport means the H.323 95 entity supports. 97 The H.323 entity MUST fully comply with the procedures defined in [3] 98 for both record retrieval and processing by the DNS client. 100 If, as a result of the ENUM DNS lookup, an H.323 URL matching local 101 policies and capabilities is retrieved, the procedure defined in 102 section "Address Resolution Procedure using DNS" of [5] SHOULD be 103 performed. 105 Conventions used in this document 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 109 this document are to be interpreted as described in RFC-2119 [1]. 111 Security Considerations 113 The h323-URL information, once populated in the DNS, effectively 114 becomes publicly accessible. The access to the H.323 destinations 115 ENUM Service Registration for H.323 URL 117 (published using ENUM) can be secured by techniques and procedures 118 defined in H.235 [4] - the security framework for H.323. The 119 framework defines means for achieving integrity, authentication, 120 non-repudiation, encryption, etc. for H.323 calls. 122 IANA Considerations 124 This document registers the "E2U+H323" ENUM service according to 125 specifications and guidelines in RFC2916bis [3] and the definitions 126 in this document. 128 Author's Addresses 130 Orit Levin 131 RADVISION 132 266 Harristown Road Phone: +1-201-689-6330 133 Glen Rock, NJ USA Email: orit@radvision.com 135 References 137 1 RFC 2119 Bradner, S., "Key words for use in RFCs to Indicate 138 Requirement Levels", BCP 14, RFC 2119, March 1997. 139 2 "Packet-based multimedia communications systems", ITU-T 140 Recommendation H.323, Nov 2000. 141 3 Faltstrom, P. and M. Mealling, "The E.164 to URI DDDS 142 Application", draft-ietf-enum-rfc2916bis-01 (work in progress), 143 June 2002. 144 4 "Security and encryption for H-Series(H.323 and other H.245- 145 based) multimedia terminals", ITU-T Recommendation H.235, Nov 146 2000. 147 5 "Use of DNS in H.323 Systems", ITU-T Recommendation H.323 Annex O 148 (work in progress).