Re: IPP> regarding "ipp:" (I spoke too soon...)
Keith Moore <moore@cs.utk.edu> Thu, 02 July 1998 21:06 UTC
Delivery-Date: Thu, 02 Jul 1998 17:06:27 -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 RAA11058
for <ietf-archive@ietf.org>; Thu, 2 Jul 1998 17:06:26 -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 RAA23452
for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 17:08:44 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com
(8.7.5/8.7.3) with SMTP id RAA08380 for <ietf-archive@cnri.reston.va.us>;
Thu, 2 Jul 1998 17:06:20 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Thu, 2 Jul 1998 17:02:11 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id
QAA07473 for ipp-outgoing; Thu, 2 Jul 1998 16:52:41 -0400 (EDT)
Message-Id: <199807022051.QAA11639@spot.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Carl-Uno Manros <manros@cp10.es.xerox.com>
cc: Keith Moore <moore@cs.utk.edu>, paf@swip.net, 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 12:37:40 PDT."
<3.0.5.32.19980702123740.00c13700@garfield>
Date: Thu, 02 Jul 1998 16:51:10 -0400
Sender: owner-ipp@pwg.org
> >HTTP is an application by itself. TCP/IP is not. > >IPP is trying to layer one application on top of another. > > In a sense you are right, but in effect IPP is sending MIME > packages over HTTP. This has been our stragegy for more than a year. > Is MIME over SMTP considered a separate application that needs > it's own scheme? It wasn't last time I checked. SMTP is not an application; end users don't use SMTP by itself. MIME is only the latest in a series of versions of the internet message format, which SMTP was tailor-made to carry. But there is at least some precedent. ARPAnet email was originally implemented by sending text messages over FTP and depositing them in a file named after the recipient. But this didn't work very well, and was soon replaced. Some TOPS-20 people layered their SMTP implementations on top of telnet support in their kernel, but eventually this turned out to be a Bad Idea. All of this was long before the net had tens of millions of users, back when casual experimentation had fewer risks associated with it. It was also before there was a formal standardization process. The belief in this case is that IPP is different enough from ordinary HTTP traffic that the two should be distinguished. > BTW, who determines whether an application can or cannot be layered > on top of another? If is you who decides, we would have liked to hear > this kind of strong objection much earlier in the project. Ultimately, the IESG determines what is acceptable in an Internet standards track protocol, with provision for appeal to the IAB. I agree that earlier notification would have been better. But IPP is trying to do something radically different than most other working groups (even though it intended to be conservative), and some of the implications of its approach were not apparent until recently. > If we are going to have these kind of discussions, it seems to me > that the IAB should get involved, as they are rather fundamental > Internet design decisions. Re-using existing infra-structure or not > seems to be one important discussion point. The IAB Chair participated in today's IESG conference call. A more detailed response will be forthcoming, and the IAB Chair has requested that IAB be in on the discussions. Keith
- IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- RE: IPP> regarding "ipp:" (I spoke too soon...) Paul Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- RE: IPP> regarding "ipp:" (I spoke too soon...) Paul Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Tom Hastings
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Scott Isaacson
- RE: IPP> regarding "ipp:" (I spoke too soon...) Josh Cohen
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Scott Lawrence
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Randy Turner
- Re: IPP> regarding "ipp:" (I spoke too soon...) Carl-Uno Manros
- Re: IPP> regarding "ipp:" (I spoke too soon...) Robert Herriot
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- RE: IPP> regarding "ipp:" (I spoke too soon...) Josh Cohen
- Re: IPP> regarding "ipp:" (I spoke too soon...) Jay Martin
- Re: IPP> regarding "ipp:" (I spoke too soon...) Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Tom Hastings
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Tom Hastings
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Keith Moore
- IPP> clarification needed re: "ipp:" proposal Keith Moore
- Re: IPP> regarding "ipp:" (I spoke too soon...) papowell
- Re: IPP> regarding "ipp:" (I spoke too soon...)[a… Tom Hastings
- RE: IPP> regarding "ipp:" (I spoke too soon...) Ron Bergman
- IPP> On clarifying the proposal for a new IPP sch… Tom Hastings
- IPP> Re: On clarifying the proposal for a new IPP… Keith Moore
- Re: IPP> Re: On clarifying the proposal for a new… Carl-Uno Manros