Overview#
Internet Draft (I-D) is a Request For Comment (RFC) Standards Track RFC Status document published by the Internet Engineering Task Force (IETF) containing preliminary technical specifications, results of networking-related research, or other technical information.Internet Draft is less mature than Proposed Standard
Often, Internet Drafts are intended to be work-in-progress documents for work that is eventually to be published as a perhaps leading to become an Internet Standard.
Internet Draft are considered inappropriate to rely on and citations should indicate work in progress.
Internet Draft is expected to adhere to the basic requirements imposed on any RFC and may be used to flag common document problems prior to submission to the IETF.
Internet Draft are short-lived specifications, only valid for six months, typically go through multiple revisions, and may change significantly between revisions. The old version is removed from the Internet Draft repository, unless it is under official review by the Internet Engineering Steering Group (IESG) when a request to publish it as an RFC has been submitted.
Internet Draft may stagnate and become no longer maintained, although in some cases they may still describe viable functionality that is worth implementing.
LDAP Server Standards and Specifications documents a list of a number of Request For Comments and Internet Drafts related to LDAP and Directory Services.
Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its Working Groups. Note that their groups may also distribute working documents as Internet Drafts.
The list of Internet Draft can be accessed at: https://www.rfc-editor.org/standards#DS
More Information#
There might be more information for this subject on one of the following:- A Schema for Logging the LDAP Protocol
- Access Token
- Authorization Cross Domain Code 1.0
- Automatic Certificate Management Environment
- Change-password
- DNS Queries over HTTPS
- DNS over HTTPS
- DNT
- DNWithOctetString
- Deprecating TLSv1.0 and TLSv1.1
- Draft Standard
- Draft-armijo-ldap-syntax-00
- Draft-behera-ldap-password-policy
- Draft-chu-ldap-ldapi-00
- Draft-chu-ldap-logschema-00.txt
- Draft-good-ldap-changelog
- Draft-howard-rfc2307bis
- Draft-ietf-pkix-generalname-00
- Draft-sermersheim-ldap-subordinate-scope
- Draft-sermersheim-nds-ldap-schema
- Draft-wahl-ldap-adminaddr-05
- Encoding claims in the OAuth 2 state parameter using a JWT
- Encrypted Server Name Indication
- Glossary Of LDAP And Directory Terminology
- Grant Management for OAuth 2.0
- GroupOfEntries
- ID
- Internet Draft
- Issues and Requirements for SNI Encryption in TLS
- JSON Hypertext Application Language
- JSON Web Token Best Current Practices
- JSON Web Token Claims
- Kurt Zeilenga
- LDAP Dereference Control
- LDAP No-Op Control
- LDAP Protocol Exchanges
- LDAP Schema for NDS
- LDAPv3 Grouping of Related Operations
- Link-based Resource Descriptor Documents
- MailboxRelatedObject
- OAuth 2.0 Demonstration of Proof-of-Possession at the Application Layer
- OAuth 2.0 Dynamic Client Registration Management Protocol
- OAuth 2.0 Incremental Authorization
- OAuth 2.0 Proof-of-Possession (PoP) Security Architecture
- OAuth 2.0 Security Best Current Practice
- OAuth 2.0 Security Considerations
- OAuth 2.0 Security-Closing Open Redirectors in OAuth
- OAuth 2.0 Software Statement
- OAuth 2.0 Token Binding
- OAuth 2.0 Token Exchange
- OAuth 2.0 Vulnerabilities
- OpenID Connect Dynamic Client Registration
- OpenID Connect Profile for SCIM Services
- OpenID Foundation
- Password Policy
- Providing User Authentication Information to OAuth 2.0 Clients
- Public Key Cryptography Based User-to-User
- Quick UDP Internet Connections
- RFC Status
- RFC Style Guide
- Request For Comment
- Roughtime
- SCIM Password Management Extension
- Same-site Cookies
- SubordinateSubtree
- Subtree Delete Control
- SupportedGroupingTypes
- Using LDAP over IPC Mechanisms
- Web Proxy Auto-Discovery Protocol