IETF Logo Mail Archive

[I2nsf] 答复: Should the draft-xibassnez-i2nsf-capability-01 be characterized as "Information model"? or something else?

"Xialiang (Frank)" <frank.xialiang@huawei.com> Mon, 22 May 2017 01:59 UTC

Return-Path: <frank.xialiang@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 A62DE126DED; Sun, 21 May 2017 18:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level:
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 YTdrOilecPpw; Sun, 21 May 2017 18:59:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F5C7126CB6; Sun, 21 May 2017 18:59:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNM68487; Mon, 22 May 2017 01:59:16 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 22 May 2017 02:59:14 +0100
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by nkgeml412-hub.china.huawei.com (10.98.56.73) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 22 May 2017 09:59:11 +0800
Received: from DGGEML502-MBS.china.huawei.com ([169.254.3.11]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0301.000; Mon, 22 May 2017 09:59:01 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, John Strassner <strazpdj@gmail.com>, "Diego R. Lopez" <diego.r.lopez@telefonica.com>, Aldo Basile <cataldo.basile@polito.it>
CC: "draft-xibassnez-i2nsf-capability@ietf.org" <draft-xibassnez-i2nsf-capability@ietf.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: Should the draft-xibassnez-i2nsf-capability-01 be characterized as "Information model"? or something else?
Thread-Index: AdLQCR2XeTbzSbyKSdWvjS8/OrtaJQCk2cAg
Date: Mon, 22 May 2017 01:59:01 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12BAE2B71@DGGEML502-MBS.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F6592A35F2@SJCEML702-CHM.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F6592A35F2@SJCEML702-CHM.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.159.76]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F12BAE2B71DGGEML502MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.592245F5.0033, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.11, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 32d4bea452f9c3c1f6b1bd083b43637d
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/41GEQtZaNNF6bMurM4cjewgXr3A>
Subject: [I2nsf] 答复: Should the draft-xibassnez-i2nsf-capability-01 be characterized as "Information model"? or something else?
X-BeenThere: i2nsf@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 22 May 2017 01:59:23 -0000

Hi Linda,
I am sure it’s an information model draft, no doubt~~
For clarification, our draft specifies both the NSF-facing interface and Registration interface, since I2NSF capability is the core element for both interfaces.

B.R.
Frank

发件人: Linda Dunbar
发送时间: 2017年5月19日 3:09
收件人: John Strassner; Xialiang (Frank); Diego R. Lopez; Aldo Basile
抄送: draft-xibassnez-i2nsf-capability@ietf.org; i2nsf@ietf.org
主题: Should the draft-xibassnez-i2nsf-capability-01 be characterized as "Information model"? or something else?

John, Frank, Diego and Aldo,

It seems to me that the draft-xibassnez-i2nsf-capability-01 covers the I2NSF rule structure.  In your view, should the draft-xibassnez-i2nsf-capability be characterized as the information model?
If it is characterized as the information model, are they exchanged over the NSF facing interface? Or over the registration interface (identified in the Framework draft)?

Thanks, Linda

v2.23.0 | Report a Bug | By Email