IETF Logo Mail Archive

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

Wang Haiguang <wang.haiguang.shieldlab@huawei.com> Sun, 28 April 2019 15:01 UTC

Return-Path: <wang.haiguang.shieldlab@huawei.com>
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 F071512012D for <i2nsf@ietfa.amsl.com>; Sun, 28 Apr 2019 08:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 1f3vkl26t8n7 for <i2nsf@ietfa.amsl.com>; Sun, 28 Apr 2019 08:01:46 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 6024C12003F for <i2nsf@ietf.org>; Sun, 28 Apr 2019 08:01:46 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 64FE6E18BECB98514EC8 for <i2nsf@ietf.org>; Sun, 28 Apr 2019 16:01:44 +0100 (IST)
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 28 Apr 2019 16:01:44 +0100
Received: from lhreml706-chm.china.huawei.com (10.201.108.55) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Sun, 28 Apr 2019 16:01:43 +0100
Received: from SINEML702-CAH.china.huawei.com (10.223.161.52) by lhreml706-chm.china.huawei.com (10.201.108.55) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Sun, 28 Apr 2019 16:01:43 +0100
Received: from SINEML521-MBX.china.huawei.com ([169.254.1.224]) by SINEML702-CAH.china.huawei.com ([169.254.255.221]) with mapi id 14.03.0415.000; Sun, 28 Apr 2019 23:01:40 +0800
From: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
To: "i2nsf@ietf.org" <i2nsf@ietf.org>
CC: "kent+ietf@watsen.net" <kent+ietf@watsen.net>
Thread-Topic: [I2nsf] Need YANG Doctor reviewing the YANG module of draft-ietf-i2nsf-sdn-ipsec-flow-protection which I2NSF is about to call WGLC
Thread-Index: AQHU/dL6iS1Y+m+rs0GADa2AAfKHNg==
Date: Sun, 28 Apr 2019 15:01:40 +0000
Message-ID: <0AE05CBFB1A6A0468C8581DAE58A31309E3E027E@SINEML521-MBX.china.huawei.com>
Accept-Language: en-SG, en-US
Content-Language: en-SG
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.34.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/n4_qL24Xcaoh05pL2c40gtlbXkA>
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 15:01:48 -0000

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

v2.23.0 | Report a Bug | By Email