DNS X-Proxied-For
draft-bellis-dnsop-xpf-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-07-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
DNSOP Working Group R. Bellis
Internet-Draft ISC
Updates: RFC 2845, RFC 2931 (if P. van Dijk
approved) (if approved) R. Gacogne
Intended status: Standards Track PowerDNS
Expires: January 4, 2018 July 03, 2017
DNS X-Proxied-For
draft-bellis-dnsop-xpf-02
Abstract
It is becoming more commonplace to install front end proxy devices in
front of DNS servers to provide (for example) load balancing or to
perform transport layer conversions.
This document defines a meta resource record that allows a DNS server
to receive information about the client's original transport protocol
parameters when supplied by trusted proxies.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 4, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Bellis, et al. Expires January 4, 2018 [Page 1]
Internet-Draft DNS X-Proxied-For July 2017
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Proxy Processing . . . . . . . . . . . . . . . . . . . . 3
3.2. Server Processing . . . . . . . . . . . . . . . . . . . . 4
3.3. Wire Format . . . . . . . . . . . . . . . . . . . . . . . 4
3.4. Presentation Format . . . . . . . . . . . . . . . . . . . 5
3.5. Signed DNS Requests . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
It is becoming more commonplace to install front end proxy devices in
front of DNS servers [RFC1035] to provide load balancing or to
perform transport layer conversions (e.g. to add DNS over TLS
[RFC7858] to a DNS server that lacks native support).
This has the unfortunate side effect of hiding the clients' source IP
addresses from the server, making it harder to employ server-side
technologies that rely on knowing those addresses (e.g. ACLs, DNS
Response Rate Limiting, etc).
This document defines a DNS meta resource record (RR) that allows a
DNS server to receive information about the client's original
transport protocol parameters when supplied by trusted proxies.
Whilst in some circumstances it would be possible to re-use the
Client Subnet EDNS Option [RFC7871] to carry a subset of this
information, a new RR is defined to allow both this feature and the
Client Subnet Option to co-exist in the same packet.
Bellis, et al. Expires January 4, 2018 [Page 2]
Internet-Draft DNS X-Proxied-For July 2017
Show full document text