RFC 987: Mapping between X.400 and RFC 822
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 987: Mapping between X.400 and RFC 822
Summary
RFC 987: Mapping between X.400 and RFC 822 is a Request for Comments[1].
Key Facts
- RFC 987: Mapping between X.400 and RFC 822 authored Mapping between X.400 and RFC 822 — author (P50): Steve Kille[2].
- RFC 987: Mapping between X.400 and RFC 822's instance of is recorded as Mapping between X.400 and RFC 822 — instance of (P31): Request for Comments[3].
- RFC 987: Mapping between X.400 and RFC 822's publisher is recorded as Mapping between X.400 and RFC 822 — publisher (P123): Internet Engineering Task Force[4].
- RFC 987: Mapping between X.400 and RFC 822's DOI is recorded as 10.17487/RFC0987[5].
- RFC 987: Mapping between X.400 and RFC 822's language of work or name is recorded as Mapping between X.400 and RFC 822 — language of work or name (P407): English[6].
- RFC 987: Mapping between X.400 and RFC 822's publication date is recorded as +1986-06-01T00:00:00Z[7].
- RFC 987: Mapping between X.400 and RFC 822's RfC ID is recorded as 987[8].
- RFC 987: Mapping between X.400 and RFC 822's main subject is recorded as Mapping between X.400 and RFC 822 — main subject (P921): X.400[9].
- RFC 987: Mapping between X.400 and RFC 822's main subject is recorded as Mapping between X.400 and RFC 822 — main subject (P921): RFC 822: Standard for the Format of ARPA Internet Text Messages[10].
- RFC 987: Mapping between X.400 and RFC 822's main subject is recorded as Mapping between X.400 and RFC 822 — main subject (P921): Recommendation X.400 (10/1984): Message handling systems: system model-service elements[11].
- RFC 987: Mapping between X.400 and RFC 822's work available at URL is recorded as https://tools.ietf.org/html/rfc987[12].
- RFC 987: Mapping between X.400 and RFC 822's work available at URL is recorded as https://tools.ietf.org/rfc/rfc987.txt[13].
- RFC 987: Mapping between X.400 and RFC 822's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc987.txt[14].
- RFC 987: Mapping between X.400 and RFC 822's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc987.txt.pdf[15].
- RFC 987: Mapping between X.400 and RFC 822's number of pages is recorded as {'unit': '1', 'amount': '+69'}[16].
- RFC 987: Mapping between X.400 and RFC 822's replaced by is recorded as Mapping between X.400 and RFC 822 — replaced by (P1366): RFC 2156: MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME[17].
- RFC 987: Mapping between X.400 and RFC 822's replaced by is recorded as Mapping between X.400 and RFC 822 — replaced by (P1366): RFC 1327: Mapping between X.400(1988) / ISO 10021 and RFC 822[18].
- RFC 987: Mapping between X.400 and RFC 822's title is recorded as Mapping between X.400 and RFC 822[19].
- RFC 987: Mapping between X.400 and RFC 822's amended by is recorded as Mapping between X.400 and RFC 822 — amended by (P2567): RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)[20].
- RFC 987: Mapping between X.400 and RFC 822's amended by is recorded as Mapping between X.400 and RFC 822 — amended by (P2567): RFC 1138: Mapping between X.400(1988) / ISO 10021 and RFC 822[21].
- RFC 987: Mapping between X.400 and RFC 822's amended by is recorded as Mapping between X.400 and RFC 822 — amended by (P2567): RFC 1148: Mapping between X.400(1988) / ISO 10021 and RFC 822[22].
- RFC 987: Mapping between X.400 and RFC 822's DBLP publication ID is recorded as journals/rfc/rfc987[23].
Body
Designation and Status
RFC 987: Mapping between X.400 and RFC 822's instance of is recorded as Mapping between X.400 and RFC 822 — instance of (P31): Request for Comments[3].