Skip to main content

Network News Transfer Protocol (NNTP) Extension for Compression
draft-murchison-nntp-compress-06

Revision differences

Document history

Date Rev. By Action
2017-01-24
06 (System) RFC Editor state changed to AUTH48-DONE from AUTH48
2017-01-11
06 (System) RFC Editor state changed to AUTH48 from RFC-EDITOR
2016-12-13
06 (System) RFC Editor state changed to RFC-EDITOR from EDIT
2016-12-12
06 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2016-12-12
06 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2016-12-08
06 (System) IANA Action state changed to In Progress from Waiting on Authors
2016-12-07
06 (System) IANA Action state changed to Waiting on Authors from In Progress
2016-12-07
06 (System) IANA Action state changed to In Progress from Waiting on Authors
2016-12-06
06 (System) IANA Action state changed to Waiting on Authors
2016-11-30
06 (System) RFC Editor state changed to EDIT
2016-11-30
06 (System) IESG state changed to RFC Ed Queue from Approved-announcement sent
2016-11-30
06 (System) Announcement was received by RFC Editor
2016-11-30
06 Cindy Morgan IESG state changed to Approved-announcement sent from Approved-announcement to be sent::Point Raised - writeup needed
2016-11-30
06 Cindy Morgan IESG has approved the document
2016-11-30
06 Cindy Morgan Closed "Approve" ballot
2016-11-30
06 Cindy Morgan Ballot approval text was generated
2016-11-21
06 Alexey Melnikov [Ballot comment]
Need to possibly create a new IETF mailing list for Expert Reviews (see Section 7.1.2).
2016-11-21
06 Alexey Melnikov Ballot comment text updated for Alexey Melnikov
2016-11-08
06 Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'No Response'
2016-11-03
06 Cindy Morgan IESG state changed to Approved-announcement to be sent::Point Raised - writeup needed from Waiting for Writeup
2016-11-03
06 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko
2016-11-03
06 Spencer Dawkins [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins
2016-11-02
06 Joel Jaeggli [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli
2016-11-02
06 Alia Atlas [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas
2016-11-02
06 Ben Campbell [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell
2016-11-02
06 (System) IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed
2016-11-02
06 Suresh Krishnan [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan
2016-11-02
06 Deborah Brungard [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard
2016-11-02
06 Alissa Cooper [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper
2016-11-01
06 Terry Manderson [Ballot Position Update] New position, No Objection, has been recorded for Terry Manderson
2016-11-01
06 Stephen Farrell
[Ballot comment]

Thanks for taking up the baton that TLS had to drop due to
CRIME!

1.3: I hope the RFC editor can try new …
[Ballot comment]

Thanks for taking up the baton that TLS had to drop due to
CRIME!

1.3: I hope the RFC editor can try new format things to meet
these requests. One question for the authors might be whether
you'd prefer an RFC now or to wait a bit (should a wait be
needed) if tooling needs changes to handle properly
representing folks' names?

2.2.1: the "algorithm" parameter description doesn't seem to
match the example in 2.1 which specifies two algorithms. The
ABNF seems to agree with 2.2.1.
2016-11-01
06 Stephen Farrell [Ballot Position Update] New position, Yes, has been recorded for Stephen Farrell
2016-10-31
06 Francis Dupont Request for Telechat review by GENART Completed: Ready. Reviewer: Francis Dupont.
2016-10-31
06 Kathleen Moriarty
[Ballot comment]
Thank you for addressing the SecDir review:
https://www.ietf.org/mail-archive/web/secdir/current/msg06916.html

And also for letting us know about an upcoming draft that:
'discourages the use of …
[Ballot comment]
Thank you for addressing the SecDir review:
https://www.ietf.org/mail-archive/web/secdir/current/msg06916.html

And also for letting us know about an upcoming draft that:
'discourages the use of TLS-level
compression, thus dealing with authentication layered with a TLS-level
compression method.'
https://www.ietf.org/mail-archive/web/secdir/current/msg06923.html
2016-10-31
06 Kathleen Moriarty [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty
2016-10-31
06 Alvaro Retana [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana
2016-10-31
06 Mirja Kühlewind
[Ballot comment]
"In the case of a conflict between these two documents, [RFC3977] takes precedence."
Really? I'd hope there is no conflict...

And …
[Ballot comment]
"In the case of a conflict between these two documents, [RFC3977] takes precedence."
Really? I'd hope there is no conflict...

And nit? In sec 7: "it MUST use the STARTTLS, AUTHINFO, and COMPRESS commands in that order." and "That is why this specification only prohibits the use of AUTHINFO after COMPRESS." Should this be 'before' instead of 'after'...?
2016-10-31
06 Mirja Kühlewind [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind
2016-10-29
06 Alexey Melnikov Ballot has been issued
2016-10-29
06 Alexey Melnikov [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov
2016-10-29
06 Alexey Melnikov Created "Approve" ballot
2016-10-29
06 Alexey Melnikov Ballot writeup was changed
2016-10-29
06 Alexey Melnikov
Michael Bäuerle  is the document shepherd:

Shepherd writeup (Date: 2016-09-29)
draft-murchison-nntp-compress-05


1) Type of RFC
==============
The document describes a useful extension to NNTP, and …
Michael Bäuerle  is the document shepherd:

Shepherd writeup (Date: 2016-09-29)
draft-murchison-nntp-compress-05


1) Type of RFC
==============
The document describes a useful extension to NNTP, and has already been shown
to be interoperable (implemented in at least a news server and a news client).

The intended category of this document will be "Standards Track".
The intended status of this document will be "Proposed Standard".


2) Document Announcement Write-Up
=================================

Technical Summary
-----------------
Document Shepherd: Michael Baeuerle
(The "ae" in "Baeuerle" is an ASCII transcription for the Umlaut U+00E4)
Area Director    : Alexey Melnikov

This document defines an extension to the Network News Transport Protocol
(NNTP) that allows a connection to be effectively and efficiently compressed
between an NNTP client and server.


Working Group Summary
---------------------
The draft was reviewed by a few people in  and the
UTA WG (but the document is not a work item of the UTA WG, because it is not
in the scope of his charter).


Document Quality
----------------
Server side implementations:
- flnews  has already implemented
  general support in its 0.13 version (released 2015-12-14).
  Full support will be present in the 0.14 version (not yet released,
  but is scheduled to before the end of the year)

Server side implementations:
- INN, a wide-spread news server
  in its 2.6.1 version (not yet released, but is scheduled to before the
  end of the year)
- Cyrus NNTP
  already released in the 2.x series

Interoperability is proven.


3) Briefly describe the review of this document
===============================================
I have supported the creation of this document and I have written the
client side implementation for flnews.


4) Shepherd concerns
====================
No concerns.


5) Further document review
==========================
Perhaps the security team?

For security currently there are at least two relevant aspects defined:
- Compression must be enabled after authentication
- Compression defaults to "off" and the user must explicitly enable it.
  Example: If a program is updated from a version without support to
  a new version with support for compression, the compression should
  not become active automatically (maybe the user has not even noticed
  the new capability and should think about security first).


6) Document issues
==================
The document draft currently states in chapter 7.1:

  [...] private compression algorithms SHOULD begin with "X-".

Best Current Practice defined in RFC 6648 specify that the "X-" prefix
should no longer be used. Simply removing the wording about the special
meaning of "X-" names should be sufficient to match RFC 6648 requirements.

The informative section 3 maybe is too detailed.

Section 3 is marked as informative rather than normative, but section
3.1 uses normative keywords (MUST and SHOULD):
Section 3.1 should become normative because the windows size is relevant
for interoperability of Deflate compression even if the implementation is
not based on zlib.

Section 6 should explicitly note SASL and TLS as "security layers".


7) IPR disclosures
==================
Both authors confirmed that there is no IPR involved.


8) Has an IPR disclosure been filed that references this document?
==================================================================
Nothing known.


9) Consensus of the interested community behind this document?
==============================================================
Currently it is possible to use compression as part of TLS, but TLSv1.3 will
drop support for compression.
There is consensus that an option for NNTP compression should stay available
in the future. The NNTP extension defined in this document will provide
compression support with and without TLS. Potential authentication is done
before compression is activated to ensure that the compression cannot weaken
the security of the authentication steps if TLS is used.


10) Anyone threatened an appeal or otherwise indicated extreme discontent?
==========================================================================
No.


11) ID nits
===========
| == Missing Reference: 'C' is mentioned on line 436, but not defined
|    '[C] AUTHINFO USER fred...'

| == Missing Reference: 'S' is mentioned on line 437, but not defined
|    '[S] 502 DEFLATE compression already active...'

"C" and "S" are direction marks (whether the client "C" or the server "S"
sends the data).

| -- Looks like a reference, but probably isn't: '1' on line 232
|    '[1] If a compression layer is already active, COMPRESS is not a v...'

It's a reference to an internal note. If such references are not allowed,
the text can be reworded to "502 Command unavailable (see text below)".


12) Required formal review criteria
===================================
?


13) Have all references within this document been identified as either
======================================================================
    normative or informative?
    =========================
References that should be moved from informative (8.2) to normative (8.1)
section (Reasons explained at question 6):
- RFC 1951 "DEFLATE Compressed Data Format Specification version 1.3"

References that should be moved from normative (8.1) to informative (8.2)
section (Reason: TLS is optional, NNTP can be used without it):
- RFC 4642 "Using Transport Layer Security (TLS) with Network News Transfer
            Protocol (NNTP)"


14) Normative references to documents that are not ready for advancement?
=========================================================================
None.


15) Are there downward normative references references (see RFC 3967)?
======================================================================
RFC 1951 stated above has state "informational", but is important for
interoperability.


16) Will publication of this document change status of any existing RFCs?
=========================================================================
No.


17) Document Shepherd's review of the IANA considerations section
=================================================================
See question 6 for reserved namespace.

The protocol extension (COMPRESS) that the document makes is associated with
the appropriate reservation in IANA registries. Any referenced IANA registries
have been clearly identified.

Newly created IANA registry for NNTP compression algorithms include a detailed
specification of the initial contents for the registry. Allocations procedures
for future registrations are defined. A reasonable name for the new registry
has been suggested.


18) IANA registries that require Expert Review for future allocations
=====================================================================
None.


19) Reviews and automated checks performed by to validate sections of the
=========================================================================
    document written in a formal language
    =====================================
None.
2016-10-27
06 Jean Mahoney Request for Telechat review by GENART is assigned to Francis Dupont
2016-10-27
06 Jean Mahoney Request for Telechat review by GENART is assigned to Francis Dupont
2016-10-26
06 (System) IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed
2016-10-26
06 Julien ÉLIE New version available: draft-murchison-nntp-compress-06.txt
2016-10-26
06 (System) New version approved
2016-10-26
05 (System) Request for posting confirmation emailed to previous authors: "Kenneth Murchison" , "Julien Elie"
2016-10-26
05 Julien ÉLIE Uploaded new revision
2016-10-15
05 Alexey Melnikov Placed on agenda for telechat - 2016-11-03
2016-10-10
05 (System) IESG state changed to Waiting for Writeup from In Last Call
2016-10-07
05 (System) IANA Review state changed to IANA OK - Actions Needed from IANA - Review Needed
2016-10-07
05 Sabrina Tanamal
(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-murchison-nntp-compress-05.txt. If any part of this review is inaccurate, please let …
(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-murchison-nntp-compress-05.txt. If any part of this review is inaccurate, please let us know.

Upon approval of this document, we understand that there are two registry actions to complete:

First, a new registry is to be created called the NNTP Compression Algorithm Registry. The new registry is to be added to the existing list of all IANA maintained protocol registries and located at:

http://www.iana.org/assignments/nntp-compression-algorithms/

The new registry will be managed via First Come, First Served as defined by RFC 5226.

There are initial registrations in the new registry as follows:

Algorithim Intended
Name Usage Reference
---------------+------------------------+-------------------
DEFLATE COMMON [ RFC-to-be ]

Second, in the NNTP capability labels registry contained in the Network News Transfer Protocol (NNTP) Parameters registry located at:

https://www.iana.org/assignments/nntp-parameters/

a single, new capability label is to be registered as follows:

Label: COMPRESS
Meaning: NNTP connection compression
Reference: [ RFC-to-be ]

We understand that these are the only actions required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.


Thank you,

Sabrina Tanamal
IANA Services Specialist
2016-09-26
05 Francis Dupont Request for Last Call review by GENART Completed: Ready. Reviewer: Francis Dupont.
2016-09-22
05 Tero Kivinen Request for Last Call review by SECDIR Completed: Has Nits. Reviewer: Barry Leiba.
2016-09-21
05 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Tina Tsou
2016-09-21
05 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Tina Tsou
2016-09-15
05 Jean Mahoney Request for Last Call review by GENART is assigned to Francis Dupont
2016-09-15
05 Jean Mahoney Request for Last Call review by GENART is assigned to Francis Dupont
2016-09-15
05 Tero Kivinen Request for Last Call review by SECDIR is assigned to Barry Leiba
2016-09-15
05 Tero Kivinen Request for Last Call review by SECDIR is assigned to Barry Leiba
2016-09-12
05 Cindy Morgan IANA Review state changed to IANA - Review Needed
2016-09-12
05 Cindy Morgan
The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: alexey.melnikov@isode.com, draft-murchison-nntp-compress@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Network News …
The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: alexey.melnikov@isode.com, draft-murchison-nntp-compress@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Network News Transfer Protocol (NNTP) Extension for Compression) to Proposed Standard


The IESG has received a request from an individual submitter to consider
the following document:
- 'Network News Transfer Protocol (NNTP) Extension for Compression'
  as Proposed 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 2016-10-10. 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.

Abstract


  This document defines an extension to the Network News Transport
  Protocol (NNTP) that allows a connection to be effectively and
  efficiently compressed between an NNTP client and server.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-murchison-nntp-compress/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-murchison-nntp-compress/ballot/


No IPR declarations have been submitted directly on this I-D.




2016-09-12
05 Cindy Morgan IESG state changed to In Last Call from Last Call Requested
2016-09-12
05 Alexey Melnikov Last call was requested
2016-09-12
05 Alexey Melnikov Last call announcement was generated
2016-09-12
05 Alexey Melnikov Ballot approval text was generated
2016-09-12
05 Alexey Melnikov Ballot writeup was generated
2016-09-12
05 Alexey Melnikov IESG state changed to Last Call Requested from AD Evaluation
2016-09-12
05 Alexey Melnikov Changed consensus to Yes from Unknown
2016-09-08
05 Alexey Melnikov IESG state changed to AD Evaluation from Publication Requested
2016-09-07
05 Alexey Melnikov Responsible AD changed to Alexey Melnikov
2016-09-07
05 Alexey Melnikov Intended Status changed to Proposed Standard
2016-09-07
05 Alexey Melnikov IESG process started in state Publication Requested
2016-09-07
05 Alexey Melnikov Stream changed to IETF from None
2016-06-23
05 Julien ÉLIE New version available: draft-murchison-nntp-compress-05.txt
2016-06-18
04 Julien ÉLIE New version available: draft-murchison-nntp-compress-04.txt
2016-06-10
03 Julien ÉLIE New version available: draft-murchison-nntp-compress-03.txt
2015-11-12
02 Kenneth Murchison New version available: draft-murchison-nntp-compress-02.txt
2010-07-30
01 (System) Document has expired
2010-01-26
01 (System) New version available: draft-murchison-nntp-compress-01.txt
2010-01-23
00 (System) New version available: draft-murchison-nntp-compress-00.txt