IPP> RFC 3117 misrepresents IPP

IPP> RFC 3117 misrepresents IPP

McDonald, Ira IMcDonald at crt.xerox.com
Sun Nov 18 20:38:15 EST 2001


Hi folks,                                      Sunday (18 November 2001)

I was just reading RFC 3117 "On the Design of Application Protocols"
(Nov 2001) by Marshall Rose.  It is, in fact, about the design process
followed for BEEP (RFC 3080).

RFC 3117 makes a series of statements about the design of IPP over
HTTP/1.1 and the IPP asynchronous notifications which are all WRONG.

RFC 3117 also references the OBSOLETE RFC 2565 (IPP/1.0 Protocol and
Encoding) rather than the Proposed Standard RFC 2910 (IPP/1.1 P/E).

Of course IPP documents are routinely held up for references.  But when
some people write an RFC obviously the same checks don't apply.

Unfortunately RFC 3117 is likely to be far more widely read than the
IETF IPP 'standards track' documents.

Cheers,
- Ira McDonald
  High North Inc



More information about the Ipp mailing list