RFC 6111: Additional Kerberos Naming Constraints
In plain English — editorial summary, not part of the RFC
This document defines new naming constraints for well-known Kerberos principal names and well-known Kerberos realm names. [STANDARDS- TRACK]
Document record
- Document ID
- RFC6111
- Published
- April 2011
- Authors
- L. Zhu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 4120
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6112Anonymity Support for KerberosObsoleted
April 2011
- RFC 6113A Generalized Framework for Kerberos Pre-AuthenticationCurrent
April 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 6066Transport Layer Security (TLS) Extensions: Extension DefinitionsUpdated
January 2011
- RFC 6158RADIUS Design GuidelinesUpdated
March 2011
- RFC 6063Dynamic Symmetric Key Provisioning Protocol (DSKPP)Current
December 2010
- RFC 6054Using Counter Modes with Encapsulating Security Payload (ESP) and Authentication Header (AH) to Protect Group TrafficCurrent
November 2010
- RFC 6170Internet X.509 Public Key Infrastructure -- Certificate ImageObsoleted
May 2011
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?