…rl in the content-type header field of the response. When the LDAP URI scheme [ RFC4516 ] is used, the URI MUST include a <dn> field containing the distinguished name of the entry holding the CRL, MUST include a single <attrdesc> that contains an appropriate attribute description…
… FILE [ RFC1738 ], FTP [ RFC1738 ], HTTP [ RFC2616 ], HTTPS [ RFC2818 ], LDAP [ RFC4516 ], and MID [ RFC2392 ] are the URI schemes most commonly used by current implementations. Example: ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, c=US???(cn=Jim%20Dolittle)":mailto…
…rl in the content-type header field of the response. When the LDAP URI scheme [ RFC4516 ] is used, the URI MUST include a <dn> field containing the distinguished name of the entry holding the CRL, MUST include a single <attrdesc> that contains an appropriate attribute description…
US
rfc5545
https://www.rfc-editor.org/rfc/inline-errata/rfc5545.html
…RFC2397], FILE [RFC1738], FTP [RFC1738], HTTP [RFC2616], HTTPS [RFC2818], LDAP [RFC4516], and MID [RFC2392] are the URI schemes most commonly used by current implementations. Example: ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, c=US???(cn=Jim%20Dolittle)":mailto:ji…
…RFC2397], FILE [RFC1738], FTP [RFC1738], HTTP [RFC2616], HTTPS [RFC2818], LDAP [RFC4516], and MID [RFC2392] are the URI schemes most commonly used by current implementations. Example: ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, c=US???(cn=Jim%20Dolittle)":mailto:ji…
…7 ], FILE RFC1738 ], FTP [ RFC1738 ], HTTP [ RFC2616 ], HTTPS [ RFC2818 ], LDAP RFC4516 ], and MID [ RFC2392 ] are the URI schemes most commonly used by current implementations. Example: ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, c=US???(cn=Jim%20Dolittle)":mailto…
…7 ], FILE RFC1738 ], FTP [ RFC1738 ], HTTP [ RFC2616 ], HTTPS [ RFC2818 ], LDAP RFC4516 ], and MID [ RFC2392 ] are the URI schemes most commonly used by current implementations. Example: ORGANIZER;DIR="ldap://example.com:6666/o=ABC%20Industries, c=US???(cn=Jim%20Dolittle)":mailto…
…rl in the content-type header field of the response. When the LDAP URI scheme [ RFC4516 ] is used, the URI MUST include a <dn> field containing the distinguished name of the entry holding the CRL, MUST include a single <attrdesc> that contains an appropriate attribute description…
…rl in the content-type header field of the response. When the LDAP URI scheme [ RFC4516 ] is used, the URI MUST include a <dn> field containing the distinguished name of the entry holding the CRL, MUST include a single <attrdesc> that contains an appropriate attribute description…
…4010 Alex_Grintsvayg ldap Lightweight Directory Access Protocol Permanent 13442 RFC4516 ldaps prov/ldaps ldaps Provisional 3906 Dave_Thaler leaptofrogans leaptofrogans Permanent 16281 RFC8589 lid prov/lid lid Provisional 10247 IS4 linkid prov/linkid linkid Provisional 1819 Christ…
…4010 Alex_Grintsvayg ldap Lightweight Directory Access Protocol Permanent 13442 RFC4516 ldaps prov/ldaps ldaps Provisional 3906 Dave_Thaler leaptofrogans leaptofrogans Permanent 16281 RFC8589 lid prov/lid lid Provisional 10247 IS4 linkid prov/linkid linkid Provisional 1819 Christ…
…4010 Alex_Grintsvayg ldap Lightweight Directory Access Protocol Permanent 13442 RFC4516 ldaps prov/ldaps ldaps Provisional 3906 Dave_Thaler leaptofrogans leaptofrogans Permanent 16281 RFC8589 lid prov/lid lid Provisional 10247 IS4 linkid prov/linkid linkid Provisional 1819 Christ…
…4010 Alex_Grintsvayg ldap Lightweight Directory Access Protocol Permanent 13442 RFC4516 ldaps prov/ldaps ldaps Provisional 3906 Dave_Thaler leaptofrogans leaptofrogans Permanent 16281 RFC8589 lid prov/lid lid Provisional 10247 IS4 linkid prov/linkid linkid Provisional 1819 Christ…