Home
last modified time | relevance | path

Searched refs:specification (Results 1 – 25 of 589) sorted by relevance

12345678910>>...24

/netbsd/src/external/bsd/openldap/dist/doc/rfc/
Drfc4510.txt38 The technical specification detailing version 3 of the Lightweight
64 to the protocol specified by this technical specification. The LDAP
78 of the LDAP technical specification.
88 This technical specification defines LDAP in terms of [X.500] as an
98 This technical specification explicitly incorporates portions of
100 this technical specification.
104 This technical specification, as defined in Section 1, obsoletes
105 entirely the previously defined LDAP technical specification defined
107 3377 itself). The technical specification was significantly
129 specification.
[all …]
Drfc3672.txt52 otherwise in this specification.
88 for the specification of a subset of entries in a subtree of the
92 subtree specification is always used within a context or scope which
94 scope of a subtree specification for a subschema administrative area
96 entries for subschema administration. Where a subtree specification
140 specification. When all of the components of SubtreeSpecification
148 The LDAP syntax specification is:
162 subtree specification is used, in which case the base component
348 technical specification. The following registration template is
381 allocation [PRIVATE], for use in this specification.
[all …]
Drfc4013.txt69 This document does not alter the technical specification of any
70 existing protocols. Any specification that wishes to use the
73 algorithm is used by implementations of that specification.
175 However, due to an anomaly [PR29] in the specification of Unicode
178 well-formed text. This specification was published despite this
179 known technical problem. It is expected that this specification will
318 specification can be obtained from the IETF on-line IPR repository at
Drfc4532.txt29 This specification provides a mechanism for Lightweight Directory
37 This specification describes a Lightweight Directory Access Protocol
43 This specification is intended to replace the existing Authorization
76 specification, the term "the authorization identity" and "the
236 allocation [PRIVATE], for use in this specification.
374 specification can be obtained from the IETF on-line IPR repository at
Drfc4518.txt88 The lack of precise specification for character string matching has
132 or referenced by this specification are derived from Unicode
134 purpose of implementing this specification.
138 This document is an integral part of the LDAP technical specification
140 specification [RFC3377] in its entirety.
183 The term "combining mark", as used in this specification, refers to
204 Note that this six-step process specification is intended to describe
208 specification.
574 specification.
766 specification can be obtained from the IETF on-line IPR repository at
/netbsd/src/external/gpl3/gcc/dist/libgomp/
Dlibgomp.texi158 * OpenMP 4.5:: Feature completion status to 4.5 specification
159 * OpenMP 5.0:: Feature completion status to 5.0 specification
160 * OpenMP 5.1:: Feature completion status to 5.1 specification
170 The OpenMP 4.5 specification is fully supported.
175 @unnumberedsubsec New features listed in Appendix B of the OpenMP specification
272 @unnumberedsubsec New features listed in Appendix B of the OpenMP specification
355 specification in version 4.5. The routines are structured in following
445 @uref{https://www.openmp.org, OpenMP specification v4.5}, Section 3.2.20.
474 @uref{https://www.openmp.org, OpenMP specification v4.5}, Section 3.2.18.
502 @uref{https://www.openmp.org, OpenMP specification v4.5}, Section 3.2.9.
[all …]
Dlibgomp.info133 * OpenMP 4.5:: Feature completion status to 4.5 specification
134 * OpenMP 5.0:: Feature completion status to 5.0 specification
135 * OpenMP 5.1:: Feature completion status to 5.1 specification
147 The OpenMP 4.5 specification is fully supported.
155 New features listed in Appendix B of the OpenMP specification
268 New features listed in Appendix B of the OpenMP specification
370 OpenMP specification in version 4.5. The routines are structured in
458 OpenMP specification v4.5 (https://www.openmp.org), Section 3.2.20.
484 OpenMP specification v4.5 (https://www.openmp.org), Section 3.2.18.
508 OpenMP specification v4.5 (https://www.openmp.org), Section 3.2.9.
[all …]
/netbsd/src/external/ibm-public/postfix/dist/src/global/
Dmap_search.ref2 unknown: warning: malformed map specification: 'type'
7 unknown: warning: malformed map specification: 'missing '}' in "{type:name"'
9 unknown: warning: malformed map specification: '{type}'
/netbsd/src/external/gpl3/gdb/dist/sim/erc32/
DREADME.erc3238 The interrupt controller is implemented as in the MEC specification with
55 specification. Traps are correctly generated, and the system fault status
102 The watchdog is implemented as in the specification. The input clock is
113 Implemented as in the specification (0x01f800004, write-only).
117 The power-down register (0x01f800008) is implemented as in the specification.
/netbsd/src/external/gpl3/gdb/dist/gdb/testsuite/gdb.cp/
Dnsalias.exp149 {specification :$im_foo_label}
155 {specification :$i_foo_label}
161 {specification :$o_foo_label}
/netbsd/src/external/gpl3/gdb/dist/gdb/tui/
Dtui-layout.h105 virtual void specification (ui_file *output, int depth) = 0;
185 void specification (ui_file *output, int depth) override;
262 void specification (ui_file *output, int depth) override;
/netbsd/src/etc/bluetooth/
Dprotocols6 # https://www.bluetooth.org/en-us/specification/assigned-numbers
7 # https://www.bluetooth.org/en-us/specification/adopted-specifications
/netbsd/src/external/bsd/wpa/dist/hostapd/
DREADME-MULTI-AP10 The Wi-Fi Alliance Multi-AP Specification is the technical specification for
17 Most of the Multi-AP specification falls outside of the scope of
42 Multi-AP specification doesn't dictate this, but typically the backhaul link
122 WPA2-Personal is supported in the Multi-AP specification, so there is no need
135 not follow the Multi-AP specification, wpa_supplicant will fail to associate.
159 [3] https://www.wi-fi.org/file/multi-ap-specification-v10
/netbsd/src/crypto/external/bsd/libsaslc/dist/ref/
Drfc4422.txt197 - protocol designers using this specification to support
305 specification. In some circumstances, the precise identity forms
308 authorization (proxy authorization) policy specification may dictate
611 and AUTH POP Response Codes [RFC3206] specification for an example).
663 either through negotiation or by its specification.
668 protocol's technical specification), only one successful SASL
693 protocol specific. The protocol's technical specification should be
703 In order for a protocol to offer SASL services, its specification
743 the specification MUST describe how messages with an empty
761 defined with this field, the specification MUST describe how
[all …]
/netbsd/src/crypto/external/bsd/heimdal/dist/lib/wind/
Drfc4013.txt69 This document does not alter the technical specification of any
70 existing protocols. Any specification that wishes to use the
73 algorithm is used by implementations of that specification.
175 However, due to an anomaly [PR29] in the specification of Unicode
178 well-formed text. This specification was published despite this
179 known technical problem. It is expected that this specification will
318 specification can be obtained from the IETF on-line IPR repository at
Drfc4518.txt88 The lack of precise specification for character string matching has
132 or referenced by this specification are derived from Unicode
134 purpose of implementing this specification.
138 This document is an integral part of the LDAP technical specification
140 specification [RFC3377] in its entirety.
183 The term "combining mark", as used in this specification, refers to
204 Note that this six-step process specification is intended to describe
208 specification.
574 specification.
766 specification can be obtained from the IETF on-line IPR repository at
/netbsd/src/crypto/dist/ipsec-tools/src/racoon/rfc/
Drfc4109.txt29 Exchange version 1 (IKEv1) specification do not reflect the current
30 reality of the IPsec market requirements. The original specification
33 specification, and is intended for all IKEv1 implementations deployed
91 MODP groups with elliptic curves. Section 4 of that specification
261 specification can be obtained from the IETF on-line IPR repository at
/netbsd/src/crypto/external/bsd/netpgp/dist/doc/
Ddeliverable.txt17 standards. This specification does not constitute a commitment to
21 The library will comply with the IETF specification currently known as
/netbsd/src/external/bsd/byacc/dist/package/
Dbyacc.spec19 specification from a file and generates an LR(1) parser for it. The
29 specification from a file and generates an LR(1) parser for it. The
/netbsd/src/external/bsd/ppp/dist/
DREADME.cbcp15 the cbcp client *only* portion of the specification. It is primarily
18 The ietf-working specification may be obtained from ftp.microsoft.com
/netbsd/src/external/bsd/wpa/dist/wpa_supplicant/
DREADME-NAN-USD5 in the Wi-Fi Aware specification v4.0 can be used with wpa_spplicant.
43 the Wi-Fi Aware specification.
68 the Wi-Fi Aware specification.
/netbsd/src/external/gpl3/binutils/dist/include/vms/
DChangeLog-101575 Add record begin/end, enumerations, type specification, value
76 specification, label, discontinue range definitions.
/netbsd/src/external/gpl3/gdb/dist/include/vms/
DChangeLog-101575 Add record begin/end, enumerations, type specification, value
76 specification, label, discontinue range definitions.
/netbsd/src/external/bsd/openldap/dist/doc/drafts/
Ddraft-sermersheim-ldap-subordinate-scope-xx.txt44 The Lightweight Directory Application Protocol (LDAP) specification
101 The LDAP URL [RFC2255] specification allows the conveyance of a
143 This specification introduces no security concerns above any
194 this technical specification. The following registration template is
298 specification can be obtained from the IETF on-line IPR repository at
/netbsd/src/external/bsd/byacc/dist/package/pkgsrc/
DDESCR3 Yacc can accept any input specification that conforms to the AT&T

12345678910>>...24