IETF Logo Mail Archive

Re: [IPsec] vendor support of RFC7427

Paul Wouters <paul@nohats.ca> Fri, 07 October 2016 17:58 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 3C7D3129694 for <ipsec@ietfa.amsl.com>; Fri, 7 Oct 2016 10:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.994
X-Spam-Level:
X-Spam-Status: No, score=-4.994 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-2.996] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDu-hk1wrMLB for <ipsec@ietfa.amsl.com>; Fri, 7 Oct 2016 10:58:47 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 2BC361296AA for <ipsec@ietf.org>; Fri, 7 Oct 2016 10:58:47 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3srHM91QfRz3mw; Fri, 7 Oct 2016 19:58:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1475863125; bh=h18cjZAvvGwpSakeO2cLaUxZZtCLF22wqhcMkbsaXPA=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=PLMt0l58e7FIcWf971kSn2HJ46NulHgwtsd0DFHdY5dBpm6M717anklG1f2HeIvW1 l1hVo37A6H1MtAsL967c2bU/wa4i3MEztocGRYrnQo4QFqAKZoyeXazylfGeeRMK0P pXj52tCrDCfiHcRUJwz7fMwtb6hJQ9HKhuWmui9s=
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 JhkWJl2NPfVX; Fri, 7 Oct 2016 19:58:43 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 7 Oct 2016 19:58:43 +0200 (CEST)
Received: from [25.19.82.228] (unknown [24.114.73.137]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id B7F015C839; Fri, 7 Oct 2016 13:58:40 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca B7F015C839
Content-Type: multipart/alternative; boundary="Apple-Mail-5607D0BA-02C8-47CA-A1D6-A791513B004F"
Mime-Version: 1.0 (1.0)
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (14A456)
In-Reply-To: <876523B00C3F9D47BFD2B654D63DBF92BEAA73FA@US70UWXCHMBA05.zam.alcatel-lucent.com>
Date: Fri, 07 Oct 2016 13:58:39 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <92992DC1-D132-4B8F-8944-529AB2D8727F@nohats.ca>
References: <876523B00C3F9D47BFD2B654D63DBF92BEAA73FA@US70UWXCHMBA05.zam.alcatel-lucent.com>
To: "Hu, Jun (Nokia - US)" <jun.hu@nokia.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/hCO9F8Gk0Mis-EH5VhPDDhEciMo>
Cc: IPsecME WG <ipsec@ietf.org>
Subject: Re: [IPsec] vendor support of RFC7427
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 07 Oct 2016 17:58:49 -0000

For libreswan, support is planned Q1 2017

Sent from my iPhone

> On Oct 7, 2016, at 13:33, Hu, Jun (Nokia - US) <jun.hu@nokia.com> wrote:
> 
> Hi,
> I plan to support RFC7427 on my product, however as part of inter-op planning, I’d like to know current industry support status for it;
> The only implementation I know so far is Strongswan which supported it since ver5.3;
> It will be highly appreciated if you could share your product status or roadmap on this RFC
>  
> ------
> Hu Jun
> IP Routing, IP/Optical Networks, Nokia
> New Email: jun.hu@nokia.com
>  
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email