IETF Logo Mail Archive

Re: [IPsec] New Version Notification for draft-ietf-ipsecme-add-ike-04.txt

Paul Wouters <paul@nohats.ca> Tue, 30 August 2022 16:37 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7404CC15C51D; Tue, 30 Aug 2022 09:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3eBaexCGknF; Tue, 30 Aug 2022 09:37:48 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1704BC15C518; Tue, 30 Aug 2022 09:37:47 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4MHCf10kvsz43J; Tue, 30 Aug 2022 18:37:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1661877465; bh=3XrtVXWB7zjLfjtYiX7i1GPokVb9Yp5P/7Bqz9bJBC8=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=hgq7A0Y7VwSwbSstMVMYtoQ2m99FCcZH0exGTLqTMTVJSrH6WwbocKeOVStX4jfKh cz5BKXpzSJfKRZhBog4wSmlx2UR+qtBjI1ya5tCF8bVY0oTtrOIGHDHvpjrZ3SGzQ2 bewSOneUlWw7fD0sah/edQFqhObfXLynTYuB92/I=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id VMBP3H9aw6Ck; Tue, 30 Aug 2022 18:37:44 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 30 Aug 2022 18:37:44 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 471A63BFD27; Tue, 30 Aug 2022 12:37:43 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 440CB3BFD26; Tue, 30 Aug 2022 12:37:43 -0400 (EDT)
Date: Tue, 30 Aug 2022 12:37:43 -0400
From: Paul Wouters <paul@nohats.ca>
To: mohamed.boucadair@orange.com
cc: "ipsec@ietf.org" <ipsec@ietf.org>, Tero Kivinen <kivinen@iki.fi>, "draft-ietf-ipsecme-add-ike@ietf.org" <draft-ietf-ipsecme-add-ike@ietf.org>
In-Reply-To: <32731_1661849667_630DD043_32731_343_1_2f6dfac6241e449d9d73d72317042be3@orange.com>
Message-ID: <4170fb34-6283-c039-7160-d24015682aaa@nohats.ca>
References: <166184767062.54385.12012013642312445776@ietfa.amsl.com> <32731_1661849667_630DD043_32731_343_1_2f6dfac6241e449d9d73d72317042be3@orange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/N1Tx5UgTlHIjDvAYjmLDr76f_-s>
Subject: Re: [IPsec] New Version Notification for draft-ietf-ipsecme-add-ike-04.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2022 16:37:52 -0000

On Tue, 30 Aug 2022, mohamed.boucadair@orange.com wrote:

> This version takes into account the comments received during the WGLC, mainly the edits suggested by Tommy.

 	If the initiator sends multiple attributes of a particular type in
 	the request, all of them MUST be distinct (either be empty or
 	containing different suggested resolvers).

What does it mean when multiple attributes of a particular type are
sent, where one is empty and one is not empty? I think perhaps this
text means to say either it sends one empty one, or it sends multiple
non-empty ones?

Another comment on text unchanged in the latest revision that I just
noticed:

    For split-tunnel VPN configurations, the endpoint uses the
    Enterprise-provided encrypted DNS resolver to resolve internal-only
    domain names.

What if one of the reasons I want a split-tunnel, is to actually use an
encrypted DNS over the VPN to protect my non-VPN traffic? This use case
is not captured in A1?

Paul

v2.23.0 | Report a Bug | By Email