Network Working Group                                           O. Levin
Request for Comments: 3508                                     RADVISION
Category: Informational                                       April 2003
        
Network Working Group                                           O. Levin
Request for Comments: 3508                                     RADVISION
Category: Informational                                       April 2003
        

H.323 Uniform Resource Locator (URL) Scheme Registration

H.323统一资源定位器(URL)方案注册

Status of this Memo

本备忘录的状况

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2003). All Rights Reserved.

版权所有(C)互联网协会(2003年)。版权所有。

Abstract

摘要

ITU-T Recommendation H.323 version 4 introduced an H.323-specific Uniform Resource Locator (URL). This document reproduces the H323- URL definition found in H.323, and is published as an RFC for ease of access and registration with the Internet Assigned Numbers Authority (IANA).

ITU-T建议H.323第4版引入了特定于H.323的统一资源定位器(URL)。本文件复制了H.323中的H323-URL定义,并以RFC形式发布,以便于访问和向互联网分配号码管理局(IANA)注册。

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 BCP 14, RFC 2119 [2].

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[2]中的描述进行解释。

Table of Contents

目录

   1. Introduction...................................................2
   2. URL Scheme Formal Syntax Definition and Character Encoding.....2
   3. Intended Usage.................................................3
   4. Applications and/or protocols, which may use H.323 URL scheme..3
   5. Security Considerations........................................3
   6. IANA Considerations............................................4
   References........................................................4
   Acknowledgments...................................................5
   Author's Address..................................................5
   Full Copyright Statement..........................................6
        
   1. Introduction...................................................2
   2. URL Scheme Formal Syntax Definition and Character Encoding.....2
   3. Intended Usage.................................................3
   4. Applications and/or protocols, which may use H.323 URL scheme..3
   5. Security Considerations........................................3
   6. IANA Considerations............................................4
   References........................................................4
   Acknowledgments...................................................5
   Author's Address..................................................5
   Full Copyright Statement..........................................6
        
1. Introduction
1. 介绍

ITU-T Recommendations H.323 [3] and H.225.0 [4] define a system for multimedia communications services over packet based networks. H.225.0 [4] defines an alias type for carrying any standard Uniform Resource Locator (URL). H.323 version 4 [3] introduced an H.323- specific URL, which may be used to resolve the address of a network entity to which H.323 calls may be directed.

ITU-T建议H.323[3]和H.225.0[4]定义了基于分组网络的多媒体通信服务系统。H.225.0[4]定义了用于承载任何标准统一资源定位器(URL)的别名类型。H.323版本4[3]引入了一个特定于H.323的URL,该URL可用于解析H.323呼叫可能指向的网络实体的地址。

This document reproduces the H323-URL definition found in ITU-T recommendation H.323 [3] and is published as an RFC for ease of access and IANA registration.

本文件复制了ITU-T建议H.323[3]中的H323-URL定义,并作为RFC发布,以便于访问和IANA注册。

2. URL Scheme Formal Syntax Definition and Character Encoding
2. URL方案的形式化语法定义和字符编码

The H.323 URL is defined in ABNF as shown below. Note that it utilizes the Core Rules specified in section 6.1 of [2].

H.323URL在ABNF中定义,如下所示。请注意,它使用了[2]第6.1节中规定的核心规则。

   H323-URL    =   "h323:" address [ url-parameters ]
   address     =   user / "@" hostport / user "@" hostport
   user        =   1*(%x21-24 / %x26-3F / %x41-7F / escaped)
                        ; The symbols "%", "@", and symbols with
                        ; a character value below 0x21 may be
                        ; represented as escaped sequences.
   hostport    =   host [ ":" port]
   host        =   hostname / IPv4address / IPv6reference
   hostname    =   *( domainlabel "." ) toplabel [ "." ]
   domainlabel =   alphanum / alphanum *( alphanum / "-" ) alphanum
   toplabel    =   ALPHA / ALPHA *( alphanum / "-" ) alphanum
   IPv4address =   1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT
   IPv6reference   =  "[" IPv6address "]"
   IPV6address =   hexpart [ ":" IPv4address ]
   hexpart     =   hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ]
   hexseq      =   hex4 *( ":" hex4 )
   hex4        =   1*4HEXDIG
   port        =   1*DIGIT
   url-parameters  =   *( ";" url-parameter )
   url-parameter   =   1*(%x21-24 / %x26-3A / %x3C-7F / escaped)
                          ; Specific parameter definitions are for
                          ; further study.
                          ; The symbols "%", ";", and symbols
                          ; with a character value below 0x21 may be
                          ; represented as escaped sequences.
   alphanum    =   ALPHA / DIGIT
   escaped     =   "%" HEXDIG HEXDIG
        
   H323-URL    =   "h323:" address [ url-parameters ]
   address     =   user / "@" hostport / user "@" hostport
   user        =   1*(%x21-24 / %x26-3F / %x41-7F / escaped)
                        ; The symbols "%", "@", and symbols with
                        ; a character value below 0x21 may be
                        ; represented as escaped sequences.
   hostport    =   host [ ":" port]
   host        =   hostname / IPv4address / IPv6reference
   hostname    =   *( domainlabel "." ) toplabel [ "." ]
   domainlabel =   alphanum / alphanum *( alphanum / "-" ) alphanum
   toplabel    =   ALPHA / ALPHA *( alphanum / "-" ) alphanum
   IPv4address =   1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT
   IPv6reference   =  "[" IPv6address "]"
   IPV6address =   hexpart [ ":" IPv4address ]
   hexpart     =   hexseq / hexseq "::" [ hexseq ] / "::" [ hexseq ]
   hexseq      =   hex4 *( ":" hex4 )
   hex4        =   1*4HEXDIG
   port        =   1*DIGIT
   url-parameters  =   *( ";" url-parameter )
   url-parameter   =   1*(%x21-24 / %x26-3A / %x3C-7F / escaped)
                          ; Specific parameter definitions are for
                          ; further study.
                          ; The symbols "%", ";", and symbols
                          ; with a character value below 0x21 may be
                          ; represented as escaped sequences.
   alphanum    =   ALPHA / DIGIT
   escaped     =   "%" HEXDIG HEXDIG
        

The host is case insensitive.

主机不区分大小写。

The "user" is a Unicode [8] string that shall be UTF-8 [7] encoded and then escaped as necessary. In the "user" field, the characters with a numeric value below 0x80 are case insensitive and the characters with a numeric value above or equal to 0x80 are case sensitive.

“用户”是一个Unicode[8]字符串,应进行UTF-8[7]编码,然后根据需要转义。在“用户”字段中,数值低于0x80的字符不区分大小写,数值高于或等于0x80的字符区分大小写。

The character set and case sensitivity of the "url-parameter" is specified in each parameter definition.

“url参数”的字符集和大小写敏感度在每个参数定义中指定。

3. Intended Usage
3. 预期用途

The H.323 URL is intended to help an entity resolve the address of another H.323 entity, where an "entity" may be a user, a device, or a service. The "user" portion of the URL specifies an alias for the entity, without carrying any information about the location of the entity. The "hostport", on the other hand, is the domain name of an Endpoint, Gatekeeper, Border Element, or other functional element to which H.323 calls may be directed or for which services may be performed.

H.323url旨在帮助实体解析另一H.323实体的地址,其中“实体”可以是用户、设备或服务。URL的“用户”部分指定实体的别名,而不包含有关实体位置的任何信息。另一方面,“主机端口”是端点、网守、边界元素或其他功能元素的域名,H.323呼叫可以指向这些元素,或者可以为这些元素执行服务。

4. Applications and/or protocols, which may use H.323 URL scheme
4. 可能使用H.323 URL方案的应用程序和/或协议

H.323 URLs may be carried by other protocols, such as SIP [6] or TRIP [9]. H.323 URLs may be also contained within web pages or within XML data, which may be utilized by H.323 entities in order to initiate calls or perform services.

H.323URL可以由其他协议承载,例如SIP[6]或TRIP[9]。H.323 URL还可以包含在网页或XML数据中,H.323实体可以利用这些URL来发起调用或执行服务。

5. Security Considerations
5. 安全考虑

When an H.323 URL is carried within H.225.0 [4] messages, security is addressed by the H.235 security framework [5]. When an H.323 URL carried within other protocols (such as SIP [6]), the security is addressed within the corresponding protocol.

当H.225.0[4]消息中包含H.323 URL时,安全性由H.235安全框架[5]解决。当在其他协议(如SIP[6])中携带H.323 URL时,安全性在相应的协议中得到解决。

In general, security, as it relates to the usage and carriage of the H.323 URLs, is considered as an issue that should be addressed within scope of H.323 or other relevant protocols and is not within the scope of this document.

一般来说,与H.323 URL的使用和传输相关的安全性被认为是一个应在H.323或其他相关协议范围内解决的问题,不在本文件范围内。

6. IANA Considerations
6. IANA考虑

The purpose of this document is serving as a reference point for the purposes of registering the H.323 URL scheme with IANA.

本文件的目的是作为向IANA注册H.323 URL方案的参考点。

Having the URL registered with IANA will ensure that there is no duplication of the URL scheme "h323". This document reproduces the exact H323-URL definition as published in ITU-T Recommendation H.323 [3].

向IANA注册URL将确保URL方案“h323”没有重复。本文件复制了ITU-T建议H.323[3]中发布的准确H323-URL定义。

Registration Template

注册模板

URL scheme name: h323

URL方案名称:h323

URL scheme syntax: Section 2 of RFC 3508

URL方案语法:RFC 3508第2节

Character encoding considerations: Section 2 of RFC 3508

字符编码注意事项:RFC 3508第2节

Intended usage: Section 3 of RFC 3508

预期用途:RFC 3508第3节

Applications and/or protocols which use this scheme: Section 4 of RFC 3508

使用此方案的应用程序和/或协议:RFC 3508第4节

Interoperability considerations: None. (Section 2 of RFC 3508 contains the first version of "h323" URL definition.)

互操作性考虑:无。(RFC 3508第2节包含“h323”URL定义的第一个版本。)

Security considerations: Section 5 of RFC 3508

安全注意事项:RFC 3508第5节

Relevant publications: [3] and [4]

相关出版物:[3]和[4]

Contact: Orit Levin, orit@radvision.com

联系人:Orit Levin,orit@radvision.com

Author/Change Controller: IESG

作者/变更控制员:IESG

References

工具书类

[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[1] Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,1997年3月。

[2] Crocker, D., Editor, and P. Overell "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.

[2] Crocker,D.,编辑和P.Overell,“语法规范的扩充BNF:ABNF”,RFC 2234,1997年11月。

[3] ITU-T Recommendation H.323v.4 "Packet-based multimedia communications systems", November 2000.

[3] ITU-T建议H.323v.4“基于分组的多媒体通信系统”,2000年11月。

[4] ITU-T Recommendation H.225.0 "Call signalling protocols and media stream packetization for packet-based multimedia communication systems", November 2000.

[4] ITU-T建议H.225.0“分组多媒体通信系统的呼叫信令协议和媒体流分组”,2000年11月。

[5] ITU-T Recommendation H.235 "Security and Encryption for H Series (H.323 and other H.245 based) multimedia terminals", November 2000.

[5] ITU-T建议H.235“H系列(H.323和其他基于H.245的)多媒体终端的安全和加密”,2000年11月。

[6] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002.

[6] Rosenberg,J.,Schulzrinne,H.,Camarillo,G.,Johnston,A.,Peterson,J.,Sparks,R.,Handley,M.和E.Schooler,“SIP:会话启动协议”,RFC 3261,2002年6月。

[7] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998.

[7] “UTF-8,ISO 10646的转换格式”,RFC 2279,1998年1月。

[8] ISO/IEC 10646-1:1993, Information technology "Universal Multiple-Octet Coded Character Set (USC)" Part 1: Architecture and Basic Multilingual Plane.

[8] ISO/IEC 10646-1:1993,信息技术“通用多八位编码字符集(USC)”第1部分:体系结构和基本多语言平面。

[9] Rosenberg, J., Salama, H. and M. Squire, "Telephony Routing over IP (TRIP)", RFC 3219, January 2002.

[9] Rosenberg,J.,Salama,H.和M.Squire,“IP电话路由(TRIP)”,RFC 3219,2002年1月。

Acknowledgments

致谢

This document is prepared and posted on behalf of SG-16 ITU-T. I wish to thank Paul E. Jones, Robert Callaghan and Cullen Jennings for their comments and active help.

本文件是代表SG-16 ITU-T编制和发布的。我要感谢Paul E.Jones、Robert Callaghan和Cullen Jennings的评论和积极帮助。

Author's Address

作者地址

Orit Levin RADVISION 266 Harristown Road Glen Rock, NJ USA

美国新泽西州格伦洛克哈里斯敦路266号Orit Levin RADVISION

   Phone:  +1-201-689-6330
   EMail:  orit@radvision.com
        
   Phone:  +1-201-689-6330
   EMail:  orit@radvision.com
        

Full Copyright Statement

完整版权声明

Copyright (C) The Internet Society (2003). All Rights Reserved.

版权所有(C)互联网协会(2003年)。版权所有。

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

本文件及其译本可复制并提供给他人,对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发,不受任何限制,前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是,不得以任何方式修改本文件本身,例如删除版权通知或对互联网协会或其他互联网组织的引用,除非出于制定互联网标准的需要,在这种情况下,必须遵循互联网标准过程中定义的版权程序,或根据需要将其翻译成英语以外的其他语言。

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

上述授予的有限许可是永久性的,互联网协会或其继承人或受让人不会撤销。

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

本文件和其中包含的信息是按“原样”提供的,互联网协会和互联网工程任务组否认所有明示或暗示的保证,包括但不限于任何保证,即使用本文中的信息不会侵犯任何权利,或对适销性或特定用途适用性的任何默示保证。

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。