RFC 2888: Secure Remote Access with L2TP
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 2888: Secure Remote Access with L2TP
Summary
RFC 2888: Secure Remote Access with L2TP is a Request for Comments[1].
Key Facts
- RFC 2888: Secure Remote Access with L2TP authored Secure Remote Access with L2TP — author (P50): Pyda Srisuresh[2].
- RFC 2888: Secure Remote Access with L2TP's instance of is recorded as Secure Remote Access with L2TP — instance of (P31): Request for Comments[3].
- RFC 2888: Secure Remote Access with L2TP's publisher is recorded as Secure Remote Access with L2TP — publisher (P123): Internet Engineering Task Force[4].
- RFC 2888: Secure Remote Access with L2TP's DOI is recorded as 10.17487/RFC2888[5].
- RFC 2888: Secure Remote Access with L2TP's language of work or name is recorded as Secure Remote Access with L2TP — language of work or name (P407): English[6].
- RFC 2888: Secure Remote Access with L2TP's publication date is recorded as +2000-08-01T00:00:00Z[7].
- RFC 2888: Secure Remote Access with L2TP's RfC ID is recorded as 2888[8].
- RFC 2888: Secure Remote Access with L2TP's main subject is recorded as Secure Remote Access with L2TP — main subject (P921): Layer 2 Tunneling Protocol[9].
- RFC 2888: Secure Remote Access with L2TP's work available at URL is recorded as https://tools.ietf.org/html/rfc2888[10].
- RFC 2888: Secure Remote Access with L2TP's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2888.txt[11].
- RFC 2888: Secure Remote Access with L2TP's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2888.txt[12].
- RFC 2888: Secure Remote Access with L2TP's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2888.txt.pdf[13].
- RFC 2888: Secure Remote Access with L2TP's number of pages is recorded as {'unit': '1', 'amount': '+19'}[14].
- RFC 2888: Secure Remote Access with L2TP's title is recorded as Secure Remote Access with L2TP[15].
- RFC 2888: Secure Remote Access with L2TP's DBLP publication ID is recorded as journals/rfc/rfc2888[16].
Body
Designation and Status
RFC 2888: Secure Remote Access with L2TP's instance of is recorded as Secure Remote Access with L2TP — instance of (P31): Request for Comments[3].