From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215736] New: uri.7: DESCRIPTION: Usage: ldap: Reference to obsolete IETF RFC 2255
Date: Thu, 24 Mar 2022 11:46:52 +0000 [thread overview]
Message-ID: <bug-215736-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215736
Bug ID: 215736
Summary: uri.7: DESCRIPTION: Usage: ldap: Reference to obsolete
IETF RFC 2255
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: alx.manpages@gmail.com
Regression: No
uri(7)::DESCRIPTION::Usage::ldap reads as:
```
ldap - Lightweight Directory Access Protocol
ldap://hostport
ldap://hostport/
ldap://hostport/dn
ldap://hostport/dn?attributes
ldap://hostport/dn?attributes?scope
ldap://hostport/dn?attributes?scope?filter
ldap://hostport/dn?attributes?scope?filter?extensions
This scheme supports queries to the Lightweight Directory
Access Protocol (LDAP), a protocol for querying a set of
servers for hierarchically organized information (such as
people and computing resources). See RFC 2255
<http://www.ietf.org/rfc/rfc2255.txt> for more informa-
tion on the LDAP URL scheme. The components of this URL
are:
[...]
```
It refers to an obsolete RFC[1]. We should update the info there.
[1]: <https://www.rfc-editor.org/rfc/rfc2255>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-03-24 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 11:46 bugzilla-daemon [this message]
2022-03-24 11:49 ` [Bug 215736] uri.7: DESCRIPTION: Usage: ldap: Reference to obsolete IETF RFCs 2251, 2253, 2254, and 2255 bugzilla-daemon
2022-03-24 12:11 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215736-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.