RFC 7268: RADIUS Attributes for IEEE 802 Networks
In plain English — editorial summary, not part of the RFC
RFC 3580 provides guidelines for the use of the Remote Authentication Dial-In User Service (RADIUS) within IEEE 802 local area networks (LANs). This document defines additional attributes for use within IEEE 802 networks and clarifies the usage of the EAP-Key-Name Attribute and the Called-Station-Id Attribute. This document updates RFCs 3580 and 4072.
Document record
- Document ID
- RFC7268
- Published
- July 2014
- Authors
- B. Aboba; J. Malinen; P. Congdon; J. Salowey; M. Jones
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 29
- Also known as
- —
- Updated by:
- RFC 8044
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7250Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)Current
June 2014
- RFC 7296Internet Key Exchange Protocol Version 2 (IKEv2)Updated
October 2014
- RFC 7301Transport Layer Security (TLS) Application-Layer Protocol Negotiation ExtensionUpdated
July 2014
- RFC 7218Adding Acronyms to Simplify Conversations about DNS-Based Authentication of Named Entities (DANE)Current
April 2014
- RFC 7321Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
August 2014
- RFC 7203An Incident Object Description Exchange Format (IODEF) Extension for Structured Cybersecurity InformationCurrent
April 2014
- RFC 7360Datagram Transport Layer Security (DTLS) as a Transport Layer for RADIUSUpdated
September 2014
- RFC 7171PT-EAP: Posture Transport (PT) Protocol for Extensible Authentication Protocol (EAP) Tunnel MethodsCurrent
May 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?