1-100 of about 282 matches for site:www.rfc-editor.org queries relating
https://www.rfc-editor.org/rfc/rfc8484.html
RFC 8484: DNS Queries over HTTPS (DoH) [ RFC Home ] [ TEXT | PDF | HTML ] [ Tracker ] [ IPR ] [ Errata ] [ Info page ] PROPOSED STANDARD Errata
https://www.rfc-editor.org/rfc/rfc6305.html
the way they connect to the Internet; this results in such queries relating to internal
https://www.rfc-editor.org/rfc/rfc6305.txt
the way they connect to the Internet; this results in such queries relating to internal
https://www.rfc-editor.org/rfc/rfc7534.html
by root servers. The idea of offloading IN-ADDR.ARPA queries relating to [ RFC1918
https://www.rfc-editor.org/rfc/rfc6304
root servers. The idea of off-loading IN-ADDR.ARPA queries relating to [ RFC1918
https://www.rfc-editor.org/rfc/rfc7534.txt
by root servers. The idea of offloading IN-ADDR.ARPA queries relating to [RFC1918
https://www.rfc-editor.org/rfc/rfc9156.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9250
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7534
by root servers. The idea of offloading IN-ADDR.ARPA queries relating to [ RFC1918
https://www.rfc-editor.org/info/rfc7534
within individual sites. Devices in such environments may occasionally originate Domain Name System (DNS) queries (so-called "reverse lookups
https://www.rfc-editor.org/rfc/rfc7535.html
approach makes it possible for any DNS zone administrator to sink traffic relating to parts
https://www.rfc-editor.org/rfc/rfc5966.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9458.html
where preventing the linking of requests might justify these costs include: ¶ DNS queries: DNS queries made to
https://www.rfc-editor.org/rfc/rfc3013
defines the mailbox SECURITY for network security issues, ABUSE for issues relating to inappropriate
https://www.rfc-editor.org/rfc/rfc7535.html
approach makes it possible for any DNS zone administrator to sink traffic relating to parts
https://www.rfc-editor.org/rfc/rfc7793.html
to the IPv4 Locally-Served DNS Zones Registry Abstract RFC 6598 specifies that "Reverse DNS queries for Shared
https://www.rfc-editor.org/rfc/rfc7553.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc4472.html
and reverse DNS updates, respectively. The eighth section introduces several miscellaneous IPv6 issues relating to DNS
https://www.rfc-editor.org/bcp/bcp46.txt
defines the mailbox SECURITY for network security issues, ABUSE for issues relating to inappropriate
https://www.rfc-editor.org/rfc/rfc6761.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8375.html
this specification: A. Recursive resolvers at sites using 'home.arpa.' MUST transparently support DNSSEC queries: queries for DNSSEC
https://www.rfc-editor.org/rfc/rfc9665.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9462.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8880.html
record queries (DNS qtype "AAAA", always returning negative responses) and unnecessary IPv4 address record queries (DNS qtype "A
https://www.rfc-editor.org/rfc/rfc7535.txt
approach makes it possible for any DNS zone administrator to sink traffic relating to parts
https://www.rfc-editor.org/rfc/rfc5966.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8484.txt
for Comments: 8484 ICANN Category: Standards Track P. McManus ISSN: 2070-1721 Mozilla October 2018 DNS Queries over HTTPS (DoH) Abstract
https://www.rfc-editor.org/rfc/rfc9230.html
both the client IP address and the content of DNS queries and answers
https://www.rfc-editor.org/rfc/rfc8412.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5782
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7320
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9462
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc6762.html
address 224.0.0.251. 5 . Querying There are two kinds of Multicast DNS queries: one-shot queries of
https://www.rfc-editor.org/rfc/rfc9230.txt
both the client IP address and the content of DNS queries and answers
https://www.rfc-editor.org/rfc/rfc9250.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7320
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5891.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc3013.html
defines the mailbox SECURITY for network security issues, ABUSE for issues relating to inappropriate
https://www.rfc-editor.org/rfc/rfc6303
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8288.html
security considerations relating to URIs. See [RFC7230], Section 9 for security considerations relating to HTTP
https://www.rfc-editor.org/rfc/rfc7793.txt
to the IPv4 Locally-Served DNS Zones Registry Abstract RFC 6598 specifies that "Reverse DNS queries for Shared
https://www.rfc-editor.org/rfc/inline-errata/rfc9250.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9250.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9224.html
to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a
https://www.rfc-editor.org/rfc/rfc8880
record queries (DNS qtype "AAAA", always returning negative responses) and unnecessary IPv4 address record queries (DNS qtype "A
https://www.rfc-editor.org/rfc/rfc9777
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5625
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc4472
and reverse DNS updates, respectively. The eighth section introduces several miscellaneous IPv6 issues relating to DNS
https://www.rfc-editor.org/rfc/rfc5988.html
for security considerations relating to URIs. See [ RFC2616 ] for security considerations relating to HTTP
https://www.rfc-editor.org/rfc/rfc8820.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8820
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
RFC 9761: Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT
https://www.rfc-editor.org/rfc/rfc9761.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc6147
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/inline-errata/rfc7320.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7320.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5397
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7033.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc6761
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8659
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc4472.txt
and reverse DNS updates, respectively. The eighth section introduces several miscellaneous IPv6 issues relating to DNS
https://www.rfc-editor.org/rfc/rfc5617.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8820.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8820
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8023.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8023.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/inline-errata/rfc7320.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7320.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9103.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5397
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7626.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7626.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9374.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/bcp/bcp40.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9665
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9162
network services that implement the protocol operations for submissions and queries that are defined in
https://www.rfc-editor.org/rfc/rfc8932.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc6762.txt
address 224.0.0.251. 5. Querying There are two kinds of Multicast DNS queries: one-shot queries of
https://www.rfc-editor.org/rfc/rfc6762
address 224.0.0.251. 5 . Querying There are two kinds of Multicast DNS queries: one-shot queries of
https://www.rfc-editor.org/rfc/rfc7626.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5855.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
RFC 8980: Report from the IAB Workshop on Design Expectations vs. Deployment Reality in Protocol Dev
https://www.rfc-editor.org/rfc/rfc8980.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
RFC 8980: Report from the IAB Workshop on Design Expectations vs. Deployment Reality in Protocol Dev
https://www.rfc-editor.org/rfc/rfc8980
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9460.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9615.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
RFC 7833: A RADIUS Attribute, Binding, Profiles, Name Identifier Format, and Confirmation Methods fo
https://www.rfc-editor.org/rfc/rfc7833.html
NAI) name identifier format. Finally, the subject confirmation methods allow requests and queries to be
RFC 6116: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
https://www.rfc-editor.org/rfc/rfc6116.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9103.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
RFC 8980: Report from the IAB Workshop on Design Expectations vs. Deployment Reality in Protocol Dev
https://www.rfc-editor.org/rfc/rfc8980.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc5855.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8617.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7809.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8155.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc9536.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc7208.html
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8980.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc3490
looking and similar sounding names. Note that this is a complex issue relating to languages
https://www.rfc-editor.org/rfc/rfc8572
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc8617.txt
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc6151
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF
https://www.rfc-editor.org/rfc/rfc6195
subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF