< draft-baker-soap-media-reg-05.txt		draft-baker-soap-media-reg-06.txt >
	Network Working Group M. Baker		Network Working Group M. Baker
	Internet-Draft Independent		Internet-Draft Independent
	Expires: October 28, 2004 M. Nottingham		Expires: November 15, 2004 M. Nottingham
	BEA Systems		BEA Systems
	April 29, 2004		May 17, 2004
	The "application/soap+xml" media type		The "application/soap+xml" media type
	draft-baker-soap-media-reg-05		draft-baker-soap-media-reg-06
	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.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that other		Task Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at http://		The list of current Internet-Drafts can be accessed at http://
	www.ietf.org/ietf/1id-abstracts.txt.		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.
	This Internet-Draft will expire on October 28, 2004.		This Internet-Draft will expire on November 15, 2004.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2004). All Rights Reserved.		Copyright (C) The Internet Society (2004). All Rights Reserved.
	Abstract		Abstract
	This document defines the "application/soap+xml" media type which can		This document defines the "application/soap+xml" media type which can
	be used to describe SOAP 1.2 messages serialized as XML 1.0.		be used to describe SOAP 1.2 messages serialized as XML 1.0.
	1. Notational Conventions		1. Notational Conventions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
			=0C
	2. Introduction		2. Introduction
	SOAP version 1.2 (SOAP) is a lightweight protocol intended for		SOAP version 1.2 (SOAP) is a lightweight protocol intended for
	exchange of structured information between peers in a decentralized,		exchange of structured information between peers in a decentralized,
	distributed environment. It defines an extensible messaging framework		distributed environment. It defines an extensible messaging framework
	that contains a message construct based on XML technologies that can		that contains a message construct based on XML technologies that can
	be exchanged over a variety of underlying protocols.		be exchanged over a variety of underlying protocols.
	This specification defines the media type "application/soap+xml"		This specification defines the media type "application/soap+xml"
	which can be used to identify SOAP 1.2 message envelopes that have		which can be used to identify SOAP 1.2 message envelopes that have
	skipping to change at page 3, line 5 ¶		skipping to change at page 3, line 5 ¶
	Although the purpose of the action parameter is to indicate the		Although the purpose of the action parameter is to indicate the
	intent of the SOAP message there is no mechanism for		intent of the SOAP message there is no mechanism for
	automatically computing the value based on the SOAP envelope.		automatically computing the value based on the SOAP envelope.
	In other words, the value has to be determined out of band.		In other words, the value has to be determined out of band.
	It is recommended that the same value be used to identify sets		It is recommended that the same value be used to identify sets
	of message types that are logically connected in some manner,		of message types that are logically connected in some manner,
	for example part of the same "service". It is strongly		for example part of the same "service". It is strongly
	RECOMMENDED that the URI be globally unique and stable over		RECOMMENDED that the URI be globally unique and stable over
	time.		time.
			=0C
	The presence and content of the action parameter MAY be used by		The presence and content of the action parameter MAY be used by
	servers such as firewalls to appropriately filter SOAP messages		servers such as firewalls to appropriately filter SOAP messages
	and it may be used by servers to facilitate dispatching of SOAP		and it may be used by servers to facilitate dispatching of SOAP
	messages to internal message handlers etc. It SHOULD NOT be		messages to internal message handlers etc. It SHOULD NOT be
	used as an insecure form of access authorization.		used as an insecure form of access authorization.
	Use of the action parameter is OPTIONAL. SOAP Receivers MAY use		Use of the action parameter is OPTIONAL. SOAP Receivers MAY use
	it as a hint to optimize processing, but SHOULD NOT require its		it as a hint to optimize processing, but SHOULD NOT require its
	presence in order to operate.		presence in order to operate.
	Encoding considerations: Identical to those of "application/xml" as		Encoding considerations: Identical to those of "application/xml" as
	described in RFC 3023 [RFC3023], section 3.2, as applied to the		described in RFC 3023 [RFC3023], section 3.2, as applied to the
	skipping to change at page 4, line 5 ¶		skipping to change at page 4, line 5 ¶
	Additional information:		Additional information:
	File extension: SOAP messages are not required or expected to be		File extension: SOAP messages are not required or expected to be
	stored as files.		stored as files.
	Fragment identifiers: Identical to that of "application/xml" as		Fragment identifiers: Identical to that of "application/xml" as
	described in RFC 3023 [RFC3023], section 5.		described in RFC 3023 [RFC3023], section 5.
	Base URI: As specified in RFC 3023 [RFC3023], section 6. Also see		Base URI: As specified in RFC 3023 [RFC3023], section 6. Also see
	SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], section Use of		SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], section Use of
	URIs in SOAP.		URIs in SOAP.
			=0C
	Macintosh File Type code: TEXT		Macintosh File Type code: TEXT
	Person and email address to contact for further information: Mark		Person and email address to contact for further information: Mark
	Nottingham <mnot@pobox.com>		Nottingham <mnot@pobox.com>
	Intended usage: COMMON		Intended usage: COMMON
	Author/Change controller: The SOAP 1.2 specification set is a work		Author/Change controller: The SOAP 1.2 specification set is a work
	product of the World Wide Web Consortium's XML Protocol Working		product of the World Wide Web Consortium's XML Protocol Working
	Group. The W3C has change control over these specifications.		Group. The W3C has change control over these specifications.
			4. Security Considerations
			See the "Security Considerations" section of the registration
			template found in Section 3.
	Normative References		Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform		[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
	Resource Identifiers (URI): Generic Syntax", RFC 2396,		Resource Identifiers (URI): Generic Syntax", RFC 2396,
	August 1998.		August 1998.
	[RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media		[RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media
	skipping to change at page 5, line 4 ¶		skipping to change at page 5, line 4 ¶
	Authors' Addresses		Authors' Addresses
	Mark A. Baker		Mark A. Baker
	Independent		Independent
	37 Charles St.		37 Charles St.
	Ottawa, Ontario K1M 1R3		Ottawa, Ontario K1M 1R3
	CA		CA
	EMail: mailto:distobj@acm.org		EMail: mailto:distobj@acm.org
			=0C
	Mark Nottingham		Mark Nottingham
	BEA Systems		BEA Systems
	235 Montgomery St., Level 15		235 Montgomery St., Level 15
	San Francisco, CA 94010		San Francisco, CA 94010
	US		US
	EMail: mailto:mnot@pobox.com		EMail: mailto:mnot@pobox.com
			=0C
	Intellectual Property Statement		Intellectual Property Statement
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	intellectual property or other rights that might be claimed to		intellectual property or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; neither does it represent that it		might or might not be available; neither does it represent that it
	has made any effort to identify any such rights. Information on the		has made any effort to identify any such rights. Information on the
	IETF's procedures with respect to rights in standards-track and		IETF's procedures with respect to rights in standards-track and
	standards-related documentation can be found in BCP-11. Copies of		standards-related documentation can be found in BCP-11. Copies of
	skipping to change at page 7, line 4 ¶		skipping to change at page 7, line 4 ¶
	followed, or as required to translate it into languages other than		followed, or as required to translate it into languages other than
	English.		English.
	The limited permissions granted above are perpetual and will not be		The limited permissions granted above are perpetual and will not be
	revoked by the Internet Society or its successors or assignees.		revoked by the Internet Society or its successors or assignees.
	This document and the information contained herein is provided on an		This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING		"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION		BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
			=0C
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
End of changes. 11 change blocks.
	5 lines changed or deleted		20 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/