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

tom petch <ietfc@btconnect.com> Wed, 12 December 2018 10:38 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 0FABA130DBE; Wed, 12 Dec 2018 02:38:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.739
X-Spam-Level: *
X-Spam-Status: No, score=1.739 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, URIBL_BLOCKED=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 RbxW7w26zCC5; Wed, 12 Dec 2018 02:38:15 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00103.outbound.protection.outlook.com [40.107.0.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2D7B12F1AC; Wed, 12 Dec 2018 02:38:14 -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=VDLzZf4teGkSypT1eoNxH9OawE+cQZhIHTuaO1bBs4A=; b=Yw6JkyuEBdt7jR6sITtzk4/oScVHFxNZytl9LfNPkAi4H32tQEN68ijEMPR21JxWIsIBJxqINjKoD/9kh/leCdsz18HDtLuMbgRU2GiJpl2lZ9EhUjQnZQuAuZThIWdazEd+peAHwYX0ww3ww9UkttvzfH3q5XUFxRLl5pVNHQA=
Received: from VI1PR07MB4717.eurprd07.prod.outlook.com (20.177.54.82) by VI1PR07MB4878.eurprd07.prod.outlook.com (20.177.200.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1425.9; Wed, 12 Dec 2018 10:38:12 +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; Wed, 12 Dec 2018 10:38:12 +0000
From: tom petch <ietfc@btconnect.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-hong-i2nsf-nsf-monitoring-data-model@ietf.org" <draft-hong-i2nsf-nsf-monitoring-data-model@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: Wed, 12 Dec 2018 10:38:12 +0000
Message-ID: <012001d49206$6ed997c0$4001a8c0@gateway.2wire.net>
References: <4A95BA014132FF49AE685FAB4B9F17F66B1F609F@SJCEML521-MBB.china.huawei.com> <039901d49143$5d6dcba0$4001a8c0@gateway.2wire.net> <4A95BA014132FF49AE685FAB4B9F17F66B20E18F@sjceml521-mbs.china.huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LNXP265CA0003.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5e::15) 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; VI1PR07MB4878; 6:V81iYO4twnf+okKtOTI3Do1Ab+XhAwYENUWVc5G9LHYtpduhvfx7dNBQ7B/5A/mx5SjchDowD7SaLs8+fmcV2QCvVPbBF99oYXpWw4fKa1/0KhE5Jr3N5IOj3YI7cPQuAeo3mBHBy+8YI7bVMH67vFKk273EPVyt+SiBVde3KAXOQtBeeqjA9uJVkD71HqkSJr+FOpe/+YVeT1gbvFqwA6hVNW8yZOqBrmNoYkvW+7oUyTvRI8Nlob6cLVK1je6gESGZMishJaJdvuNj33kg/++ZqrkkN+wLjB0Ku2rZ+vmoo9tlBh2DQLvtO6uESiTA/E5PxvXKTcVL+TYxcmiPPhGScX0lnz27noLksuEZ91uJ3iItH0j2qAb3aY7iYoqeErM0PtTUMq+vZGoy+a0iCzpVsBfZFAsydL5S2PqUf9iwtGVu8aG+wQ+EpYtSyIgXBysE+CT+mc4t1e3aH5l1HQ==; 5:R2EsjC0GtJQlkREbURKXgr5Y7gL8gWa4mwLK0mvONHy2rekERvkBO1a9V3ZTpR1Km+twYs8ydf9drjiOxj5/+8axRH/oT+SlmP3/eXafFpalm820KRjiFEU13prr5MG7N39+t5duK3vkGNw5YW3DaK4OPcM+0BsoW8UUo3hmV8w=; 7:HzPshhC+peVc/hvzivjgmINn908IajoMViI+G4VXQp5+XDR5rNAPus2LtbmEYOkCrmvLdZ9rMvqDqlCB9nwFpVAW9Dx3xwy2ynolEeyHV++5jaqvoqGfTz0db4qLRVKrmICMGDDZW/DeqEqTLBEn6Q==
x-ms-office365-filtering-correlation-id: 0c644ed8-a8aa-4e89-9d1b-08d6601dea2a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:VI1PR07MB4878;
x-ms-traffictypediagnostic: VI1PR07MB4878:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-microsoft-antispam-prvs: <VI1PR07MB4878B326343F44F21A1DAAA4A0A70@VI1PR07MB4878.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(3230017)(999002)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231472)(944501520)(4982022)(52105112)(6055026)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699051)(76991095); SRVR:VI1PR07MB4878; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB4878;
x-forefront-prvs: 0884AAA693
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(136003)(396003)(366004)(376002)(199004)(189003)(13464003)(51444003)(14444005)(14496001)(26005)(102836004)(105586002)(5660300001)(2501003)(229853002)(6486002)(44736005)(186003)(6306002)(86152003)(6512007)(305945005)(97736004)(15188155005)(1556002)(9686003)(106356001)(53936002)(256004)(110136005)(71190400001)(71200400001)(6436002)(2201001)(7736002)(316002)(86362001)(325944009)(8936002)(6116002)(84392002)(14454004)(3846002)(16799955002)(8676002)(81166006)(81156014)(478600001)(2906002)(66066001)(33896004)(76176011)(486006)(6506007)(386003)(53546011)(6246003)(4326008)(25786009)(99286004)(52116002)(966005)(68736007)(476003)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4878; 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: MYeeE+ySB7FgwSAXhOe1wrPYg2ZuS9cVBAd6PQNGEwq7zFvbtnA3wnufd/yaYkMIapo4xrMWDx8XjvGowMHIuqb8Yz8qlfcAOPyss2bo37EIHbUkkxigAKhPeQFT77kWLm1UlYtf3574sv2LriI6oSfrxvUth5HrtJKXwmRIh/ctMJ187ZsO5aIayl4prkQWSp7CrOSjY1o7cBUsAUrI+THPRf2bAMK+r3jZGV6VsjiRvrIUzyd1ZANSCijWlzjIt0LcFaX4XfsRKlK0jUpjc2pS7hsapOCv2PGfKSJQfMXvFDiEnT1P3ccJrzMzxwTW
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <5DEADF58C3543D4982466687232CB214@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0c644ed8-a8aa-4e89-9d1b-08d6601dea2a
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Dec 2018 10:38:12.2135 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4878
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2nsf/caa4xQwKDPLLLMNbHfhOn8WPEo0>
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: Wed, 12 Dec 2018 10:38:18 -0000

----- Original Message -----
From: "Linda Dunbar" <linda.dunbar@huawei.com>
Sent: Tuesday, December 11, 2018 4:12 PM

> Tom,
>
> Thank you very much for the review and comments. So there is no
duplicated work in OpsArea?

Linda

I suspect that there is duplicated work but the absence of YANG
'reference' statements in the module make that harder to assess.  If two
YANG modules reference the same section of the same document, then they
are likely modelling the same object!  Even if the reference is only to
the document, it does make comparison easier.  Here, there are zero
references.

There is certainly overlap with work in NETCONF where pull-push, pub-sub
and the like have been much debated, often in a seemingly circular
manner, with I-Ds such as
draft-ietf-netconf-subscribed-notifications
draft-ietf-netconf-udp-pub-channel-03
draft-ietf-netconf-yang-push
draft-ietf-netconf-netconf-event-notifications
draft-ietf-netconf-restconf-notif
but that WG is also wrestling with seven client-server drafts which
interact with them so I find it hard to keep track of this work.

On the approach to event/alarm/notification, there is overlap with
draft-ietf-ccamp-alarm-module
which is all about alarms and not much to do with ccamp IMHO. This work
is an evolution of RFC3877 so is probably the one that you should be
familiar with.  I think that if this I-D looks different to RFC3877, it
is because ITU-T have moved on and we have followed.

On the identities, ip, ipv4, ftp etc there is overlap everywhere.

Not sure that that helps but that is the IETF.

Tom Petch

> Authors of the draft-hong-i2nsf-nsf-monitoring-data-model: Can you
please update the draft per Tom's comments.
>
> Linda.
>
> -----Original Message-----
> From: tom petch [mailto:ietfc@btconnect.com]
> Sent: Tuesday, December 11, 2018 5:22 AM
> To: Linda Dunbar <linda.dunbar@huawei.com>; opsawg@ietf.org
> Cc: i2nsf@ietf.org
> Subject: Re: [OPSAWG] is there any work in Ops Area for monitoring
network functions?
>
> 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>
>
>