EDNS X-Proxied-For
draft-bellis-dnsop-xpf-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-01-09
|
|
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
Intended status: Standards Track January 09, 2017
Expires: July 13, 2017
EDNS X-Proxied-For
draft-bellis-dnsop-xpf-01
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 an option within the EDNS(0) Extension
Mechanism for DNS that allows a DNS server to receive the original
client source IP address 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 July 13, 2017.
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
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Bellis Expires July 13, 2017 [Page 1]
Internet-Draft EDNS X-Proxied-For January 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. EDNS Option Format . . . . . . . . . . . . . . . . . . . 3
3.2. Proxy Processing . . . . . . . . . . . . . . . . . . . . 4
3.3. Server Processing . . . . . . . . . . . . . . . . . . . . 4
3.4. Secret Key Transaction Authentication for DNS (TSIG) . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
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 address (e.g. ACLs, DNS
Response Rate Limiting, etc).
This document defines an option within the EDNS(0) Extension
Mechanism for DNS [RFC6891] that allows a DNS server to receive the
original client source IP address when supplied by trusted proxies.
Whilst in some circumstances it would be possible to re-use the
Client Subnet EDNS Option [RFC7871] to carry this information, a new
option is defined to allow both this option and the Client Subnet
option to co-exist in the same packet.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
"Key words for use in RFCs to Indicate Requirement Levels" [RFC2119].
Show full document text