idnits 2.17.1 

draft-levin-iptel-h323-url-scheme-05.txt:
  Skipping this file; it looks like a tombstone file to me.
--------------------------------------------------------------------------------

1	A new Request for Comments is now available in online RFC libraries.

3	        RFC 3508

5	        Title:      H.323 Uniform Resource Locator (URL) Scheme
6	                    Registration
7	        Author(s):  O. Levin
8	        Status:     Informational
9	        Date:       April 2003
10	        Mailbox:    orit@radvision.com
11	        Pages:      6
12	        Characters: 10983
13	        Updates/Obsoletes/SeeAlso:  None

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

17	        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3508.txt

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

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

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

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

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

42	        help: ways_to_get_rfcs

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