Split DNS Configuration for IKEv2
draft-ietf-ipsecme-split-dns-17

Document Type Active Internet-Draft (ipsecme WG)
Last updated 2019-03-21 (latest revision 2019-03-11)
Replaces draft-pauly-ipsecme-split-dns
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
On Agenda ipsecme at IETF-104
Document shepherd David Waltermire
Shepherd write-up Show (last changed 2018-03-01)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Eric Rescorla
Send notices to David Waltermire <david.waltermire@nist.gov>
IANA IANA review state Version Changed - Review Needed
IANA action state In Progress
RFC Editor RFC Editor state EDIT
Network                                                         T. Pauly
Internet-Draft                                                Apple Inc.
Intended status: Standards Track                              P. Wouters
Expires: September 12, 2019                                      Red Hat
                                                          March 11, 2019

                   Split DNS Configuration for IKEv2
                    draft-ietf-ipsecme-split-dns-17

Abstract

   This document defines two Configuration Payload Attribute Types
   (INTERNAL_DNS_DOMAIN and INTERNAL_DNSSEC_TA) for the Internet Key
   Exchange Protocol Version 2 (IKEv2).  These payloads add support for
   private (internal-only) DNS domains.  These domains are intended to
   be resolved using non-public DNS servers that are only reachable
   through the IPsec connection.  DNS resolution for other domains
   remains unchanged.  These Configuration Payloads only apply to split
   tunnel configurations.

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 https://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 September 12, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Pauly & Wouters        Expires September 12, 2019               [Page 1]
Internet-Draft      Split DNS Configuration for IKEv2         March 2019

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Exchange . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Configuration Request . . . . . . . . . . . . . . . . . .   5
     3.2.  Configuration Reply . . . . . . . . . . . . . . . . . . .   6
     3.3.  Mapping DNS Servers to Domains  . . . . . . . . . . . . .   6
     3.4.  Example Exchanges . . . . . . . . . . . . . . . . . . . .   6
       3.4.1.  Simple Case . . . . . . . . . . . . . . . . . . . . .   6
       3.4.2.  Requesting Domains and DNSSEC trust anchors . . . . .   7
   4.  Payload Formats . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  INTERNAL_DNS_DOMAIN Configuration Attribute Type Request
           and Reply . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  INTERNAL_DNSSEC_TA Configuration Attribute  . . . . . . .   9
   5.  INTERNAL_DNS_DOMAIN Usage Guidelines  . . . . . . . . . . . .  10
   6.  INTERNAL_DNSSEC_TA Usage Guidelines . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   Split tunnel Virtual Private Network ("VPN") configurations only send
   packets with a specific destination IP range, usually chosen from
   [RFC1918], via the VPN.  All other traffic is not sent via the VPN.
   This allows an enterprise deployment to offer Remote Access VPN
   services without needing to accept and forward all the non-enterprise
   related network traffic generated by their remote users.  Resources
   within the enterprise can be accessed by the user via the VPN, while
   all other traffic generated by the user is not send over the VPN.

   These internal resources tend to only have internal-only DNS names
   and require the use of special internal-only DNS servers to get
   resolved.  Split DNS [RFC2775] is a common configuration that is part
   of split tunnel VPN configurations to support configuring Remote
Show full document text