RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management
0 sources
RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management
Summary
RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management is a Request for Comments[1].
Key Facts
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management authored Guidance for Authentication, Authorization, and Accounting (AAA) Key Management — author (P50): Russ Housley[2].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management authored Guidance for Authentication, Authorization, and Accounting (AAA) Key Management — author (P50): Bernard D. Aboba[3].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's instance of is recorded as Guidance for Authentication, Authorization, and Accounting (AAA) Key Management — instance of (P31): Request for Comments[4].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's publisher is recorded as Guidance for Authentication, Authorization, and Accounting (AAA) Key Management — publisher (P123): Internet Engineering Task Force[5].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's DOI is recorded as 10.17487/RFC4962[6].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's language of work or name is recorded as Guidance for Authentication, Authorization, and Accounting (AAA) Key Management — language of work or name (P407): English[7].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's publication date is recorded as +2007-07-01T00:00:00Z[8].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's RfC ID is recorded as 4962[9].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's work available at URL is recorded as https://tools.ietf.org/html/rfc4962[10].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4962.txt[11].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4962.txt[12].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4962.txt.pdf[13].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's number of pages is recorded as {'unit': '1', 'amount': '+23'}[14].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's title is recorded as Guidance for Authentication, Authorization, and Accounting (AAA) Key Management[15].
- RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's DBLP publication ID is recorded as journals/rfc/rfc4962[16].
Body
Designation and Status
RFC 4962: Guidance for Authentication, Authorization, and Accounting (AAA) Key Management's instance of is recorded as Guidance for Authentication, Authorization, and Accounting (AAA) Key Management — instance of (P31): Request for Comments[4].