Browse Prior Art Database

H.323 Uniform Resource Locator (URL) Scheme Registration (RFC3508)

IP.com Disclosure Number: IPCOM000012008D
Original Publication Date: 2003-Apr-01
Included in the Prior Art Database: 2003-Apr-02
Document File: 7 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

O. Levin: AUTHOR

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).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Network Working Group                                           O. Levin

Request for Comments: 3508                                     RADVISION

Category: Informational                                       April 2003

        H.323 Uniform Resource Locator (URL) Scheme Registration

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.

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).

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].

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

Levin                        Informational                      [Page 1]

RFC 3508                    H.323 URL Scheme                  April 2003

1.   Introduction

   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.

   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.

2.   URL Scheme Formal Syntax Definition and Character Encoding

   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].

   H323-URL®..