|
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.cso refers to RADIUS Extensions, IETF RFC, June 2000.
|
|
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=2869
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
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] Rigney, C., Willens, S., Rubens, A. and W. Simpson, "Remote/
Authentication Dial In User Service (RADIUS)", RFC 2865, June/
2000./
/
[2] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000./
/
[3] Blunk, L. and J. Vollbrecht, "PPP Extensible Authentication/
Protocol (EAP)", RFC 2284, March 1998./
/
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March, 1997./
/
[5] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700,/
October 1994./
/
[6] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M. and/
I. Goyret, "RADIUS Attributes for Tunnel Protocol Support", RFC/
2868, June 2000./
/
[7] Zorn, G., Aboba, B. and D. Mitton, "RADIUS Accounting/
Modifications for Tunnel Protocol Support", RFC 2867, June 2000./
/
[8] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC/
2279, January 1998./
|
|
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
|
|
