Re: [IPsec] WG adoptation call for draft-smyslov-ipsecme-ikev2-aux-02
Tobias Heider <heidert@nm.ifi.lmu.de> Wed, 20 March 2019 20:48 UTC
Return-Path: <heidert@nm.ifi.lmu.de>
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 855B912796D for <ipsec@ietfa.amsl.com>; Wed, 20 Mar 2019 13:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YWBwYFML2hY for <ipsec@ietfa.amsl.com>; Wed, 20 Mar 2019 13:48:35 -0700 (PDT)
Received: from acheron.ifi.lmu.de (acheron.ifi.lmu.de [IPv6:2001:4ca0:4000:1:129:187:214:135]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 485EB124BF6 for <ipsec@ietf.org>; Wed, 20 Mar 2019 13:48:35 -0700 (PDT)
Received: from [192.168.1.144] (r099168.stusta.swh.mhn.de [10.150.99.168]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: heidert) by acheron.ifi.lmu.de (Postfix) with ESMTPSA id B3E16360D60 for <ipsec@ietf.org>; Wed, 20 Mar 2019 21:48:32 +0100 (CET)
From: Tobias Heider <heidert@nm.ifi.lmu.de>
To: ipsec@ietf.org
References: <23688.31062.426962.985107@fireball.acr.fi> <01c701d4da41$3c61f890$b525e9b0$@gmail.com> <6454f07af680410e918431971f3489f2@XCH-ALN-010.cisco.com> <001e01d4ddac$5502d770$ff088650$@nm.ifi.lmu.de> <059301d4de2d$faa5a000$eff0e000$@gmail.com> <000a01d4de79$31d3cc00$957b6400$@nm.ifi.lmu.de> <06b701d4deed$706f1310$514d3930$@gmail.com>
Message-ID: <78b108b7-ab63-3a25-f0e3-9a934a3692a7@nm.ifi.lmu.de>
Date: Wed, 20 Mar 2019 21:48:31 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <06b701d4deed$706f1310$514d3930$@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US-large
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/oakbHXAbpYVI11zOnZFOWul7gg4>
Subject: Re: [IPsec] WG adoptation call for draft-smyslov-ipsecme-ikev2-aux-02
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 20 Mar 2019 20:48:37 -0000
Hi Valery, >> If there is a chance that this is a potential thread (and I fear >> it'll be impossible to proof the opposite), my >> feeling is that the document should say that IKE_INTERMEDIATE MUST >> NOT be supported without the >> support of at least one document defining the payload. > That is implied. I can make this more explicit, by adding something > like that: > > Successful exchange of INTERMEDIATE_EXCHANGE_SUPPORTED > notification only confirms that both parties support INTERMEDIATE > exchange. It is not enough condition to start doing INTERMEDIATE exchange. > A separate documents that utilize this exchange MUST define the > conditions in which peers would do INTERMEDIATE exchanges, the > conditions for ending the sequence of these exchanges and start IKE_AUTH, > and the payloads these exchanges should carry. > > Is it OK for you? I was wondering about what happens when multiple documents utilize the IKE_INTERMEDIATE exchange at the same time. Can two different documents utilize a single exchange of IKE_INTERMEDIATE messages, or must every document add an additional exchange of IKE_INTERMEDIATE messages? Currently the only "user" is the Hybrid PQKE draft which adds up to seven INTERMEDIATE exchanges before the IKE_AUTH, could i just define a draft that includes an additional payload in the first INTERMEDIATE exchange (not knowing whether Hybrid KE is used or not) or would i have to add an eighth INTERMEDIATE exchange? I couldn't find any info on this in the current draft and i feel like this is quite relevant for future users of the exchange. Regards, (another) Tobias
- [IPsec] WG adoptation call for draft-smyslov-ipse… Tero Kivinen
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Panos Kampanakis (pkampana)
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Guggemos
- Re: [IPsec] WG adoptation call for draft-smyslov-… Paul Wouters
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Guggemos
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Andreas Steffen
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Guggemos
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Heider
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Paul Wouters
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Heider
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Heider
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Valery Smyslov
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Heider
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Guggemos
- Re: [IPsec] WG adoptation call for draft-smyslov-… Tobias Guggemos