Home
last modified time | relevance | path

Searched refs:rfc (Results 1 – 25 of 101) sorted by relevance

12345

/netbsd-src/external/mpl/bind/dist/doc/arm/
H A Dgeneral.rst27 https://www.rfc-editor.org/.
29 While reading RFCs, please keep in mind that :rfc:`not all RFCs are
50 :rfc:`1034` - P. Mockapetris. *Domain Names — Concepts and Facilities.* November
53 :rfc:`1035` - P. Mockapetris. *Domain Names — Implementation and Specification.*
56 :rfc:`1183` - C. F. Everhart, L. A. Mamakos, R. Ullmann, P. Mockapetris. *New DNS RR
59 :rfc:`1521` - N. Borenstein, N. Freed - *MIME (Multipurpose Internet Mail Extensions)
63 :rfc:`1706` - B. Manning and R. Colella. *DNS NSAP Resource Records.* October 1994.
65 :rfc:`1712` - C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni. *DNS Encoding of
68 :rfc:`1876` - C. Davis, P. Vixie, T. Goodwin, and I. Dickinson. *A Means for Expressing
71 :rfc
[all...]
H A Dhistory.rst18 1984 with the publication of :rfc:`920`, the core of the new system was
19 described in 1983 in :rfc:`882` and :rfc:`883`. From 1984 to 1987, the ARPAnet
24 based on the working model. :rfc:`1034`, "Domain Names-Concepts and
25 Facilities," and :rfc:`1035`, "Domain Names-Implementation and
H A Dmanaged-keys.inc.rst17 BIND is able to maintain DNSSEC trust anchors using :rfc:`5011` key
25 To configure a validating resolver to use :rfc:`5011` to maintain a trust
33 To set up an authoritative zone for :rfc:`5011` trust anchor maintenance,
39 :rfc:`5011`-managed trust anchor takes note of the stand-by KSKs in the
72 See :rfc:`5011` for more details on key rollover scenarios.
H A Dsig0.inc.rst16 specified in :rfc:`2535` and :rfc:`2931`. SIG(0) uses public/private keys to
H A Dadvanced.inc.rst24 and meaning of these messages is specified in :rfc:`2136`.
40 Updating of secure zones (zones using DNSSEC) follows :rfc:`3007`: RRSIG,
103 The NOTIFY protocol is specified in :rfc:`1996`.
117 zone. The IXFR protocol is specified in :rfc:`1995`.
162 internal networks that are behind filters or in :rfc:`1918` space (reserved
163 IP space, as documented in :rfc:`1918`) to resolve DNS on the Internet.
376 For forward lookups, BIND 9 supports only AAAA records. :rfc:`3363`
387 been completely removed per :rfc:`3363`. Many applications in BIND 9 do not
H A Dlogging-categories.inc.rst37 Log queries that have been forced to use plain DNS due to timeouts. This is often due to the remote servers not being :rfc:`1034`-compliant (not always returning FORMERR or similar to EDNS queries and other extensions to the DNS when they are not understood). In other words, this is targeted at servers that fail to respond to DNS queries that they don't understand.
39 Note: the log message can also be due to packet loss. Before reporting servers for non-:rfc:`1034` compliance they should be re-tested to determine the nature of the non-compliance. This testing should prevent or reduce the number of false-positive reports.
41 Note: eventually :iscman:`named` will have to stop treating such timeouts as due to :rfc:`1034` non-compliance and start treating it as plain packet loss. Falsely classifying packet loss as due to :rfc:`1034` non-compliance impacts DNSSEC validation, which requires EDNS for the DNSSEC records to be returned.
H A Dzones.inc.rst19 This section, largely borrowed from :rfc:`1034`, describes the concept of a
101 server or resolver. In the examples provided in :rfc:`1034`, a style
215 responses from this server. Further details can be found in :rfc:`2308`.
262 The DNS "master file" format was initially defined in :rfc:`1035` and has
317 :rfc:`1035` specifies that the current origin should be restored after
320 construed as a deviation from :rfc:`1035`, a feature, or both.
332 **$TTL** is defined in :rfc:`2308`.
408 to support sub-/24 reverse delegations described in :rfc:`2317`:
/netbsd-src/external/bsd/openldap/dist/doc/guide/
H A Dpreamble.sdf122 RFC Editor|RFC Editor|https://www.rfc-editor.org/
285 …and an Object Class to Hold Uniform Resource Identifiers|https://www.rfc-editor.org/rfc/rfc2079.txt
286 RFC2296|PS|Use of Language Codes in LDAP|https://www.rfc-editor.org/rfc/rfc2296.txt
287 …Approach for Using LDAP as a Network Information Service|https://www.rfc-editor.org/rfc/rfc2307.txt
288 …Protocol (v3): Extensions for Dynamic Directory Services|https://www.rfc-editor.org/rfc/rfc2589.txt
289 RFC2798|I|Definition of the inetOrgPerson LDAP Object Class|https://www.rfc-editor.org/rfc/rfc2798.…
290 RFC2831|PS|Using Digest Authentication as a SASL Mechanism|https://www.rfc-editor.org/rfc/rfc2831.t…
291 RFC2849|PS|The LDAP Data Interchange Format|https://www.rfc-editor.org/rfc/rfc2849.txt
292 RFC3088|X|OpenLDAP Root Service|https://www.rfc-editor.org/rfc/rfc3088.txt
293 RFC3296|PS|Named Subordinate References in LDAP|https://www.rfc-editor.org/rfc/rfc3296.txt
[all …]
/netbsd-src/external/bsd/ppp/dist/
H A DREADME.MPPE49 <http://www.ietf.org/rfc/rfc3078.txt> MPPE
50 <http://www.ietf.org/rfc/rfc3079.txt> MPPE Key Derivation
51 <http://www.ietf.org/rfc/rfc2118.txt> MPPC
52 <http://www.ietf.org/rfc/rfc2637.txt> PPTP
53 <http://www.ietf.org/rfc/rfc2548.txt> MS RADIUS Attributes
/netbsd-src/external/zlib/pigz/dist/zopfli/
H A DREADME14 http://www.ietf.org/rfc/rfc1951.txt
16 http://www.ietf.org/rfc/rfc1950.txt
18 http://www.ietf.org/rfc/rfc1952.txt
/netbsd-src/crypto/external/bsd/openssl/dist/providers/common/der/
H A DEC.asn110 -- (https://www.rfc-editor.org/rfc/rfc3279.html#section-3)
67 -- (https://www.rfc-editor.org/rfc/rfc5758.html#section-3.2)
H A DDSA.asn110 -- (https://www.rfc-editor.org/rfc/rfc3279.html#section-3)
H A DRSA.asn110 -- (https://www.rfc-editor.org/rfc/rfc8017.html#appendix-C)
/netbsd-src/sys/dev/qbus/
H A Dfiles.uba94 device rfc { drive=-1 }
95 attach rfc at uba
97 attach rf at rfc
98 file dev/qbus/rf.c rf | rfc needs-flag
/netbsd-src/external/mpl/bind/dist/doc/notes/
H A Dnotes-9.18.3.rst
/netbsd-src/external/mpl/bind/dist/bin/dnssec/
H A Ddnssec-dsfromkey.rst158 :rfc:`3658` (DS RRs), :rfc:`4509` (SHA-256 for DS RRs),
159 :rfc:`6605` (SHA-384 for DS RRs), :rfc:`7344` (CDS and CDNSKEY RRs).
H A Ddnssec-revoke.rst30 key as defined in :rfc:`5011`, and creates a new pair of key files
78 :iscman:`dnssec-keygen(8) <dnssec-keygen>`, BIND 9 Administrator Reference Manual, :rfc:`5011`.
/netbsd-src/external/mpl/bind/dist/bin/tools/
H A Dnamed-rrchecker.rst62 :rfc:`1034`, :rfc:`1035`, :iscman:`named(8) <named>`.
/netbsd-src/external/bsd/file/dist/magic/magdir/
H A Dssh7 # https://www.rfc-editor.org/rfc/rfc5958
H A Dder143 # Reference: https://www.rfc-editor.org/rfc/rfc2315
/netbsd-src/crypto/external/bsd/openssl/dist/doc/man3/
H A DEVP_chacha20.pod50 L<RFC 7539|https://www.rfc-editor.org/rfc/rfc7539.html#section-2.4>
H A DOSSL_ALGORITHM.pod58 L<PKCS#1 RFC's ASN.1 module|https://www.rfc-editor.org/rfc/rfc8017#appendix-C>
/netbsd-src/crypto/external/bsd/openssl/dist/test/recipes/30-test_evp_data/
H A Devpciph_camellia_cts.txt18 # but is listed here in https://www.rfc-editor.org/errata_search.php?rfc=6803
/netbsd-src/external/bsd/nsd/dist/doc/
H A DREQUIREMENTS198 sent to the address/port the queries originated from. (rfc 2181 4)
212 message is prepended with a 2 byte size (rfc 1035 4.2.2)
246 discarded. (In spirit of rfc 1035 sect 7.3)
248 + RD is copied into the response (rfc 1035 4.1.1) the RA bit is
277 response off (rfc 1035 6.2)
509 When processing the additional section priority is (rfc 2535 3.5 and
510 rfc 2874 4)
572 -NS, SOA, CNAME, and PTR (rfc 1035 3.3)
574 Others defined in (rfc 1035 3.3) are not compressed.
576 BIND8 does compression for all RR from rfc 1035 for which dnames
[all …]
/netbsd-src/external/bsd/openldap/dist/doc/rfc/
H A Drfc2079.txt106 ftp://ds.internic.net/rfc/rfc822.txt
205 <URL:ftp://ds.internic.net/rfc/rfc1738.txt>
208 2.0", RFC 1866, <URL:ftp://ds.internic.net/rfc/rfc1866.txt>

12345