Re: [I2nsf] Hi, I2NSF chairs. Request time slots for 2 data model drafts:

"Diego R. Lopez" <diego.r.lopez@telefonica.com> Sat, 03 November 2018 15:20 UTC

Return-Path: <diego.r.lopez@telefonica.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 8D69B1286E7 for <i2nsf@ietfa.amsl.com>; Sat, 3 Nov 2018 08:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level:
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.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 4C3QPp8pcKkm for <i2nsf@ietfa.amsl.com>; Sat, 3 Nov 2018 08:20:41 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0716.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe02::716]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8591D1277D2 for <i2nsf@ietf.org>; Sat, 3 Nov 2018 08:20:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BYopX7kPe5Wyr8j9FucO+ZHHH0DiQJf2SXxjzF9O+/g=; b=Z3XLqkpAINrzjLLHj+/8Xvcmk2vyd5Gm08TbDeqy7T9JV5dpqP1rM0C3yrTkdSsEaM60pyv3KJIjmF7NaO/l3NUS0eaUAvbqucjTos005jcJKR1orfiPhxE41PmMRo1omzrOE8nXhxZfCj9Zcq5pt7YqKC2pzFt+fB4c5a1vP2Y=
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com (52.134.70.148) by DB3PR0602MB3772.eurprd06.prod.outlook.com (52.134.73.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.26; Sat, 3 Nov 2018 15:20:37 +0000
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::7469:d759:740d:7c53]) by DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::7469:d759:740d:7c53%3]) with mapi id 15.20.1273.032; Sat, 3 Nov 2018 15:20:37 +0000
From: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
To: "Panwei (William)" <william.panwei@huawei.com>, Linda Dunbar <linda.dunbar@huawei.com>, Yoav Nir <ynir.ietf@gmail.com>
CC: "Linqiushi (Jessica, CSPL)" <linqiushi@huawei.com>, "i2nsf@ietf.org" <i2nsf@ietf.org>, "Xialiang (Frank, Network Integration Technology Research Dept)" <frank.xialiang@huawei.com>
Thread-Topic: [I2nsf] Hi, I2NSF chairs. Request time slots for 2 data model drafts:
Thread-Index: AQHUc4i00D2f03RLL0WWaa2yBVPrfQ==
Date: Sat, 03 Nov 2018 15:20:08 +0000
Message-ID: <BF2F488E-8515-4029-9167-374AC35AEE00@telefonica.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.3.181015
authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com;
x-originating-ip: [81.44.233.203]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB3PR0602MB3772; 6:DrDPW2/xGUsHy2BblsJ0A7j9m3+RQXfLIj+bEkdXs+VdESDWqrtU6DicfZLnZLuXPXdAFPZVfIDWNxQofQ6tpwBNp6Edg5Q/TMqNoQVXEPuPIlkvtkO/jDSYBkgGa3VbFyGwBmATQxgc0wAjgXiKd3KOqmejUjEuQjY65HwuJd9A9zsxVSYaMPx2ws9baHlFt6y7Zr4v6/pms83qKoGiQ2sVykrZ58Wzi4bRoX2YN18wip847swhy0Jc/FAwYTdGL04zaUhETrFPOXcyyK8zXVv6LOmWGDa5TePV7x5p/bAEGJrYobwbhSWNImn3yJpGCleJlC0XJ70TFX++WfpSQ7vG2I+OR77Tu61Fn2O69AFKGoxKKuPpHIl+pXWZw7hlCvpryE2JF7E3GznR3Uaw40w8rrcB7248YSW1uHYDdJ/IFNs/iLbC1INTQBUBwT6JUqtibMdEjVpNZzs0rLDebQ==; 5:jGnk8XqcqHys+9Zo32F4T1bV4LwWV5897MF+PFXlWBVDoGM6ZnWNFjK/1hY4B2IA1ANAJeYzUVgyyadX9MhUsp3uxyE/LaMltld8Hh1d032w8S3I8tqRnfdwoWxDFxQ5aOpd7Q6mo3y0nMvFBeM5SweXFLnKH3Z0WLwpMsD5CU4=; 7:vKjuV9BF1Tu7ipilYdTA/t51bcrIlxHfh0fc2oG06Bogcr+C55GHybosZF/b9fsTLCbFOPoFydf47kO7HBhMQtlKIxI5ItOKMOQqZV+ZFJtPBG8NBEE98krXBMiTbUbBBEf6jjUzRdJxEqscIv54vw==
x-ms-office365-filtering-correlation-id: 44b9d483-121c-4158-cb10-08d6419fe8a0
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DB3PR0602MB3772;
x-ms-traffictypediagnostic: DB3PR0602MB3772:
x-microsoft-antispam-prvs: <DB3PR0602MB37721443E6EAAE3E09564447DFC80@DB3PR0602MB3772.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(128460861657000)(81160342030619)(40392960112811)(50582790962513)(192374486261705)(85827821059158)(163750095850)(21748063052155)(28532068793085)(190501279198761);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231382)(944501410)(52105095)(6055026)(148016)(149066)(150057)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:DB3PR0602MB3772; BCL:0; PCL:0; RULEID:; SRVR:DB3PR0602MB3772;
x-forefront-prvs: 08457955C4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(136003)(366004)(396003)(39860400002)(252514010)(40134004)(189003)(199004)(81166006)(110136005)(476003)(6436002)(54906003)(316002)(99286004)(58126008)(25786009)(39060400002)(786003)(53936002)(6486002)(14444005)(256004)(26005)(97736004)(102836004)(6246003)(4326008)(2906002)(186003)(82746002)(86362001)(6506007)(3846002)(53546011)(105586002)(106356001)(66066001)(966005)(6116002)(6512007)(790700001)(2616005)(81156014)(606006)(36756003)(229853002)(8936002)(478600001)(54896002)(6306002)(8676002)(7736002)(71190400001)(71200400001)(14454004)(6666004)(45080400002)(236005)(83716004)(68736007)(5660300001)(2900100001)(66574009)(486006)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR0602MB3772; H:DB3PR0602MB3788.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: zOKtFDhWPAv1YMtHgWZuY+WEB8NkiGGa5k6AGSDMBx8OTC9NjUhbEYsUIk3P/z2S5f9qwXtkIWxlcGq+xkfjPI3SZSbpSzXwSR/6+IJzfGRrECrPjqv9IiTvM9DKrNRxy0FLnHGtrzYnFW4jplCrBPMTUcxVxCPwpp/FXw+DJajOEeqsP2mi7DY5JERj7NM6Wcr9ChJa+KgwgVQXhLTySL4CiIPzJ3OVusf6ha1UbKJV1ES9ZRkE5UnYGV4BPvxPgocN5YX8gv5norZcrJl6fIWLjAIorwB3046h9xcXZk2KLAw2y3XTQ3CBaQ/ErhfP3iDEqms4LqybaQhn2ySm/EjeZgLcP82wzI7GAGz52xk=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BF2F488E851540299167374AC35AEE00telefonicacom_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 44b9d483-121c-4158-cb10-08d6419fe8a0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Nov 2018 15:20:08.3237 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR0602MB3772
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/5gn2uR0VeZNhD9IubHYIdEzMItA>
Subject: Re: [I2nsf] Hi, I2NSF chairs. Request time slots for 2 data model drafts:
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: Sat, 03 Nov 2018 15:20:44 -0000

Hi,

Does draft-ietf-i2nsf-nsf-facing-interface-dm describe how extensions or additions should be made? In the first case, separate documents could make sense. If not, I’d prefer to see the whole model specified in a single document.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com<mailto:diego.r.lopez@telefonica.com>
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------

On 01/11/2018, 10:18, "I2nsf on behalf of Panwei (William)" <i2nsf-bounces@ietf.org<mailto:i2nsf-bounces@ietf.org> on behalf of william.panwei@huawei.com<mailto:william.panwei@huawei.com>> wrote:

Hi Linda,

The draft-ietf-i2nsf-nsf-facing-interface-dm defines a ECA-way I2NSF Policy Rule data model, and its focus is the architecture of the NSF-Facing Interface..
Our drafts focus on some concrete functions and attributes, they are the additional enhancement and supplement to the draft-ietf-i2nsf-nsf-facing-interface-dm. For example, the draft-dong-i2nsf-asf-config is trying to define the configuration data model of some common advance security functions which are just part of the ACTION in draft-ietf-i2nsf-nsf-facing-interface-dm.
In addition, the data model of our drafts can be not only used for NSF, but also can be used as customer-facing interface.

So from our points of view, the focus between our drafts and draft-ietf-i2nsf-nsf-facing-interface-dm is different. And separating them may be the effective way to keep their work without affecting each other. The other enhancement with different focus of the draft can also be separated. Besides, if we merge our drafts into draft-ietf-i2nsf-nsf-facing-interface-dm, the size of the draft may be too large.

Best Regards
Wei Pan

发件人: Linda Dunbar
发送时间: 2018年11月1日 5:47
收件人: Xialiang (Frank, Network Integration Technology Research Dept) <frank.xialiang@huawei.com>; Yoav Nir <ynir.ietf@gmail.com>
抄送: Linqiushi (Jessica, CSPL) <linqiushi@huawei.com>; Panwei (William) <william.panwei@huawei.com>; i2nsf@ietf.org
主题: RE: Hi, I2NSF chairs. Request time slots for 2 data model drafts:

Frank,

Can you please explain why it is necessary to have additional two data model drafts? Instead of merging into draft-ietf-i2nsf-nsf-facing-interface-dm?
When you present to I2NSF WG session, can you please highlight how it is aligned with the draft-ietf-i2nsf-nsf-facing-interface-dm and the reasons for separating them.

Thank you.

Linda Dunbar

From: Xialiang (Frank, Network Integration Technology Research Dept)
Sent: Tuesday, October 23, 2018 9:24 PM
To: Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>>; Yoav Nir <ynir.ietf@gmail.com<mailto:ynir.ietf@gmail..com>>
Cc: Linqiushi (Jessica, CSPL) <linqiushi@huawei.com<mailto:linqiushi@huawei..com>>; Panwei (William) <william.panwei@huawei.com<mailto:william.panwei@huawei.com>>
Subject: Hi, I2NSF chairs. Request time slots for 2 data model drafts:

Hi Linda and Yoav,
We have updated two individual drafts about the data model for I2NSF policy object and application layer security functions, which we’d like to request the time slots for presentation:
                   Draft                                              presenter                            time
draft-xia-i2nsf-sec-object-dm-01              Qiushi Lin                   15 minutes
draft-dong-i2nsf-asf-config-01                   Wei Pan                      15 minutes

Thanks a lot!

B.R.
Frank

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição