TLS User Mapping Extension
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- Abstract
- This document specifies a TLS extension that enables clients to send generic user mapping hints in a supplemental data handshake message defined in RFC 4680. One such mapping hint is defined in an informative section, the UpnDomainHint, which may be used by a server to locate a user in a directory database. Other mapping hints may be defined in other documents in the future. [STANDARDS-TRACK]
- Publication Date
- 2006-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4681- Link
- https://doi.org/10.17487/RFC4681
- Author(s)
- Stefan SantessonAri MedvinskyJoshua Ball
- Keyword(s)
- TLS
Latest version of IETF RFC 4681
Document Versions — IETF RFC 4681
-
▶ IETF RFC 4681 (2006-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1034 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 2246 [Superseded*]
- IETF RFC 2434 [Superseded*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 4346 [Superseded*]
- IETF RFC 4366 [Superseded*]
- IETF RFC 4680 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4681.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4681, TLS User Mapping Extension. Available at https://doi.org/10.17487/RFC4681
Snippet:
IETF RFC 4681, TLS User Mapping Extension. Available at https://doi.org/10.17487/RFC4681
HTML (ISO 690 compliant)
Preview:
IETF RFC 4681, TLS User Mapping Extension. Available at https://doi.org/10.17487/RFC4681
Snippet:
<span class="citation"><cite>IETF RFC 4681</cite>, TLS User Mapping Extension. Available at <a href="https://doi.org/10.17487/RFC4681" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4681</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc4681">IETF RFC 4681</cite>, TLS User Mapping Extension <span class="doi">10.17487/RFC4681</span> </li>
Referenced By
- IETF RFC 8996 [Active*]