IETF Logo Mail Archive

[IPsec] Hi, chairs. Request a time slot for a new draft: Using ShangMi in the Internet Key Exchange Protocol Version 2 (IKEv2)

Tero Kivinen <kivinen@iki.fi> Wed, 13 March 2024 00:32 UTC

Return-Path: <kivinen@iki.fi>
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 4CA26C14F69E for <ipsec@ietfa.amsl.com>; Tue, 12 Mar 2024 17:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iki.fi
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 fr_n-yiCOF9A for <ipsec@ietfa.amsl.com>; Tue, 12 Mar 2024 17:32:09 -0700 (PDT)
Received: from meesny.iki.fi (meesny.iki.fi [IPv6:2001:67c:2b0:1c1::201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24CF0C14F5EB for <ipsec@ietf.org>; Tue, 12 Mar 2024 17:32:03 -0700 (PDT)
Received: from fireball.acr.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kivinen@iki.fi) by meesny.iki.fi (Postfix) with ESMTPSA id 4TvWfl2dZ9zyPV; Wed, 13 Mar 2024 02:31:59 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1710289919; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RWz45dmo8hAMiQR77sy8v4VIlAMjLmMuLA1bKkLCr4Y=; b=QJS6hiJrCNb5FPF+UpadSvi+ZUprvGNnC9XptAIerB6JdvFxXOM3iOUEaFTOnbuUzsNVfS WvcNLUJBJxpg4J/rf/WNuamd/jnWHPMS75okMlA2UHZjRIKMbmOX0KeWYw9g6Vtydan290 5umAshfTGJKX347+dSEJUUytKdpTjcc=
ARC-Seal: i=1; s=meesny; d=iki.fi; t=1710289919; a=rsa-sha256; cv=none; b=Y2Zn0p/ynRFvP1hEWb81VWo9QabNZFEQix4AGQUCLBxW+tuLY6kibY/Bp7nSIGvTaL37kP hEtqzwu1WcUnaO9ER809xqYwbA3wgPa3+E9oK+drV08sM0Z20jurKMcdlHRp1o6USeMpjF 2ST8OZ+dDxSKm5X+9M2ifgKsfOndomw=
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen@iki.fi smtp.mailfrom=kivinen@iki.fi
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1710289919; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RWz45dmo8hAMiQR77sy8v4VIlAMjLmMuLA1bKkLCr4Y=; b=oJcyqIgpPK/sywYx1rHUS6Sdqf//0vccaPh9cKKHBDLfR3klRP9zGvD+JBzCAx5S632cMJ 9qkA8BUFD67iADmvKTsfHz1M8jAXvd0OUNJ9ZKNOk/+212vIof0t51FWcomQgFPxsPFKHG gO0I8RiX0OT83R9a5RYagTcd7AlfE7A=
Received: by fireball.acr.fi (Postfix, from userid 15204) id C6F1C25C12AF; Wed, 13 Mar 2024 02:31:58 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <26096.62462.734013.501918@fireball.acr.fi>
Date: Wed, 13 Mar 2024 02:31:58 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: "Xialiang(Frank, IP Security Standard)" <frank.xialiang=40huawei.com@dmarc.ietf.org>
Cc: "ipsec@ietf.org" <ipsec@ietf.org>
In-Reply-To: <213ef59ef084497da9f7247b0e787790@huawei.com>
References: <213ef59ef084497da9f7247b0e787790@huawei.com>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 1 min
X-Total-Time: 1 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/VwkhLoArOVRIkwuir1Zce5-DjoM>
Subject: [IPsec] Hi, chairs. Request a time slot for a new draft: Using ShangMi in the Internet Key Exchange Protocol Version 2 (IKEv2)
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: Wed, 13 Mar 2024 00:32:10 -0000

Xialiang\(Frank,  IP Security Standard\) writes:
> We have a new draft on IKEv2 support for ShangMi cryptographic algorithm
> suites: 
> https://datatracker.ietf.org/doc/draft-guo-ipsecme-ikev2-using-shangmi/.
> 
> The main purpose of this draft is to describe how the Chinese mandatory and
> ISO standard ShangMi cryptographic algorithms can be used with IKEv2 to enable
> interoperability between vendors in use cases where it needs to be supported.
> In addition, it is recommended that related algorithms be added to the IANA
> table of IKEv2 Parameters.
> 
> So, we request 10 minutes to present it and collect the comments from the
> working group.

I think we will have time for short presentation for this in the
IPsecME, even if it would then end up on ISE or some other stream. I
added it to the end of agenda.
-- 
kivinen@iki.fi

v2.23.0 | Report a Bug | By Email