IPP> Yet another revised set of IPP/1.1 Model & Semantics and IPP/1.1 Encoding and Transport I-Ds

IPP> Yet another revised set of IPP/1.1 Model & Semantics and IPP/1.1 Encoding and Transport I-Ds

IPP> Yet another revised set of IPP/1.1 Model & Semantics and IPP/1.1 Encoding and Transport I-Ds

Manros, Carl-Uno B cmanros at cp10.es.xerox.com
Tue Mar 7 13:59:56 EST 2000


Gentlemen,

I recently sent you a message with the following introduction:

"I was alerted early this year that IANA had questioned why there wasn't an
IANA section in the IPP/1.1 Encoding & Transport draft. The original reason
was that all the relevant text on IANA registrations was defined in the
IPP/1.1 Model & Semantics draft. However, we decided to add an IANA section
in the IPP/1.1 Encoding & Transport draft and also decided to improve a bit
on the IANA section in the IPP/1.1 Model & Semantics document to make sure
that we had a complete and watertight description. In essence, the rules now
state that there are certain code ranges reserved for future standards track
extensions. In some cases there are also code ranges for vendor extensions.
Both kinds need to be registered by IANA. For completeness, we also added a
new section on I18N in the IPP/1.1 Encoding & Transport draft, which
basically references back to the IPP/1.1 Model & Semantics draft, where
these details are described.

While updating the IPP/1.1 Model & Semantics draft (sections 6 and 11), we
also folded in the revised version of Appendix C, which was earlier sent to
the IESG as a separate draft (draft-ietf-ipp-media-engineering-00.txt)
asking it to replace the old Appendix C before publishing as RFC. A few
minor editorial fixes were also made, but absolutely no changes were made to
the technical content, which would cause a new technical review of the
drafts. It is our hope that these revisions will help IESG and IANA in the
continued review process."

It turned out that the drafts I pointed you to last time had some ASCII 
formatting errors, in particular missing page breaks, so the editors have 
produced new versions to use instead. Sorry for any extra trouble this 
may cause you in keeping track of things.

Here are the revised details:

Replacing <draft-ietf-ipp-protocol-v11-03.txt and -04.text> is:

	Title		: Internet Printing Protocol/1.1: Encoding and
Transport
	Author(s)	: R. Herriot, S. Butler, P. Moore, R. Turner, J.
Wenn
	Filename	: draft-ietf-ipp-protocol-v11-05.txt
	Pages		: 44
	Date		: 06-Mar-00
	A URL for this Internet-Draft is:
	
http://www.ietf.org/internet-drafts/draft-ietf-ipp-protocol-v11-05.txt

Replacing <draft-ietf-ipp-model-v11-04.txt and -05.txt> and
<draft-ietf-ipp-media-engineering-00.txt> is:

	Title		: Internet Printing Protocol/1.1: Model and
Semantics
	Author(s)	: R. de Bry, T. Hastings, R. Herriot, 
                          S. Isaacson, P. Powell
	Filename	: draft-ietf-ipp-model-v11-06.txt
	Pages		: 204
	Date		: 06-Mar-00
	A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipp-model-v11-06.txt

Hope to hear some news about these drafts soon considering that a number of
IPP/1.1 implementations are already under way, and one company has already 
released products. The latter company did not want to go out with an
"experimental" IPP/1.0 product, so have waited since last summer for the 
real IPP standards track RFCs to come out. Apparently they gave up waiting.

Regards,

Carl-Uno Manros
Chair of IETF IPP WG

Principal Engineer - Xerox Architecture Center - Xerox Corporation
701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
Phone +1-310-333 8273, Fax +1-310-333 5514
Email: manros at cp10.es.xerox.com 



More information about the Ipp mailing list