RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response
Summary
RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response is a Request for Comments[1].
Key Facts
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response authored IMAP/POP AUTHorize Extension for Simple Challenge/Response — author (P50): John Klensin[2].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's instance of is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — instance of (P31): Request for Comments[3].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's publisher is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — publisher (P123): Internet Engineering Task Force[4].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's DOI is recorded as 10.17487/RFC2195[5].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's language of work or name is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — language of work or name (P407): English[6].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's publication date is recorded as +1997-09-01T00:00:00Z[7].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's RfC ID is recorded as 2195[8].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's main subject is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — main subject (P921): Internet Message Access Protocol[9].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's main subject is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — main subject (P921): Post Office Protocol 3[10].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's work available at URL is recorded as https://tools.ietf.org/html/rfc2195[11].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2195.txt[12].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2195.txt[13].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2195.txt.pdf[14].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's number of pages is recorded as {'unit': '1', 'amount': '+5'}[15].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's replaces is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — replaces (P1365): RFC 2095: IMAP/POP AUTHorize Extension for Simple Challenge/Response[16].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's title is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response[17].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's author name string is recorded as R. Catoe[18].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's author name string is recorded as P. Krumviede[19].
- RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's DBLP publication ID is recorded as journals/rfc/rfc2195[20].
Body
Designation and Status
RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response's instance of is recorded as IMAP/POP AUTHorize Extension for Simple Challenge/Response — instance of (P31): Request for Comments[3].