(1) What type of RFC is being requested (BCP, Proposed Standard, Internet
Standard, Informational, Experimental, or Historic)? Why is this the
proper type of RFC? Is this type of RFC indicated in the title page
header?
Informational. This is an update to an existing informational RFC. The
RFC type is on the title page header.
(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:
Technical Summary
---------
Zstandard, or "zstd" (pronounced "zee standard"), is a data
compression mechanism. This document describes the mechanism and
registers a media type and content encoding to be used when
transporting zstd-compressed content via Multipurpose Internet Mail
Extensions (MIME).
Despite use of the word "standard" as part of its name, readers are
advised that this document is not an Internet Standards Track
specification; it is being published for informational purposes only.
Working Group Summary
---------
This is not the product of a working group.
Document Quality
---------
This protocol is widely implemented already. See section 9 of this
document.
Thorough review was done for RFC 8478. This is an update containing a
small number of minor corrections, mostly in errata reports.
One of the co-authors is a media type reviewer. No other formal reviews
are necessary.
Personnel
---------
Subodh Iyengar is the Document Shepherd.
Barry Leiba is the Responsible Area Director.
(3) Briefly describe the review of this document that was performed by
the Document Shepherd. If this version of the document is not ready for
publication, please explain why the document is being forwarded to the
IESG.
The document contains clarifications that have come to light since RFC
8478. The document fixes certain normative constraints in RFC 8478 that
were never implemented, so that future implementors don't try to
implement them. These are all minor changes.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
No.
(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that took
place.
No. Authors believe that the changes do not impact security in any
meaningful way.
(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the IESG
should be aware of? For example, perhaps he or she is uncomfortable with
certain parts of the document, or has concerns whether there really is a
need for it. In any event, if the interested community has discussed
those issues and has indicated that it still wishes to advance the
document, detail those concerns here.
I have no specific concerns.
(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.
Yes.
(8) Has an IPR disclosure been filed that references this document? If
so, summarize any discussion and conclusion regarding the IPR
disclosures.
None.
(9) How solid is the consensus of the interested community behind this
document? Does it represent the strong concurrence of a few individuals,
with others being silent, or does the interested community as a whole
understand and agree with it?
No current implementor has voiced any conerns about this change.
(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)
No
(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.
The id-nits run is clean.
(12) Describe how the document meets any required formal review criteria,
such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.
There are no formal reviews required for compression. One author is a
media type reviewer. The media type suffix registration has a typo by
referring to the wrong section for security considerations.
(13) Have all references within this document been identified as either
normative or informative?
Yes.
(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?
No new references have been added since RFC 8478.
(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in the
Last Call procedure.
No.
(16) Will publication of this document change the status of any existing
RFCs? Are those RFCs listed on the title page header, listed in the
abstract, and discussed in the introduction? If the RFCs are not listed
in the Abstract and Introduction, explain why, and point to the part of
the document where the relationship of this document to the other RFCs is
discussed. If this information is not in the document, explain why the
interested community considers it unnecessary.
This document updates RFC 8478. The title page does not call out this
update explicitly and should.
(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly identified.
Confirm that newly created IANA registries include a detailed
specification of the initial contents for the registry, that allocations
procedures for future registrations are defined, and a reasonable name
for the new registry has been suggested (see RFC 8126).
The IANA considerations section appears to be correct and complete.
(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find useful
in selecting the IANA Experts for these new registries.
No new registries are being created.
(19) Describe reviews and automated checks performed by to validate
sections of the document written in a formal language, such as XML code,
BNF rules, MIB definitions, YANG modules, etc.
No formal languages are used.
(20) If the document contains a YANG module, has the module been checked
with any of the recommended validation tools
(https://trac.ietf.org/trac/ops/wiki/yang-review-tools) for syntax and
formatting validation? If there are any resulting errors or warnings,
what is the justification for not fixing them at this time? Does the YANG
module comply with the Network Management Datastore Architecture (NMDA)
as specified in RFC8342?
No YANG modules are defined is in this document.