Re: [OPSAWG] Minutes for 104

tom petch <ietfc@btconnect.com> Fri, 10 May 2019 16:46 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC64C1201EB for <opsawg@ietfa.amsl.com>; Fri, 10 May 2019 09:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, 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 bgP8rKvGkeBg for <opsawg@ietfa.amsl.com>; Fri, 10 May 2019 09:46:23 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70100.outbound.protection.outlook.com [40.107.7.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D215C1200FF for <opsawg@ietf.org>; Fri, 10 May 2019 09:46:22 -0700 (PDT)
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=RscfvneLr2vtwxsSLqlp23cIVZnpSVJrIMRdIdtxppQ=; b=e0ia03JbmqNaaeAlgZfp8j1uSMM5UnU0CmhVLbDp9WJInlPWHhW0S9ZDbhCir3b/XHpFi3pkBimr61kq6N1fSoflMWHuQTgTIqIUU+twdFsrESWUjNB20LScXof8mO4SESye7QgsODKhYFADNnFwR41Mzp69fcWI4qHaIj8GUEU=
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com (10.175.242.156) by VI1PR07MB5038.eurprd07.prod.outlook.com (20.177.203.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.18; Fri, 10 May 2019 16:46:20 +0000
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b]) by VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b%3]) with mapi id 15.20.1900.006; Fri, 10 May 2019 16:46:20 +0000
From: tom petch <ietfc@btconnect.com>
To: Warren Kumari <warren@kumari.net>, "Joe Clarke (jclarke)" <jclarke@cisco.com>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Minutes for 104
Thread-Index: AQHVBYZ+PNi8GRISn0WMBzsAxPcPoQ==
Date: Fri, 10 May 2019 16:46:20 +0000
Message-ID: <011801d5074f$61e66e80$4001a8c0@gateway.2wire.net>
References: <BF8526FE-C5E9-4045-BFC8-20E67F189C70@cisco.com> <05bd01d50585$fda2ecc0$4001a8c0@gateway.2wire.net> <682E7E7C-84D8-4DAF-9F76-CE519682B8CB@cisco.com> <CAHw9_iLVYOhdpxqzFuE6ms7TivJpQsPTE-wRzh+kp_jX6Uv9dg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LNXP265CA0088.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:76::28) To VI1PR07MB3118.eurprd07.prod.outlook.com (2603:10a6:802:20::28)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 705208a4-b88a-4431-20d7-08d6d567071c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB5038;
x-ms-traffictypediagnostic: VI1PR07MB5038:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <VI1PR07MB50383AB20A50A6E6EC87AC3DA00C0@VI1PR07MB5038.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0033AAD26D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(346002)(39860400002)(376002)(13464003)(51914003)(189003)(199004)(446003)(71200400001)(86152003)(62236002)(71190400001)(61296003)(186003)(102836004)(44716002)(476003)(50226002)(14496001)(4720700003)(66066001)(2906002)(84392002)(478600001)(966005)(6116002)(14454004)(66476007)(81156014)(8676002)(81166006)(99286004)(8936002)(66946007)(73956011)(66446008)(64756008)(66556008)(3846002)(305945005)(81686011)(9686003)(4326008)(76176011)(81816011)(6246003)(7736002)(6306002)(1556002)(256004)(68736007)(486006)(6486002)(53936002)(86362001)(229853002)(5660300002)(316002)(110136005)(52116002)(6512007)(26005)(25786009)(53546011)(44736005)(6506007)(386003)(6436002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB5038; H:VI1PR07MB3118.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: kqEwIkZEBX/vD+S3VYcrsZgHrOQ2WvbQZit6OX4zhn0lT7/dxuseUvKBz0cX+K82Q8Ht+Z3Hr1w1M1BZZLlLQJJbtsK5jqQd2rNHaIqN/w3+UqK029ABclwC1Hnzqny+/JIU7FClDYtzd6VzSt1sZxW+4P7pdjt9rVfgq80X28kJAiMA6MZHfsXYdywtWjiMM0F6Z+p9GH7HoMlQt9+Bnjr5b9TczAyg8BzWNxxIY6JymsRGRHQ8lj8JPAuxPzotUP5PS52Db05XH1Xg7RMFnFRmyHqqBBimnVDUGJbnAXwvsoJ3EFTETUvN971OZCpELcYLhNv8UTsZf9L0PIBwGj2rpRvIWdXZJ0okT99bmhEeHZoumCM9ulydOnswKTwQqliuL1jOg/pxu0EpQhlIbrOqkuSgmJ7pC9GLIoMXLik=
Content-Type: text/plain; charset="utf-8"
Content-ID: <76FBBCCC3D222B4D8A781427261693AC@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 705208a4-b88a-4431-20d7-08d6d567071c
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2019 16:46:20.1103 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5038
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/R-uoM7ndMCpHLXG40yaOtTk2DZw>
Subject: Re: [OPSAWG] Minutes for 104
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 16:46:28 -0000

Warren

Thanks for the info.

It seems to me that
draft-turner-ccmib-02
is doing for SMI what a number of I-D are struggling (IMHO) to do for
NETCONF/YANG right now.

Apart from the overall objective e.g.
"it describes managed objects used to
   manage key management implementations including asymmetric keys,
   symmetric keys, trust anchors, and cryptographic-related firmware"
they seem to have little or nothing in common; and I know which approach
seems, to a non-cryptographer like me, to have the right resonance.

It is hard to be specific because
draft-turner-ccmib-02
is disastrously short of descriptive text, not fit to be an RFC IMHO.
It would be a shame if it were to proceed in its present form just as it
would be a shame if the contents were not used to inform those working
on the NETCONF/NETMOD equivalents.

Tom Petch

----- Original Message -----
From: "Warren Kumari" warren@kumari.net
Sent: Wednesday, May 08, 2019 4:37 PM

This was largely a “here is a document which we want to send through the
ISE, does the WG want it instead / anyone have any objections?”

He and I had decided that it was polite to check with the WG, even
though
we were fairly sure the WG would not want it...

W

On Wed, May 8, 2019 at 10:25 AM Joe Clarke (jclarke) <jclarke@cisco.com>
wrote:

>
>
> > On May 8, 2019, at 06:12, tom petch <ietfc@btconnect.com> wrote:
> >
> > Joe
> >
> > I am struck by
> >
> > "CCMIB Sean Turner 5 minutes
> > Sean wants no one to comment and no one commented"
> >
> > which seems consistent; no identifier for the whatever-it-is and so
> > no-one said anything!
>
> I didn’t know how to summarize that any differently.  That’s more or
less
> what he said at the mic.  But his presentation is there for the
details of
> what he wants.
>
> Joe
>
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
> > To: <opsawg@ietf.org>
> > Sent: Saturday, May 04, 2019 10:52 PM
> > Subject: [OPSAWG] Minutes for 104
> >
> >
> >> After a long delay I have posted the draft minutes from the IETF
104
> > opsawg/Ops Area session.  I took these from notes I did in Etherpad
as
> > well as the video recording on YouTube.  I missed one Huawei name at
the
> > mic with the NTF draft, but I think I captured most everything else.
> >>
> >> Please review and Tianran or I know what we need to change.
> >>
> >> Thanks.
> >>
> >>
> >
https://datatracker.ietf.org/meeting/104/materials/minutes-104-opsawg-00
> >>
> >> Joe
> >> _______________________________________________
> >> OPSAWG mailing list
> >> OPSAWG@ietf.org
> >> https://www.ietf.org/mailman/listinfo/opsawg
> >
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>
--
I don't think the execution is relevant when it was obviously a bad idea
in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf