From: Int-area <int-area-boun...@ietf.org> on behalf of Michael Sweet 
<msweet=40msweet....@dmarc.ietf.org>
Sent: 07 April 2022 15:11
Re: [Int-area] [Iotops] Last Call: Moving TPC.INT and NSAP.INT infrastructure 
domains to historic

Michael

I am well familiar with the work of IPP in the IETF.  You mention MIBs which I 
know of.  Is there anything similar in YANG?

Tom Petch


Toerless,

> On Apr 7, 2022, at 5:38 AM, Toerless Eckert <t...@cs.fau.de> wrote:
> ...
> 2.) RFC1528 from Experimental to Historic
>
> I am not aware of a better, interoperable standard solution for remote 
> printing (or should
> i say Internet FAX ?). Instead it feels to me as if every printer vendor has 
> started
> its own proprietary remote-printing cloud-service. I hope i am wrong 
> (pointers please),
> but if not, then i fear this decade old experiment is still the best we have ?

I don't know if this was meant as serious?  But FWIW the IETF published the 
Internet Printing Protocol (STD 92) more than 2 decades ago, and it is used by 
nearly every network printer ("billions of printers") and most "cloud" printing 
services (including Microsoft's Azure-based Universal Print Service).  Any 
printer with "AirPrint", "IPP Everywhere", "Mopria", or "Wi-Fi Direct" on the 
box supports IPP.

The Printer Working Group (who is the current steward of IPP and the variable 
SNMP printing MIBs) has also defined numerous IPP extensions, including 
standards for cloud printing and Internet fax using a streamable subset of PDF.

So, assuming somebody doesn't just email you a file you can print it quite 
easily using a single, standard protocol.

[But of course telephone-based fax still hasn't died - boggles the mind...]

________________________
Michael Sweet




_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to