|
1.
|
Clear description of the referenced document:
|
|
|
|
|
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 2635 (June 1999).
|
|
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=2635
|
|
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] See for example spam-l@peach.ease.lsoft.com/
[2] Fraser, B., "Site Security Handbook", FYI 8, RFC 2196, September/
1997./
[3] "Current Spam thresholds and guidelines," Lewis, Chris and Tim/
Skirvin, http://www.killfile.org/~tskirvin/faqs/spam.html./
[4] Schwartz, Alan and Simson Garfinkel, "Stopping Spam," O'Reilly/
and Associates, 1998./
[5] Crocker, D., "Standard for the format of ARPA Internet text/
messages", STD 11, RFC 822, August 1982./
[6] Braden, R., "Requirements for Internet hosts - application and/
support", STD 3, RFC 1123, October 1989./
[7] Crocker, D., "Mailbox Names for Common Services, Roles and/
Functions", RFC 2142, May 1997./
|
|
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):
|
|
|
- IETF RFC 2635 "A Set of Guidelines for Mass Unsolicited Mailings and Postings": available at "http://www.ietf.org/rfc/rfc2635.txt?number=2635"
|
