RFC 4466: Collected Extensions to IMAP4 ABNF
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 4466: Collected Extensions to IMAP4 ABNF
Summary
RFC 4466: Collected Extensions to IMAP4 ABNF is a Request for Comments[1].
Key Facts
- RFC 4466: Collected Extensions to IMAP4 ABNF authored Collected Extensions to IMAP4 ABNF — author (P50): Alexey Melnikov[2].
- RFC 4466: Collected Extensions to IMAP4 ABNF authored Collected Extensions to IMAP4 ABNF — author (P50): Cyrus Daboo[3].
- RFC 4466: Collected Extensions to IMAP4 ABNF's instance of is recorded as Collected Extensions to IMAP4 ABNF — instance of (P31): Request for Comments[4].
- RFC 4466: Collected Extensions to IMAP4 ABNF's publisher is recorded as Collected Extensions to IMAP4 ABNF — publisher (P123): Internet Engineering Task Force[5].
- RFC 4466: Collected Extensions to IMAP4 ABNF's based on is recorded as Collected Extensions to IMAP4 ABNF — based on (P144): RFC 2088: IMAP4 non-synchronizing literals[6].
- RFC 4466: Collected Extensions to IMAP4 ABNF's based on is recorded as Collected Extensions to IMAP4 ABNF — based on (P144): RFC 2342: IMAP4 Namespace[7].
- RFC 4466: Collected Extensions to IMAP4 ABNF's based on is recorded as Collected Extensions to IMAP4 ABNF — based on (P144): RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1[8].
- RFC 4466: Collected Extensions to IMAP4 ABNF's based on is recorded as Collected Extensions to IMAP4 ABNF — based on (P144): RFC 3502: Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension[9].
- RFC 4466: Collected Extensions to IMAP4 ABNF's based on is recorded as Collected Extensions to IMAP4 ABNF — based on (P144): RFC 3516: IMAP4 Binary Content Extension[10].
- RFC 4466: Collected Extensions to IMAP4 ABNF's DOI is recorded as 10.17487/RFC4466[11].
- RFC 4466: Collected Extensions to IMAP4 ABNF's language of work or name is recorded as Collected Extensions to IMAP4 ABNF — language of work or name (P407): English[12].
- RFC 4466: Collected Extensions to IMAP4 ABNF's publication date is recorded as +2006-04-01T00:00:00Z[13].
- RFC 4466: Collected Extensions to IMAP4 ABNF's RfC ID is recorded as 4466[14].
- RFC 4466: Collected Extensions to IMAP4 ABNF's work available at URL is recorded as https://tools.ietf.org/html/rfc4466[15].
- RFC 4466: Collected Extensions to IMAP4 ABNF's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4466.txt[16].
- RFC 4466: Collected Extensions to IMAP4 ABNF's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4466.txt[17].
- RFC 4466: Collected Extensions to IMAP4 ABNF's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4466.txt.pdf[18].
- RFC 4466: Collected Extensions to IMAP4 ABNF's number of pages is recorded as {'unit': '1', 'amount': '+17'}[19].
- RFC 4466: Collected Extensions to IMAP4 ABNF's title is recorded as Collected Extensions to IMAP4 ABNF[20].
- RFC 4466: Collected Extensions to IMAP4 ABNF's amended by is recorded as Collected Extensions to IMAP4 ABNF — amended by (P2567): RFC 6237: IMAP4 Multimailbox SEARCH Extension[21].
- RFC 4466: Collected Extensions to IMAP4 ABNF's amended by is recorded as Collected Extensions to IMAP4 ABNF — amended by (P2567): RFC 7377: IMAP4 Multimailbox SEARCH Extension[22].
- RFC 4466: Collected Extensions to IMAP4 ABNF's DBLP publication ID is recorded as journals/rfc/rfc4466[23].
Body
Designation and Status
RFC 4466: Collected Extensions to IMAP4 ABNF's instance of is recorded as Collected Extensions to IMAP4 ABNF — instance of (P31): Request for Comments[4].