Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : H.265 (V2)     
  ITU-T A.5 justification information for referenced document IETF RFC 1321 (1992) in draft H.265 (V2)
1. Clear description of the referenced document:
Name: IETF RFC 1321 (1992)
Title: The MD5 Message-Digest Algorithm, IETF RFC, April 1992.
2. Status of approval:
Informational RFC approved April 1992.
3. Justification for the specific reference:
The reference to this hash function is needed to identify a widely-used hash function for integrity checking. Even though this is an Informal RFC, this specification is widely used, and it is referenced in H.265 as a way to (optionally) check the integrity of decoded pictures when an encoder sends the result of this hash function (applied to the decoded picture values).
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=1321
5. Other useful information describing the "Quality" of the document:
Informational RFC. Updated by RFC 6151. Errata exist.
6. The degree of stability or maturity of the document:
Informal RFC approved April 1992.
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:
None.
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
Note: This form is based on Recommendation ITU-T A.5