RFC 2406: IP Encapsulating Security Payload (ESP)
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 2406: IP Encapsulating Security Payload (ESP)
Summary
RFC 2406: IP Encapsulating Security Payload (ESP) is a Request for Comments[1].
Key Facts
- RFC 2406: IP Encapsulating Security Payload (ESP) authored IP Encapsulating Security Payload (ESP) — author (P50): Stephen Kent[2].
- RFC 2406: IP Encapsulating Security Payload (ESP) authored IP Encapsulating Security Payload (ESP) — author (P50): Randall J. Atkinson[3].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s instance of is recorded as IP Encapsulating Security Payload (ESP) — instance of (P31): Request for Comments[4].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s publisher is recorded as IP Encapsulating Security Payload (ESP) — publisher (P123): Internet Engineering Task Force[5].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s DOI is recorded as 10.17487/RFC2406[6].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s language of work or name is recorded as IP Encapsulating Security Payload (ESP) — language of work or name (P407): English[7].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s publication date is recorded as +1998-11-01T00:00:00Z[8].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s RfC ID is recorded as 2406[9].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s main subject is recorded as IP Encapsulating Security Payload (ESP) — main subject (P921): Encapsulating Security Payload[10].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s work available at URL is recorded as https://tools.ietf.org/html/rfc2406[11].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc2406.txt[12].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2406.txt[13].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2406.txt.pdf[14].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s number of pages is recorded as {'unit': '1', 'amount': '+22'}[15].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s replaces is recorded as IP Encapsulating Security Payload (ESP) — replaces (P1365): RFC 1827: IP Encapsulating Security Payload (ESP)[16].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s replaced by is recorded as IP Encapsulating Security Payload (ESP) — replaced by (P1366): RFC 4303: IP Encapsulating Security Payload (ESP)[17].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s replaced by is recorded as IP Encapsulating Security Payload (ESP) — replaced by (P1366): RFC 4305: Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)[18].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s title is recorded as IP Encapsulating Security Payload (ESP)[19].
- RFC 2406: IP Encapsulating Security Payload (ESP)'s DBLP publication ID is recorded as journals/rfc/rfc2406[20].
Body
Designation and Status
RFC 2406: IP Encapsulating Security Payload (ESP)'s instance of is recorded as IP Encapsulating Security Payload (ESP) — instance of (P31): Request for Comments[4].