RFC 5178: Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type
In plain English — editorial summary, not part of the RFC
This document describes domain-name-based service principal names and the corresponding name type for the Generic Security Service Application Programming Interface (GSS-API). Internationalization of the GSS-API is also covered. Domain-based service names are similar to host-based service names, but using a domain name (not necessarily an Internet domain name) in addition to a hostname. The primary purpose of domain-based names is to provide a measure of protection to applications that utilize insecure service discovery protocols. This is achieved by providing a way to name clustered services after the "domain" which they service, thereby allowing their clients to authorize the service's servers based on authentication of their service names. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5178
- Published
- May 2008
- Authors
- N. Williams; A. Melnikov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5179Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS MechanismCurrent
May 2008
- RFC 5176Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)Updated
January 2008
- RFC 5169Handover Key Management and Re-Authentication Problem StatementCurrent
March 2008
- RFC 5197On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and ExtensionsCurrent
June 2008
- RFC 5209Network Endpoint Assessment (NEA): Overview and RequirementsCurrent
June 2008
- RFC 5216The EAP-TLS Authentication ProtocolUpdated
March 2008
- RFC 5126CMS Advanced Electronic Signatures (CAdES)Current
March 2008
- RFC 5246The Transport Layer Security (TLS) Protocol Version 1.2Obsoleted
August 2008
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?