IETF Logo Mail Archive

[mile] ROLIE Data Model Enumeration

"Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov> Mon, 12 December 2016 16:02 UTC

Return-Path: <stephen.banghart@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C45F7129D17 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2016 08:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.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 2zd9kD529ZNZ for <mile@ietfa.amsl.com>; Mon, 12 Dec 2016 08:02:37 -0800 (PST)
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0121.outbound.protection.outlook.com [23.103.200.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60D8B129CEC for <mile@ietf.org>; Mon, 12 Dec 2016 08:00:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nsh+GAImjkdWDx4xxM+2uk98RzLoRyomxGJ0F4m+UrE=; b=qh5P59aXY/haLXw6F/X1pvbcV5tc6LRYQyHG6Gm2548x8yiZtuIV00w/MhWNXJSsQMCXOWIzwR4a/Nzkm6wnHBMpFuPkVfzFeY+rDsKFTAKmqXZakkZJ9WtzbxhMdSEGOXiPH5eX2YhoZNPDrZ5cmez/szEWSo5taa2aK32YmKU=
Received: from SN1PR09MB0960.namprd09.prod.outlook.com (10.162.102.148) by SN1PR09MB0957.namprd09.prod.outlook.com (10.162.102.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.761.9; Mon, 12 Dec 2016 16:00:48 +0000
Received: from SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) by SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) with mapi id 15.01.0761.022; Mon, 12 Dec 2016 16:00:49 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: ROLIE Data Model Enumeration
Thread-Index: AdJUkLkVdwqU2UKsSJC6MkKU9WhzPg==
Date: Mon, 12 Dec 2016 16:00:48 +0000
Message-ID: <SN1PR09MB09602C26522BDBDEFD9C9235F0980@SN1PR09MB0960.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov;
x-originating-ip: [129.6.227.79]
x-ms-office365-filtering-correlation-id: 2dc3ca0c-bd80-4ae2-dadd-08d422a80a61
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:SN1PR09MB0957;
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0957; 7:JUtgLyXsQrTEihYd1jdqEaJlxPicxspwVkFyATApAMulLSp7HOKTPf2VdY+B0VhBmJ7u4XLcJlBS6LDwUSM+4jmHtX4UcFkl/0KVWkLt5sjarNK2gg5SBgcFdhlTGI4boO+NUJeGWC/VOTNF/rPAqqGbFxGUoSfxLcLF+Zvyn7PwQrpD1jqDiEIDpPO100ytp9ub+Dd+6+N7yLDt8oXhEUXPwCY6z/q6T71CQTjjWjEMe6WvRoBVxTWzpuZ08EonRXaky8Y6JPRoqNDF3f6uOQo88BpFJbiZM3MuBZZHQ2skMu3761txpE92c8aTBnhnWPByJl9zX7HXWL2G0HM82Bu27EzJ0FKjb3G/4XLlB3e5GgQrv0IZmkvEe5B5OF9xyAJb7MAhoLy2w33pXwPEqTILG9rkpcr7jsOnfOkjGKQPEIT/SyoEk/p2qI+cBySb++oVT5me1pDZ0tAr6sg9Xg==
x-microsoft-antispam-prvs: <SN1PR09MB0957380BFB437D010A02DECAF0980@SN1PR09MB0957.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(6072148); SRVR:SN1PR09MB0957; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0957;
x-forefront-prvs: 0154C61618
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39450400003)(39850400002)(39410400002)(39840400002)(189002)(199003)(189998001)(3280700002)(7696004)(2906002)(33656002)(7736002)(450100001)(561944003)(3660700001)(5660300001)(68736007)(5630700001)(77096006)(8936002)(107886002)(3480700004)(6916009)(2501003)(97736004)(110136003)(101416001)(38730400001)(54356999)(50986999)(99286002)(86362001)(2900100001)(106356001)(105586002)(92566002)(122556002)(6506006)(2351001)(66066001)(9686002)(6436002)(3846002)(790700001)(6116002)(102836003)(8676002)(76576001)(81166006)(1730700003)(5640700002)(81156014)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR09MB0957; H:SN1PR09MB0960.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR09MB09602C26522BDBDEFD9C9235F0980SN1PR09MB0960namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Dec 2016 16:00:48.7905 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0957
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/olu75mfr2uZqU3AgFb91Lm-sogE>
Subject: [mile] ROLIE Data Model Enumeration
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2016 16:02:40 -0000

All,

The other issue discussed at the IETF 97 MILE meeting was the Enumeration and Registration of Data Models.

Data model enumeration/registration would involve requiring extension documents to register their supported data models for a given information type with IANA.

Pros:
■        Provides one location that lists all officially registered data formats.
Cons:
■        Requires document authors to choose (often arbitrarily!) and register data format namespaces
■        Registered identifiers don't help implementations understand data formats, and if chosen arbitrarily may not even help identify the format in a way that is meaningful to clients.
■        Provides no additional automation support.
■        Increases work load on extension authors
■        Extensions must provide IANA considerations section that specifies data model registration and perhaps an additional table for the data models.
■        Extensions must have a separate section describing the data model in addition to the IANA consideration

Proposal:
                Do not require data format registration in extension drafts. This does not preclude an extension from establishing a registry for supported data models if needed. Extension specifications may additionally discuss the data models intended to be used for a given information type. We believe this provides for adequate coverage of the model namespaces to be used in the extension specification, without requiring the extra burden of dealing with IANA considerations for models.

Any feedback on this proposal? I personally feel like requiring registration is not worth the price.

Thanks,
Stephen Banghart

v2.23.0 | Report a Bug | By Email