CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 22:44:27 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=u5001.oB_dLTgbcoTa0VQEQOvWvAx7rXLr.6jEzTvFQ-1760136267-1.0.1.1-fK1ynVqCtP47qMylI.wb9GyZa6y2XiTPUvIalbgahsCCOeQm3r6FGrSYNPjD7aGigyl8kSk2zmlqo4QsHqBFUer7n3sieTjiZVfkYMnWVmI; path=/; expires=Fri, 10-Oct-25 23:14:27 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c9a4729aacc195-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 7585 » RFC Editor
Search RFCs
RFC 7585
Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS Based on the Network Access Identifier (NAI), October 2015
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7585
Discuss this RFC: Send questions or comments to the mailing list radext@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7585
Abstract
This document specifies a means to find authoritative RADIUS servers for a given realm. It is used in conjunction with either RADIUS over Transport Layer Security (RADIUS/TLS) or RADIUS over Datagram Transport Layer Security (RADIUS/DTLS).
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us