--- 1/draft-ietf-ipsecme-split-dns-04.txt 2018-02-06 09:13:23.491256768 -0800 +++ 2/draft-ietf-ipsecme-split-dns-05.txt 2018-02-06 09:13:23.519257437 -0800 @@ -1,19 +1,19 @@ Network T. Pauly Internet-Draft Apple Inc. Intended status: Standards Track P. Wouters -Expires: July 26, 2018 Red Hat - January 22, 2018 +Expires: August 10, 2018 Red Hat + February 6, 2018 Split DNS Configuration for IKEv2 - draft-ietf-ipsecme-split-dns-04 + draft-ietf-ipsecme-split-dns-05 Abstract This document defines two Configuration Payload Attribute Types for the IKEv2 protocol that add support for private DNS domains. These domains should be resolved using DNS servers reachable through an IPsec connection, while leaving all other DNS resolution unchanged. This approach of resolving a subset of domains using non-public DNS servers is referred to as "Split DNS". @@ -25,21 +25,21 @@ 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 26, 2018. + This Internet-Draft will expire on August 10, 2018. Copyright Notice Copyright (c) 2018 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 @@ -278,57 +278,57 @@ | | +---------------------------------------------------------------+ o Reserved (1 bit) - Defined in IKEv2 RFC [RFC7296]. o Attribute Type (15 bits) 25 - INTERNAL_DNS_DOMAIN. o Length (2 octets, unsigned integer) - Length of domain name. o Domain Name (0 or more octets) - A Fully Qualified Domain Name - used for Split DNS rules, such as example.com, in DNS presentation - format and optionally using IDNA [RFC5890] for Internationalized - Domain Names. Implementors need to be careful that this value is - not null-terminated. + used for Split DNS rules, such as "example.com", in DNS + presentation format and optionally using IDNA [RFC5890] for + Internationalized Domain Names. Implementors need to be careful + that this value is not null-terminated. 4.2. INTERNAL_DNSSEC_TA Configuration Attribute 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-----------------------------+-------------------------------+ |R| Attribute Type | Length | +-+-----------------------------+---------------+---------------+ - | Key Tag | Algorithm | Digest Type | + | DNSKEY Key Tag | DNSKEY Alg | Digest Type | +-------------------------------+---------------+---------------+ | | - ~ Digest ~ + ~ Digest Data ~ | | +---------------------------------------------------------------+ o Reserved (1 bit) - Defined in IKEv2 RFC [RFC7296]. o Attribute Type (15 bits) [TBD IANA] - INTERNAL_DNSSEC_TA. o Length (2 octets, unsigned integer) - Length of DNSSEC Trust Anchor data. - o Key Tag value (0 or 2 octets, unsigned integer) - Key Tag as - specified in [RFC4034] Section 5.1 + o DNSKEY Key Tag value (2 octets) - Delegation Signer (DS) Key Tag + as specified in [RFC4034] Section 5.1 - o Algorithm (0 or 1 octet) - DNSKEY algorithm value from the IANA + o DNSKEY Algorithm (1 octet) - DNSKEY algorithm value from the IANA DNS Security Algorithm Numbers Registry - o DS algorithm (0 or 1 octet) - DS algorithm value from the IANA + o Digest Type (1 octet) - DS algorithm value from the IANA Delegation Signer (DS) Resource Record (RR) Type Digest Algorithms Registry - o Digest (0 or more octets) - The DNSKEY digest as specified in + o Digest Data (2 or more octets) - The DNSKEY digest as specified in [RFC4034] Section 5.1 in presentation format. 5. Split DNS Usage Guidelines If a CFG_REPLY payload contains no INTERNAL_DNS_DOMAIN attributes, the client MAY use the provided INTERNAL_IP4_DNS or INTERNAL_IP6_DNS servers as the default DNS server(s) for all queries. If a client is configured by local policy to only accept a limited number of INTERNAL_DNS_DOMAIN values, the client MUST ignore any