RFC 3767: Securely Available Credentials Protocol
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 3767: Securely Available Credentials Protocol
Summary
RFC 3767: Securely Available Credentials Protocol is a Request for Comments[1].
Key Facts
- RFC 3767: Securely Available Credentials Protocol authored Securely Available Credentials Protocol — author (P50): Stephen Farrell[2].
- RFC 3767: Securely Available Credentials Protocol's instance of is recorded as Securely Available Credentials Protocol — instance of (P31): Request for Comments[3].
- RFC 3767: Securely Available Credentials Protocol's publisher is recorded as Securely Available Credentials Protocol — publisher (P123): Internet Engineering Task Force[4].
- RFC 3767: Securely Available Credentials Protocol's DOI is recorded as 10.17487/RFC3767[5].
- RFC 3767: Securely Available Credentials Protocol's language of work or name is recorded as Securely Available Credentials Protocol — language of work or name (P407): English[6].
- RFC 3767: Securely Available Credentials Protocol's publication date is recorded as +2004-06-01T00:00:00Z[7].
- RFC 3767: Securely Available Credentials Protocol's RfC ID is recorded as 3767[8].
- RFC 3767: Securely Available Credentials Protocol's work available at URL is recorded as https://tools.ietf.org/html/rfc3767[9].
- RFC 3767: Securely Available Credentials Protocol's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3767.txt[10].
- RFC 3767: Securely Available Credentials Protocol's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3767.txt[11].
- RFC 3767: Securely Available Credentials Protocol's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3767.txt.pdf[12].
- RFC 3767: Securely Available Credentials Protocol's number of pages is recorded as {'unit': '1', 'amount': '+25'}[13].
- RFC 3767: Securely Available Credentials Protocol's title is recorded as Securely Available Credentials Protocol[14].
- RFC 3767: Securely Available Credentials Protocol's amended by is recorded as Securely Available Credentials Protocol — amended by (P2567): RFC 8996: Deprecating TLS 1.0 and TLS 1.1[15].
- RFC 3767: Securely Available Credentials Protocol's DBLP publication ID is recorded as journals/rfc/rfc3767[16].
Body
Designation and Status
RFC 3767: Securely Available Credentials Protocol's instance of is recorded as Securely Available Credentials Protocol — instance of (P31): Request for Comments[3].