RFC 1495: Mapping between X.400 and RFC-822 Message Bodies
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 1495: Mapping between X.400 and RFC-822 Message Bodies
Summary
RFC 1495: Mapping between X.400 and RFC-822 Message Bodies is a Request for Comments[1].
Key Facts
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies authored Mapping between X.400 and RFC-822 Message Bodies — author (P50): Marshall Rose[2].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies authored Mapping between X.400 and RFC-822 Message Bodies — author (P50): Harald Tveit Alvestrand[3].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies authored Mapping between X.400 and RFC-822 Message Bodies — author (P50): Steve Kille[4].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's instance of is recorded as Mapping between X.400 and RFC-822 Message Bodies — instance of (P31): Request for Comments[5].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's publisher is recorded as Mapping between X.400 and RFC-822 Message Bodies — publisher (P123): Internet Engineering Task Force[6].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's based on is recorded as Mapping between X.400 and RFC-822 Message Bodies — based on (P144): RFC 1327: Mapping between X.400(1988) / ISO 10021 and RFC 822[7].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's DOI is recorded as 10.17487/RFC1495[8].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's language of work or name is recorded as Mapping between X.400 and RFC-822 Message Bodies — language of work or name (P407): English[9].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's publication date is recorded as +1993-08-01T00:00:00Z[10].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's RfC ID is recorded as 1495[11].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's work available at URL is recorded as https://tools.ietf.org/html/rfc1495[12].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's work available at URL is recorded as https://tools.ietf.org/rfc/rfc1495.txt[13].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1495.txt[14].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1495.txt.pdf[15].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's number of pages is recorded as {'unit': '1', 'amount': '+11'}[16].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's replaced by is recorded as Mapping between X.400 and RFC-822 Message Bodies — replaced by (P1366): RFC 2156: MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME[17].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's title is recorded as Mapping between X.400 and RFC-822 Message Bodies[18].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's author name string is recorded as R. Miles[19].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's author name string is recorded as S. Thompson[20].
- RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's DBLP publication ID is recorded as journals/rfc/rfc1495[21].
Body
Designation and Status
RFC 1495: Mapping between X.400 and RFC-822 Message Bodies's instance of is recorded as Mapping between X.400 and RFC-822 Message Bodies — instance of (P31): Request for Comments[5].