|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 8907
|
|
Title:
|
The Terminal Access Controller Access-Control System Plus (TACACS+) Protocol
|
|
|
2.
|
Status of approval:
|
|
|
Approved September 2020
|
|
3.
|
Justification for the specific reference:
|
|
|
The draft Recommendation ITU-T Q.ETFRM mentions RFC 8907 as an example of Authentication, Authorisation and Accounting (AAA) protocols which can be used for the user access in the context of testbeds federation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No IPR disclosures have been submitted directly on RFC 8907.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
An errata exists: https://www.rfc-editor.org/errata/rfc8907
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This document describes the Terminal Access Controller Access-Control System Plus (TACACS+) protocol, which is widely deployed today to provide Device Administration for routers, network access servers, and other networked computing devices via one or more centralized servers.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Draft Recommendation ITU-T Q.ETFRM
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC0020]/
Cerf, V., "ASCII format for network interchange", STD 80, RFC 20, DOI 10.17487/RFC0020, October 1969, . /
[RFC1321]/
Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, DOI 10.17487/RFC1321, April 1992, . /
[RFC1334]/
Lloyd, B. and W. Simpson, "PPP Authentication Protocols", RFC 1334, DOI 10.17487/RFC1334, October 1992, . /
[RFC2119]/
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . /
[RFC2433]/
Zorn, G. and S. Cobb, "Microsoft PPP CHAP Extensions", RFC 2433, DOI 10.17487/RFC2433, October 1998, . /
[RFC2759]/
Zorn, G., "Microsoft PPP CHAP Extensions, Version 2", RFC 2759, DOI 10.17487/RFC2759, January 2000, . /
[RFC3579]/
Aboba, B. and P. Calhoun, "RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)", RFC 3579, DOI 10.17487/RFC3579, September 2003, . /
[RFC4086]/
Eastlake 3rd, D., Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, DOI 10.17487/RFC4086, June 2005, . /
[RFC4120]/
Neuman, C., Yu, T., Hartman, S., and K. Raeburn, "The Kerberos Network Authentication Service (V5)", RFC 4120, DOI 10.17487/RFC4120, July 2005, . /
[RFC5952]/
Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 Address Text Representation", RFC 5952, DOI 10.17487/RFC5952, August 2010, . /
[RFC8174]/
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . /
[RFC8265]/
Saint-Andre, P. and A. Melnikov, "Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords", RFC 8265, DOI 10.17487/RFC8265, October 2017, .
|
|
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
|
|
