1.
|
Clear description of the referenced document:
|
|
|
2.
|
Status of approval:
|
|
The referred RFC was approved by IESG (Internet Engineering Steering Group).
|
3.
|
Justification for the specific reference:
|
|
The referenced document is the text on which draft Recommendation X.nsom-sec is based.
|
4.
|
Current information, if any, about IPR issues:
|
|
None.
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
The RFC is "Proposed Standard".
|
6.
|
The degree of stability or maturity of the document:
|
|
The RFC is "Proposed Standard" and obsoletes RFC 2086.
|
7.
|
Relationship with other existing or emerging documents:
|
|
The RFC is "Proposed Standard" and obsoletes RFC 2086.
|
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./
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005./
[IMAP4] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", RFC 3501, March 2003./
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003./
[Stringprep] Hoffman, P. and M. Blanchet, "Preparation of Internationalized Strings ("stringprep")", RFC 3454, December 2002./
[SASLprep] Zeilenga, K., "SASLprep: Stringprep Profile for User Names and Passwords", RFC 4013, February 2005.
|
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
|