IETF Logo Mail Archive

Re: IPP> regarding "ipp:" (I spoke too soon...)

Keith Moore <moore@cs.utk.edu> Thu, 02 July 1998 18:51 UTC

Delivery-Date: Thu, 02 Jul 1998 14:51:13 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id OAA09737 for <ietf-archive@ietf.org>; Thu, 2 Jul 1998 14:51:12 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id OAA22785 for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 14:53:31 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id OAA02208 for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 14:51:07 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Thu, 2 Jul 1998 14:47:06 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id OAA01635 for ipp-outgoing; Thu, 2 Jul 1998 14:43:17 -0400 (EDT)
Message-Id: <199807021843.OAA11349@spot.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Moore <paulmo@microsoft.com>
cc: "'Keith Moore'" <moore@cs.utk.edu>, ipp@pwg.org, moore@cs.utk.edu
Subject: Re: IPP> regarding "ipp:" (I spoke too soon...)
In-reply-to: Your message of "Thu, 02 Jul 1998 11:24:48 PDT." <CB6657D3A5E0D111A97700805FFE6587BF6E2C@red-msg-51.dns.microsoft.com>
Date: Thu, 02 Jul 1998 14:43:05 -0400
Sender: owner-ipp@pwg.org

> Not so. Every IPP packet is a fully conformant HTTP packet. We are not
> inventing a new protocol in the scheme sense. 

That's not the way IESG sees it.  IPP is chartered to develop a protocol.

If you are having problems that no other working group is having, 
because you're layering over http, maybe you're taking the wrong approach.

> Point any lan sniffer at an
> IPP exchange and ask it what the protocol is - it will say its HTTP. 

This could be considered a bug with IPP.

> The argument you are using would say that SMTP is not TCP/IP. 
> IPP is layered on top of HTTP - same way that form-based upload is.

HTTP is an application by itself.  TCP/IP is not.  
IPP is trying to layer one application on top of another.

Keith

v2.8.7 | Report a Bug | By Email