RFC 5172

E877707

RFC 5172 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier PPP specifications to define enhanced cryptographic and security mechanisms for Point-to-Point Protocol connections.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (1)

Label Occurrences
RFC 5172 canonical 1

Statements (42)

Predicate Object
instanceOf IETF standard
Request for Comments
aimsTo enhance security of PPP authentication
provide stronger cryptographic protection for PPP EAP
area Security
category Standards Track
defines HMAC-based authentication for PPP EAP
PPP EAP authentication method using keyed hash message authentication codes
PPP EAP authentication using keyed message digests
negotiation of HMAC algorithms within EAP over PPP
focusesOn cryptographic authentication mechanisms
keyed hash message authentication codes
security mechanisms for PPP connections
hasAbbreviation RFC 5172 NERFINISHED
intendedFor PPP links
PPP-based network access authentication
language English
medium electronic document
obsoletes RFC 2716 NERFINISHED
organization IETF NERFINISHED
Internet Engineering Task Force NERFINISHED
partOf RFC series NERFINISHED
protocol EAP NERFINISHED
PPP Extensible Authentication Protocol NERFINISHED
Point-to-Point Protocol NERFINISHED
publishedBy Internet Engineering Task Force
surface form: IETF

Internet Engineering Task Force
standardizes HMAC algorithm negotiation for PPP EAP
use of HMAC for EAP authentication over PPP
status Proposed Standard
stream Internet Engineering Task Force
surface form: IETF
subject EAP NERFINISHED
HMAC NERFINISHED
PPP NERFINISHED
link-layer authentication
network security
title Negotiation for Keyed Hash Message Authentication Code (HMAC) Authentication within PPP Extensible Authentication Protocol (EAP)
updates RFC 1994 NERFINISHED
RFC 2716
RFC 3748 NERFINISHED
uses HMAC NERFINISHED
keyed hash functions

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 1661 obsoletedBy RFC 5172