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

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

Delivery-Date: Thu, 02 Jul 1998 00:56:58 -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 AAA26714 for <ietf-archive@ietf.org>; Thu, 2 Jul 1998 00:56:57 -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 AAA19868 for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 00:59:15 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id AAA12605 for <ietf-archive@cnri.reston.va.us>; Thu, 2 Jul 1998 00:56:51 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Thu, 2 Jul 1998 00:51:54 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id AAA12044 for ipp-outgoing; Thu, 2 Jul 1998 00:46:29 -0400 (EDT)
Message-Id: <199807020446.AAA05817@spot.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1 BC 08 05 7F 42 81 7E 90
To: ipp@pwg.org
Subject: IPP> regarding "ipp:" (I spoke too soon...)
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Thu, 02 Jul 1998 00:46:24 -0400
Sender: owner-ipp@pwg.org

On a careful re-reading the list of resolutions for the IPP 
documents, I was surprised to see that the WG had decided not 
to adopt an "ipp:" URL prefix.  (I was out of town last
week and unable to follow the list as closely as I would
have liked.)

In my earlier poll of IESG there was strong agreement that both
a separate port and a new URL prefix were needed, though the
questions were not asked separately  We're having a phone 
conference on July 2 (today or tomorrow depending on your
current time zone), so I'll ask them again just to be sure.

Other than the issue with interoperability with http proxies 
(which are easily addressed), I'd like to know what the
technical problems were with using an "ipp:" prefix.  I've
reviewed most of the list discussion since the teleconference
that I participated in, and didn't see any good explanation
of why this would cause problems.

Keith