CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 16:58:36 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=fqfe320m19ovmq145bkdqsr35r; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f290d1bb62c464-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
Found 1 record.
Status: Verified (1)
RFC 3494, "Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status", March 2003
Source of RFC: Legacy
Errata ID: 264
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Marshall Price
Date Reported: 2004-10-15
In the "Dependent Specifications" section, it says:
RFC 1781 is a technical specification for "User Friendly Naming" which replies on particular syntaxes described in RFC 1779.
It should say:
RFC 1781 is a technical specification for "User Friendly Naming" which relies on particular syntaxes described in RFC 1779.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us