< draft-ietf-ipp-not-06.txt		draft-ietf-ipp-not-07.txt >
	Internet Printing Protocol WG Tom Hastings (editor)		Internet Printing Protocol WG Tom Hastings (editor)
	INTERNET DRAFT Xerox Corporation		INTERNET DRAFT Xerox Corporation
	<draft-ietf-ipp-not-06.txt> Roger K deBry		<draft-ietf-ipp-not-07.txt> Roger K deBry
	[Target Category: Informational] Utah Valley State College		[Target Category: Informational] Utah Valley State College
	Expires: January 17, 2002 Harry Lewis		Expires: December 21, 2004 Harry Lewis
	IBM Corporation		IBM Corporation
	July 17, 2001		June 21, 2004
	Internet Printing Protocol (IPP): Requirements for IPP Notifications		Internet Printing Protocol (IPP): Requirements for IPP Notifications
	Copyright (C) The Internet Society (2001). All Rights Reserved.		Copyright (C) The Internet Society (2001). All Rights Reserved.
	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
	skipping to change at page 2, line 13 ¶		skipping to change at page 2, line 13 ¶
	requirements for notifications as an optional part of an IPP Service.		requirements for notifications as an optional part of an IPP Service.
	Table of Contents		Table of Contents
	1 Scope............................................................3		1 Scope............................................................3
	2 Terminology......................................................3		2 Terminology......................................................3
	3 Scenarios........................................................7		3 Scenarios........................................................7
	4 Requirements....................................................11		4 Requirements....................................................10
	5 Security considerations for IPP Notifications requirements......13		5 Security considerations for IPP Notifications requirements......13
	6 Internationalization Considerations.............................14		6 Internationalization Considerations.............................14
	7 IANA Considerations.............................................14		7 IANA Considerations.............................................14
	8 References......................................................14		8 References......................................................14
	9 Author's Address................................................15		9 Author's Address................................................15
	10 Appendix A: Description of the Base IPP Documents..............16		10 Appendix A: Description of the Base IPP Documents..............15
	11 Appendix B: Full Copyright Statement...........................17		11 Appendix B: Full Copyright Statement...........................16
	1 Scope		1 Scope
	This document is one of a set of documents which together describe		This document is one of a set of documents which together describe
	all aspects of a new Internet Printing Protocol (IPP). IPP is an		all aspects of a new Internet Printing Protocol (IPP). IPP is an
	application level protocol that can be used for distributed printing		application level protocol that can be used for distributed printing
	on the Internet. There are multiple parts to IPP, but the primary		on the Internet. There are multiple parts to IPP, but the primary
	architectural components are the Model, the Protocol and an interface		architectural components are the Model, the Protocol and an interface
	to Directory Services. This document provides a statement of the		to Directory Services. This document provides a statement of the
	requirements for notifications as an optional part of an IPP Service.		requirements for notifications as an optional part of an IPP Service.
	skipping to change at page 4, line 10 ¶		skipping to change at page 4, line 10 ¶
	of a Job Submitting End User, which submits a print job to an IPP		of a Job Submitting End User, which submits a print job to an IPP
	Printer. The application may or may not be within the same security		Printer. The application may or may not be within the same security
	domain as the Printer. This application may or may not be		domain as the Printer. This application may or may not be
	geographically near the printer.		geographically near the printer.
	2.5 Security Domain		2.5 Security Domain
	For the purposes of this discussion, the set of network components		For the purposes of this discussion, the set of network components
	which can communicate without going through a proxy or firewall. A		which can communicate without going through a proxy or firewall. A
	security domain may be geographically very large, for example -		security domain may be geographically very large, for example -
	anyplace within IBM.COM.		anyplace within example.com.
	2.6 IPP Client		2.6 IPP Client
	The software component that sends IPP requests to an IPP Printer		The software component that sends IPP requests to an IPP Printer
	object and accepts IPP responses from an IPP Printer.		object and accepts IPP responses from an IPP Printer.
	2.7 Job Recipient		2.7 Job Recipient
	A human who is the ultimate consumer of the print job. In many cases		A human who is the ultimate consumer of the print job. In many cases
	this will be the same person as the Job Submitting End User, but this		this will be the same person as the Job Submitting End User, but this
	need not always be the case. For example, if I use IPP to print a		need not always be the case. For example, if I use IPP to print a
	document on a printer in a business partner's office, I am the Job		document on a printer in a business partner's office, I am the Job
	Submitting End User, while the person I intend the document for in my		Submitting End User, while the person I intend the document for in my
	business partner's office is the Job Recipient. Since one of the		business partner's office is the Job Recipient. Since one of the
	goals of IPP is to be able to print near the Job Recipient of the		goals of IPP is to be able to print near the Job Recipient of the
	printed output, we would normally expect that person to be in the		printed output, we would normally expect that person to be in the
	same security domain as, and geographically near, the Printer.		same security domain as, and geographically near, the Printer.
	However, this may not always be the case. For example, I submit a		However, this may not always be the case. For example, I submit a
	print job across the Internet to a Kinko's print shop. I am both the		print job across the Internet to a XYZ's print shop. I am both the
	Submitting end User and the Job Recipient, but I am neither near nor		Submitting end User and the Job Recipient, but I am neither near nor
	in the same security domain as the Printer.		in the same security domain as the Printer.
	2.8 Job Recipient Proxy		2.8 Job Recipient Proxy
	A person acting on behalf of the Job Recipient. In particular, the		A person acting on behalf of the Job Recipient. In particular, the
	Job Recipient Proxy physically picks up the printed document from the		Job Recipient Proxy physically picks up the printed document from the
	Printer, if the Job Recipient cannot perform that function. The Proxy		Printer, if the Job Recipient cannot perform that function. The Proxy
	is by definition geographically near and in the same security domain		is by definition geographically near and in the same security domain
	as the printer. For example, I submit a print job from home to be		as the printer. For example, I submit a print job from home to be
	skipping to change at page 7, line 37 ¶		skipping to change at page 7, line 35 ¶
	only. The Notification Recipient could process the machine readable		only. The Notification Recipient could process the machine readable
	Event Notification into human readable format.		Event Notification into human readable format.
	2.24 Mixed Notification		2.24 Mixed Notification
	A mixed notification contains both Human Consumable and Machine		A mixed notification contains both Human Consumable and Machine
	Consumable information.		Consumable information.
	3 Scenarios		3 Scenarios
	1.I am sitting in my office and submit a print job to the printer		1. I am sitting in my office and submit a print job to the printer
	down the hall. I am in the same security domain as the printer and		down the hall. I am in the same security domain as the printer and
	of course, geographically near. I want to know immediately when		of course, geographically near. I want to know immediately when
	my print job will be completed (or if there is a problem) because		my print job will be completed (or if there is a problem) because
	the document I am working on is urgent. I submit the print job		the document I am working on is urgent. I submit the print job
	with the following attributes:		with the following attributes:
	? Notification Recipient - me		. Notification Recipient - me
	? Notification Events - all		. Notification Events - all
	? Notification Attributes - job-state-reason		. Notification Attributes - job-state-reason
	? Notification Type - immediate		. Notification Type - immediate
	2.I am working from home and submit a print job to the same printer		2. I am working from home and submit a print job to the same printer
	as in the previous example. However, since I am not at work, I		as in the previous example. However, since I am not at work, I
	cannot physically get the print file or do anything with it. It		cannot physically get the print file or do anything with it. It
	can wait until I get to work this afternoon. However, I'd like my		can wait until I get to work this afternoon. However, I'd like my
	secretary to pick up the output and put it on my desk so it		secretary to pick up the output and put it on my desk so it
	doesn't get lost or miss-filed. I'd also like a store and forward		doesn't get lost or miss-filed. I'd also like a store and forward
	notification sent to my email so that when I get to work I can		notification sent to my email so that when I get to work I can
	tell if there was a problem with the print job. I submit a print		tell if there was a problem with the print job. I submit a print
	job with the following attributes:		job with the following attributes:
	? Notification Recipient - my secretary		. Notification Recipient - my secretary
	? Notification Events - print complete		. Notification Events - print complete
	? Notification Type - immediate		. Notification Type - immediate
	? Notification Recipient - me		. Notification Recipient - me
	? Notification Events - print complete		. Notification Events - print complete
	? Notification Attributes - impressions completed		. Notification Attributes - impressions completed
	? Notification Type - store and forward		. Notification Type - store and forward
	3.I am sitting in my office and submit a print job to a client at an		3. I am sitting in my office and submit a print job to a client at an
	engineering firm we work with on a daily basis. The engineering		engineering firm we work with on a daily basis. The engineering
	firm is in Belgium. I would like my client to know when the print		firm is in Belgium. I would like my client to know when the print
	job is complete, so that she can pick it up from the printer in		job is complete, so that she can pick it up from the printer in
	her building. It is important that she review it right away and		her building. It is important that she review it right away and
	get her comments back to me. I submit the print job with the		get her comments back to me. I submit the print job with the
	following attributes:		following attributes:
	? Notification Recipient - client at engineering firm		. Notification Recipient - client at engineering firm
	? Notification Events - print complete		. Notification Events - print complete
	? Notification Type - immediate		. Notification Type - immediate
	? Notification Language - French		. Notification Language - French
	4.I am in a hotel room and send a print job to a Kinko's store in		4. I am in a hotel room and send a print job to a Kinko's store in
	the town I am working in, in order to get a printed report for the		the town I am working in, in order to get a printed report for the
	meeting I am attending in the morning. Since I'm going out to		meeting I am attending in the morning. Since I'm going out to
	dinner after I get this job submitted, an immediate notification		dinner after I get this job submitted, an immediate notification
	won't do me much good. However, I'd like to check in the morning		won't do me much good. However, I'd like to check in the morning
	before I drive to the Kinko's store to see if the file has been		before I drive to the Kinko's store to see if the file has been
	printed. An email notification is sufficient for this purpose. I		printed. An email notification is sufficient for this purpose. I
	submit the print job with the following attributes:		submit the print job with the following attributes:
	? Notification Recipient - me		. Notification Recipient - me
	? Notification Events - print complete		. Notification Events - print complete
	? Notification Type - store and forward		. Notification Type - store and forward
	5.I am printing a large, complex print file. I want to have some		5. I am printing a large, complex print file. I want to have some
	immediate feedback on the progress of the print job as it prints.		immediate feedback on the progress of the print job as it prints.
	I submit the print job with the following attributes:		I submit the print job with the following attributes:
	? Notification Recipient - me		. Notification Recipient - me
	? Notification Type - immediate		. Notification Type - immediate
	? Notification Events - all state transitions		. Notification Events - all state transitions
	? Notification Attributes - impression completed		. Notification Attributes - impression completed
	6.I am an operator and my duties is to keep the printer running. I		6. I am an operator and my duties is to keep the printer running. I
	subscribe independently from a job submission so that my		subscribe independently from a job submission so that my
	subscription outlasts any particular job. I subscribe with the		subscription outlasts any particular job. I subscribe with the
	following attributes:		following attributes:
	? Notification Recipient - me		. Notification Recipient - me
	? Notification Type - immediate		. Notification Type - immediate
	? Notification Events - all Printer state transitions		. Notification Events - all Printer state transitions
	? Notification Attributes - Printer state, printer state reasons,		. Notification Attributes - Printer state, printer state reasons,
	device powering up, device powering down.		device powering up, device powering down.
	7.I am a usage statistics gathering application. I subscribe		7. I am a usage statistics gathering application. I subscribe
	independently from a job submission so that my subscription		independently from a job submission so that my subscription
	outlasts any particular job. My subscription may persists across		outlasts any particular job. My subscription may persists across
	power cycles. I subscribe with the following attributes:		power cycles. I subscribe with the following attributes:
	? Notification Recipient - me		. Notification Recipient - me
	? Notification Type - immediate		. Notification Type - immediate
	? Notification Events - job completion		. Notification Events - job completion
	? Notification Attributes - impression completed, sheets		. Notification Attributes - impression completed, sheets
	completed, time submitted, time started, time completed, job		completed, time submitted, time started, time completed, job
	owner, job size in octets, etc.		owner, job size in octets, etc.
	8.I am a client application program that displays a list of jobs		8. I am a client application program that displays a list of jobs
	currently queued for printing on a printer. I display the "job-		currently queued for printing on a printer. I display the "job-
	name", "job-state", "job-state-reasons", "page-count", and		name", "job-state", "job-state-reasons", "page-count", and
	"intervening-jobs" either for the user's jobs or for all jobs.		"intervening-jobs" either for the user's jobs or for all jobs.
	The window displaying the job list remains open for an independent		The window displaying the job list remains open for an independent
	amount of time, and it is desired that it represent the current		amount of time, and it is desired that it represent the current
	state of the queue. It is desired that the application only need		state of the queue. It is desired that the application only need
	to perform a slow poll in order to recover from any missed		to perform a slow poll in order to recover from any missed
	notifications. So the event delivery mechanism provides the means		notifications. So the event delivery mechanism provides the means
	to update the screen on all needed changes, including querying for		to update the screen on all needed changes, including querying for
	some attributes that may not be delivered in the Notification.		some attributes that may not be delivered in the Notification.
	9.I am a client application program that displays a list of		9. I am a client application program that displays a list of
	printers. For each Printer I display the current state and		printers. For each Printer I display the current state and
	configuration. The window displaying the printer list remains		configuration. The window displaying the printer list remains
	open for an independent amount of time, and it is desired that it		open for an independent amount of time, and it is desired that it
	represent the current state of each printer. It is desired that		represent the current state of each printer. It is desired that
	the application only need to perform a slow poll in order to		the application only need to perform a slow poll in order to
	recover from any missed notifications. So the event delivery		recover from any missed notifications. So the event delivery
	mechanism provides the means to update the screen on all needed		mechanism provides the means to update the screen on all needed
	changes, including querying for some attributes that may not be		changes, including querying for some attributes that may not be
	delivered in the Notification.		delivered in the Notification.
	skipping to change at page 11, line 8 ¶		skipping to change at page 11, line 4 ¶
	Notification Recipient. When I get a Job Creation request, I		Notification Recipient. When I get a Job Creation request, I
	decide to which IPP Printer to send the job. When I do so, I also		decide to which IPP Printer to send the job. When I do so, I also
	add a job subscription for Job events with me as the Notification		add a job subscription for Job events with me as the Notification
	Recipient to the job's job subscriptions supplied by my clients		Recipient to the job's job subscriptions supplied by my clients
	(this usage is called "piggy-backing"). These IPP Printers		(this usage is called "piggy-backing"). These IPP Printers
	automatically remove their job subscriptions when the job		automatically remove their job subscriptions when the job
	completes as for all job subscriptions so that I no longer get Job		completes as for all job subscriptions so that I no longer get Job
	events when my jobs are completed.		events when my jobs are completed.
	4 Requirements		4 Requirements
	The following requirements are intended to be met by the IPP		The following requirements are intended to be met by the IPP
	Notification specification (not the implementation). The resulting		Notification specification (not the implementation). The resulting
	IPP Notification Specification document:		IPP Notification Specification document:
	1.must indicate which of these requirements are REQUIRED and which		1. must indicate which of these requirements are REQUIRED and which
	are OPTIONAL for a conforming implementation to support. See		are OPTIONAL for a conforming implementation to support. See
	[RFC2911] section 12.1 for the definition of these important		[RFC2911] section 12.1 for the definition of these important
	conformance terms.		conformance terms.
	2.must be designed to that an IPP Printer can transparently support		2. must be designed to that an IPP Printer can transparently support
	the IPP Notification semantics using third party notification		the IPP Notification semantics using third party notification
	services that exist today or that may be standardized in the		services that exist today or that may be standardized in the
	future.		future.
	3.must define means for a Job Submitting End User to specify zero or		3. must define means for a Job Submitting End User to specify zero or
	more Notification Recipients when submitting a print job. A		more Notification Recipients when submitting a print job. A
	Submitter will not be able to prevent out of band subscriptions		Submitter will not be able to prevent out of band subscriptions
	from authorized persons, such as Operators.		from authorized persons, such as Operators.
	4.must define means when specifying a Notification Recipient, for a		4. must define means when specifying a Notification Recipient, for a
	Notification Subscriber to be able to specify one or more		Notification Subscriber to be able to specify one or more
	notification events for that Notification Recipient, subject to		notification events for that Notification Recipient, subject to
	administrative and security policy restrictions. Any of the		administrative and security policy restrictions. Any of the
	following constitute Job or Printer Events that a Job Submitting		following constitute Job or Printer Events that a Job Submitting
	End User can specify notifications be sent for:		End User can specify notifications be sent for:
	? Any standard Printer MIB alert (i.e. device alerts) (critical		. Any standard Printer MIB alert (i.e. device alerts) (critical
	and warning?) (state change notifications)?		and warning?) (state change notifications)?
	? Job Received (transition from Unknown to Pending)		. Job Received (transition from Unknown to Pending)
	? Job Started (Transition from Pending to Processing)		. Job Started (Transition from Pending to Processing)
	? Page Complete (Page is stacked)		. Page Complete (Page is stacked)
	? Collated Copy Complete (last sheet of collated copy is		. Collated Copy Complete (last sheet of collated copy is
	stacked)		stacked)
	? Job Complete (transition from Processing or Processing-		. Job Complete (transition from Processing or Processing-
	stopped to Completed)		stopped to Completed)
	? Job aborted (transition from Pending, Pending-held,		. Job aborted (transition from Pending, Pending-held,
	Processing, or Processing-stopped to Aborted)		Processing, or Processing-stopped to Aborted)
	? Job canceled (transition from Pending, Pending-held,		. Job canceled (transition from Pending, Pending-held,
	Processing, or Processing-held to Canceled)		Processing, or Processing-held to Canceled)
	? Other job state changes like 'paused', purged?		. Other job state changes like 'paused', purged?
	? Device problems for which the job is destined		. Device problems for which the job is destined
	? Job (interpreter) issues		. Job (interpreter) issues
	5.must define how an End User or Operator subscribes for:		5. must define how an End User or Operator subscribes for:
	? Any set of Job Events for a specific job.		. Any set of Job Events for a specific job.
	? Any set of Printer Events while a specific job is not		. Any set of Printer Events while a specific job is not
	complete.		complete.
	6.must define how an End User or Operator subscribes for the		6. must define how an End User or Operator subscribes for the
	following without having to submit a Job:		following without having to submit a Job:
	? Any set of Printer Events for a defined period.		. Any set of Printer Events for a defined period.
	? Any set of Job Events for all jobs with no control over which		. Any set of Job Events for all jobs with no control over which
	jobs.		jobs.
	7.must define how the Notification Subscriber is able to specify		7. must define how the Notification Subscriber is able to specify
	either immediate or store and forward notification independently		either immediate or store and forward notification independently
	for each Notification Recipient. The means may be explicit, or		for each Notification Recipient. The means may be explicit, or
	implied by the method of delivery chosen by the Job Submitting End		implied by the method of delivery chosen by the Job Submitting End
	User.		User.
	8.must define common delivery methods, e.g. email, must be defined.		8. must define common delivery methods, e.g. email, must be defined.
	9.must define how an IPP Printer validates its ability to deliver an		9. must define how an IPP Printer validates its ability to deliver an
	Event using the specified delivery scheme. If it does not support		Event using the specified delivery scheme. If it does not support
	the specified scheme, or the specified scheme is invalid for some		the specified scheme, or the specified scheme is invalid for some
	reason, then the IPP Printer accepts and performs the request		reason, then the IPP Printer accepts and performs the request
	anyway and responds indicating the unsupported attribute values.		anyway and responds indicating the unsupported attribute values.
	There is no requirement for the IPP Printer receiving the print		There is no requirement for the IPP Printer receiving the print
	request to validate the identity of an Notification Recipient, nor		request to validate the identity of an Notification Recipient, nor
	the ability of the system to deliver an event to that recipient as		the ability of the system to deliver an event to that recipient as
	requested (for example, if the Notification Recipient is not at		requested (for example, if the Notification Recipient is not at
	work today).		work today).
	skipping to change at page 14, line 29 ¶		skipping to change at page 14, line 25 ¶
	Notification Subscriber specifies within the choice of natural		Notification Subscriber specifies within the choice of natural
	languages and charsets that the IPP Printer supports. See [RFC2566].		languages and charsets that the IPP Printer supports. See [RFC2566].
	7 IANA Considerations		7 IANA Considerations
	There will be some notification delivery methods registered with IANA		There will be some notification delivery methods registered with IANA
	for use in URLs. These will be defined in other documents.		for use in URLs. These will be defined in other documents.
	8 References		8 References
			8.1 Normative References
			[RFC2910]
			Herriot, R., Butler, S., Moore, P., Turner, R., "Internet Printing
			Protocol/1.1: Encoding and Transport", RFC 2910, September 2000.
			[RFC2911]
			deBry, R., , Hastings, T., Herriot, R., Isaacson, S., Powell, P.,
			"Internet Printing Protocol/1.1: Model and Semantics", RFC 2911,
			September 2000.
	[ipp-ntfy]		[ipp-ntfy]
	Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M.,		Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M.,
	Bergman, R., " IPP Event Notification Specification", <draft-ietf-		Bergman, R., " IPP Event Notification Specification", <draft-ietf-
	ipp-not-spec-07.txt>, work in progress, July 17, 2001.		ipp-not-spec-07.txt>, work in progress, July 17, 2001.
	[RFC2565]		8.2 Informative References
			[RFC2565]
	Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing		Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing
	Protocol/1.0: Encoding and Transport", RFC 2565, April 1999.		Protocol/1.0: Encoding and Transport", RFC 2565, April 1999.
	[RFC2566]		[RFC2566]
	R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,		R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell,
	"Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,		"Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,
	April 1999.		April 1999.
	[RFC2567]		[RFC2567]
	Wright, D., "Design Goals for an Internet Printing Protocol", RFC		Wright, D., "Design Goals for an Internet Printing Protocol", RFC
	skipping to change at page 15, line 13 ¶		skipping to change at page 15, line 17 ¶
	the Internet Printing Protocol", RFC 2568, April 1999.		the Internet Printing Protocol", RFC 2568, April 1999.
	[RFC2569]		[RFC2569]
	Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between		Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between
	LPD and IPP Protocols", RFC 2569, April 1999.		LPD and IPP Protocols", RFC 2569, April 1999.
	[RFC2639]		[RFC2639]
	T. Hastings, C. Manros. "Internet Printing Protocol/1.0:		T. Hastings, C. Manros. "Internet Printing Protocol/1.0:
	Implementer's Guide", RFC 2639, July 1999.		Implementer's Guide", RFC 2639, July 1999.
	[RFC2910]
	Herriot, R., Butler, S., Moore, P., Turner, R., "Internet Printing
	Protocol/1.1: Encoding and Transport", RFC 2910, September 2000.
	[RFC2911]
	deBry, R., , Hastings, T., Herriot, R., Isaacson, S., Powell, P.,
	"Internet Printing Protocol/1.1: Model and Semantics", RFC 2911,
	September 2000.
	9 Author's Address		9 Author's Address
	Harry Lewis
	HUC/003G
	IBM Corporation
	P.O. Box 1900
	Boulder, CO 80301-9191
	Phone: (303) 924-5337
	Fax: (303) 924-9889
	e-mail: harryl@us.ibm.com
	Roger deBry
	Utah Valley State College
	Orem, UT 84058
	Phone: (801) 222-8000
	e-mail: debryro@uvsc.edu
	Tom Hastings (editor)		Tom Hastings (editor)
	Xerox Corporation		Xerox Corporation
	737 Hawaii St. ESAE 231		737 Hawaii St. ESAE 231
	El Segundo, CA 90245		El Segundo, CA 90245
	Phone: 310-333-6413		Phone: 310-333-6413
	Fax: 310-333-5514		Fax: 310-333-5514
	e-mail: hastings@cp10.es.xerox.com		e-mail: hastings@cp10.es.xerox.com
	IPP Web Page: http://www.pwg.org/ipp/		Roger deBry
	IPP Mailing List: ipp@pwg.org		Utah Valley State College
			Orem, UT 84058
	To subscribe to the ipp mailing list, send the following email:		Phone: (801) 222-8000
	1) send it to majordomo@pwg.org		e-mail: debryro@uvsc.edu
	2) leave the subject line blank
	3) put the following two lines in the message body:
	subscribe ipp
	end
	Implementers of this specification document are encouraged to join		Harry Lewis
	the IPP Mailing List in order to participate in any discussions of		HUC/003G
	clarification issues and review of registration proposals for		IBM Corporation
	additional attributes and values. In order to reduce spam the		P.O. Box 1900
	mailing list rejects mail from non-subscribers, so you must subscribe		Boulder, CO 80301-9191
	to the mailing list in order to send a question or comment to the
	mailing list.
	10 Appendix A: Description of the Base IPP Documents		Phone: (303) 924-5337
			Fax: (303) 924-9889
			e-mail: harryl@us.ibm.com
			10 Appendix A: Description of the Base IPP Documents
	The base set of IPP documents includes:		The base set of IPP documents includes:
	Design Goals for an Internet Printing Protocol [RFC2567]		Design Goals for an Internet Printing Protocol [RFC2567]
	Rationale for the Structure and Model and Protocol for the Internet		Rationale for the Structure and Model and Protocol for the Internet
	Printing Protocol [RFC2568]		Printing Protocol [RFC2568]
	Internet Printing Protocol/1.1: Model and Semantics [RFC2911]		Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
	Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]		Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
	Internet Printing Protocol/1.1: Implementer's Guide [IPP-IIG]		Internet Printing Protocol/1.1: Implementer's Guide [IPP-IIG]
	Mapping between LPD and IPP Protocols [RFC2569]		Mapping between LPD and IPP Protocols [RFC2569]
	The "Design Goals for an Internet Printing Protocol" document takes a		The "Design Goals for an Internet Printing Protocol" document takes a
	broad look at distributed printing functionality, and it enumerates		broad look at distributed printing functionality, and it enumerates
End of changes. 52 change blocks.
	116 lines changed or deleted		97 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/