Re: IPP> Where do we stand in the debate?
Randy Turner <rturner@sharplabs.com> Wed, 15 July 1998 16:12 UTC
Delivery-Date: Wed, 15 Jul 1998 12:12:24 -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 MAA19090
for <ietf-archive@ietf.org>; Wed, 15 Jul 1998 12:12:19 -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 MAA15524
for <ietf-archive@cnri.reston.va.us>; Wed, 15 Jul 1998 12:12:17 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com
(8.7.5/8.7.3) with SMTP id MAA25809 for <ietf-archive@cnri.reston.va.us>;
Wed, 15 Jul 1998 12:12:18 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Wed, 15 Jul 1998 12:05:18 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id
MAA25089 for ipp-outgoing; Wed, 15 Jul 1998 12:00:08 -0400 (EDT)
Message-Id: <199807151602.JAA06387@mail.pacifier.com>
X-Sender: rturner@webmail.sharplabs.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Wed, 15 Jul 1998 08:56:20 -0700
To: Harry Lewis <harryl@us.ibm.com>
From: Randy Turner <rturner@sharplabs.com>
Subject: Re: IPP> Where do we stand in the debate?
Cc: ipp@pwg.org
In-Reply-To: <5030100023168486000002L062*@MHS>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipp@pwg.org
At 11:02 AM 7/15/98 -0400, you wrote: >Carl-Uno. thank you very much for the summary. This is quite helpful. I would >like to seek even further clarification. > >>"ipp:" will NEVER be used on the HTTP layer. > >Is this the same as saying that (by example) >ipp://my.printer.com will ALWAYS mean >http://my.printer.com:631 >and (by further example) >ipp://my.printer.com:444 will mean >http://my.printer.com:444? > > >Harry Lewis - IBM Printing Systems > I don't think that's what the compromise says. The quick take is, 1. "Published" URLs (that users and administrators will see) will be "ipp:" URLs. 2. Within application/ipp body parts, "ipp:" URLs will be used to reference IPP printer and job objects. 3. But you will never see "ipp:" URLs in HTTP 1.1 request headers. This is very close to our usage model published last week at Monterey. Randy
- IPP> Where do we stand in the debate? Carl-Uno Manros
- Re: IPP> Where do we stand in the debate? Harry Lewis
- Re: IPP> Where do we stand in the debate? Randy Turner