Re: IPP> clarification needed re: "ipp:" proposal
Randy Turner <rturner@sharplabs.com> Sat, 04 July 1998 00:57 UTC
Delivery-Date: Fri, 03 Jul 1998 20:57:20 -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 UAA29571
for <ietf-archive@ietf.org>; Fri, 3 Jul 1998 20:57:08 -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 UAA25981
for <ietf-archive@cnri.reston.va.us>; Fri, 3 Jul 1998 20:59:29 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com
(8.7.5/8.7.3) with SMTP id UAA18151 for <ietf-archive@cnri.reston.va.us>;
Fri, 3 Jul 1998 20:57:07 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Fri, 3 Jul 1998 20:52:34 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id
UAA17545 for ipp-outgoing; Fri, 3 Jul 1998 20:50:29 -0400 (EDT)
Message-Id: <199807040050.RAA27752@mail.pacifier.com>
X-Sender: rturner@webmail.sharplabs.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Fri, 03 Jul 1998 17:45:23 -0700
To: Keith Moore <moore@cs.utk.edu>, Tom Hastings <hastings@cp10.es.xerox.com>
From: Randy Turner <rturner@sharplabs.com>
Subject: Re: IPP> clarification needed re: "ipp:" proposal
Cc: Keith Moore <moore@cs.utk.edu>, ipp@pwg.org, moore@cs.utk.edu
In-Reply-To: <199807032351.TAA21523@spot.cs.utk.edu>
References: <Your message of "Fri, 03 Jul 1998 13:26:17 PDT."
<3.0.5.32.19980703132617.0093ea50@garfield>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ipp@pwg.org
What Larry and I worked on was a quick brief of what we thought were the major elements of the proposal. It was not an I-D. If sufficient interest exists in pursuing the proposal (by the WG, IESG, or anyone else), then we will definitely translate the brief into a draft. The I-D would outline the exact details, however just FYI, I believe either "ipp" or "http" schemes MAY be included, but this is dependent upon the means used to determine the URL in the first place. The administrator of such a service would publish which ever URL was appropriate for how his/her server is configured. Randy At 07:51 PM 7/3/98 -0400, Keith Moore wrote: >On re-reading the proposal again, I realize that I might have misunderstood >it. The proposal doesn't seem to say whether http: URLs are allowed in IPP >protocol elements (as opposed to HTTP request headers when talking to >a proxy.) On earlier readings I thought it had said that http: would be >allowed. > >So it would help to have the proposal explicitly state whether ipp: >URLs (SHOULD|MUST) be used in IPP protocol elements when referring to >printer or job objects, and whether http: URLs (MAY|SHOULD NOT|MUST NOT) >be used. And if http: URLs are going to be allowed at this level, >please explain why they are needed or useful. > >thanks, > >Keith >
- Re: IPP> clarification needed re: "ipp:" proposal Randy Turner
- Re: IPP> clarification needed re: "ipp:" proposal Keith Moore
- Re: IPP> clarification needed re: "ipp:" proposal Randy Turner
- Re: IPP> clarification needed re: "ipp:" proposal Keith Moore
- RE: IPP> clarification needed re: "ipp:" proposal Paul Moore