|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. This refence is needed in Rec. E.804 for the definition of store-and-forward services measurements.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
It is a mature document..
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2177 has a status of STANDARD and was published in 1997. Since then it has been widely implemented and became one of the major components of Internet.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
The following file is maintained by ISOC/IETF and has all the requested information: http://www.ietf.org/iesg/1rfc_index.txt .
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[IMAP4] Crispin, M., "Internet Message Access Protocol - Version/
4rev1", RFC 2060, December 1996./
|
|
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
|
