[IPsec] IETF114 scheduling
Robert Moskowitz <rgm-sec@htt-consult.com> Tue, 28 June 2022 11:15 UTC
Return-Path: <rgm-sec@htt-consult.com>
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 1B80AC15C7DD for <ipsec@ietfa.amsl.com>; Tue, 28 Jun 2022 04:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 oR9NB7kpVbyc for <ipsec@ietfa.amsl.com>; Tue, 28 Jun 2022 04:15:24 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 B0D97C131828 for <ipsec@ietf.org>; Tue, 28 Jun 2022 04:15:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 9090762573 for <ipsec@ietf.org>; Tue, 28 Jun 2022 07:14:25 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mwGkQA0DLEIL for <ipsec@ietf.org>; Tue, 28 Jun 2022 07:14:21 -0400 (EDT)
Received: from [10.20.15.47] (unknown [65.38.93.2]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 578BE624D4 for <ipsec@ietf.org>; Tue, 28 Jun 2022 07:14:20 -0400 (EDT)
Message-ID: <5be1df0b-4669-4e92-7335-92f1f42a60e8@htt-consult.com>
Date: Tue, 28 Jun 2022 07:15:02 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
From: Robert Moskowitz <rgm-sec@htt-consult.com>
To: IPsecME WG <ipsec@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/HrQ4dcJKgBg3Vb0IJPQBaR_krm4>
Subject: [IPsec] IETF114 scheduling
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, 28 Jun 2022 11:15:26 -0000
Right now, ipsecme is slotted together with tls. I guess they assume no overlap of interest? :) I do have interest in both, provided there is discussion of diet-esp at 114. I do have commitments working with the FAA on their TLS extension. Bob
- [IPsec] IETF114 scheduling Robert Moskowitz
- Re: [IPsec] IETF114 scheduling Daniel Migault