... LDAP: Additional Matching Rules February 2004 The following descriptors have been added: NAME Type OID ------------------------ ---- --------- booleanMatch M 2.5.13.13 caseExactMatch M 2.5.13.5 caseExactOrderingMatch M 2.5.13.6 caseExactSubstringsMatch M ...
... Values: format typical maximum _ _ _ 0 0 _ _ L 4 5 _ _ Last 9 13 _ M _ 4 5 _ M L 5 10 _ M Last 13 18 _ Middle _ 8 14 _ Middle L 12 19 Finseth [Page 3] RFC 1439 Uniqueness of Unique Identifiers March 1993 _ Middle Last 17 27 F _ _ 4 5 F _ L 5 10 F _ Last ...
... further information: Kurt Zeilenga <kurt@OpenLDAP.org> Usage: see table Specification: RFC 4523 Author/Change Controller: IESG algorithmIdentifierMatch M 2.5.13.40 authorityRevocationList A 2.5.4.38 * cACertificate A 2.5.4.37 * cRLDistributionPoint O 2.5 ...
... A 2.5.4.38 [RFC2256] Zeilenga Best Current Practice [Page 14] RFC 3383 IANA Considerations for LDAP September 2002 bitStringMatch M 2.5.13.16 [RFC2252] buildingName A 0.9.2342.19200300.100.1.48 [RFC1274] businessCategory A 2.5.4.15 [RFC2256] C A 2.5.4.6 ...
... k-1 octets: EM = EME-PKCS1-V1_5-ENCODE (M, k-1) If the encoding operation outputs ... to the encoded message EM to recover a message M: M = EME-PKCS1-V1_5-DECODE (EM ...
[
Текст
]
Ссылки http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc2437.txt.pdf -- 47.6 Кб -- 27.03.2002 Похожие документы
... Slot Width (GHz) = 12.5 GHz * m The Reserved field MUST be set to zero on transmission and SHOULD be ignored on receipt. ... 05 - 193.1) / 0.00625 = -8 m = 4 : Slot Width (GHz) = 12.5 GHz * m 50 (GHz) = 12.5 (GHz) * mm = 50 / 12.5 = 4 Farrel, et al ...