Skip to main content

H.323 Uniform Resource Locator (URL) Scheme Registration

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3508.
Author Orit Levin
Last updated 2015-10-14 (Latest revision 2002-11-06)
RFC stream Independent Submission
Intended RFC status Informational
Stream ISE state (None)
Consensus boilerplate Unknown
Document shepherd (None)
IESG IESG state Became RFC 3508 (Informational)
Action Holders
Telechat date (None)
Responsible AD Scott O. Bradner
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3508

        Title:      H.323 Uniform Resource Locator (URL) Scheme
        Author(s):  O. Levin
        Status:     Informational
        Date:       April 2003
        Pages:      6
        Characters: 10983
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-levin-iptel-h323-url-scheme-05.txt


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

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

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.