< draft-ietf-opes-scenarios-00.txt		draft-ietf-opes-scenarios-01.txt >
	Network Working Group A. Barbir		Network Working Group A. Barbir
	Internet-Draft Nortel Networks		Internet-Draft Nortel Networks
	Expires: December 20, 2002 E. Burger		Expires: February 5, 2002 E. Burger
	SnowShore Networks, Inc.		SnowShore Networks, Inc.
	R. Chen		R. Chen
	AT&T Labs		AT&T Labs
	S. McHenry		S. McHenry
	CacheWare, Inc.		Individual Contributor
	H. Orman		H. Orman
	Purple Streak Development		Purple Streak Development
	R. Penno		R. Penno
	Nortel Networks		Nortel Networks
	June 21, 2002		Aug 5, 2002
	OPES Use Cases and Deployment Scenarios		OPES Use Cases and Deployment Scenarios
	draft-ietf-opes-scenarios-00		draft-ietf-opes-scenarios-01
	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		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	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 December 20, 2002.		This Internet-Draft will expire on February 5, 2003.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2002). All Rights Reserved.
	Abstract		Abstract
	This memo provides a discussion of use cases and deployment scenarios		This memo provides a discussion of use cases and deployment scenarios
	for Open Pluggable Edge Services (OPES). The work examines services		for Open Pluggable Edge Services (OPES). The work examines services
	that could be performed to requests and/or responses.		that could be performed to requests and/or responses.
	skipping to change at page 5, line 10 ¶		skipping to change at page 5, line 10 ¶
	2.1.1 Services intending to modify requests		2.1.1 Services intending to modify requests
	An OPES processor may modify a service request on behalf of the data		An OPES processor may modify a service request on behalf of the data
	consumer for various reasons, such as:		consumer for various reasons, such as:
	o Owner of a Web access device might need control over what kind of		o Owner of a Web access device might need control over what kind of
	Web content can be accessed with the device, parental control for		Web content can be accessed with the device, parental control for
	example.		example.
	o Organization may restrict or redirect access to certain web		o Organization may restrict or redirect access to certain web
	services based on various criterias such as time of the day or the		services based on various criteria such as time of the day or the
	employee access privileges.		employee access privileges.
	o Hiding the data consumer's identity, user agent, or referrer.		o Hiding the data consumer's identity, user agent, or referrer.
	o Adding user preferences or device profile to the service request		o Adding user preferences or device profile to the service request
	to get personalized or adapted services.		to get personalized or adapted services.
	o Blocking or redirecting a service request due to a corporate		o Blocking or redirecting a service request due to a corporate
	policy.		policy.
	skipping to change at page 6, line 47 ¶		skipping to change at page 6, line 47 ¶
	consumer application.		consumer application.
	Consider a content provider offering web pages that include a local		Consider a content provider offering web pages that include a local
	weather forecast based on the requestor's preferences. The OPES		weather forecast based on the requestor's preferences. The OPES
	service could analyze received requests, identify associated user		service could analyze received requests, identify associated user
	preferences, select appropriate templates, insert the corresponding		preferences, select appropriate templates, insert the corresponding
	local weather forecasts, and would then deliver the content to the		local weather forecasts, and would then deliver the content to the
	requestor. Note that the OPES processor may perform the tasks with		requestor. Note that the OPES processor may perform the tasks with
	or without direct access to the weather data. For example, the		or without direct access to the weather data. For example, the
	service could use locally cached weather data or it could simply		service could use locally cached weather data or it could simply
	embedd a URL pointing to another server that holds the latest local		embed a URL pointing to another server that holds the latest local
	weather forecast information.		weather forecast information.
	3. OPES deployment scenarios		3. OPES deployment scenarios
	OPES entities can be deployed over an overlay network that supports		OPES entities can be deployed over an overlay network that supports
	the provisioning of data services in a distributed manner. Overlay		the provisioning of data services in a distributed manner. Overlay
	networks are an abstraction that creates a virtual network of		networks are an abstraction that creates a virtual network of
	connected devices layered on an existing underlying IP networks in		connected devices layered on an existing underlying IP networks in
	order to perform application level services.		order to perform application level services.
	skipping to change at page 10, line 34 ¶		skipping to change at page 10, line 34 ¶
	3.5 Chaining of OPES data filters and callout servers		3.5 Chaining of OPES data filters and callout servers
	OPES data processors can be "chained" in two dimensions: along the		OPES data processors can be "chained" in two dimensions: along the
	content path or along the callout path. In the latter case, the		content path or along the callout path. In the latter case, the
	callout servers can themselves be organized in series for handling		callout servers can themselves be organized in series for handling
	requests. Any content that is touched by more than one data		requests. Any content that is touched by more than one data
	processor or more than one callout server has been handled by a		processor or more than one callout server has been handled by a
	"chain".		"chain".
			NOTE: Chaining of callout servers is deferred from version 1 of the
			Protocol. The discussion of chaining is included here for
			completeness.
	3.5.1 Chaining along the content path		3.5.1 Chaining along the content path
	An OPES provider may have assigned OPES services to a set of		An OPES provider may have assigned OPES services to a set of
	processors arranged in series. All content might move through the		processors arranged in series. All content might move through the
	series, and if the content matches the rules for a processor, it is		series, and if the content matches the rules for a processor, it is
	subjected to the service. In this way, the content can be enhanced		subjected to the service. In this way, the content can be enhanced
	by several services. This kind of chaining can be successful if the		by several services. This kind of chaining can be successful if the
	services are relatively independent. For example, the content might		services are relatively independent. For example, the content might
	be assembled by a service early in the chain and then further		be assembled by a service early in the chain and then further
	decorated by a later service.		decorated by a later service.
	skipping to change at page 15, line 9 ¶		skipping to change at page 15, line 9 ¶
	5. Security Considerations		5. Security Considerations
	The document presents usage scenarios and deployment cases. Issues		The document presents usage scenarios and deployment cases. Issues
	related to the overall security of OPES entities are given in [1].		related to the overall security of OPES entities are given in [1].
	References		References
	[1] A. Barbir et. al, "An Architecture for Open Pluggable Edge		[1] A. Barbir et. al, "An Architecture for Open Pluggable Edge
	Services (OPES)", Internet-Draft: http://www.ietf.org/internet-		Services (OPES)", Internet-Draft: http://www.ietf.org/internet-
	drafts/draft-ietf-opes-architecture-02.txt, June 2002.		drafts/draft-ietf-opes-architecture-02.txt, Jul 2002.
	[2] Floyd, S. and L. Daigle, "IAB Architectural and Policy		[2] Floyd, S. and L. Daigle, "IAB Architectural and Policy
	Considerations for Open Pluggable Edge Services", RFC 3238,		Considerations for Open Pluggable Edge Services", RFC 3238,
	January 2002.		January 2002.
	[3] Westerinen, A., Schnizlein, J., Strassner, J., Scherling, M.,		[3] Westerinen, A., Schnizlein, J., Strassner, J., Scherling, M.,
	Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry, J. and S.		Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry, J. and S.
	Waldbusser, "Terminology for Policy-Based Management", RFC 3198,		Waldbusser, "Terminology for Policy-Based Management", RFC 3198,
	November 2001.		November 2001.
	skipping to change at page 15, line 32 ¶		skipping to change at page 15, line 32 ¶
	HTTP/1.1", RFC 2616, June 1999.		HTTP/1.1", RFC 2616, June 1999.
	[5] OPES working group, "OPES Service Authorization and Enforcement		[5] OPES working group, "OPES Service Authorization and Enforcement
	Requirements", Internet-Draft TBD, May 2002.		Requirements", Internet-Draft TBD, May 2002.
	[6] OPES working group, "OPES Ruleset Schema", Internet-Draft TBD,		[6] OPES working group, "OPES Ruleset Schema", Internet-Draft TBD,
	May 2002.		May 2002.
	[7] A. Beck et al., "Requirements for OPES Callout Protocols",		[7] A. Beck et al., "Requirements for OPES Callout Protocols",
	Internet-Draft http://www.ietf.org/internet-drafts/draft-ietf-		Internet-Draft http://www.ietf.org/internet-drafts/draft-ietf-
	opes-protocol-reqs-00.txt, May 2002.		opes-protocol-reqs-02.txt, Jul 2002.
	Authors' Addresses		Authors' Addresses
	Abbie Barbir		Abbie Barbir
	Nortel Networks		Nortel Networks
	3500 Carling Avenue		3500 Carling Avenue
	Nepean, Ontario K2H 8E9		Nepean, Ontario K2H 8E9
	Canada		Canada
	Phone: +1 613 763 5229		Phone: +1 613 763 5229
	skipping to change at page 16, line 23 ¶		skipping to change at page 16, line 23 ¶
	Robin Chen		Robin Chen
	AT&T Labs		AT&T Labs
	Room E219, 180 Park Avenue		Room E219, 180 Park Avenue
	Florham Park, NJ 07932		Florham Park, NJ 07932
	US		US
	Phone: +1 973 360 8653		Phone: +1 973 360 8653
	EMail: chen@research.att.com		EMail: chen@research.att.com
	Stephen McHenry		Stephen McHenry
	CacheWare, Inc.		305 Vineyard Town Center, #251
	Suite 150		Morgan Hill, CA 95037
	655 Campbell Technology Parkway, Suite 150
	Campbell, CA 95008
	US		US
	Phone: (408) 540-1270		Phone: (408) 683-2500
	EMail: stephen@cacheware.com		EMail: smchenry@mchenry.net
	Hilarie Orman		Hilarie Orman
	Purple Streak Development		Purple Streak Development
	Phone:		Phone:
	EMail: ho@alum.mit.edu		EMail: ho@alum.mit.edu
	Reinaldo Penno		Reinaldo Penno
	Nortel Networks		Nortel Networks
	4555 Great America Parkway		4555 Great America Parkway
	Santa Clara, CA 95054		Santa Clara, CA 95054
	US		US
	EMail: rpenno@nortelnetworks.com		EMail: rpenno@nortelnetworks.com
	Appendix A. Acknowledgements		Appendix A. Acknowledgements
	TBD		The authors would like to thank the participants of the OPES WG for
			their comments on this draft.
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2002). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
End of changes. 14 change blocks.
	17 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/