[IPP] Fwd: [Editorial Errata Reported] RFC2910 (4100)

[IPP] Fwd: [Editorial Errata Reported] RFC2910 (4100)

[IPP] Fwd: [Editorial Errata Reported] RFC2910 (4100)

Michael Sweet msweet at apple.com
Fri Sep 5 15:50:46 UTC 2014



Begin forwarded message:

> From: RFC Errata System <rfc-editor at rfc-editor.org>
> Subject: [Editorial Errata Reported] RFC2910 (4100)
> Date: September 5, 2014 at 11:44:08 AM EDT
> To: robert.herriot at pahv.xerox.com, sbutler at boi.hp.com, pmoore at peerless.com, jwenn at cp10.es.xerox.com, tom.hastings at alum.mit.edu, robert.herriot at pahv.xerox.com, barryleiba at computer.org, presnick at qti.qualcomm.com, carl at manros.com
> Cc: msweet at apple.com, rfc-editor at rfc-editor.org
> 
> The following errata report has been submitted for RFC2910,
> "Internet Printing Protocol/1.1: Encoding and Transport".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2910&eid=4100
> 
> --------------------------------------
> Type: Editorial
> Reported by: Michael Sweet <msweet at apple.com>
> 
> Section: 8.1.2
> 
> Original Text
> -------------
>   IPP Printers SHOULD support Transport Layer Security (TLS) [RFC2246]
>   for Server Authentication and Operation Privacy. IPP Printers MAY
>   also support TLS for Client Authentication.  If an IPP Printer
>   supports TLS, it MUST support the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
>   cipher suite as mandated by RFC 2246 [RFC2246].  All other cipher
>   suites are OPTIONAL.  An IPP Printer MAY support Basic Authentication
>   (described in HTTP/1.1 [RFC2617])  for Client Authentication if the
>   channel is secure. TLS with the above mandated cipher suite can
>   provide such a secure channel.
> 
>   If a IPP client supports TLS, it MUST support the
>   TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite as mandated by RFC
>   2246 [RFC2246].  All other cipher suites are OPTIONAL.
> 
> 
> Corrected Text
> --------------
>   IPP Printers SHOULD support Transport Layer Security (TLS) [RFC2246]
>   for Server Authentication and Operation Privacy. IPP Printers MAY
>   also support TLS for Client Authentication.  An IPP Printer MAY
>   support Basic Authentication (described in HTTP/1.1 [RFC2617]) for
>   Client Authentication if the channel is secure.
> 
> 
> Notes
> -----
> Per the PWG IPP WG discussions at the August 2014 F2F, any mention of cipher suites in RFC 2910 is inappropriate. In particular, the cipher suite mentioned is no longer mandatory in TLS/1.2.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC2910 (draft-ietf-ipp-protocol-v11-06)
> --------------------------------------
> Title               : Internet Printing Protocol/1.1: Encoding and Transport
> Publication Date    : September 2000
> Author(s)           : R. Herriot, Ed., S. Butler, P. Moore, R. Turner, J. Wenn
> Category            : PROPOSED STANDARD
> Source              : Internet Printing Protocol
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4881 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140905/07693aee/attachment.p7s>


More information about the ipp mailing list