Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?

tom petch <ietfc@btconnect.com> Tue, 11 December 2018 11:21 UTC

Return-Path: <ietfc@btconnect.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 2DC90130DDE; Tue, 11 Dec 2018 03:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.738
X-Spam-Level: *
X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RATWARE_OUTLOOK_NONAME=2.95, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 fAJz24YjwQCQ; Tue, 11 Dec 2018 03:21:52 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150133.outbound.protection.outlook.com [40.107.15.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7E3130DD0; Tue, 11 Dec 2018 03:21:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jA9poiVb1mMfbIvG6Txzr1e4IgdA+LzFPXqdA8FZVbk=; b=aGX9hVNixbZOKFZgbNbeB6O23wjx1c5FPpgbCih3+KtcfVqSFCt00BL9e3ztA8ZN5a2Nb8yOZkKTaL1cFycP/5VxJ96B67nLPSCvAY0LkXWvw/nj8eWIwqu2eBiY30Ly74q3+yFr+e5PAjbwAmopfOO27NW2x7d9Hae0PifOGUI=
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com (20.177.54.82) by VI1PR07MB0958.eurprd07.prod.outlook.com (10.161.110.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1425.12; Tue, 11 Dec 2018 11:21:49 +0000
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com ([fe80::1575:d33b:33dd:c7c4]) by VI1PR07MB4717.eurprd07.prod.outlook.com ([fe80::1575:d33b:33dd:c7c4%5]) with mapi id 15.20.1425.016; Tue, 11 Dec 2018 11:21:49 +0000
From: tom petch <ietfc@btconnect.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>
CC: "i2nsf@ietf.org" <i2nsf@ietf.org>
Thread-Topic: [OPSAWG] is there any work in Ops Area for monitoring network functions?
Thread-Index: AQHUkUO1T0Lu/xD+tkuIG3RwDsQz5w==
Date: Tue, 11 Dec 2018 11:21:49 +0000
Message-ID: <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0196.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::16) To VI1PR07MB4717.eurprd07.prod.outlook.com (2603:10a6:803:69::18)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [86.139.215.184]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB0958; 6:7JPxeOcaJAFwMdO9GmkqRs+A2gEJ8Us4Q6lEJFaDeQuzC71PLqGfEzJvQPU6PAln7M0Kb+fscksbayVOwj3PTKAaxyFNyEvsraf+iZvEyB4KVGGPDUi9V9mOAWu0ocglzyYlAxjJvMe+bGDJeggxvYTwBapcDYMll2G+6I93ZEJqvt59XQk9R1aZmo50mmL5C9qxWZRlAwEJXd2eASuwHC31ZrCMVZRkyMQAl+91ECqhyzzaGNrABeCUMlT2ROmAJLtH4EXXWQJYvndAhNDuBOns8t2mmrcqoJ/6i8BPogMCKr6ir93ro7B0ENLPKg4lAi2ahcKoQItM2LhrYqiyq2XMY/xkbuaCA2TUM2p7Oan7goT6znpkYr7Yx5gfiNxmkTqICyqing2ciOMLSm3mPsJO7xlqmJKk9CSo7xqk+fQwyryfpJA6trEoCVJG9If+XLB8TuI88m1alxaSekKEYemHNffsJXYKuLqZXebg1U4=; 5:bS2ry1mL/am+RtdRuTcsy1iro2uifxInkmwd11Hsw/yiA0ixaOgkhr/6k2oM3puHl6vueAy++rmt5Y1WXEFTvOBXwPom895/DVXIDZPYmaLqYuEBM1gdz6+LdgE5GS+3tREHoe4Nl0evCEcgxR6dHOmn61Ada/NgTb/Xttc+tpg=; 7:XDHpmy+XL6hlpFBKupdu33isQ2AgRLsIgGrOXl+i/07NtTDq9w4g8uAU8bonvFdTUz7YnE4nRrV2wsmewAeivcvdY4vu2DtEg8TyKn3yuBpShqBs9QgtWDf06JBiwTRcCbhpsaxlY0Ju9JHEBC/TqQ==
x-ms-office365-filtering-correlation-id: e9114df8-7a1c-4bfc-c00b-08d65f5ad809
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7193020); SRVR:VI1PR07MB0958;
x-ms-traffictypediagnostic: VI1PR07MB0958:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-microsoft-antispam-prvs: <VI1PR07MB0958377504E8912D88148A30A0A60@VI1PR07MB0958.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(3230017)(999002)(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231472)(944501520)(4982022)(52105112)(6055026)(148016)(149066)(150057)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:VI1PR07MB0958; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB0958;
x-forefront-prvs: 08831F51DC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(136003)(376002)(366004)(346002)(396003)(199004)(189003)(13464003)(105586002)(6246003)(325944009)(966005)(478600001)(305945005)(2501003)(1556002)(6306002)(6512007)(9686003)(53936002)(86152003)(14496001)(7736002)(81156014)(81166006)(316002)(14454004)(110136005)(8936002)(106356001)(14444005)(3846002)(15188155005)(186003)(71190400001)(26005)(71200400001)(97736004)(52116002)(6486002)(6116002)(8676002)(84392002)(66066001)(76176011)(44736005)(53546011)(6506007)(25786009)(2906002)(33896004)(386003)(229853002)(16799955002)(446003)(68736007)(99286004)(102836004)(4326008)(6436002)(5660300001)(486006)(476003)(86362001)(256004); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB0958; H:VI1PR07MB4717.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 2gE2+CDRSu9vIM6aHwKjwSe3iiroZpUCVa6WuRrn3uAEWRKYGtT7EqSB3cpdMTlkDk5RvcbKHS+XxUYDaU3/I/YmRiy1mDc5ubE4LkoGlcX7A6SsLWlxBkRnXi75l+Wno1sod5do62ap9y93ldsdj+qCY4mDEh4OLyyE5FtzA5+u2J54OVelKV4GeXq0Oko4P18eRWhlStrgv5sCbKAHvT3j+K6WCuYC+GZArekddl1nVOQ6EOv6rwzJiVHp663aYcL7a+lQGMyCKK03Wp5m2n0rI5W3Uixa0RJp36WrZ/2DebbCgHa4afw0xcNbgN2y
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <8F61734ECFF19E48AF48C2C824558BCD@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e9114df8-7a1c-4bfc-c00b-08d65f5ad809
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Dec 2018 11:21:49.8028 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB0958
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/N98kLFE8zDu9lzpExmi47FbKLAs>
Subject: Re: [I2nsf] [OPSAWG] is there any work in Ops Area for monitoring network functions?
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: Tue, 11 Dec 2018 11:21:55 -0000

Linda

I looked at the draft and think that it needs some work before it is a
YANG module:-)

- NMDA conformance is not mentioned

- the reference to RFC2119 is out of date

- the format for tree diagrams is now specified in RFC8340

- YANG import statements lack 'reference' as in
     import ietf-inet-types {
       prefix "inet";
       reference "RFC 6991 - Common YANG Data Types";

- YANG module has no copyright

- YANG module has (almost) no reference statements to tell the user
(like me)  whereto go to understand it. look, for example, at
draft-ietf-opsawg-nat-yang
for a module that is well supplied with reference statements

- YANG module should reference the RFC from which it comes

- the one and only reference in the YANG module is
      reference
         "draft-zhang-i2nsf-info-model-monitoring-07";
but the I-D is
         draft-hong-i2nsf-nsf-monitoring-data-model-06
I do not understand

- where you reference an I-D, it needs a Note to the RFC Editor e.g.
 reference       "draft-zhang-i2nsf-info-model-monitoring-07";
becomes
 reference RFC YYYY "....."
-- Note to RFC Editor please replace YYYY with the number assigned to
         "draft-zhang-i2nsf-info-model-monitoring"

- IANA Considerations must be present

- Security Considerations must include the YANG template

HTH:-)

I am not on the I2NSF list.

Tom Petch

----- Original Message -----
From: "Linda Dunbar" <linda.dunbar@huawei.com>
To: <opsawg@ietf.org>
Cc: <i2nsf@ietf.org>
Sent: Wednesday, December 05, 2018 5:27 PM

> OpsaWG:
>
> I2NSF WG has a draft on data models (and information model) of
monitoring network security functions:
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-0
6
>
> It includes data models to retrieve System Alarms, System Events,
counters, NSF Events/logs, etc.
>
> Want to see if there are data models already specified by Ops Area for
monitoring network functions which might have some common attributes
that I2NSF can import.
>
> Thanks, Linda Dunbar
>
> From: Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com]
> Sent: Thursday, November 15, 2018 6:35 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: i2nsf@ietf.org<mailto:i2nsf@ietf.org>;
skku_secu-brain_all@googlegroups.com<mailto:skku_secu-brain_all@googlegr
oups.com>; Sangwon Hyun <swhyun77@gmail.com<mailto:swhyun77@gmail.com>>;
Mr. Jaehoon Paul Jeong
<jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>>
> Subject: Request for WG Adoption Call on NSF Monitoring Draft
>
> Hi Linda and Yoav,
> As we discussed the last Bangkok meeting,
> I have merged the two drafts of Information Model and Data Model
> for NSF Monitoring into a new draft called
draft-hong-i2nsf-nsf-monitoring-data-model-06:
>
> - Two Information and Data Model Drafts
>  . draft-zhang-i2nsf-info-model-monitoring-07
>  . draft-hong-i2nsf-nsf-monitoring-data-model-05
>
> - A Merged Data Model Draft
>  . draft-hong-i2nsf-nsf-monitoring-data-model-06
>  .
https://tools.ietf.org/html/draft-hong-i2nsf-nsf-monitoring-data-model-0
6
>
> The NSF monitoring is very important to manage the I2NSF security
service system
> in a reliable and scalable fashion.
>
> Could you start a WG adoption call for this draft?
>
> Thanks.
>
> Best Regards,
> Paul
> --
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Associate Professor
> Department of Software
> Sungkyunkwan University
> Office: +82-31-299-4957
> Email: jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>,
pauljeong@skku.edu<mailto:pauljeong@skku.edu>
> Personal Homepage:
http://iotlab.skku.edu/people-jaehoon-jeong.php<http://cpslab.skku.edu/p
eople-jaehoon-jeong.php>