[IPP] Fwd: Protocol Action: 'Internet Printing Protocol/1.1: Encoding and Transport' to Proposed Standard (draft-sweet-rfc2910bis-09.txt)

[IPP] Fwd: Protocol Action: 'Internet Printing Protocol/1.1: Encoding and Transport' to Proposed Standard (draft-sweet-rfc2910bis-09.txt)

Michael Sweet msweet at apple.com
Mon Aug 8 18:35:19 UTC 2016


One half of IPP/1.1 has been approved!


> Begin forwarded message:
> 
> From: The IESG <iesg-secretary at ietf.org>
> Subject: Protocol Action: 'Internet Printing Protocol/1.1: Encoding and Transport' to Proposed Standard (draft-sweet-rfc2910bis-09.txt)
> Date: August 8, 2016 at 2:29:39 PM EDT
> To: IETF-Announce <ietf-announce at ietf.org>
> Cc: Barry Leiba <barryleiba at computer.org>, draft-sweet-rfc2910bis at ietf.org, The IESG <iesg at ietf.org>, alexey.melnikov at isode.com, barryleiba at computer.org, rfc-editor at rfc-editor.org
> Resent-From: alias-bounces at ietf.org
> Resent-To: msweet at apple.com, blueroofmusic at gmail.com
> 
> The IESG has approved the following document:
> - 'Internet Printing Protocol/1.1: Encoding and Transport'
>  (draft-sweet-rfc2910bis-09.txt) as Proposed Standard
> 
> This document has been reviewed in the IETF but is not the product of an
> IETF Working Group.
> 
> The IESG contact person is Alexey Melnikov.
> 
> A URL of this Internet Draft is:
> https://datatracker.ietf.org/doc/draft-sweet-rfc2910bis/
> 
> 
> 
> 
> Technical Summary
> 
>    The 2910bis and 2911bis documents are making necessary updates to the Internet Printing
> Protocol that was produced by the IPP working group and published as RFCs 2910 and 2911
> in 2000.  The updates bring the protocol up to date with what is currently deployed.
> 
> Working Group Summary
> 
>   This is not a product of any WG.
> 
> Document Quality
> 
>   After the IPP working group was closed down in 2000, further work on Internet printing moved
> out of the IETF and into the IEEE-ISTO's Printer Working Group (IPP WG).  These documents
> represent the work of that group, which is where all the operators/implementors of IPP do
> their work (they are, basically, the ones who worked in the IETF IPP working group when it
> was active).  The documents have consensus of that group, and the consensus and implementation
> are solid and broad.
> 
>   The documents are being brought back into the IETF for last call and publication because
> they are updating (replacing) IETF Standards Track documents.  There is no active work in the
> IETF on Internet printing now.
> 
> Personnel
> 
>  Barry Leiba is the document shepherd.  Alexey Melnikov is the responsible Area Director.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer



More information about the ipp mailing list