Re: [I2nsf] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC

Kent Watsen <kent+ietf@watsen.net> Sun, 28 April 2019 23:32 UTC

Return-Path: <0100016a664b52b2-9624f8ca-e827-448b-8380-5e630932e187-000000@amazonses.watsen.net>
X-Original-To: i2nsf@ietfa.amsl.com
Delivered-To: i2nsf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59DBE120221 for <i2nsf@ietfa.amsl.com>; Sun, 28 Apr 2019 16:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 CAyhZjfSOIAf for <i2nsf@ietfa.amsl.com>; Sun, 28 Apr 2019 16:32:55 -0700 (PDT)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF73120241 for <i2nsf@ietf.org>; Sun, 28 Apr 2019 16:32:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1556494373; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=N0fx6qWqck1ZFvjkG78fr9IIna8xfdJKKniK4U6635Q=; b=mHBAFZ4u3Ugx1KH5QlcrKFpRUQurcLQeEfaAmAVyfffTLr7nb3am3hCbNFThsGKv 7fch8XUr4fcC7bVKDyIxFfJUMij2fc04YIh5Y2zZ3i/uzbClQ4r+BkmaSVJq1mTf1IC RJ69m4ceZEbv7GpRBSXdLW1rcL8B8qBJ1i4TMmpc=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016a664b52b2-9624f8ca-e827-448b-8380-5e630932e187-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E71B1C2B-FBF1-450E-B7B9-9F46327D1B3B"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Sun, 28 Apr 2019 23:32:53 +0000
In-Reply-To: <0AE05CBFB1A6A0468C8581DAE58A31309E3E027E@SINEML521-MBX.china.huawei.com>
Cc: "i2nsf@ietf.org" <i2nsf@ietf.org>
To: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
References: <0AE05CBFB1A6A0468C8581DAE58A31309E3E027E@SINEML521-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.04.28-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/3BBBOLaMR4FxLtpxcEyOBRxrr0w>
Subject: Re: [I2nsf] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "*I2NSF: Interface to Network Security Functions mailing list*" <i2nsf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2nsf/>
List-Post: <mailto:i2nsf@ietf.org>
List-Help: <mailto:i2nsf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2nsf>, <mailto:i2nsf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Apr 2019 23:33:07 -0000

Minor updates:

1. The name of the draft is "draft-ietf-netconf-crypto-types" (https://tools.ietf.org/html/draft-ietf-netconf-crypto-types <https://tools.ietf.org/html/draft-ietf-netconf-crypto-types>)

2. The thread on the NETCONF list is here: https://mailarchive.ietf.org/arch/msg/netconf/OLTTOvHZ_6Pk-ush_j7xJOlGe4g <https://mailarchive.ietf.org/arch/msg/netconf/OLTTOvHZ_6Pk-ush_j7xJOlGe4g>;.

Kent



> On Apr 28, 2019, at 11:01 AM, Wang Haiguang <wang.haiguang.shieldlab@huawei.com>; wrote:
> 
> Hi, all
> 
> This is Haiguang Wang from Huawei. I am one of the co-authors of ietf-draft-crypto-types. 
> 
> In view of the discussion in i2nsf mailing list regarding the impact of crypto algorithm types over i2ns snd-ipsec draft, I raise the issue in the netconf mailing list. 
> 
> Expert their has discuss about the issue and give some suggestion. 
> 
> If you are interested in the discussion in i2nsf, please visit the discussion thread with following title in NetConf mailing list. 
> "The maintenance of the algorithm identifiers in draft-ietf-crypto-types"
> 
> We are going to address this in our next draft shortly. 
> 
> Best regards.
> 
> Haiguang
>