|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Informative RFC
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.xacml3 refers to Internet Security Glossary, Version 2
|
|
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=4949
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since 2007.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4949 was published in 2007. It is a standards-track document. Current standards status of this document can be found at http://www.rfc-editor.org/rfcxx00.html.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes RFC 2828
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[R2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 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):
|
|
|
None
|
