Actually, I thought that it would be easier to get a firewall administrator
to let in a harmless trickle of IPP notifications over HTTP, if they
couldn't get confused with other traffic. Most administrators don't let
HTTP in, only HTTP out, correct?
I have been told that different firewalls have different filter mechanisms,
some on ports, some on MIME types, and some on HTTP methods (needs to be
verified). Therefore, I thought that making the port, MIME types, and HTTP
method all different from ordinary HTTP web access requests would give the
administrator the most flexibility to allow IPP Notifications where he/she
might not allow other HTTP protocol requests.
I couldn't agree more with Ron on getting IETF IESG feedback and input on
Lets get IETF IESG input on this. Those attending the IETF meeting next
week in Washington, please get this feedback.
Our INTERNET-DRAFT on this delivery method that uses HTTP is:
We'd appreciate your feedback on this delivery method.
From: Ron Bergman [mailto:rbergma at mailgate.dpc.com]
Sent: Thursday, November 04, 1999 08:12
To: Hastings, Tom N
Subject: Re: IPP> NOT - How about using a new HTTP method for the "IPP
NotificationDelivery Protocol over HTTP"
Doesn't defining a new scheme, port, and method make it harder and less
that a system administrator will configure the firewall for IPP
I still believe that we should be honest with the IETF and get their input
this issue before we go any further. We are making the assumption that this
will be a requirement of the IETF. Let's not assume!
Hitachi Koki Imaging Solutions
"Hastings, Tom N" wrote:
>> In your proposal for the "IPP Notification Delivery Protocol over HTTP",
> need to do whatever we can to make it most likely that fire wall
> administrators will allow the notifications to flow out across the
> that contains the IPP Printer AND flow across the firewall that contains
> Notification Recipient.
>> In addition to using a new scheme (ipp-ntfy) and a new default port (???),
> how about also using a new HTTP method for the "IPP Notification Delivery
> Protocol over HTTP"? Perhaps we could call the new method "notify" or