All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215736] uri.7: DESCRIPTION: Usage: ldap: Reference to obsolete IETF RFCs 2251, 2253, 2254, and 2255
Date: Thu, 24 Mar 2022 11:49:45 +0000	[thread overview]
Message-ID: <bug-215736-11311-SU88V4bdf0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215736-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215736

Alejandro Colomar (man-pages) (alx.manpages@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|uri.7: DESCRIPTION: Usage:  |uri.7: DESCRIPTION: Usage:
                   |ldap: Reference to obsolete |ldap: Reference to obsolete
                   |IETF RFC 2255               |IETF RFCs 2251, 2253, 2254,
                   |                            |and 2255

--- Comment #1 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
More references to obsolete RFCs[2][3][4] in the same ldap entry:

```
       dn          the LDAP Distinguished Name, which identifies
                   the  base  object  of  the  LDAP  search (see
                   RFC 2253             <http://www.ietf.org/rfc
                   /rfc2253.txt>  section 3).

       attributes  a  comma-separated  list  of attributes to be
                   returned; see  RFC 2251  section  4.1.5.   If
                   omitted, all attributes should be returned.

       scope       specifies  the scope of the search, which can
                   be one of "base" (for a base object  search),
                   "one" (for a one-level search), or "sub" (for
                   a  subtree  search).   If  scope  is omitted,
                   "base" is assumed.

       filter      specifies the search filter  (subset  of  en-
                   tries  to  return).   If omitted, all entries
                   should    be    returned.     See    RFC 2254
                   <http://www.ietf.org/rfc/rfc2254.txt>    sec-
                   tion 4.
```

[2]: <https://www.rfc-editor.org/rfc/rfc2253>
[3]: <https://www.rfc-editor.org/rfc/rfc2251>
[4]: <https://www.rfc-editor.org/rfc/rfc2254>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2022-03-24 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 11:46 [Bug 215736] New: uri.7: DESCRIPTION: Usage: ldap: Reference to obsolete IETF RFC 2255 bugzilla-daemon
2022-03-24 11:49 ` bugzilla-daemon [this message]
2022-03-24 12:11 ` [Bug 215736] uri.7: DESCRIPTION: Usage: ldap: Reference to obsolete IETF RFCs 2251, 2253, 2254, and 2255 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-SU88V4bdf0@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.