RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)
0 sources
RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)
Summary
RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822) is a Request for Comments[1].
Key Facts
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822) authored Addendum to RFC 987: (Mapping between X.400 and RFC-822) — author (P50): Steve Kille[2].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s instance of is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — instance of (P31): Request for Comments[3].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s publisher is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — publisher (P123): Internet Engineering Task Force[4].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s based on is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — based on (P144): RFC 987: Mapping between X.400 and RFC 822[5].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s DOI is recorded as 10.17487/RFC1026[6].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s language of work or name is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — language of work or name (P407): English[7].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s publication date is recorded as +1987-09-01T00:00:00Z[8].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s RfC ID is recorded as 1026[9].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s work available at URL is recorded as https://tools.ietf.org/html/rfc1026[10].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc1026.txt[11].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1026.txt[12].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1026.txt.pdf[13].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s number of pages is recorded as {'unit': '1', 'amount': '+4'}[14].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s replaced by is recorded as Addendum to RFC 987: (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[15].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s replaced by is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — replaced by (P1366): RFC 1327: Mapping between X.400(1988) / ISO 10021 and RFC 822[16].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s title is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822)[17].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s amended by is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — amended by (P2567): RFC 1138: Mapping between X.400(1988) / ISO 10021 and RFC 822[18].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s amended by is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — amended by (P2567): RFC 1148: Mapping between X.400(1988) / ISO 10021 and RFC 822[19].
- RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s DBLP publication ID is recorded as journals/rfc/rfc1026[20].
Body
Designation and Status
RFC 1026: Addendum to RFC 987: (Mapping between X.400 and RFC-822)'s instance of is recorded as Addendum to RFC 987: (Mapping between X.400 and RFC-822) — instance of (P31): Request for Comments[3].