Internet Printing Protocol/1.1 to Internet Standard
status-change-change-ipp-to-internet-standard-00

The following approval message was sent
From: The IESG
To: IETF-Announce 
Cc: The IESG ,
    Barry Leiba ,
    draft-sweet-rfc2911bis@ietf.org,
    draft-sweet-rfc2910bis@ietf.org,
    barryleiba@computer.org,
    rfc-editor@rfc-editor.org
Subject: Protocol Action: Internet Printing Protocol/1.1: Encoding and Transport to Internet Standard

The IESG has approved changing the status of the following document:
- Internet Printing Protocol/1.1: Encoding and Transport
  (rfc8010) to Internet Standard

This protocol action is documented at:
https://datatracker.ietf.org/doc/status-change-change-ipp-to-internet-standard/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc8010/

Status Change Details:

As specified in RFC 6410:

  (1) There are at least two independent interoperating implementations
      with widespread deployment and successful operational experience.

      - Over 98% of all digital network printers shipped in the last
      decade support IPP/1.1 (originally defined in RFC 2910/2911,
      September 2000).

  (2) There are no errata against the specification that would cause a
      new implementation to fail to interoperate with deployed ones.

      - There are currently no errata against RFC 8010/8011.

  (3) There are no unused features in the specification that greatly
      increase implementation complexity.

      - There are no unused features in RFC 8010/8011.

      - The Purge-Jobs operation (from RFC 2911) is DEPRECATED in
      RFC 8011 (page 73) with "SHOULD NOT support" because it
      destroys Printer accounting implementation.  This operation
      has never been widely implemented in digital network printers.

      - The Restart-Job operation (from RFC 2911) is DEPRECATED in
      RFC 8011 (page 89) with "SHOULD NOT support" because it
      destroys Printer accounting implementation.  This operation
      has never been widely implemented in digital network printers.

  (4) If the technology required to implement the specification
      requires patented or otherwise controlled technology, then the
      set of implementations must demonstrate at least two independent,
      separate and successful uses of the licensing process.

      - There is no patented or otherwise controlled technology that
      is required to implement IPP/1.1 per RFC 8010/8011.

Personnel

  Alexey Melnikov is the responsible Area Director.

The following approval message was sent
From: The IESG
To: IETF-Announce 
Cc: The IESG ,
    Barry Leiba ,
    draft-sweet-rfc2911bis@ietf.org,
    draft-sweet-rfc2910bis@ietf.org,
    barryleiba@computer.org,
    rfc-editor@rfc-editor.org
Subject: Protocol Action: Internet Printing Protocol/1.1: Model and Semantics to Internet Standard

The IESG has approved changing the status of the following document:
- Internet Printing Protocol/1.1: Model and Semantics
  (rfc8011) to Internet Standard

This protocol action is documented at:
https://datatracker.ietf.org/doc/status-change-change-ipp-to-internet-standard/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc8011/

Status Change Details:

As specified in RFC 6410:

  (1) There are at least two independent interoperating implementations
      with widespread deployment and successful operational experience.

      - Over 98% of all digital network printers shipped in the last
      decade support IPP/1.1 (originally defined in RFC 2910/2911,
      September 2000).

  (2) There are no errata against the specification that would cause a
      new implementation to fail to interoperate with deployed ones.

      - There are currently no errata against RFC 8010/8011.

  (3) There are no unused features in the specification that greatly
      increase implementation complexity.

      - There are no unused features in RFC 8010/8011.

      - The Purge-Jobs operation (from RFC 2911) is DEPRECATED in
      RFC 8011 (page 73) with "SHOULD NOT support" because it
      destroys Printer accounting implementation.  This operation
      has never been widely implemented in digital network printers.

      - The Restart-Job operation (from RFC 2911) is DEPRECATED in
      RFC 8011 (page 89) with "SHOULD NOT support" because it
      destroys Printer accounting implementation.  This operation
      has never been widely implemented in digital network printers.

  (4) If the technology required to implement the specification
      requires patented or otherwise controlled technology, then the
      set of implementations must demonstrate at least two independent,
      separate and successful uses of the licensing process.

      - There is no patented or otherwise controlled technology that
      is required to implement IPP/1.1 per RFC 8010/8011.

Personnel

  Alexey Melnikov is the responsible Area Director.

[Ballot comment]
I need to check "ipps" service name assignment (which is supposed to be an alias for "ipp") with authors. This will be done as a separate Management Item, as strictly speaking it is not related to these 2 documents.

The following Last Call announcement was sent out (ends 2018-06-06):

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call: Internet Printing Protocol/1.1 to Internet Standard


The IESG has received a request from IEEE-ISTO Printer Working Group (PWG) to make the
following status changes:

- RFC8011 from Proposed Standard to Internet Standard
    (Internet Printing Protocol/1.1: Model and Semantics)

- RFC8010 from Proposed Standard to Internet Standard
    (Internet Printing Protocol/1.1: Encoding and Transport)

The supporting document for this request can be found here:

https://datatracker.ietf.org/doc/status-change-change-ipp-to-internet-standard/

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-06-06. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

The affected documents can be obtained via
https://datatracker.ietf.org/doc/rfc8011/
https://datatracker.ietf.org/doc/rfc8010/

IESG discussion of this request can be tracked via
https://datatracker.ietf.org/doc/status-change-change-ipp-to-internet-standard/ballot/