|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 1951 (1996)
|
|
Title:
|
DEFLATE Compressed Data Format Specification Version 1.3, IETF RFC, 1996.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-1 can use DEFLATE Compressed Data Format Specification as discussed in [20] to reduce data size.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=1951
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Huffman, D. A., "A Method for the Construction of Minimum/
Redundancy Codes", Proceedings of the Institute of Radio/
Engineers, September 1952, Volume 40, Number 9, pp. 1098-1101./
/
[2] Ziv J., Lempel A., "A Universal Algorithm for Sequential Data/
Compression", IEEE Transactions on Information Theory, Vol. 23,/
No. 3, pp. 337-343./
/
[3] Gailly, J.-L., and Adler, M., ZLIB documentation and sources,/
available in ftp://ftp.uu.net/pub/archiving/zip/doc//
/
[4] Gailly, J.-L., and Adler, M., GZIP documentation and sources,/
available as gzip-*.tar in ftp://prep.ai.mit.edu/pub/gnu//
/
[5] Schwartz, E. S., and Kallick, B. "Generating a canonical prefix/
encoding." Comm. ACM, 7,3 (Mar. 1964), pp. 166-169./
/
[6] Hirschberg and Lelewer, "Efficient decoding of prefix codes,"/
Comm. ACM, 33,4, April 1990, pp. 449-459./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
