Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1240     
  ITU-T A.5 justification information for referenced document IETF RFC 3685 (2004) in draft X.1240
1. Clear description of the referenced document:
Name: IETF RFC 3685 (2004)
Title: SIEVE Spamtest and Virustest Extensions
2. Status of approval:
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
3. Justification for the specific reference:
Draft Rec. X.gcs refers to abstract part of IETF RFC 3685 (February 2004).
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=3685
5. Other useful information describing the "Quality" of the document:
The status of all the referred specifications is "approved specification".
6. The degree of stability or maturity of the document:
The status of all the referred specifications is "approved specification".
7. Relationship with other existing or emerging documents:
References within the referenced specifications are listed under item (8).
8. Any explicit references within that referenced document should also be listed:
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RELATIONAL] Segmuller, W., "Sieve Extension: Relational Tests", RFC 3431, December 2002./
[SIEVE] Showalter, T., "Sieve: A Mail Filtering Language", RFC 3028, January 2001./
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