< draft-ietf-urlreg-procedures-07.txt		draft-ietf-urlreg-procedures-08.txt >
	Ian King <iking@microsoft.com>
	Speech Product Group
	MICROSOFT CORPORATION
	INTERNET-DRAFT R. Petke		INTERNET-DRAFT R. Petke
	<draft-ietf-urlreg-procedures-07.txt> UUNET Technologies		<draft-ietf-urlreg-procedures-08.txt> UUNET Technologies
	I. King		I. King
	Microsoft Corporation		Microsoft Corporation
	August 12, 1999		September 26, 1999
	Registration Procedures for URL Scheme Names		Registration Procedures for URL Scheme Names
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026. Internet-Drafts are		all provisions of Section 10 of RFC2026. Internet-Drafts are
	working documents of the Internet Engineering Task Force (IETF), its		working documents of the Internet Engineering Task Force (IETF), its
	areas, and its working groups. Note that other groups may also		areas, and its working groups. Note that other groups may also
	distribute working documents as Internet-Drafts. Internet-Drafts		distribute working documents as Internet-Drafts. Internet-Drafts
	skipping to change at line 33 ¶		skipping to change at line 29 ¶
	cite them other than as "work in progress."		cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Distribution of this Internet-Draft is unlimited.		Distribution of this Internet-Draft is unlimited.
	This Internet-Draft expires March 12, 2000.		This Internet-Draft expires April 26, 2000.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (1999). All Rights Reserved.		Copyright (C) The Internet Society (1999). All Rights Reserved.
	Abstract		Abstract
	This document defines the process by which new URL scheme names are		This document defines the process by which new URL scheme names are
	registered.		registered.
	skipping to change at line 129 ¶		skipping to change at line 125 ¶
	3.1 General Requirements		3.1 General Requirements
	All new URL schemes, regardless of registration tree, MUST conform		All new URL schemes, regardless of registration tree, MUST conform
	to the generic syntax for URLs as specified in RFC 2396.		to the generic syntax for URLs as specified in RFC 2396.
	3.2 The IETF Tree		3.2 The IETF Tree
	Registration in the IETF tree requires publication of the URL scheme		Registration in the IETF tree requires publication of the URL scheme
	syntax and semantics in either an Informational or Standards Track		syntax and semantics in either an Informational or Standards Track
	RFC.		RFC. In general, the creation of a new URL scheme requires a
			Standards Track RFC. An Informational RFC may be employed for
			registration only in the case of a URL scheme which is already in
			wide usage and meets other standards set forth in [RFC-GUIDELINES],
			such as "demonstrated utility" within the Internet Architecture; the
			IESG shall have broad discretion in determining whether an
			Informational RFC is suitable in any given case, and may either
			recommend changes to such document prior to publication, or reject
			it for publication. An Informational RFC purporting to describe a
			URL scheme shall not be published without IESG approval. This is a
			departure from practice for Informational RFCs as set forth in RFC
			2026, for the purpose of ensuring that the registration of URL
			schemes shall serve the best interests of the Internet community.
	The NAMES of schemes registered in the IETF tree MUST NOT contain		The NAMES of schemes registered in the IETF tree MUST NOT contain
	the dash (also known as the hyphen and minus sign) character ('-')		the dash (also known as the hyphen and minus sign) character ('-')
	USASCII value 2Dh. Use of this character can cause confusion with		USASCII value 2Dh. Use of this character can cause confusion with
	schemes registered in alternative trees (see section 3.3).		schemes registered in alternative trees (see section 3.3).
	An analysis of the security issues inherent in the new URL scheme		An analysis of the security issues inherent in the new URL scheme
	is REQUIRED. (This is in accordance with the basic requirements for		is REQUIRED. (This is in accordance with the basic requirements for
	all IETF protocols.) URL schemes registered in the IETF tree should		all IETF protocols.) URL schemes registered in the IETF tree should
	not introduce additional security risks into the Internet Architec-		not introduce additional security risks into the Internet Architec-
End of changes. 5 change blocks.
	8 lines changed or deleted		16 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/