
From nobody Sun Feb  1 01:48:53 2015
Return-Path: <athiasjerome@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 438771A879B for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 01:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 pCf2N03csnFa for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 01:48:51 -0800 (PST)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4D361A8799 for <sacm@ietf.org>; Sun,  1 Feb 2015 01:48:50 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id hv19so32607526lab.13 for <sacm@ietf.org>; Sun, 01 Feb 2015 01:48:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=LQ6vOlzZ2kJcFUBb7OK1+jBRh79m4RWQ7IItzKDREzo=; b=QA4CYQRhiRLx2/HobjayWuLPsI0YmhMMSHzKp8REx/ztCT7HVJvG8X274uW/jHiVeK Y5Xpdc05NzD3cTMGb0h2vRWNGbAlAtDtpLidL9LT8PLAWC2w3t4HG1v6or2rwBM19mhc zA3qiZ5W/HncasMLMfqzjJRCbHcYPUulpIfkO/l58XmeU8SztNI5qTOfeVmCbl9UkL2O 9A0bk8ptu0Q/TIe2aNyWoj1el5eol13cZ1SVSlcFZ0nvT3CkMrEdoAaMOAMQ2PEEpaHj ZJWOaI1gbrWIhADIFFZ8fsU0X6iqt0M6a5ZDhm7DG/Z0SorN0z44b0rKbB4xEhufwwiS s4Bw==
MIME-Version: 1.0
X-Received: by 10.112.35.165 with SMTP id i5mr13946150lbj.49.1422784129187; Sun, 01 Feb 2015 01:48:49 -0800 (PST)
Received: by 10.25.209.5 with HTTP; Sun, 1 Feb 2015 01:48:49 -0800 (PST)
Date: Sun, 1 Feb 2015 10:48:49 +0100
Message-ID: <CAA=AuEeUOkBQOMZPoxdQ3NuEr_Qe8GsGxe38uUQ7ajjrg8xaRw@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/WWdXnNPw6-m516Z_gz951vQUtYE>
Subject: [sacm] ETSI Machine-to-Machine communications (M2M)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 09:48:52 -0000

Hi,

for information, ETSI (European Telecommunications Standards
Institute) released a Technical Specification for Machine-to-Machine
communications (M2M); Interoperability Test Specification

Ref: ETSI TS 103 315 V1.1.1 (2015-01)
http://www.etsi.org/deliver/etsi_ts/103300_103399/103315/01.01.01_60/ts_103315v010101p.pdf

Best regards


From nobody Sun Feb  1 06:39:18 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F8A1A88CF for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 06:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 P4_e7Lxpcze4 for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 06:39:14 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0089.outbound.protection.outlook.com [65.55.169.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C1B41A88CB for <sacm@ietf.org>; Sun,  1 Feb 2015 06:39:14 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sun, 1 Feb 2015 14:39:11 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Sun, 1 Feb 2015 14:39:11 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Comments on Network Interface
Thread-Index: AQHP+GodCKGp54AXtUubmJnUXWgtPpzcZT1Q
Date: Sun, 1 Feb 2015 14:39:10 +0000
Message-ID: <CY1PR0601MB13558C1FC7233F20FA1F61D9B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <54590118.9050702@sit.fraunhofer.de>
In-Reply-To: <54590118.9050702@sit.fraunhofer.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: sit.fraunhofer.de; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1355;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1355; 
x-forefront-prvs: 04740D25F1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(13464003)(52314003)(377454003)(53754006)(2656002)(54606007)(87936001)(86362001)(46102003)(66066001)(76576001)(62966003)(102836002)(77156002)(50986999)(54356999)(33656002)(76176999)(561944003)(54206007)(2950100001)(99286002)(2501002)(106116001)(40100003)(122556002)(19580395003)(19580405001)(92566002)(74316001)(107886001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1355; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2015 14:39:10.9499 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1355
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/DUU9d7hs-JikMRgOrlQZa06Sxd4>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 14:39:16 -0000

SGVuaywNCkJlbGF0ZWQgcmVzcG9uc2UgaGVyZS4NCg0KQXMgSSB1bmRlcnN0YW5kIHlvdSwgeW91
IHdvdWxkIHJlbW92ZSB0aGUgY2xhc3MgInNlc3Npb24iLCBtZW50aW9uZWQgaW4gdGhlIGRpYWdy
YW0gYW5kIGluIHNlY3Rpb24gNC4xMCBvZiBkcmFmdC1pZXRmLXNhY20taW5mb3JtYXRpb24tbW9k
ZWwuIElzIHRoYXQgdHJ1ZT8gDQoNCkkgcmVhbGl6ZSB0aGVyZSBpcyBtb3JlIHRvIHlvdXIgcHJv
cG9zYWwuIEJ1dCBJIHdhbnQgdG8gcmVzcG9uZCB0byByZW1vdmluZyAic2Vzc2lvbiIuIExldCdz
IGNvbnNpZGVyIHdoeSBzZXNzaW9ucyB3ZXJlIHRoZXJlLiANCg0KU3VwcG9zZSBhbiBlbmRwb2lu
dCdzIGxheWVyIDIgaW50ZXJmYWNlIGNvbWVzIG9ubGluZSBhZnRlciBhIFJBRElVUyBleGNoYW5n
ZS4gU29tZSBvZiB1cyB3b3VsZCBzYXkgYSBsYXllciAyIHNlc3Npb24gaGFzIGJlZ3VuOyB0aGF0
IG1heSBiZSBtaXN1c2Ugb2YgdGhlIHdvcmQgInNlc3Npb24iLiBBbnl3YXksIHRoZSBSQURJVVMg
c2VydmVyIGtub3dzOg0KLSB0aGUgZW5kcG9pbnQncyBNQUMgYWRkcmVzcw0KLSB0aGUgY3JlZGVu
dGlhbHMgdXNlZCBpbiB0aGUgUkFESVVTIGF1dGhlbnRpY2F0aW9uIA0KLSB0aGUgYXV0aG9yaXph
dGlvbiB0aGF0IGl0IGdyYW50ZWQgKFZMQU4sIGEgZmlsdGVyLWlkIGRlbm90aW5nIGZpcmV3YWxs
IHJ1bGVzKQ0KLSB0aGUgZW5kcG9pbnQncyBjb21wbGlhbmNlLCBpZiBORUEgY2hlY2tpbmcgd2Fz
IGRvbmUgZHVyaW5nIHRoZSBSQURJVVMgZXhjaGFuZ2UNCi0gc29tZXRpbWVzLCBhbiBJUCBhZGRy
ZXNzIChpZiB0aGUgc3dpdGNoIGRvZXMgREhDUCBzbm9vcGluZyBhbmQgcmVwb3J0cyBpdHMgZmlu
ZGluZ3MgaW4gUkFESVVTIEFjY291bnRpbmcgbWVzc2FnZXMpDQoNClRoYXQgaW5mb3JtYXRpb24g
aXMgcmVsZXZhbnQgZm9yIFNBQ00uIEF1dGhvcml6YXRpb24gaXMgcmVsZXZhbnQgYmVjYXVzZSBl
bmRwb2ludHMgdGhhdCBoYXZlIGFjY2VzcyB0byBzZW5zaXRpdmUgcmVzb3VyY2VzIG1heSBiZSBz
dWJqZWN0IHRvIG1vcmUgc3RyaW5nZW50IGNvbXBsaWFuY2UgcG9saWNpZXMuIChIbS4gRG8gd2Ug
aGF2ZSB0aGF0IGluIG91ciB1c2UgY2FzZXM/IFNob3VsZCB3ZT8pIA0KDQpQZXJoYXBzIHdlIGRv
bid0IG5lZWQgYSBzZXNzaW9uIGluIHRoZSBtb2RlbC4gUGVyaGFwcyB0aGUgUkFESVVTIHNlcnZl
ciBjYW4ganVzdCBtYWtlIGFuIGVuZHBvaW50IGF0dHJpYnV0ZSBhc3NlcnRpb24gc3RhdGluZyB0
aGUgYWJvdmUgYXR0cmlidXRlcy4gSSBsaWtlIHRoZSBzaW1wbGlmaWNhdGlvbi4gDQoNCk90aGVy
IGtpbmRzIG9mIG5ldHdvcmsgc2Vzc2lvbnMgKFRDUCBjb25uZWN0aW9ucywgZXRjLikgYXJlIGNl
cnRhaW5seSByZWxldmFudCBmb3Igc2VjdXJpdHkuIEJ1dCB0aGV5IHNlZW0gdG8gYmUgb3V0c2lk
ZSBvZiB0aGUgU0FDTSBXRydzIGNoYXJ0ZXIuIA0KDQpJbiBzdW0sIEkgY2Fubm90IHNlZSBhIHJl
YXNvbiB0byBrZWVwICJzZXNzaW9uIiBpbiB0aGUgaW5mb3JtYXRpb24gbW9kZWwuICANCg0KV2hh
dCBkbyBvdGhlcnMgdGhpbms/DQoNCkJlc3QsDQoJCQlDbGlmZg0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogSGVuayBCaXJraG9seiBbbWFpbHRvOmhlbmsuYmlya2hvbHpAc2l0
LmZyYXVuaG9mZXIuZGVdIA0KU2VudDogVHVlc2RheSwgTm92ZW1iZXIgMDQsIDIwMTQgMTE6Mzkg
QU0NClRvOiBzYWNtQGlldGYub3JnDQpTdWJqZWN0OiBbc2FjbV0gQ29tbWVudHMgb24gTmV0d29y
ayBJbnRlcmZhY2UNCg0KSGkgYWxsLA0KDQp0aGUgbmV3IGRyYWZ0IChkcmFmdC1pZXRmLXNhY20t
aW5mb3JtYXRpb24tbW9kZWwtMDApIG5vdyBpbmNsdWRlcyBhIA0KY29tYmluZWQgc2VjdGlvbiBm
b3IgIk5ldHdvcmsgU2Vzc2lvbiIgYW5kICJOZXR3b3JrIEludGVyZmFjZSIgKDQuMTAuKS4NCg0K
TXkgcmVjb21tZW5kYXRpb24gaXMgdG8gZGl2aWRlIHRoZSBlbGVtZW50cyBOZXR3b3JrIFNlc3Np
b24sIE5ldHdvcmsgDQpJbnRlcmZhY2UgYW5kIHBvdGVudGlhbGx5IChOZXR3b3JrKSBBZGRyZXNz
IGludG8gc2VwYXJhdGUgc2VjdGlvbnMgb2YgDQp0aGUgc2FtZSBsZXZlbCAoNC54KS4NCg0KV2hp
bGUgYm90aCB0ZXJtcyBhcmUgcmVsYXRlZCwgb2YgY291cnNlLCB0aGVyZSBhcmUgc2V2ZXJhbCAo
bW9yZSBvciBsZXNzIA0KaW1wb3J0YW50KSByZWFzb25zIGZvciB0aGlzOg0KQSBzZXNzaW9uIHR5
cGljYWxseSBpbnZvbHZlcyBtdWx0aXBsZSBwYXJ0aWNpcGFudHMgKGUuZy4gZW5kcG9pbnRzLCBv
ciAtIA0KYnJva2VuIGRvd24gLSBldmVudHVhbGx5IGFkZHJlc3NlcyBvciBpbnRlcmZhY2VzKSBh
bmQgdHlwaWNhbGx5IGhhcyBhIA0KbGltaXRlZCBsaWZlLXRpbWUuIEFuIGludGVyZmFjZSwgaW4g
Y29udHJhc3QsIGlzIGEgc2luZ3VsYXIgZW50aXR5IHRoYXQgDQpjYW4gZXhpc3Qgb3ZlciB0aGUg
Y29tcGxldGUgbGlmZS1jeWNsZSBvZiBhbiBlbmRwb2ludCAodmlydHVhbCANCmludGVyZmFjZXMg
Y2FuIGhhdmUgYSBmb3Jlc2VlYWJsZSBsaW1pdGVkIGxpZmUtdGltZSkuIEFzIElyYSBwb2ludGVk
IA0Kb3V0LCBhbiBpbnRlcmZhY2UgdHlwaWNhbGx5IHByb3ZpZGVzIGNvbm5lY3Rpdml0eSB0byBh
IG5ldHdvcmsgb24gbGF5ZXIgDQp0d28gdG8gdGhyZWUsIHdoaWxlIGEgbmV0d29yayBzZXNzaW9u
IGlzIHR5cGljYWxseSBhc3NvY2lhdGVkIHdpdGggDQpsYXllcnMgYWJvdmUgdGhvc2UuDQoNCkFs
dGhvdWdoIGNsb3NlbHkgcmVsYXRlZCwgdGhleSBhcmUgcXVpdGUgZGlmZmVyZW50LCBzZW1hbnRp
Y2FsbHksIGFuZCANCm1heSBldmVuIG5lZWQgc2VwYXJhdGUgcmVwcmVzZW50YXRpb25zIGluIHRo
ZSBTQUNNIElNLg0KDQpNeSBwcm9wb3NhbCBmb3IgYSBzZXBhcmF0ZSAiTmV0d29yayBJbnRlcmZh
Y2UiIHNlY3Rpb246DQoNCi0tLXNuaXAtLS0NCk5ldHdvcmsgSW50ZXJmYWNlDQoNCkFuIGVuZHBv
aW50IGlzIGNvbm5lY3RlZCB0byBhIG5ldHdvcmsgdmlhIG9uZSBvciBtb3JlIGludGVyZmFjZXMu
IA0KSW50ZXJmYWNlcyBjYW4gYmUgcGh5c2ljYWwgb3IgdmlydHVhbC4gSW50ZXJmYWNlcyBvZiBh
biBlbmRwb2ludCBjYW4gDQpvcGVyYXRlIG9uIGRpZmZlcmVudCBsYXllcnMsIG1vc3QgcHJvbWlu
ZW50bHkgd2hhdCBpcyBub3cgY29tbW9ubHkgDQpjYWxsZWQgbGF5ZXIgMiBhbmQgMy4gV2l0aGlu
IGEgbGF5ZXIsIGludGVyZmFjZXMgY2FuIGJlIG5lc3RlZC4NCk9uIGxheWVyIDIsIGEgcm9vdCBp
bnRlcmZhY2UgaXMgdHlwaWNhbGx5IGFzc29jaWF0ZWQgd2l0aCBhIHBoeXNpY2FsIA0KaW50ZXJm
YWNlIHBvcnQgYW5kIG5lc3RlZCBpbnRlcmZhY2VzIGFyZSB2aXJ0dWFsIGludGVyZmFjZXMuIElu
IHRoZSBjYXNlIA0Kb2YgYSB2aXJ0dWFsIGVuZHBvaW50LCBhIHJvb3QgaW50ZXJmYWNlIGNhbiBi
ZSBhIHZpcnR1YWwgaW50ZXJmYWNlLiANClZpcnR1YWwgbGF5ZXIgMiBpbnRlcmZhY2VzIG9mIG9u
ZSBvciBtb3JlIGVuZHBvaW50cyBjYW4gYWxzbw0KY29uc3RpdHV0ZSBhbiBhZ2dyZWdhdGVkIGdy
b3VwIG9mIGxpbmtzIHRoYXQgYWN0IGFzIG9uZS4NCk9uIGxheWVyIDMsIG5lc3RlZCBpbnRlcmZh
Y2VzIHR5cGljYWxseSBjb25zdGl0dXRlIHZpcnR1YWwgdHVubmVscyBvciANCm5ldHdvcmtzLg0K
RXhhbXBsZXMgaW5jbHVkZTogcGh5c2ljYWwgRXRoZXJuZXQgcG9ydCwgbGF5ZXIgMiBWTEFOIGlu
dGVyZmFjZSwgYSANCk1DLUxBRyBzZXR1cCwgbGF5ZXIgMyBQb2ludC10by1Qb2ludCB0dW5uZWwg
aW5ncmVzcyBvciBlZ3Jlc3MuDQotLS1zbmFwLS0tDQoNCkEgc21hbGwgYWRkaXRpb24gdG8gdGhl
ICJBZGRyZXNzIiBzZWN0aW9uLCBhbmFsb2dvdXNseToNCg0KLS0tc25pcC0tLQ0KTmV0d29yayBB
ZGRyZXNzDQoNCk5ldHdvcmsgYWRkcmVzc2VzIGFyZSBsYXllciBzcGVjaWZpYyBhbmQgZm9sbG93
IGxheWVyIHNwZWNpZmljIGFkZHJlc3MgDQpzY2hlbWVzLiBFYWNoIGludGVyZmFjZSBvZiBhIHNw
ZWNpZmljIGxheWVyIGNhbiBiZSBhc3NvY2lhdGVkIHdpdGggb25lIA0Kb3IgbW9yZSBhZGRyZXNz
ZXMgYXBwcm9wcmlhdGUgZm9yIHRoYXQgbGF5ZXIuDQpUaGVyZSBpcyBubyBndWFyYW50ZWUgdGhh
dCBhbiBhZGRyZXNzIGlzIGdsb2JhbGx5IHVuaXF1ZS4gSW4gZ2VuZXJhbCwgDQp0aGVyZSBpcyBh
IHNjb3BlIHRvIGFuIGFkZHJlc3MgaW4gd2hpY2ggaXQgaXMgaW50ZW5kZWQgdG8gYmUgdW5pcXVl
Lg0KRXhhbXBsZXMgaW5jbHVkZTogcGh5c2ljYWwgRXRoZXJuZXQgcG9ydCB3aXRoIGEgTUFDIGFk
ZHJlc3MsIGxheWVyIDIgDQpWTEFOIGludGVyZmFjZSB3aXRoIGEgTUFDIGFkZHJlc3MsIGxheWVy
IDMgaW50ZXJmYWNlIHdpdGggbXVsdGlwbGUgSVB2NiANCmFkZHJlc3NlcywgbGF5ZXIgMyB0dW5u
ZWwgaW5ncmVzcyBvciBlZ3Jlc3Mgd2l0aCBhbiBJUHY0IGFkZHJlc3MuDQotLS1zbmFwLS0tDQoN
ClNvbWV0aW1lcywgdGhlIGNvbXBsZXhpdHkgYSBzZXR1cCBvZiBpbnRlcmZhY2VzIGNhbiBpbmNv
cnBvcmF0ZSBpcyBhIA0KbGl0dGxlIGJpdCB1bmRlcmVzdGltYXRlZCwgSU1ITy4gVGhlIHByb3Bv
c2VkIHRleHQgYWJvdmUgb25seSBpbmNsdWRlcyANCnRoZSBtb3N0IGNvbW1vbiBjYXNlcyBhbmQg
ZG9lcyBub3QgdG91Y2ggZW1lcmdpbmcgcHJhY3RpY2VzLCBzdWNoIGFzIA0KcGh5c2ljYWwgaW50
ZXJmYWNlIG1vZHVsZXMgdGhhdCBwcm92aWRlIGEgc2V0IG9mIHNpbmdsZSBwaHlzaWNhbCANCmlu
dGVyZmFjZXMsIHdoaWNoIGFyZSBhc3NvY2lhdGVkIHdpdGggbXVsdGlwbGUgZGlzdGluZ3Vpc2hh
YmxlIGVuZHBvaW50cyANCmF0IHRoZSBzYW1lIHRpbWUuDQoNCkluIG9yZGVyIHRvIGFkZHJlc3Mg
bmV0d29yayBjZW50cmljIHNlY3VyaXR5L21vbml0b3JpbmcgcHJvY2Vzc2VzLCANCmVmZmVjdGl2
ZWx5LCB0aGUgU0FDTSBJTSBzaG91bGQgYmUgYWJsZSB0byBoYW5kbGUgdGhlIGNvbXBsZXhpdHkg
b2YgDQphcHBsaWVkIGNvbW1vbiBwcmFjdGljZSBpbiBpdHMgZGVmaW5pdGlvbiBvZiAiTmV0d29y
ayBJbnRlcmZhY2UiLCBJIHRoaW5rLg0KDQpCZXN0LA0KDQpIZW5rDQoNCg==


From nobody Sun Feb  1 07:38:49 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E287B1A037B for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 07:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 fncEtcseQPIT for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 07:38:44 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0645.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:645]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFA861A8A8D for <sacm@ietf.org>; Sun,  1 Feb 2015 07:38:43 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1353.namprd06.prod.outlook.com (25.161.212.11) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sun, 1 Feb 2015 15:38:20 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Sun, 1 Feb 2015 15:38:20 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Comments on Network Interface
Thread-Index: AQHP+GodCKGp54AXtUubmJnUXWgtPpzcZT1QgAAFQFA=
Date: Sun, 1 Feb 2015 15:38:20 +0000
Message-ID: <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <54590118.9050702@sit.fraunhofer.de> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: sit.fraunhofer.de; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1353;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1353; 
x-forefront-prvs: 04740D25F1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(52314003)(377454003)(13464003)(53754006)(87936001)(2656002)(76576001)(62966003)(19580395003)(19580405001)(2501002)(46102003)(106116001)(107886001)(99286002)(54206007)(86362001)(66066001)(54356999)(50986999)(76176999)(54606007)(92566002)(102836002)(2900100001)(74316001)(77156002)(40100003)(33656002)(122556002)(561944003); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1353; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2015 15:38:20.1158 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1353
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/kQbhyfx7WSN4CYyIi7uTVFwb4XU>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 15:38:47 -0000

SGVuaywNCkZpcnN0LCBhIGNvcnJlY3Rpb24uIEkgc2FpZCwgaW5jb3JyZWN0bHksIHRoYXQgeW91
IGhhZCBwcm9wb3NlZCByZW1vdmluZyB0aGUgaWRlYSBvZiAic2Vzc2lvbiIuIFlvdSBhY3R1YWxs
eSBwcm9wb3NlZCBzZXBhcmF0aW5nIGl0IGZyb20gImludGVyZmFjZSIuIChJIGRvIHN1Z2dlc3Qg
d2UgcmVtb3ZlICJzZXNzaW9uIiBhbHRvZ2V0aGVyLikgDQoNClNlY29uZCwgSSBsaWtlIHlvdXIg
c3VnZ2VzdGlvbiBvZiBwcm9tb3Rpbmcgc2VjdGlvbiA0LjEwLjEsICJBZGRyZXNzIiwgdG8gYSA0
Lnggc2VjdGlvbi4gDQoNClRoaXJkLCBJIGxpa2UgeW91ciBhZGRpdGlvbiB0byB0aGUgIkFkZHJl
c3MiIHNlY3Rpb24uIA0KDQpGb3VydGgsIGxldCdzIGNvbnNpZGVyIHRha2luZyBpdCBmdXJ0aGVy
LiBJbiBhIHNpZGUgY29udmVyc2F0aW9uIHlvdSBwb2ludGVkIG91dCB0aGF0IGEgcG9ydCBudW1i
ZXIgaXMgcmVhbGx5IHBhcnQgb2YgYW4gYWRkcmVzcy4gVGhlIHBvcnQgbnVtYmVyIG1hdHRlcnMg
Zm9yIHNvbWUgcHVycG9zZXMsIGJ1dCBub3QgZm9yIG90aGVycy4gT25lIHBsYWNlIHdoZXJlIGl0
IG1hdHRlcnM6IHlvdSBwb2ludGVkIG91dCB0aGF0IGNvbXBsaWFuY2UgcG9saWNpZXMgYWJvdXQg
bmV0d29yayBpbmdyZXNzIG1ha2UgYSBsb3Qgb2Ygc2Vuc2UuIEZvciBleGFtcGxlLCBhIHBvbGlj
eSBjb3VsZCBkaXNhcHByb3ZlIG9mIGFuIGVuZHBvaW50IGxpc3RlbmluZyBvbiB0aGUgTVNTUUwg
cG9ydCAoMTQzMykuIE1hbnkgc3VjY2Vzc2Z1bCBhdHRhY2tzIGhhdmUgYmVlbiBtYWRlIG9uIHBv
cnRzIHVuaW50ZW50aW9uYWxseSBsZWZ0IG9wZW4sIHNvIHRoaXMgaXMgd2VsbCBtb3RpdmF0ZWQu
IA0KDQpIb3cgd291bGQgd2UgbW9kZWwgdGhpcz8gSXMgMS4xLjEuMToxNDMzIGEgc3ViLWFkZHJl
c3Mgb2YgMS4xLjEuMT8gDQoNCkZpZnRoLCBhbmQgbW9zdCBjZW50cmFsOiB5b3Ugd3JpdGUgdGhh
dCB3ZSBzaG91bGQgY2FwdHVyZSB0aGUgbmVzdGVkIGFuZCBsYXllcmVkIHN0cnVjdHVyZSBvZiBp
bnRlcmZhY2VzIHRvICJhZGRyZXNzIG5ldHdvcmsgY2VudHJpYyBzZWN1cml0eS9tb25pdG9yaW5n
IHByb2Nlc3NlcywgZWZmZWN0aXZlbHkiLiBJIGRvbid0IHVuZGVyc3RhbmQgeWV0IGhvdyBhIG5l
dHdvcmsgYmFzZWQgYXR0cmlidXRlIGNvbGxlY3RvciAoYSAic2Vuc29yIikgd291bGQga25vdyBv
ciBjYXJlLiAgQSBzZW5zb3Igb2JzZXJ2ZXMgb3IgaW5qZWN0cyBuZXR3b3JrIHRyYWZmaWMuIEl0
IGtub3dzIGFkZHJlc3Nlcy4gSG93IGNhbiBpdCBiZSBhd2FyZSBvZiBuZXR3b3JrIGludGVyZmFj
ZXM/IEhvdyBjYW4gaXQgZGlzY2VybiB3aGV0aGVyIG9uZSBpbnRlcmZhY2UgbmVzdHMgaW4gYW5v
dGhlcj8gDQoNCkFuIGF0dHJpYnV0ZSBjb2xsZWN0b3IgdGhhdCBydW5zIG9uIHRoZSBlbmRwb2lu
dCwgb3IgdGhhdCBxdWVyaWVzIHRoZSBlbmRwb2ludCB1c2luZyBhIG1hbmFnZW1lbnQgcHJvdG9j
b2wsIG1heSBkaXNjZXJuIHRoZSBuZXN0aW5nLiBCdXQgaXQgaXMgbm90IGEgc2Vuc29yLiBXb3Vs
ZCBpbmZvcm1hdGlvbiBmcm9tIHRoZSB0d28ga2luZHMgb2YgY29sbGVjdG9ycyBoYXZlIHRvIGJl
IGNvbWJpbmVkPyANCg0KQmVzdCwNCgkJCUNsaWZmDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBDbGlmZm9yZCBLYWhuIA0KU2VudDogU3VuZGF5LCBGZWJydWFyeSAwMSwgMjAx
NSA5OjM5IEFNDQpUbzogJ0hlbmsgQmlya2hvbHonOyBzYWNtQGlldGYub3JnDQpTdWJqZWN0OiBS
RTogW3NhY21dIENvbW1lbnRzIG9uIE5ldHdvcmsgSW50ZXJmYWNlDQoNCkhlbmssDQpCZWxhdGVk
IHJlc3BvbnNlIGhlcmUuDQoNCkFzIEkgdW5kZXJzdGFuZCB5b3UsIHlvdSB3b3VsZCByZW1vdmUg
dGhlIGNsYXNzICJzZXNzaW9uIiwgbWVudGlvbmVkIGluIHRoZSBkaWFncmFtIGFuZCBpbiBzZWN0
aW9uIDQuMTAgb2YgZHJhZnQtaWV0Zi1zYWNtLWluZm9ybWF0aW9uLW1vZGVsLiBJcyB0aGF0IHRy
dWU/IA0KDQpJIHJlYWxpemUgdGhlcmUgaXMgbW9yZSB0byB5b3VyIHByb3Bvc2FsLiBCdXQgSSB3
YW50IHRvIHJlc3BvbmQgdG8gcmVtb3ZpbmcgInNlc3Npb24iLiBMZXQncyBjb25zaWRlciB3aHkg
c2Vzc2lvbnMgd2VyZSB0aGVyZS4gDQoNClN1cHBvc2UgYW4gZW5kcG9pbnQncyBsYXllciAyIGlu
dGVyZmFjZSBjb21lcyBvbmxpbmUgYWZ0ZXIgYSBSQURJVVMgZXhjaGFuZ2UuIFNvbWUgb2YgdXMg
d291bGQgc2F5IGEgbGF5ZXIgMiBzZXNzaW9uIGhhcyBiZWd1bjsgdGhhdCBtYXkgYmUgbWlzdXNl
IG9mIHRoZSB3b3JkICJzZXNzaW9uIi4gQW55d2F5LCB0aGUgUkFESVVTIHNlcnZlciBrbm93czoN
Ci0gdGhlIGVuZHBvaW50J3MgTUFDIGFkZHJlc3MNCi0gdGhlIGNyZWRlbnRpYWxzIHVzZWQgaW4g
dGhlIFJBRElVUyBhdXRoZW50aWNhdGlvbg0KLSB0aGUgYXV0aG9yaXphdGlvbiB0aGF0IGl0IGdy
YW50ZWQgKFZMQU4sIGEgZmlsdGVyLWlkIGRlbm90aW5nIGZpcmV3YWxsIHJ1bGVzKQ0KLSB0aGUg
ZW5kcG9pbnQncyBjb21wbGlhbmNlLCBpZiBORUEgY2hlY2tpbmcgd2FzIGRvbmUgZHVyaW5nIHRo
ZSBSQURJVVMgZXhjaGFuZ2UNCi0gc29tZXRpbWVzLCBhbiBJUCBhZGRyZXNzIChpZiB0aGUgc3dp
dGNoIGRvZXMgREhDUCBzbm9vcGluZyBhbmQgcmVwb3J0cyBpdHMgZmluZGluZ3MgaW4gUkFESVVT
IEFjY291bnRpbmcgbWVzc2FnZXMpDQoNClRoYXQgaW5mb3JtYXRpb24gaXMgcmVsZXZhbnQgZm9y
IFNBQ00uIEF1dGhvcml6YXRpb24gaXMgcmVsZXZhbnQgYmVjYXVzZSBlbmRwb2ludHMgdGhhdCBo
YXZlIGFjY2VzcyB0byBzZW5zaXRpdmUgcmVzb3VyY2VzIG1heSBiZSBzdWJqZWN0IHRvIG1vcmUg
c3RyaW5nZW50IGNvbXBsaWFuY2UgcG9saWNpZXMuIChIbS4gRG8gd2UgaGF2ZSB0aGF0IGluIG91
ciB1c2UgY2FzZXM/IFNob3VsZCB3ZT8pIA0KDQpQZXJoYXBzIHdlIGRvbid0IG5lZWQgYSBzZXNz
aW9uIGluIHRoZSBtb2RlbC4gUGVyaGFwcyB0aGUgUkFESVVTIHNlcnZlciBjYW4ganVzdCBtYWtl
IGFuIGVuZHBvaW50IGF0dHJpYnV0ZSBhc3NlcnRpb24gc3RhdGluZyB0aGUgYWJvdmUgYXR0cmli
dXRlcy4gSSBsaWtlIHRoZSBzaW1wbGlmaWNhdGlvbi4gDQoNCk90aGVyIGtpbmRzIG9mIG5ldHdv
cmsgc2Vzc2lvbnMgKFRDUCBjb25uZWN0aW9ucywgZXRjLikgYXJlIGNlcnRhaW5seSByZWxldmFu
dCBmb3Igc2VjdXJpdHkuIEJ1dCB0aGV5IHNlZW0gdG8gYmUgb3V0c2lkZSBvZiB0aGUgU0FDTSBX
RydzIGNoYXJ0ZXIuIA0KDQpJbiBzdW0sIEkgY2Fubm90IHNlZSBhIHJlYXNvbiB0byBrZWVwICJz
ZXNzaW9uIiBpbiB0aGUgaW5mb3JtYXRpb24gbW9kZWwuICANCg0KV2hhdCBkbyBvdGhlcnMgdGhp
bms/DQoNCkJlc3QsDQoJCQlDbGlmZg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogSGVuayBCaXJraG9seiBbbWFpbHRvOmhlbmsuYmlya2hvbHpAc2l0LmZyYXVuaG9mZXIuZGVd
DQpTZW50OiBUdWVzZGF5LCBOb3ZlbWJlciAwNCwgMjAxNCAxMTozOSBBTQ0KVG86IHNhY21AaWV0
Zi5vcmcNClN1YmplY3Q6IFtzYWNtXSBDb21tZW50cyBvbiBOZXR3b3JrIEludGVyZmFjZQ0KDQpI
aSBhbGwsDQoNCnRoZSBuZXcgZHJhZnQgKGRyYWZ0LWlldGYtc2FjbS1pbmZvcm1hdGlvbi1tb2Rl
bC0wMCkgbm93IGluY2x1ZGVzIGEgY29tYmluZWQgc2VjdGlvbiBmb3IgIk5ldHdvcmsgU2Vzc2lv
biIgYW5kICJOZXR3b3JrIEludGVyZmFjZSIgKDQuMTAuKS4NCg0KTXkgcmVjb21tZW5kYXRpb24g
aXMgdG8gZGl2aWRlIHRoZSBlbGVtZW50cyBOZXR3b3JrIFNlc3Npb24sIE5ldHdvcmsgSW50ZXJm
YWNlIGFuZCBwb3RlbnRpYWxseSAoTmV0d29yaykgQWRkcmVzcyBpbnRvIHNlcGFyYXRlIHNlY3Rp
b25zIG9mIHRoZSBzYW1lIGxldmVsICg0LngpLg0KDQpXaGlsZSBib3RoIHRlcm1zIGFyZSByZWxh
dGVkLCBvZiBjb3Vyc2UsIHRoZXJlIGFyZSBzZXZlcmFsIChtb3JlIG9yIGxlc3MNCmltcG9ydGFu
dCkgcmVhc29ucyBmb3IgdGhpczoNCkEgc2Vzc2lvbiB0eXBpY2FsbHkgaW52b2x2ZXMgbXVsdGlw
bGUgcGFydGljaXBhbnRzIChlLmcuIGVuZHBvaW50cywgb3IgLSBicm9rZW4gZG93biAtIGV2ZW50
dWFsbHkgYWRkcmVzc2VzIG9yIGludGVyZmFjZXMpIGFuZCB0eXBpY2FsbHkgaGFzIGEgbGltaXRl
ZCBsaWZlLXRpbWUuIEFuIGludGVyZmFjZSwgaW4gY29udHJhc3QsIGlzIGEgc2luZ3VsYXIgZW50
aXR5IHRoYXQgY2FuIGV4aXN0IG92ZXIgdGhlIGNvbXBsZXRlIGxpZmUtY3ljbGUgb2YgYW4gZW5k
cG9pbnQgKHZpcnR1YWwgaW50ZXJmYWNlcyBjYW4gaGF2ZSBhIGZvcmVzZWVhYmxlIGxpbWl0ZWQg
bGlmZS10aW1lKS4gQXMgSXJhIHBvaW50ZWQgb3V0LCBhbiBpbnRlcmZhY2UgdHlwaWNhbGx5IHBy
b3ZpZGVzIGNvbm5lY3Rpdml0eSB0byBhIG5ldHdvcmsgb24gbGF5ZXIgdHdvIHRvIHRocmVlLCB3
aGlsZSBhIG5ldHdvcmsgc2Vzc2lvbiBpcyB0eXBpY2FsbHkgYXNzb2NpYXRlZCB3aXRoIGxheWVy
cyBhYm92ZSB0aG9zZS4NCg0KQWx0aG91Z2ggY2xvc2VseSByZWxhdGVkLCB0aGV5IGFyZSBxdWl0
ZSBkaWZmZXJlbnQsIHNlbWFudGljYWxseSwgYW5kIG1heSBldmVuIG5lZWQgc2VwYXJhdGUgcmVw
cmVzZW50YXRpb25zIGluIHRoZSBTQUNNIElNLg0KDQpNeSBwcm9wb3NhbCBmb3IgYSBzZXBhcmF0
ZSAiTmV0d29yayBJbnRlcmZhY2UiIHNlY3Rpb246DQoNCi0tLXNuaXAtLS0NCk5ldHdvcmsgSW50
ZXJmYWNlDQoNCkFuIGVuZHBvaW50IGlzIGNvbm5lY3RlZCB0byBhIG5ldHdvcmsgdmlhIG9uZSBv
ciBtb3JlIGludGVyZmFjZXMuIA0KSW50ZXJmYWNlcyBjYW4gYmUgcGh5c2ljYWwgb3IgdmlydHVh
bC4gSW50ZXJmYWNlcyBvZiBhbiBlbmRwb2ludCBjYW4gb3BlcmF0ZSBvbiBkaWZmZXJlbnQgbGF5
ZXJzLCBtb3N0IHByb21pbmVudGx5IHdoYXQgaXMgbm93IGNvbW1vbmx5IGNhbGxlZCBsYXllciAy
IGFuZCAzLiBXaXRoaW4gYSBsYXllciwgaW50ZXJmYWNlcyBjYW4gYmUgbmVzdGVkLg0KT24gbGF5
ZXIgMiwgYSByb290IGludGVyZmFjZSBpcyB0eXBpY2FsbHkgYXNzb2NpYXRlZCB3aXRoIGEgcGh5
c2ljYWwgaW50ZXJmYWNlIHBvcnQgYW5kIG5lc3RlZCBpbnRlcmZhY2VzIGFyZSB2aXJ0dWFsIGlu
dGVyZmFjZXMuIEluIHRoZSBjYXNlIG9mIGEgdmlydHVhbCBlbmRwb2ludCwgYSByb290IGludGVy
ZmFjZSBjYW4gYmUgYSB2aXJ0dWFsIGludGVyZmFjZS4gDQpWaXJ0dWFsIGxheWVyIDIgaW50ZXJm
YWNlcyBvZiBvbmUgb3IgbW9yZSBlbmRwb2ludHMgY2FuIGFsc28gY29uc3RpdHV0ZSBhbiBhZ2dy
ZWdhdGVkIGdyb3VwIG9mIGxpbmtzIHRoYXQgYWN0IGFzIG9uZS4NCk9uIGxheWVyIDMsIG5lc3Rl
ZCBpbnRlcmZhY2VzIHR5cGljYWxseSBjb25zdGl0dXRlIHZpcnR1YWwgdHVubmVscyBvciBuZXR3
b3Jrcy4NCkV4YW1wbGVzIGluY2x1ZGU6IHBoeXNpY2FsIEV0aGVybmV0IHBvcnQsIGxheWVyIDIg
VkxBTiBpbnRlcmZhY2UsIGEgTUMtTEFHIHNldHVwLCBsYXllciAzIFBvaW50LXRvLVBvaW50IHR1
bm5lbCBpbmdyZXNzIG9yIGVncmVzcy4NCi0tLXNuYXAtLS0NCg0KQSBzbWFsbCBhZGRpdGlvbiB0
byB0aGUgIkFkZHJlc3MiIHNlY3Rpb24sIGFuYWxvZ291c2x5Og0KDQotLS1zbmlwLS0tDQpOZXR3
b3JrIEFkZHJlc3MNCg0KTmV0d29yayBhZGRyZXNzZXMgYXJlIGxheWVyIHNwZWNpZmljIGFuZCBm
b2xsb3cgbGF5ZXIgc3BlY2lmaWMgYWRkcmVzcyBzY2hlbWVzLiBFYWNoIGludGVyZmFjZSBvZiBh
IHNwZWNpZmljIGxheWVyIGNhbiBiZSBhc3NvY2lhdGVkIHdpdGggb25lIG9yIG1vcmUgYWRkcmVz
c2VzIGFwcHJvcHJpYXRlIGZvciB0aGF0IGxheWVyLg0KVGhlcmUgaXMgbm8gZ3VhcmFudGVlIHRo
YXQgYW4gYWRkcmVzcyBpcyBnbG9iYWxseSB1bmlxdWUuIEluIGdlbmVyYWwsIHRoZXJlIGlzIGEg
c2NvcGUgdG8gYW4gYWRkcmVzcyBpbiB3aGljaCBpdCBpcyBpbnRlbmRlZCB0byBiZSB1bmlxdWUu
DQpFeGFtcGxlcyBpbmNsdWRlOiBwaHlzaWNhbCBFdGhlcm5ldCBwb3J0IHdpdGggYSBNQUMgYWRk
cmVzcywgbGF5ZXIgMiBWTEFOIGludGVyZmFjZSB3aXRoIGEgTUFDIGFkZHJlc3MsIGxheWVyIDMg
aW50ZXJmYWNlIHdpdGggbXVsdGlwbGUgSVB2NiBhZGRyZXNzZXMsIGxheWVyIDMgdHVubmVsIGlu
Z3Jlc3Mgb3IgZWdyZXNzIHdpdGggYW4gSVB2NCBhZGRyZXNzLg0KLS0tc25hcC0tLQ0KDQpTb21l
dGltZXMsIHRoZSBjb21wbGV4aXR5IGEgc2V0dXAgb2YgaW50ZXJmYWNlcyBjYW4gaW5jb3Jwb3Jh
dGUgaXMgYSBsaXR0bGUgYml0IHVuZGVyZXN0aW1hdGVkLCBJTUhPLiBUaGUgcHJvcG9zZWQgdGV4
dCBhYm92ZSBvbmx5IGluY2x1ZGVzIHRoZSBtb3N0IGNvbW1vbiBjYXNlcyBhbmQgZG9lcyBub3Qg
dG91Y2ggZW1lcmdpbmcgcHJhY3RpY2VzLCBzdWNoIGFzIHBoeXNpY2FsIGludGVyZmFjZSBtb2R1
bGVzIHRoYXQgcHJvdmlkZSBhIHNldCBvZiBzaW5nbGUgcGh5c2ljYWwgaW50ZXJmYWNlcywgd2hp
Y2ggYXJlIGFzc29jaWF0ZWQgd2l0aCBtdWx0aXBsZSBkaXN0aW5ndWlzaGFibGUgZW5kcG9pbnRz
IGF0IHRoZSBzYW1lIHRpbWUuDQoNCkluIG9yZGVyIHRvIGFkZHJlc3MgbmV0d29yayBjZW50cmlj
IHNlY3VyaXR5L21vbml0b3JpbmcgcHJvY2Vzc2VzLCBlZmZlY3RpdmVseSwgdGhlIFNBQ00gSU0g
c2hvdWxkIGJlIGFibGUgdG8gaGFuZGxlIHRoZSBjb21wbGV4aXR5IG9mIGFwcGxpZWQgY29tbW9u
IHByYWN0aWNlIGluIGl0cyBkZWZpbml0aW9uIG9mICJOZXR3b3JrIEludGVyZmFjZSIsIEkgdGhp
bmsuDQoNCkJlc3QsDQoNCkhlbmsNCg0K


From nobody Sun Feb  1 08:09:50 2015
Return-Path: <blueroofmusic@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9181A8928 for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 08:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham
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 At8DFTXAc9mO for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 08:09:44 -0800 (PST)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 193561A03AB for <sacm@ietf.org>; Sun,  1 Feb 2015 08:09:44 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id q59so34960664wes.3 for <sacm@ietf.org>; Sun, 01 Feb 2015 08:09:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=vIlDTz+UPgNk6eDP5G8l5fwPsrfmj5CpFh5eBINyrYo=; b=xMtXtY+zafKozFVZ5ODrjMRJ3L0w0uQ/TI2nngvz4ZeEuTyc09L4QuRxj//u3ZrTKK HEkt4ziAR1PMCPbXeVX879T9cfgt/9lKoBOdS1aKj/u7O+CQqARbIUkBQVxGLLH5VEBz j2Ebdx9QwIMdAtEcu6uVFEUhPmgvhDtg9UfLuTFha/uPPIQeDcQGVIt8Mdl6cDKarr6Z 6dO4LRwT+NaVb9wQ4W3uds9uiwtkVBYrOvUJW/LtGVHgzY/8PXZua/iC+aWp9VXHlwDs iBOfMbQnsB2Q/1kBIc+fM7+ENeZTmjCSL8pCi4N7gRbaBz1E1hhCAlAVfLy2fz9rH0i0 rgjA==
X-Received: by 10.180.37.197 with SMTP id a5mr15389936wik.2.1422806982745; Sun, 01 Feb 2015 08:09:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.32.77 with HTTP; Sun, 1 Feb 2015 08:09:22 -0800 (PST)
In-Reply-To: <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <54590118.9050702@sit.fraunhofer.de> <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
From: Ira McDonald <blueroofmusic@gmail.com>
Date: Sun, 1 Feb 2015 11:09:22 -0500
Message-ID: <CAN40gSt0Nk9d7V0gPE+L6uKYBKDkpJ_kf874ZeqDS9ChpN1xNA@mail.gmail.com>
To: Clifford Kahn <cliffordk@pulsesecure.net>, Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f50309cca656e050e0910c2
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/Gr8FQkMIlDDKI31johsFMyWzWCM>
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 16:09:48 -0000

--e89a8f50309cca656e050e0910c2
Content-Type: text/plain; charset=UTF-8

Hi Cliff,

I'll let Henk respond to most of your questions.

But I wanted to clarify the terms "address" and "session" a bit.

In your example, "1.1.1.1" is a layer 3 (IP) network layer address (a host
device address).
Applications do not "listen" directly to such an address.

OTOH, "1.1.1.1:1433" is a layer 4 (TCP, UDP, or SCTP) transport layer
address (often
called an endpoint application address).

Firewalls mostly operate on layer 4 (and above) addresses.  The port *is*
always
present in a layer 4 address - it's not separate.  Firewall port masks
select allowed
incoming (and separate outgoing) sets of port numbers.

An application layer gateway (ALG) is sometimes incorporated into a
firewall and
will inspect the headers (and sometimes the data for IPR protection) in a
layer 5
(session), layer 6 (presentation), or layer 7 (application) packet (e.g.,
the headers
in an HTTP PUT request).

The term "connection" is only correctly used for a layer 4 pair of
endpoints that
uses a reliable transport protocol (e.g., TCP) that re-orders received
packets,
eliminates duplicates, retransmits as necessary, and catches dropped packets
(ones not fixed by retransmission).  In all cases an unrecoverable dropped
packet MUST result in a closed connection.

The term "session" is only correctly used for a layer 5 or higher pair of
endpoints.
Here, a number of packets may make up a single "message" (such as HTTP PUT
request).

The term "association" can be used at any level from layer 2 on up.  A
"security
association" is simply a refinement of an "association" (that has some
specific
security attributes and guarantees).  It's possible to have an
"association" using
any connectionless datagram protocol (e.g., IP at layer 3 and UDP at layer
4).

We now return you to your regular discussion...

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434


On Sun, Feb 1, 2015 at 10:38 AM, Clifford Kahn <cliffordk@pulsesecure.net>
wrote:

> Henk,
> First, a correction. I said, incorrectly, that you had proposed removing
> the idea of "session". You actually proposed separating it from
> "interface". (I do suggest we remove "session" altogether.)
>
> Second, I like your suggestion of promoting section 4.10.1, "Address", to
> a 4.x section.
>
> Third, I like your addition to the "Address" section.
>
> Fourth, let's consider taking it further. In a side conversation you
> pointed out that a port number is really part of an address. The port
> number matters for some purposes, but not for others. One place where it
> matters: you pointed out that compliance policies about network ingress
> make a lot of sense. For example, a policy could disapprove of an endpoint
> listening on the MSSQL port (1433). Many successful attacks have been made
> on ports unintentionally left open, so this is well motivated.
>
> How would we model this? Is 1.1.1.1:1433 a sub-address of 1.1.1.1?
>
> Fifth, and most central: you write that we should capture the nested and
> layered structure of interfaces to "address network centric
> security/monitoring processes, effectively". I don't understand yet how a
> network based attribute collector (a "sensor") would know or care.  A
> sensor observes or injects network traffic. It knows addresses. How can it
> be aware of network interfaces? How can it discern whether one interface
> nests in another?
>
> An attribute collector that runs on the endpoint, or that queries the
> endpoint using a management protocol, may discern the nesting. But it is
> not a sensor. Would information from the two kinds of collectors have to be
> combined?
>
> Best,
>                         Cliff
>
> -----Original Message-----
> From: Clifford Kahn
> Sent: Sunday, February 01, 2015 9:39 AM
> To: 'Henk Birkholz'; sacm@ietf.org
> Subject: RE: [sacm] Comments on Network Interface
>
> Henk,
> Belated response here.
>
> As I understand you, you would remove the class "session", mentioned in
> the diagram and in section 4.10 of draft-ietf-sacm-information-model. Is
> that true?
>
> I realize there is more to your proposal. But I want to respond to
> removing "session". Let's consider why sessions were there.
>
> Suppose an endpoint's layer 2 interface comes online after a RADIUS
> exchange. Some of us would say a layer 2 session has begun; that may be
> misuse of the word "session". Anyway, the RADIUS server knows:
> - the endpoint's MAC address
> - the credentials used in the RADIUS authentication
> - the authorization that it granted (VLAN, a filter-id denoting firewall
> rules)
> - the endpoint's compliance, if NEA checking was done during the RADIUS
> exchange
> - sometimes, an IP address (if the switch does DHCP snooping and reports
> its findings in RADIUS Accounting messages)
>
> That information is relevant for SACM. Authorization is relevant because
> endpoints that have access to sensitive resources may be subject to more
> stringent compliance policies. (Hm. Do we have that in our use cases?
> Should we?)
>
> Perhaps we don't need a session in the model. Perhaps the RADIUS server
> can just make an endpoint attribute assertion stating the above attributes.
> I like the simplification.
>
> Other kinds of network sessions (TCP connections, etc.) are certainly
> relevant for security. But they seem to be outside of the SACM WG's charter.
>
> In sum, I cannot see a reason to keep "session" in the information model.
>
> What do others think?
>
> Best,
>                         Cliff
>
> -----Original Message-----
> From: Henk Birkholz [mailto:henk.birkholz@sit.fraunhofer.de]
> Sent: Tuesday, November 04, 2014 11:39 AM
> To: sacm@ietf.org
> Subject: [sacm] Comments on Network Interface
>
> Hi all,
>
> the new draft (draft-ietf-sacm-information-model-00) now includes a
> combined section for "Network Session" and "Network Interface" (4.10.).
>
> My recommendation is to divide the elements Network Session, Network
> Interface and potentially (Network) Address into separate sections of the
> same level (4.x).
>
> While both terms are related, of course, there are several (more or less
> important) reasons for this:
> A session typically involves multiple participants (e.g. endpoints, or -
> broken down - eventually addresses or interfaces) and typically has a
> limited life-time. An interface, in contrast, is a singular entity that can
> exist over the complete life-cycle of an endpoint (virtual interfaces can
> have a foreseeable limited life-time). As Ira pointed out, an interface
> typically provides connectivity to a network on layer two to three, while a
> network session is typically associated with layers above those.
>
> Although closely related, they are quite different, semantically, and may
> even need separate representations in the SACM IM.
>
> My proposal for a separate "Network Interface" section:
>
> ---snip---
> Network Interface
>
> An endpoint is connected to a network via one or more interfaces.
> Interfaces can be physical or virtual. Interfaces of an endpoint can
> operate on different layers, most prominently what is now commonly called
> layer 2 and 3. Within a layer, interfaces can be nested.
> On layer 2, a root interface is typically associated with a physical
> interface port and nested interfaces are virtual interfaces. In the case of
> a virtual endpoint, a root interface can be a virtual interface.
> Virtual layer 2 interfaces of one or more endpoints can also constitute an
> aggregated group of links that act as one.
> On layer 3, nested interfaces typically constitute virtual tunnels or
> networks.
> Examples include: physical Ethernet port, layer 2 VLAN interface, a MC-LAG
> setup, layer 3 Point-to-Point tunnel ingress or egress.
> ---snap---
>
> A small addition to the "Address" section, analogously:
>
> ---snip---
> Network Address
>
> Network addresses are layer specific and follow layer specific address
> schemes. Each interface of a specific layer can be associated with one or
> more addresses appropriate for that layer.
> There is no guarantee that an address is globally unique. In general,
> there is a scope to an address in which it is intended to be unique.
> Examples include: physical Ethernet port with a MAC address, layer 2 VLAN
> interface with a MAC address, layer 3 interface with multiple IPv6
> addresses, layer 3 tunnel ingress or egress with an IPv4 address.
> ---snap---
>
> Sometimes, the complexity a setup of interfaces can incorporate is a
> little bit underestimated, IMHO. The proposed text above only includes the
> most common cases and does not touch emerging practices, such as physical
> interface modules that provide a set of single physical interfaces, which
> are associated with multiple distinguishable endpoints at the same time.
>
> In order to address network centric security/monitoring processes,
> effectively, the SACM IM should be able to handle the complexity of applied
> common practice in its definition of "Network Interface", I think.
>
> Best,
>
> Henk
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>

--e89a8f50309cca656e050e0910c2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Cliff,<br><br>I&#39;ll let Henk respond to most of your questions.<br><b=
r>But I wanted to clarify the terms &quot;address&quot; and &quot;session&q=
uot; a bit.<br><br>In your example, &quot;1.1.1.1&quot; is a layer 3 (IP) n=
etwork layer address (a host device address).<br>Applications do not &quot;=
listen&quot; directly to such an address.<br><br>OTOH, &quot;<a href=3D"htt=
p://1.1.1.1:1433">1.1.1.1:1433</a>&quot; is a layer 4 (TCP, UDP, or SCTP) t=
ransport layer address (often<br>called an endpoint application address).<b=
r><br>Firewalls mostly operate on layer 4 (and above) addresses.=C2=A0 The =
port *is* always<br>present in a layer 4 address - it&#39;s not separate.=
=C2=A0 Firewall port masks select allowed<br>incoming (and separate outgoin=
g) sets of port numbers.=C2=A0 <br><br>An application layer gateway (ALG) i=
s sometimes incorporated into a firewall and <br>will inspect the headers (=
and sometimes the data for IPR protection) in a layer 5 <br>(session), laye=
r 6 (presentation), or layer 7 (application) packet (e.g., the headers <br>=
in an HTTP PUT request).<br><br>The term &quot;connection&quot; is only cor=
rectly used for a layer 4 pair of endpoints that<br>uses a reliable transpo=
rt protocol (e.g., TCP) that re-orders received packets,<br>eliminates dupl=
icates, retransmits as necessary, and catches dropped packets<br>(ones not =
fixed by retransmission).=C2=A0 In all cases an unrecoverable dropped <br>p=
acket MUST result in a closed connection.<br><br>The term &quot;session&quo=
t; is only correctly used for a layer 5 or higher pair of endpoints.<br>Her=
e, a number of packets may make up a single &quot;message&quot; (such as HT=
TP PUT<br>request).<br><br>The term &quot;association&quot; can be used at =
any level from layer 2 on up.=C2=A0 A &quot;security<br>association&quot; i=
s simply a refinement of an &quot;association&quot; (that has some specific=
<br>security attributes and guarantees).=C2=A0 It&#39;s possible to have an=
 &quot;association&quot; using <br>any connectionless datagram protocol (e.=
g., IP at layer 3 and UDP at layer 4).<br><br>We now return you to your reg=
ular discussion...<br><br>Cheers,<br>- Ira<br><br clear=3D"all"><div><div c=
lass=3D"gmail_signature"><div dir=3D"ltr">Ira McDonald (Musician / Software=
 Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linu=
x Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Grou=
p<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designa=
ted Expert - IPP &amp; Printer MIB<br>Blue Roof Music / High North Inc<br><=
a style=3D"color:rgb(51,51,255)" href=3D"http://sites.google.com/site/bluer=
oofmusic" target=3D"_blank">http://sites.google.com/site/blueroofmusic</a><=
br><a style=3D"color:rgb(102,0,204)" href=3D"http://sites.google.com/site/h=
ighnorthinc" target=3D"_blank">http://sites.google.com/site/highnorthinc</a=
><br>mailto: <a href=3D"mailto:blueroofmusic@gmail.com" target=3D"_blank">b=
lueroofmusic@gmail.com</a><br>Winter=C2=A0 579 Park Place=C2=A0 Saline, MI=
=C2=A0 48176=C2=A0 734-944-0094<br>Summer=C2=A0 PO Box 221=C2=A0 Grand Mara=
is, MI 49839=C2=A0 906-494-2434<br><br><div style=3D"display:inline"></div>=
<div style=3D"display:inline"></div><div style=3D"display:inline"></div><di=
v></div><div></div><div></div><div></div></div></div></div>
<br><div class=3D"gmail_quote">On Sun, Feb 1, 2015 at 10:38 AM, Clifford Ka=
hn <span dir=3D"ltr">&lt;<a href=3D"mailto:cliffordk@pulsesecure.net" targe=
t=3D"_blank">cliffordk@pulsesecure.net</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Henk,<br>
First, a correction. I said, incorrectly, that you had proposed removing th=
e idea of &quot;session&quot;. You actually proposed separating it from &qu=
ot;interface&quot;. (I do suggest we remove &quot;session&quot; altogether.=
)<br>
<br>
Second, I like your suggestion of promoting section 4.10.1, &quot;Address&q=
uot;, to a 4.x section.<br>
<br>
Third, I like your addition to the &quot;Address&quot; section.<br>
<br>
Fourth, let&#39;s consider taking it further. In a side conversation you po=
inted out that a port number is really part of an address. The port number =
matters for some purposes, but not for others. One place where it matters: =
you pointed out that compliance policies about network ingress make a lot o=
f sense. For example, a policy could disapprove of an endpoint listening on=
 the MSSQL port (1433). Many successful attacks have been made on ports uni=
ntentionally left open, so this is well motivated.<br>
<br>
How would we model this? Is <a href=3D"http://1.1.1.1:1433" target=3D"_blan=
k">1.1.1.1:1433</a> a sub-address of 1.1.1.1?<br>
<br>
Fifth, and most central: you write that we should capture the nested and la=
yered structure of interfaces to &quot;address network centric security/mon=
itoring processes, effectively&quot;. I don&#39;t understand yet how a netw=
ork based attribute collector (a &quot;sensor&quot;) would know or care.=C2=
=A0 A sensor observes or injects network traffic. It knows addresses. How c=
an it be aware of network interfaces? How can it discern whether one interf=
ace nests in another?<br>
<br>
An attribute collector that runs on the endpoint, or that queries the endpo=
int using a management protocol, may discern the nesting. But it is not a s=
ensor. Would information from the two kinds of collectors have to be combin=
ed?<br>
<br>
Best,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 Cliff<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: Clifford Kahn<br>
Sent: Sunday, February 01, 2015 9:39 AM<br>
To: &#39;Henk Birkholz&#39;; <a href=3D"mailto:sacm@ietf.org">sacm@ietf.org=
</a><br>
Subject: RE: [sacm] Comments on Network Interface<br>
<br>
Henk,<br>
Belated response here.<br>
<br>
As I understand you, you would remove the class &quot;session&quot;, mentio=
ned in the diagram and in section 4.10 of draft-ietf-sacm-information-model=
. Is that true?<br>
<br>
I realize there is more to your proposal. But I want to respond to removing=
 &quot;session&quot;. Let&#39;s consider why sessions were there.<br>
<br>
Suppose an endpoint&#39;s layer 2 interface comes online after a RADIUS exc=
hange. Some of us would say a layer 2 session has begun; that may be misuse=
 of the word &quot;session&quot;. Anyway, the RADIUS server knows:<br>
- the endpoint&#39;s MAC address<br>
- the credentials used in the RADIUS authentication<br>
- the authorization that it granted (VLAN, a filter-id denoting firewall ru=
les)<br>
- the endpoint&#39;s compliance, if NEA checking was done during the RADIUS=
 exchange<br>
- sometimes, an IP address (if the switch does DHCP snooping and reports it=
s findings in RADIUS Accounting messages)<br>
<br>
That information is relevant for SACM. Authorization is relevant because en=
dpoints that have access to sensitive resources may be subject to more stri=
ngent compliance policies. (Hm. Do we have that in our use cases? Should we=
?)<br>
<br>
Perhaps we don&#39;t need a session in the model. Perhaps the RADIUS server=
 can just make an endpoint attribute assertion stating the above attributes=
. I like the simplification.<br>
<br>
Other kinds of network sessions (TCP connections, etc.) are certainly relev=
ant for security. But they seem to be outside of the SACM WG&#39;s charter.=
<br>
<br>
In sum, I cannot see a reason to keep &quot;session&quot; in the informatio=
n model.<br>
<br>
What do others think?<br>
<br>
Best,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 Cliff<br>
<br>
-----Original Message-----<br>
From: Henk Birkholz [mailto:<a href=3D"mailto:henk.birkholz@sit.fraunhofer.=
de">henk.birkholz@sit.fraunhofer.de</a>]<br>
Sent: Tuesday, November 04, 2014 11:39 AM<br>
To: <a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
Subject: [sacm] Comments on Network Interface<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">Hi all,<br>
<br>
the new draft (draft-ietf-sacm-information-model-00) now includes a combine=
d section for &quot;Network Session&quot; and &quot;Network Interface&quot;=
 (4.10.).<br>
<br>
My recommendation is to divide the elements Network Session, Network Interf=
ace and potentially (Network) Address into separate sections of the same le=
vel (4.x).<br>
<br>
While both terms are related, of course, there are several (more or less<br=
>
important) reasons for this:<br>
A session typically involves multiple participants (e.g. endpoints, or - br=
oken down - eventually addresses or interfaces) and typically has a limited=
 life-time. An interface, in contrast, is a singular entity that can exist =
over the complete life-cycle of an endpoint (virtual interfaces can have a =
foreseeable limited life-time). As Ira pointed out, an interface typically =
provides connectivity to a network on layer two to three, while a network s=
ession is typically associated with layers above those.<br>
<br>
Although closely related, they are quite different, semantically, and may e=
ven need separate representations in the SACM IM.<br>
<br>
My proposal for a separate &quot;Network Interface&quot; section:<br>
<br>
---snip---<br>
Network Interface<br>
<br>
An endpoint is connected to a network via one or more interfaces.<br>
Interfaces can be physical or virtual. Interfaces of an endpoint can operat=
e on different layers, most prominently what is now commonly called layer 2=
 and 3. Within a layer, interfaces can be nested.<br>
On layer 2, a root interface is typically associated with a physical interf=
ace port and nested interfaces are virtual interfaces. In the case of a vir=
tual endpoint, a root interface can be a virtual interface.<br>
Virtual layer 2 interfaces of one or more endpoints can also constitute an =
aggregated group of links that act as one.<br>
On layer 3, nested interfaces typically constitute virtual tunnels or netwo=
rks.<br>
Examples include: physical Ethernet port, layer 2 VLAN interface, a MC-LAG =
setup, layer 3 Point-to-Point tunnel ingress or egress.<br>
---snap---<br>
<br>
A small addition to the &quot;Address&quot; section, analogously:<br>
<br>
---snip---<br>
Network Address<br>
<br>
Network addresses are layer specific and follow layer specific address sche=
mes. Each interface of a specific layer can be associated with one or more =
addresses appropriate for that layer.<br>
There is no guarantee that an address is globally unique. In general, there=
 is a scope to an address in which it is intended to be unique.<br>
Examples include: physical Ethernet port with a MAC address, layer 2 VLAN i=
nterface with a MAC address, layer 3 interface with multiple IPv6 addresses=
, layer 3 tunnel ingress or egress with an IPv4 address.<br>
---snap---<br>
<br>
Sometimes, the complexity a setup of interfaces can incorporate is a little=
 bit underestimated, IMHO. The proposed text above only includes the most c=
ommon cases and does not touch emerging practices, such as physical interfa=
ce modules that provide a set of single physical interfaces, which are asso=
ciated with multiple distinguishable endpoints at the same time.<br>
<br>
In order to address network centric security/monitoring processes, effectiv=
ely, the SACM IM should be able to handle the complexity of applied common =
practice in its definition of &quot;Network Interface&quot;, I think.<br>
<br>
Best,<br>
<br>
Henk<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">_______________________=
________________________<br>
sacm mailing list<br>
<a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/sacm</a><br>
</div></div></blockquote></div><br>

--e89a8f50309cca656e050e0910c2--


From nobody Sun Feb  1 09:33:03 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8FA1A8A7D for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 09:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 tK2vDgreWFm6 for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 09:32:55 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0057.outbound.protection.outlook.com [207.46.100.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4541A1A36 for <sacm@ietf.org>; Sun,  1 Feb 2015 09:32:48 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1354.namprd06.prod.outlook.com (25.161.212.12) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sun, 1 Feb 2015 17:32:46 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Sun, 1 Feb 2015 17:32:46 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: New version of the information model diagram
Thread-Index: AdA+RMRU0inuW65EQle0W8iyZ0HKKw==
Date: Sun, 1 Feb 2015 17:32:45 +0000
Message-ID: <CY1PR0601MB1355F7B3B6BA924F28B80135B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1354;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1354; 
x-forefront-prvs: 04740D25F1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(16236675004)(86362001)(54356999)(54206007)(50986999)(2501002)(74316001)(92566002)(40100003)(229853001)(19580395003)(15975445007)(110136001)(2351001)(54606007)(107886001)(102836002)(2900100001)(122556002)(46102003)(77156002)(62966003)(450100001)(66066001)(19625215002)(19300405004)(87936001)(99286002)(33656002)(76576001)(2656002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1354; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_CY1PR0601MB1355F7B3B6BA924F28B80135B73F0CY1PR0601MB1355_"
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2015 17:32:45.7370 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1354
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/SFweHRtwvoJFkSz87mizmURux88>
Subject: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 17:32:59 -0000

--_000_CY1PR0601MB1355F7B3B6BA924F28B80135B73F0CY1PR0601MB1355_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,
I reference draft-ietf-sacm-information-model-00.

I would eliminate figure 1. It's redundant.

I would change
                "Figure 2 depicts an instance of the information model."
to
                "Figure 1 depicts the information model."

Here is a new version of the figure.  (View the figure using a fixed-width =
font, such as Courier.)

  +---------+ +---------+              +--------+____________________
  |Hardware | |Software |    __________|Location|*_______________    |
  |Component| |Component|   |         *+--------+*               |   |
  +---------+ +---------+   |                                    |   |
       |1          |1       |         +----------+               |   |
       |*          |*       |   ______|Credential|____________   |   |
  +---------+ +--------+    |  |     *+----------+*           |* |*  |
  |Hardware | |Software|    |  |         +---------+       +-------+ |
  |Instance | |Instance|    |  |         |Network  |_______|Account| |
  +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |
       |*      |*          *| *|         |- - - - -|                *|
       |       |____1+----------+1______*|Network  |__________+-------+
       |_____________| Endpoint |_____   |Interface|*     1..*|Address|
                    1|          |0..1 |  +---------+          +-------+
                     +----------+     |      1|
          _____________|1    |*       |       |_____+-------------+
         |                   |________|            *|Authorization|
         |                    part-of>              +-------------+
  .......|..............................................................
         |            |0..1
         |            |
         |            |*
         |         +-----+            +---------+___________________
        |         | AVP |____________|Endpoint |1..*   <based-on   |
        ^|         +-----+1..*       1|Attribute|________           |
hosted-by|           *|               |Assertion|*       |          |
         |            |               +---------+        |          |
        |            |produced-using   |*    |*         |         *|
        |           1|V                |     |__________|     +-------+
        |        +--------+            |       <based-on      |Summary|
         |        | Method |            |                      +-------+
         |        +--------+            |produced-by               *|
         |____________________          |V                          |
                              |*       1|                           |
    +--------+1____________*+-----------+                          |
    |        |    guides>   | SACM      |__________________________|
    |Guidance|              | Component |1       <produced-by
    +--------+*____________1+-----------+
               <produced-by

         -------------------------------------------------------------
         ..... Above this line is the monitorable world
         -------------------------------------------------------------
The figure has additions for provenance:

*         A class "Method"

*         The produced-using relationship between an AVP and  a Method

*         The produced-by relationship between a Guidance and a SACM Compon=
ent

*         The hosted-by relationship between a SACM Component and an Endpoi=
nt

The figure has other changes:

*         asserted-by and summarized-by have been renamed to produced-by.

*         "User" is now "Account". If a user has different credentials, SAC=
M cannot know that they belong to the same user. But, per Kim W, many organ=
izations do have accounts that associate credentials.

*         The multiplicity of the based-on relationships have been correcte=
d.

*         More relationships now have labels, per UML convention.

*         I got rid of the causal arrows, which had become redundant and we=
re nonstandard and clutter.

Still to come:

*         We are still discussing network sessions and network interfaces a=
nd how to model them. I left that part of the figure alone for now.

*         More provenance.

*         Should Level of Assurance be a class?

*         If an endpoint provides information about itself to an external a=
ttribute collector, which turns the information into SACM notation, how do =
we model the endpoint's and the collector's parts in the chain of custody?

*         Will a SACM controller ever add an AVP to an endpoint attribute a=
ssertion? If so, how will we model that?

*         Coverage. I know Kim is interested in capturing enough informatio=
n so that gaps in coverage can be found. (Is this in our requirements? It s=
hould be, I think.) She has suggested something like, each SACM component s=
hould publish a description of what it covers. The "guides" relationship mi=
ght look sufficient, but it isn't. If a piece of guidance says "Capture the=
 SWID tag inventory", a SACM component can heed that, but only for some end=
points.


Clifford Kahn
Principal Engineeer, Technical Lead


--_000_CY1PR0601MB1355F7B3B6BA924F28B80135B73F0CY1PR0601MB1355_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:51273718;
	mso-list-type:hybrid;
	mso-list-template-ids:-2062762052 67698689 67698689 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:204029165;
	mso-list-type:hybrid;
	mso-list-template-ids:1061309302 -540740942 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:638413199;
	mso-list-type:hybrid;
	mso-list-template-ids:978585464 67698689 -622056514 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level2
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3
	{mso-list-id:1075981360;
	mso-list-type:hybrid;
	mso-list-template-ids:-919074748 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l4
	{mso-list-id:1341617650;
	mso-list-type:hybrid;
	mso-list-template-ids:2023512300 -1828662774 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l4:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l4:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l4:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l4:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l4:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l4:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l4:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l4:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l4:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l5
	{mso-list-id:2040273349;
	mso-list-type:hybrid;
	mso-list-template-ids:-1579648226 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l5:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l5:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l5:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l5:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l5:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l5:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l5:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l5:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l5:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l6
	{mso-list-id:2061395641;
	mso-list-type:hybrid;
	mso-list-template-ids:354078946 67698689 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l6:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l6:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l6:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l6:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l6:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l6:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l6:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l6:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l6:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">All,<o:p></o:p></p>
<p class=3D"MsoNormal">I reference draft-ietf-sacm-information-model-00. <o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would eliminate figure 1. It's redundant.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would change<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 2 depicts an instance =
of the information model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">to<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 1 depicts the informat=
ion model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is a new version of the figure. &nbsp;(View the=
 figure using a fixed-width font, such as Courier.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;--------&#43;_______=
_____________<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software |&nbsp;&nbsp;&nbsp; __________|Location|*_____=
__________&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Component| |Component|&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; *&#43;--------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; ___=
___|Credential|____________&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp; &nbsp;&nbsp;*&#43;----------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |* |*&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; &#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Instance | |Instance|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Network&nbsp; |_______|Account| |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Session&nbsp; |*&nbsp; 0..1=
&#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *| *|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |- - - - -|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *|<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|____1&#43;----------&#43;1______*|Network&nbsp; |__________&#43;-------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_____________| Endpoint |_____&nbsp;&=
nbsp; |Interface|*&nbsp;&nbsp;&nbsp;&nbsp; 1..*|Address|<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;1|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|0..1 |&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nb=
sp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; _____________|1&nbsp=
;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; |_____&#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|________|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; *|Authorization|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;part-of&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; .......|............................................................=
..<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;&nbsp;&nbsp;&#43;-----&#43;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;___________________<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;| AVP |____________|Endpoint |1..* &nbsp;&nbsp;&lt;b=
ased-on &nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;^| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&#43;-----&#43;1..* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
1|Attribute|________&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
hosted-by| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&n=
bsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;|Assertion|*&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&#43;---------&#43;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp; &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-using &nbsp;&nbsp;|* &nb=
sp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|V&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&=
nbsp;|__________| &nbsp;&nbsp;&nbsp;&nbsp;&#43;-------&#43;<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;based-=
on&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;|Summary|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;| Method | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#=
43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-by &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|____________________=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|V&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;|* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;1____________*&#43;-----------&#4=
3;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;=
&nbsp;&nbsp; guides&gt;&nbsp;&nbsp; | SACM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_=
_________________________|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|Guidance|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Component |1&nbsp;&nbsp; &nbsp;&nbs=
p;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;*____________1&#43;-----------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ..... Above this line is t=
he monitorable world<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal">The figure has additions for provenance:<o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo3"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>A class &quot;Method&quot;<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo3"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The produced-using relationship between an A=
VP and&nbsp; a Method<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo3"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The produced-by relationship between a Guida=
nce and a SACM Component<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo3"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The hosted-by relationship between a SACM Co=
mponent and an Endpoint<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has other changes:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>asserted-by and summarized-by have been rena=
med to produced-by.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>&quot;User&quot; is now &quot;Account&quot;.=
 If a user has different credentials, SACM cannot know that they belong to =
the same user. But, per Kim W, many organizations do have accounts that ass=
ociate credentials.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The multiplicity of the based-on relationshi=
ps have been corrected.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>More relationships now have labels, per UML =
convention.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>I got rid of the causal arrows, which had be=
come redundant and were nonstandard and clutter.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Still to come:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo7"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>We are still discussing network sessions and=
 network interfaces and how to model them. I left that part of the figure a=
lone for now.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo7"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>More provenance. <o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo7">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Should Level of Assurance be a class? <o:p><=
/o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo7">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>If an endpoint provides information about it=
self to an external attribute collector, which turns the information into S=
ACM notation, how do we model the endpoint's and the collector's parts in t=
he chain of custody?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo7">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Will a SACM controller ever add an AVP to an=
 endpoint attribute assertion? If so, how will we model that?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo7"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Coverage. I know Kim is interested in captur=
ing enough information so that gaps in coverage can be found. (Is this in o=
ur requirements? It should be, I think.) She has suggested something like, =
each SACM component should publish
 a description of what it covers. The &quot;guides&quot; relationship might=
 look sufficient, but it isn't. If a piece of guidance says &quot;Capture t=
he SWID tag inventory&quot;, a SACM component can heed that, but only for s=
ome endpoints.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Clifford Kahn<o:p></o:p></p>
<p class=3D"MsoNormal">Principal Engineeer, Technical Lead<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CY1PR0601MB1355F7B3B6BA924F28B80135B73F0CY1PR0601MB1355_--


From nobody Sun Feb  1 09:37:22 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BDBC1A8A7D for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 09:37:21 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 TQUbEcmfi4LH for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 09:37:17 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0087.outbound.protection.outlook.com [207.46.100.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A11A1A1A45 for <sacm@ietf.org>; Sun,  1 Feb 2015 09:37:17 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1354.namprd06.prod.outlook.com (25.161.212.12) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sun, 1 Feb 2015 17:37:16 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Sun, 1 Feb 2015 17:37:16 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: New version of the information model diagram
Thread-Index: AdA+RMRU0inuW65EQle0W8iyZ0HKKwAAMNug
Date: Sun, 1 Feb 2015 17:37:16 +0000
Message-ID: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1354;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1354; 
x-forefront-prvs: 04740D25F1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(62966003)(46102003)(77156002)(2900100001)(122556002)(99286002)(87936001)(76576001)(2656002)(33656002)(19625215002)(450100001)(66066001)(19300405004)(54206007)(50986999)(54356999)(16236675004)(86362001)(110136001)(15975445007)(102836002)(107886001)(2351001)(54606007)(19580405001)(2501002)(19580395003)(40100003)(92566002)(74316001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1354; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_CY1PR0601MB1355A0219D54FB93A0421236B73F0CY1PR0601MB1355_"
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2015 17:37:16.2715 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1354
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/5Cp3OROY2KqjxBFxfECBC5m6GSY>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 17:37:21 -0000

--_000_CY1PR0601MB1355A0219D54FB93A0421236B73F0CY1PR0601MB1355_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

With glitches in the figure fixed (sorry)

From: Clifford Kahn
Sent: Sunday, February 01, 2015 12:33 PM
To: 'sacm@ietf.org'
Subject: New version of the information model diagram

All,
I reference draft-ietf-sacm-information-model-00.

I would eliminate figure 1. It's redundant.

I would change
                "Figure 2 depicts an instance of the information model."
to
                "Figure 1 depicts the information model."

Here is a new version of the figure.  (View the figure using a fixed-width =
font, such as Courier.)

  +---------+ +---------+              +--------+____________________
  |Hardware | |Software |    __________|Location|*_______________    |
  |Component| |Component|   |         *+--------+*               |   |
  +---------+ +---------+   |                                    |   |
       |1          |1       |         +----------+               |   |
       |*          |*       |   ______|Credential|____________   |   |
  +---------+ +--------+    |  |     *+----------+*           |* |*  |
  |Hardware | |Software|    |  |         +---------+       +-------+ |
  |Instance | |Instance|    |  |         |Network  |_______|Account| |
  +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |
       |*      |*          *| *|         |- - - - -|                *|
       |       |____1+----------+1______*|Network  |__________+-------+
       |_____________| Endpoint |_____   |Interface|*     1..*|Address|
                    1|          |0..1 |  +---------+          +-------+
                     +----------+     |      1|
          _____________|1    |*       |       |_____+-------------+
         |                   |________|            *|Authorization|
         |                    part-of>              +-------------+
  .......|..............................................................
         |            |0..1
         |            |
         |            |*
         |         +-----+            +---------+___________________
         |         | AVP |____________|Endpoint |1..*   <based-on   |
        ^|         +-----+1..*       1|Attribute|________           |
hosted-by|           *|               |Assertion|*       |          |
         |            |               +---------+        |          |
         |            |produced-using   |*    |*         |         *|
         |           1|V                |     |__________|     +-------+
         |        +--------+            |       <based-on      |Summary|
         |        | Method |            |                      +-------+
         |        +--------+            |produced-by               *|
         |____________________          |V                          |
                              |*       1|                           |
    +--------+1____________*+-----------+                           |
    |        |    guides>   | SACM      |___________________________|
    |Guidance|              | Component |1       <produced-by
    +--------+*____________1+-----------+
               <produced-by

         -------------------------------------------------------------
         ..... Above this line is the monitorable world
         -------------------------------------------------------------

The figure has additions for provenance:

*         A class "Method"

*         The produced-using relationship between an AVP and  a Method

*         The produced-by relationship between a Guidance and a SACM Compon=
ent

*         The hosted-by relationship between a SACM Component and an Endpoi=
nt

The figure has other changes:

*         asserted-by and summarized-by have been renamed to produced-by.

*         "User" is now "Account". If a user has different credentials, SAC=
M cannot know that they belong to the same user. But, per Kim W, many organ=
izations do have accounts that associate credentials.

*         The multiplicity of the based-on relationships have been correcte=
d.

*         More relationships now have labels, per UML convention.

*         I got rid of the causal arrows, which had become redundant and we=
re nonstandard and clutter.

Still to come:

*         We are still discussing network sessions and network interfaces a=
nd how to model them. I left that part of the figure alone for now.

*         More provenance.

*         Should Level of Assurance be a class?

*         If an endpoint provides information about itself to an external a=
ttribute collector, which turns the information into SACM notation, how do =
we model the endpoint's and the collector's parts in the chain of custody?

*         Will a SACM controller ever add an AVP to an endpoint attribute a=
ssertion? If so, how will we model that?

*         Coverage. I know Kim is interested in capturing enough informatio=
n so that gaps in coverage can be found. (Is this in our requirements? It s=
hould be, I think.) She has suggested something like, each SACM component s=
hould publish a description of what it covers. The "guides" relationship mi=
ght look sufficient, but it isn't. If a piece of guidance says "Capture the=
 SWID tag inventory", a SACM component can heed that, but only for some end=
points.


Clifford Kahn
Principal Engineeer, Technical Lead


--_000_CY1PR0601MB1355A0219D54FB93A0421236B73F0CY1PR0601MB1355_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:51273718;
	mso-list-type:hybrid;
	mso-list-template-ids:-2062762052 67698689 67698689 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:638413199;
	mso-list-type:hybrid;
	mso-list-template-ids:978585464 67698689 -622056514 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1075981360;
	mso-list-type:hybrid;
	mso-list-template-ids:-919074748 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">With glitches in the f=
igure fixed (sorry)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Clifford Kahn <br>
<b>Sent:</b> Sunday, February 01, 2015 12:33 PM<br>
<b>To:</b> 'sacm@ietf.org'<br>
<b>Subject:</b> New version of the information model diagram<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">All,<o:p></o:p></p>
<p class=3D"MsoNormal">I reference draft-ietf-sacm-information-model-00. <o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would eliminate figure 1. It's redundant.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would change<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 2 depicts an instance =
of the information model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">to<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 1 depicts the informat=
ion model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is a new version of the figure. &nbsp;(View the=
 figure using a fixed-width font, such as Courier.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;--------&#43;_______=
_____________<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software |&nbsp;&nbsp;&nbsp; __________|Location|*_____=
__________&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Component| |Component|&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; *&#43;--------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; ___=
___|Credential|____________&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp; &nbsp;&nbsp;*&#43;----------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |* |*&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; &#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Instance | |Instance|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Network&nbsp; |_______|Account| |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Session&nbsp; |*&nbsp; 0..1=
&#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *| *|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |- - - - -|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *|<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|____1&#43;----------&#43;1______*|Network&nbsp; |__________&#43;-------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_____________| Endpoint |_____&nbsp;&=
nbsp; |Interface|*&nbsp;&nbsp;&nbsp;&nbsp; 1..*|Address|<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;1|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|0..1 |&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nb=
sp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; _____________|1&nbsp=
;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; |_____&#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|________|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; *|Authorization|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;part-of&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; .......|............................................................=
..<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;&nbsp;&nbsp;&#43;-----&#43;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;___________________<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;| AVP |____________|Endpoint |1..* &nbsp;&nbsp;&lt;=
based-on &nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;^| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&#43;-----&#43;1..* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
1|Attribute|________&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
hosted-by| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&n=
bsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;|Assertion|*&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&#43;---------&#43;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-using &nbsp;&nbsp;|* &nbsp;&n=
bsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;1|V&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;|_____=
_____| &nbsp;&nbsp;&nbsp;&nbsp;&#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;based-on&nbsp; &nbsp;&n=
bsp;&nbsp;&nbsp;|Summary|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;| Method | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#=
43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-by &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|____________________=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|V&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;|* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;1____________*&#43;-----------&#4=
3;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;=
&nbsp;&nbsp; guides&gt;&nbsp;&nbsp; | SACM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_=
_________________<span style=3D"color:#1F497D">_</span>________|<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|Guidance|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Component |1&nbsp;&nbsp; &nbsp;&nbs=
p;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;*____________1&#43;-----------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ..... Above this line is t=
he monitorable world<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has additions for provenance:<o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>A class &quot;Method&quot;<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The produced-using relationship between an A=
VP and&nbsp; a Method<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The produced-by relationship between a Guida=
nce and a SACM Component<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The hosted-by relationship between a SACM Co=
mponent and an Endpoint<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has other changes:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>asserted-by and summarized-by have been rena=
med to produced-by.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>&quot;User&quot; is now &quot;Account&quot;.=
 If a user has different credentials, SACM cannot know that they belong to =
the same user. But, per Kim W, many organizations do have accounts that ass=
ociate credentials.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The multiplicity of the based-on relationshi=
ps have been corrected.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>More relationships now have labels, per UML =
convention.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>I got rid of the causal arrows, which had be=
come redundant and were nonstandard and clutter.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Still to come:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>We are still discussing network sessions and=
 network interfaces and how to model them. I left that part of the figure a=
lone for now.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>More provenance. <o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo6">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Should Level of Assurance be a class? <o:p><=
/o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo6">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>If an endpoint provides information about it=
self to an external attribute collector, which turns the information into S=
ACM notation, how do we model the endpoint's and the collector's parts in t=
he chain of custody?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo6">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Will a SACM controller ever add an AVP to an=
 endpoint attribute assertion? If so, how will we model that?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Coverage. I know Kim is interested in captur=
ing enough information so that gaps in coverage can be found. (Is this in o=
ur requirements? It should be, I think.) She has suggested something like, =
each SACM component should publish
 a description of what it covers. The &quot;guides&quot; relationship might=
 look sufficient, but it isn't. If a piece of guidance says &quot;Capture t=
he SWID tag inventory&quot;, a SACM component can heed that, but only for s=
ome endpoints.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Clifford Kahn<o:p></o:p></p>
<p class=3D"MsoNormal">Principal Engineeer, Technical Lead<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CY1PR0601MB1355A0219D54FB93A0421236B73F0CY1PR0601MB1355_--


From nobody Sun Feb  1 11:43:00 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC761A9119 for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 11:42:58 -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, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 QEipW_gf7xpR for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 11:42:53 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0679.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::679]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65F4A1A9117 for <sacm@ietf.org>; Sun,  1 Feb 2015 11:42:53 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1353.namprd06.prod.outlook.com (25.161.212.11) with Microsoft SMTP Server (TLS) id 15.1.75.20; Sun, 1 Feb 2015 19:42:29 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Sun, 1 Feb 2015 19:42:29 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] New version of the information model diagram
Thread-Index: AdA+RMRU0inuW65EQle0W8iyZ0HKKwAAMNugAARrA0A=
Date: Sun, 1 Feb 2015 19:42:28 +0000
Message-ID: <CY1PR0601MB13554E530E3083462FD2EA67B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1353;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1353; 
x-forefront-prvs: 04740D25F1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(76576001)(87936001)(2656002)(62966003)(19580395003)(19580405001)(110136001)(2501002)(46102003)(107886001)(2351001)(16236675004)(99286002)(54206007)(86362001)(66066001)(54356999)(50986999)(76176999)(54606007)(92566002)(102836002)(15975445007)(2950100001)(2900100001)(19300405004)(450100001)(74316001)(77156002)(40100003)(33656002)(122556002)(19625215002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1353; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_CY1PR0601MB13554E530E3083462FD2EA67B73F0CY1PR0601MB1355_"
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Feb 2015 19:42:28.1978 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1353
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/HfSNhCKNbAPbO7fSFv04O4C7Dig>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 19:42:58 -0000

--_000_CY1PR0601MB13554E530E3083462FD2EA67B73F0CY1PR0601MB1355_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

A bug:

A summary can be based-on summaries. And a summary is produced-using a meth=
od.

Best,
                                                Cliff

From: Clifford Kahn [mailto:cliffordk@pulsesecure.net]
Sent: Sunday, February 01, 2015 12:37 PM
To: sacm@ietf.org
Subject: Re: [sacm] New version of the information model diagram

With glitches in the figure fixed (sorry)

From: Clifford Kahn
Sent: Sunday, February 01, 2015 12:33 PM
To: 'sacm@ietf.org'
Subject: New version of the information model diagram

All,
I reference draft-ietf-sacm-information-model-00.

I would eliminate figure 1. It's redundant.

I would change
                "Figure 2 depicts an instance of the information model."
to
                "Figure 1 depicts the information model."

Here is a new version of the figure.  (View the figure using a fixed-width =
font, such as Courier.)

  +---------+ +---------+              +--------+____________________
  |Hardware | |Software |    __________|Location|*_______________    |
  |Component| |Component|   |         *+--------+*               |   |
  +---------+ +---------+   |                                    |   |
       |1          |1       |         +----------+               |   |
       |*          |*       |   ______|Credential|____________   |   |
  +---------+ +--------+    |  |     *+----------+*           |* |*  |
  |Hardware | |Software|    |  |         +---------+       +-------+ |
  |Instance | |Instance|    |  |         |Network  |_______|Account| |
  +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |
       |*      |*          *| *|         |- - - - -|                *|
       |       |____1+----------+1______*|Network  |__________+-------+
       |_____________| Endpoint |_____   |Interface|*     1..*|Address|
                    1|          |0..1 |  +---------+          +-------+
                     +----------+     |      1|
          _____________|1    |*       |       |_____+-------------+
         |                   |________|            *|Authorization|
         |                    part-of>              +-------------+
  .......|..............................................................
         |            |0..1
         |            |
         |            |*
         |         +-----+            +---------+___________________
         |         | AVP |____________|Endpoint |1..*   <based-on   |
        ^|         +-----+1..*       1|Attribute|________           |
hosted-by|           *|               |Assertion|*       |          |
         |            |               +---------+        |          |
         |            |produced-using   |*    |*         |         *|
         |           1|V                |     |__________|     +-------+
         |        +--------+            |       <based-on      |Summary|
         |        | Method |            |                      +-------+
         |        +--------+            |produced-by               *|
         |____________________          |V                          |
                              |*       1|                           |
    +--------+1____________*+-----------+                           |
    |        |    guides>   | SACM      |___________________________|
    |Guidance|              | Component |1       <produced-by
    +--------+*____________1+-----------+
               <produced-by

         -------------------------------------------------------------
         ..... Above this line is the monitorable world
         -------------------------------------------------------------

The figure has additions for provenance:

*         A class "Method"

*         The produced-using relationship between an AVP and  a Method

*         The produced-by relationship between a Guidance and a SACM Compon=
ent

*         The hosted-by relationship between a SACM Component and an Endpoi=
nt

The figure has other changes:

*         asserted-by and summarized-by have been renamed to produced-by.

*         "User" is now "Account". If a user has different credentials, SAC=
M cannot know that they belong to the same user. But, per Kim W, many organ=
izations do have accounts that associate credentials.

*         The multiplicity of the based-on relationships have been correcte=
d.

*         More relationships now have labels, per UML convention.

*         I got rid of the causal arrows, which had become redundant and we=
re nonstandard and clutter.

Still to come:

*         We are still discussing network sessions and network interfaces a=
nd how to model them. I left that part of the figure alone for now.

*         More provenance.

*         Should Level of Assurance be a class?

*         If an endpoint provides information about itself to an external a=
ttribute collector, which turns the information into SACM notation, how do =
we model the endpoint's and the collector's parts in the chain of custody?

*         Will a SACM controller ever add an AVP to an endpoint attribute a=
ssertion? If so, how will we model that?

*         Coverage. I know Kim is interested in capturing enough informatio=
n so that gaps in coverage can be found. (Is this in our requirements? It s=
hould be, I think.) She has suggested something like, each SACM component s=
hould publish a description of what it covers. The "guides" relationship mi=
ght look sufficient, but it isn't. If a piece of guidance says "Capture the=
 SWID tag inventory", a SACM component can heed that, but only for some end=
points.


Clifford Kahn
Principal Engineeer, Technical Lead


--_000_CY1PR0601MB13554E530E3083462FD2EA67B73F0CY1PR0601MB1355_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:51273718;
	mso-list-type:hybrid;
	mso-list-template-ids:-2062762052 67698689 67698689 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:497188676;
	mso-list-type:hybrid;
	mso-list-template-ids:907974292 67698689 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:38.7pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:74.7pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:110.7pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:146.7pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:182.7pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:218.7pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:254.7pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:290.7pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:326.7pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:638413199;
	mso-list-type:hybrid;
	mso-list-template-ids:978585464 67698689 -622056514 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level2
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3
	{mso-list-id:1075981360;
	mso-list-type:hybrid;
	mso-list-template-ids:-919074748 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">A bug:<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">A summary can be based=
-on summaries. And a summary is produced-using a method.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cliff<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Clifford Kahn [mailto:cliffordk@pulsese=
cure.net]
<br>
<b>Sent:</b> Sunday, February 01, 2015 12:37 PM<br>
<b>To:</b> sacm@ietf.org<br>
<b>Subject:</b> Re: [sacm] New version of the information model diagram<o:p=
></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">With glitches in the f=
igure fixed (sorry)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Clifford Kahn <br>
<b>Sent:</b> Sunday, February 01, 2015 12:33 PM<br>
<b>To:</b> 'sacm@ietf.org'<br>
<b>Subject:</b> New version of the information model diagram<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">All,<o:p></o:p></p>
<p class=3D"MsoNormal">I reference draft-ietf-sacm-information-model-00. <o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would eliminate figure 1. It's redundant.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would change<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 2 depicts an instance =
of the information model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">to<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 1 depicts the informat=
ion model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is a new version of the figure. &nbsp;(View the=
 figure using a fixed-width font, such as Courier.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;--------&#43;_______=
_____________<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software |&nbsp;&nbsp;&nbsp; __________|Location|*_____=
__________&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Component| |Component|&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; *&#43;--------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; ___=
___|Credential|____________&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp; &nbsp;&nbsp;*&#43;----------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |* |*&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; &#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Instance | |Instance|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Network&nbsp; |_______|Account| |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Session&nbsp; |*&nbsp; 0..1=
&#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *| *|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |- - - - -|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *|<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|____1&#43;----------&#43;1______*|Network&nbsp; |__________&#43;-------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_____________| Endpoint |_____&nbsp;&=
nbsp; |Interface|*&nbsp;&nbsp;&nbsp;&nbsp; 1..*|Address|<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;1|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|0..1 |&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nb=
sp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; _____________|1&nbsp=
;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; |_____&#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|________|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; *|Authorization|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;part-of&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; .......|............................................................=
..<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;&nbsp;&nbsp;&#43;-----&#43;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;___________________<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;| AVP |____________|Endpoint |1..* &nbsp;&nbsp;&lt;=
based-on &nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;^| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&#43;-----&#43;1..* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
1|Attribute|________&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
hosted-by| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&n=
bsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;|Assertion|*&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&#43;---------&#43;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-using &nbsp;&nbsp;|* &nbsp;&n=
bsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;1|V&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;|_____=
_____| &nbsp;&nbsp;&nbsp;&nbsp;&#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;based-on&nbsp; &nbsp;&n=
bsp;&nbsp;&nbsp;|Summary|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;| Method | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#=
43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-by &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|____________________=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|V&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;|* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;1____________*&#43;-----------&#4=
3;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;=
&nbsp;&nbsp; guides&gt;&nbsp;&nbsp; | SACM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_=
_________________<span style=3D"color:#1F497D">_</span>________|<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|Guidance|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Component |1&nbsp;&nbsp; &nbsp;&nbs=
p;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;*____________1&#43;-----------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ..... Above this line is t=
he monitorable world<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has additions for provenance:<o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>A class &quot;Method&quot;<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The produced-using relationship between an A=
VP and&nbsp; a Method<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The produced-by relationship between a Guida=
nce and a SACM Component<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The hosted-by relationship between a SACM Co=
mponent and an Endpoint<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has other changes:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>asserted-by and summarized-by have been rena=
med to produced-by.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>&quot;User&quot; is now &quot;Account&quot;.=
 If a user has different credentials, SACM cannot know that they belong to =
the same user. But, per Kim W, many organizations do have accounts that ass=
ociate credentials.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The multiplicity of the based-on relationshi=
ps have been corrected.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>More relationships now have labels, per UML =
convention.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo4"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>I got rid of the causal arrows, which had be=
come redundant and were nonstandard and clutter.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Still to come:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>We are still discussing network sessions and=
 network interfaces and how to model them. I left that part of the figure a=
lone for now.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>More provenance. <o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo6">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Should Level of Assurance be a class? <o:p><=
/o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo6">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>If an endpoint provides information about it=
self to an external attribute collector, which turns the information into S=
ACM notation, how do we model the endpoint's and the collector's parts in t=
he chain of custody?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo6">
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Will a SACM controller ever add an AVP to an=
 endpoint attribute assertion? If so, how will we model that?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo6"><![if !supportLists]><span style=3D"font-family:Symbol"><span style=
=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roma=
n&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Coverage. I know Kim is interested in captur=
ing enough information so that gaps in coverage can be found. (Is this in o=
ur requirements? It should be, I think.) She has suggested something like, =
each SACM component should publish
 a description of what it covers. The &quot;guides&quot; relationship might=
 look sufficient, but it isn't. If a piece of guidance says &quot;Capture t=
he SWID tag inventory&quot;, a SACM component can heed that, but only for s=
ome endpoints.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Clifford Kahn<o:p></o:p></p>
<p class=3D"MsoNormal">Principal Engineeer, Technical Lead<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CY1PR0601MB13554E530E3083462FD2EA67B73F0CY1PR0601MB1355_--


From nobody Sun Feb  1 12:45:58 2015
Return-Path: <blueroofmusic@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0E9B1A8A5F for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 12:45:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 5d-skCUXz5wF for <sacm@ietfa.amsl.com>; Sun,  1 Feb 2015 12:45:53 -0800 (PST)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A8B21A1B0E for <sacm@ietf.org>; Sun,  1 Feb 2015 12:45:53 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id w55so30298019wes.1 for <sacm@ietf.org>; Sun, 01 Feb 2015 12:45:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ko7sRL4Nwbw6MBp10nEUBIvkCs4RqQ7jibu8Fggtp3M=; b=0CwMPqxvkt6/pgcHFXGT6VHSLfJo2nsqVPgIa7npH+65C6QX/A3pDj7+RSEH6/VI+p 5nF4b1g/PhTRzfa7IGtAMXyi/3TLZMZ600maQdkhClV/2FjdTMBZWJgSiyObJFzktztN Af7MbY73l725+1FEqj/2eg0fqLHCprJ4444uhcKYfmtqPsjAPGfowH7eenQP1i3SNlJC 4ii1S1NE1w4GOgg+s1s6XTV71GWdnpd9VqCZVp06KXQj89r2UbS31G7OZUQIlpz5loI0 DnyMmo/Wocir9F2YBnpyos3gHuzMjAZuhushfeDXb6QkS1Kd70l7k/G0EfqByc0HSZeJ Rnrw==
X-Received: by 10.194.108.162 with SMTP id hl2mr35069399wjb.134.1422823552029;  Sun, 01 Feb 2015 12:45:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.32.77 with HTTP; Sun, 1 Feb 2015 12:45:31 -0800 (PST)
In-Reply-To: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
From: Ira McDonald <blueroofmusic@gmail.com>
Date: Sun, 1 Feb 2015 15:45:31 -0500
Message-ID: <CAN40gSvxzgb8F6GTZJBw2YroxEensjAdtB3-ve-DYbbnVFhiSA@mail.gmail.com>
To: Clifford Kahn <cliffordk@pulsesecure.net>, Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/alternative; boundary=089e0102f2126599fe050e0cecea
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/CdTgbGXHzSyCE1sgN6T4fkrNOzY>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Feb 2015 20:45:57 -0000

--089e0102f2126599fe050e0cecea
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Cliff,

Your first note had a fairly complete diagram with fixed-width font.

Your second note had an incomplete garbage diagram.

Perhaps a simple plaintext attachment would help?

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434


On Sun, Feb 1, 2015 at 12:37 PM, Clifford Kahn <cliffordk@pulsesecure.net>
wrote:

>  With glitches in the figure fixed (sorry)
>
>
>
> *From:* Clifford Kahn
> *Sent:* Sunday, February 01, 2015 12:33 PM
> *To:* 'sacm@ietf.org'
> *Subject:* New version of the information model diagram
>
>
>
> All,
>
> I reference draft-ietf-sacm-information-model-00.
>
>
>
> I would eliminate figure 1. It's redundant.
>
>
>
> I would change
>
>                 =E2=80=9CFigure 2 depicts an instance of the information =
model.=E2=80=9D
>
> to
>
>                 =E2=80=9CFigure 1 depicts the information model.=E2=80=9D
>
>
>
> Here is a new version of the figure.  (View the figure using a fixed-widt=
h
> font, such as Courier.)
>
>
>
>   +---------+ +---------+              +--------+____________________
>
>   |Hardware | |Software |    __________|Location|*_______________    |
>
>   |Component| |Component|   |         *+--------+*               |   |
>
>   +---------+ +---------+   |                                    |   |
>
>        |1          |1       |         +----------+               |   |
>
>        |*          |*       |   ______|Credential|____________   |   |
>
>   +---------+ +--------+    |  |     *+----------+*           |* |*  |
>
>   |Hardware | |Software|    |  |         +---------+       +-------+ |
>
>   |Instance | |Instance|    |  |         |Network  |_______|Account| |
>
>   +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |
>
>        |*      |*          *| *|         |- - - - -|                *|
>
>        |       |____1+----------+1______*|Network  |__________+-------+
>
>        |_____________| Endpoint |_____   |Interface|*     1..*|Address|
>
>                     1|          |0..1 |  +---------+          +-------+
>
>                      +----------+     |      1|
>
>           _____________|1    |*       |       |_____+-------------+
>
>          |                   |________|            *|Authorization|
>
>          |                    part-of>              +-------------+
>
>   .......|..............................................................
>
>          |            |0..1
>
>          |            |
>
>          |            |*
>
>          |         +-----+            +---------+___________________
>
>          |         | AVP |____________|Endpoint |1..*   <based-on   |
>
>         ^|         +-----+1..*       1|Attribute|________           |
>
> hosted-by|           *|               |Assertion|*       |          |
>
>          |            |               +---------+        |          |
>
>          |            |produced-using   |*    |*         |         *|
>
>          |           1|V                |     |__________|     +-------+
>
>          |        +--------+            |       <based-on      |Summary|
>
>          |        | Method |            |                      +-------+
>
>          |        +--------+            |produced-by
>               *|
>
>          |____________________          |V                          |
>
>                               |*       1|                           |
>
>     +--------+1____________*+-----------+                           |
>
>     |        |    guides>   | SACM      |___________________________|
>
>     |Guidance|              | Component |1       <produced-by
>
>     +--------+*____________1+-----------+
>
>                <produced-by
>
>
>
>          -------------------------------------------------------------
>
>          ..... Above this line is the monitorable world
>
>          -------------------------------------------------------------
>
>
>
> The figure has additions for provenance:
>
> =C2=B7         A class "Method"
>
> =C2=B7         The produced-using relationship between an AVP and  a Meth=
od
>
> =C2=B7         The produced-by relationship between a Guidance and a SACM
> Component
>
> =C2=B7         The hosted-by relationship between a SACM Component and an
> Endpoint
>
>
>
> The figure has other changes:
>
> =C2=B7         asserted-by and summarized-by have been renamed to produce=
d-by.
>
> =C2=B7         "User" is now "Account". If a user has different credentia=
ls,
> SACM cannot know that they belong to the same user. But, per Kim W, many
> organizations do have accounts that associate credentials.
>
> =C2=B7         The multiplicity of the based-on relationships have been
> corrected.
>
> =C2=B7         More relationships now have labels, per UML convention.
>
> =C2=B7         I got rid of the causal arrows, which had become redundant=
 and
> were nonstandard and clutter.
>
>
>
> Still to come:
>
> =C2=B7         We are still discussing network sessions and network inter=
faces
> and how to model them. I left that part of the figure alone for now.
>
> =C2=B7         More provenance.
>
> =C2=B7         Should Level of Assurance be a class?
>
> =C2=B7         If an endpoint provides information about itself to an ext=
ernal
> attribute collector, which turns the information into SACM notation, how =
do
> we model the endpoint's and the collector's parts in the chain of custody=
?
>
> =C2=B7         Will a SACM controller ever add an AVP to an endpoint attr=
ibute
> assertion? If so, how will we model that?
>
> =C2=B7         Coverage. I know Kim is interested in capturing enough
> information so that gaps in coverage can be found. (Is this in our
> requirements? It should be, I think.) She has suggested something like,
> each SACM component should publish a description of what it covers. The
> "guides" relationship might look sufficient, but it isn't. If a piece of
> guidance says "Capture the SWID tag inventory", a SACM component can heed
> that, but only for some endpoints.
>
>
>
>
>
> Clifford Kahn
>
> Principal Engineeer, Technical Lead
>
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>
>

--089e0102f2126599fe050e0cecea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Cliff,<br><br>Your first note had a fairly complete diagram with fixed-w=
idth font.<br><br>Your second note had an incomplete garbage diagram.<br><b=
r>Perhaps a simple plaintext attachment would help?<br><br>Cheers,<br>- Ira=
<br><br clear=3D"all"><div><div class=3D"gmail_signature"><div dir=3D"ltr">=
Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobi=
lity Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary=
 - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Pri=
nting Protocol WG<br>IETF Designated Expert - IPP &amp; Printer MIB<br>Blue=
 Roof Music / High North Inc<br><a style=3D"color:rgb(51,51,255)" href=3D"h=
ttp://sites.google.com/site/blueroofmusic" target=3D"_blank">http://sites.g=
oogle.com/site/blueroofmusic</a><br><a style=3D"color:rgb(102,0,204)" href=
=3D"http://sites.google.com/site/highnorthinc" target=3D"_blank">http://sit=
es.google.com/site/highnorthinc</a><br>mailto: <a href=3D"mailto:blueroofmu=
sic@gmail.com" target=3D"_blank">blueroofmusic@gmail.com</a><br>Winter=C2=
=A0 579 Park Place=C2=A0 Saline, MI=C2=A0 48176=C2=A0 734-944-0094<br>Summe=
r=C2=A0 PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434<br><br><=
div style=3D"display:inline"></div><div style=3D"display:inline"></div><div=
 style=3D"display:inline"></div><div></div><div></div><div></div><div></div=
></div></div></div>
<br><div class=3D"gmail_quote">On Sun, Feb 1, 2015 at 12:37 PM, Clifford Ka=
hn <span dir=3D"ltr">&lt;<a href=3D"mailto:cliffordk@pulsesecure.net" targe=
t=3D"_blank">cliffordk@pulsesecure.net</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">





<div link=3D"#0563C1" vlink=3D"#954F72" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">With glitches in the f=
igure fixed (sorry)<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Clifford Kahn <br>
<b>Sent:</b> Sunday, February 01, 2015 12:33 PM<br>
<b>To:</b> &#39;<a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@iet=
f.org</a>&#39;<br>
<b>Subject:</b> New version of the information model diagram<u></u><u></u><=
/p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">All,<u></u><u></u></p>
<p class=3D"MsoNormal">I reference draft-ietf-sacm-information-model-00. <u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I would eliminate figure 1. It&#39;s redundant.<u></=
u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I would change<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =E2=80=9CFigure 2 depicts an instan=
ce of the information model.=E2=80=9D<u></u><u></u></p>
<p class=3D"MsoNormal">to<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =E2=80=9CFigure 1 depicts the infor=
mation model.=E2=80=9D<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Here is a new version of the figure. =C2=A0(View the=
 figure using a fixed-width font, such as Courier.)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 +---------+ +---------+=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +--------+____________________<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 |Hardware | |Software |=C2=A0=C2=A0=C2=A0 __________|Location|*_____=
__________=C2=A0=C2=A0=C2=A0 |<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 |Component| |Component|=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 *+--------+*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0 |<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 +---------+ +---------+=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0 |<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 |1=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0+----------+=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0 |<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 |*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0 ___=
___|Credential|____________=C2=A0=C2=A0 |=C2=A0=C2=A0 |<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 +---------+ +--------+=C2=A0=C2=A0=C2=A0 |=C2=A0 |=C2=A0=C2=A0 =C2=
=A0=C2=A0*+----------+*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 |* |*=C2=A0 |<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 |Hardware | |Software|=C2=A0=C2=A0=C2=A0 |=C2=A0 |=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +---------+=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 +-------+ |<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 |Instance | |Instance|=C2=A0=C2=A0=C2=A0 |=C2=A0 |=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |Network=C2=A0 |_______|Account| |<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 +---------+ +--------+=C2=A0=C2=A0=C2=A0 |=C2=A0 |=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |Session=C2=A0 |*=C2=A0 0..1+-------+ |<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |*=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 *| *|=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |- - - - -|=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 *|<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
|____1+----------+1______*|Network=C2=A0 |__________+-------+<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |_____________| Endpoint |_____=C2=A0=
=C2=A0 |Interface|*=C2=A0=C2=A0=C2=A0=C2=A0 1..*|Address|<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A01|=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0|0..1 |=C2=A0 +---------+=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-------+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0+----------+=C2=A0=C2=A0=C2=
=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 _____________|1=C2=
=A0=C2=A0=C2=A0 |*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 |_____+-------------+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0|________|=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 *|Authorization|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0|=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0part-of&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-------------+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 .......|............................................................=
..<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0 =C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|0..1=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0 =C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|*=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0=C2=A0=
=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0+-----+=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0+---------+___________________<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0<span style=3D"color:#1f497d">
</span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0 =C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0| AVP |____________|Endpoint |1..* =C2=A0=C2=A0&lt;=
based-on =C2=A0=C2=A0|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0^| =C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0+-----+1..* =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A01|Attr=
ibute|________=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
hosted-by| =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0*|=
=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0|Assertion|*=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0| =C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0 =C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0+---------+=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0<span style=3D"color:#1f497d">
</span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|produced-using =C2=A0=C2=A0|* =C2=A0=
=C2=A0=C2=A0|*=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | =C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0*|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0<span style=3D"color:#1f497d">
</span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A01|V=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0| =C2=A0=C2=A0=C2=A0=C2=A0|___=
_______| =C2=A0=C2=A0=C2=A0=C2=A0+-------+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0<span style=3D"color:#1f497d">
</span>=C2=A0=C2=A0=C2=A0=C2=A0| =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
+--------+ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0|=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0&lt;based-on=C2=A0 =C2=A0=C2=A0=C2=
=A0=C2=A0|Summary|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0| =C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0| Method | =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
+-------+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0|=C2=A0 =C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0+--------+ =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0|produced-by =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0*|=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|____________________=
=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|V=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0|* =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A01|=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0+--------+1____________*+-----------+=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0<span style=3D"color:#1f497d">
</span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|<u></u><u></u=
></span></p>
</div></div><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier=
 New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0|=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 |=C2=A0=C2=A0=C2=A0 guides&gt;=C2=A0=C2=A0 | SACM=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 |__________________<span style=3D"color:#1f497d">_</span>_____=
___|<u></u><u></u></span></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0|Guidance|=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | Component |1=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0&lt;produced-by<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0+--------+*____________1+-----------+<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0&lt;produced-by<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 --------------------------=
-----------------------------------<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ..... Above this line is t=
he monitorable world<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 --------------------------=
-----------------------------------<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The figure has additions for provenance:<u></u><u></=
u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>A class &quot;Method&quot;<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>The produced-using relationship between an AVP =
and=C2=A0 a Method<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>The produced-by relationship between a Guidance=
 and a SACM Component<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>The hosted-by relationship between a SACM Compo=
nent and an Endpoint<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The figure has other changes:<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>asserted-by and summarized-by have been renamed=
 to produced-by.<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>&quot;User&quot; is now &quot;Account&quot;. If=
 a user has different credentials, SACM cannot know that they belong to the=
 same user. But, per Kim W, many organizations do have accounts that associ=
ate credentials.
<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>The multiplicity of the based-on relationships =
have been corrected.
<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>More relationships now have labels, per UML con=
vention.
<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>I got rid of the causal arrows, which had becom=
e redundant and were nonstandard and clutter.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Still to come:<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>We are still discussing network sessions and ne=
twork interfaces and how to model them. I left that part of the figure alon=
e for now.<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>More provenance. <u></u><u></u></p>
<p style=3D"margin-left:1.0in">
<u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0
</span></span></span><u></u>Should Level of Assurance be a class? <u></u><u=
></u></p>
<p style=3D"margin-left:1.0in">
<u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0
</span></span></span><u></u>If an endpoint provides information about itsel=
f to an external attribute collector, which turns the information into SACM=
 notation, how do we model the endpoint&#39;s and the collector&#39;s parts=
 in the chain of custody?
<u></u><u></u></p>
<p style=3D"margin-left:1.0in">
<u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0
</span></span></span><u></u>Will a SACM controller ever add an AVP to an en=
dpoint attribute assertion? If so, how will we model that?
<u></u><u></u></p>
<p><u></u><span style=3D"font-family:Symbol"><span>=C2=B7<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0
</span></span></span><u></u>Coverage. I know Kim is interested in capturing=
 enough information so that gaps in coverage can be found. (Is this in our =
requirements? It should be, I think.) She has suggested something like, eac=
h SACM component should publish
 a description of what it covers. The &quot;guides&quot; relationship might=
 look sufficient, but it isn&#39;t. If a piece of guidance says &quot;Captu=
re the SWID tag inventory&quot;, a SACM component can heed that, but only f=
or some endpoints.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Clifford Kahn<u></u><u></u></p>
<p class=3D"MsoNormal">Principal Engineeer, Technical Lead<u></u><u></u></p=
>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div></div></div>
</div>

<br>_______________________________________________<br>
sacm mailing list<br>
<a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/sacm</a><br>
<br></blockquote></div><br>

--089e0102f2126599fe050e0cecea--


From nobody Mon Feb  2 02:18:20 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0111A00B2 for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 02:18:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.51
X-Spam-Level: 
X-Spam-Status: No, score=-5.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ibnORe7zbxZD for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 02:18:13 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990071A0092 for <sacm@ietf.org>; Mon,  2 Feb 2015 02:18:13 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmgFALRNz1SHCzIm/2dsb2JhbABbgmQiUlkEsiAGkj6FcQKBF0MBAQEBAQF8hAwBAQEBAxIoNBcEAgEIDQQEAQELFAkHMhQJCAIEARIIGogLAQyzLqAYAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSGBIlDOAaDEIETBY8Jg06MKowJIoNub4FEfgEBAQ
X-IronPort-AV: E=Sophos;i="5.09,505,1418101200"; d="scan'208";a="102261804"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Feb 2015 05:18:12 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 02 Feb 2015 05:18:12 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Mon, 2 Feb 2015 11:18:10 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jerome Athias <athiasjerome@gmail.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] ETSI Machine-to-Machine communications (M2M)
Thread-Index: AQHQPgRL0OzixmXJYEOJzXTNCcOxrZzdJtMQ
Date: Mon, 2 Feb 2015 10:18:10 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C97DDF1@AZ-FFEXMB04.global.avaya.com>
References: <CAA=AuEeUOkBQOMZPoxdQ3NuEr_Qe8GsGxe38uUQ7ajjrg8xaRw@mail.gmail.com>
In-Reply-To: <CAA=AuEeUOkBQOMZPoxdQ3NuEr_Qe8GsGxe38uUQ7ajjrg8xaRw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/vyz-bOJW4vL7V7k3VVLTOBL6bb4>
Subject: Re: [sacm] ETSI Machine-to-Machine communications (M2M)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 10:18:18 -0000

Hi Jerome,

Can you shortly explain how this ETSI document is significant for SACM?=20

Thanks and Regards,

Dan


> -----Original Message-----
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Jerome Athias
> Sent: Sunday, February 01, 2015 11:49 AM
> To: sacm@ietf.org
> Subject: [sacm] ETSI Machine-to-Machine communications (M2M)
>=20
> Hi,
>=20
> for information, ETSI (European Telecommunications Standards
> Institute) released a Technical Specification for Machine-to-Machine
> communications (M2M); Interoperability Test Specification
>=20
> Ref: ETSI TS 103 315 V1.1.1 (2015-01)
> https://urldefense.proofpoint.com/v2/url?u=3Dhttp-
> 3A__www.etsi.org_deliver_etsi-5Fts_103300-5F103399_103315_01.01.01-
> 5F60_ts-
> 5F103315v010101p.pdf&d=3DAwICAg&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGx
> R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DjtYVHqXpV3lDUHonGsit5-
> cqB2WMJNnkHAMrmioym-Q&s=3DbgMgjNPQU3s_G-
> QVupzTBN3hAatyRKcJ6Tlbusq0TUA&e=3D
>=20
> Best regards
>=20
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-
> 3A__www.ietf.org_mailman_listinfo_sacm&d=3DAwICAg&c=3DBFpWQw8bsuKpl
> 1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DjtYVHq
> XpV3lDUHonGsit5-cqB2WMJNnkHAMrmioym-
> Q&s=3DOY8WxyApL98Uf1lgyTPbCCd_oER3UX6e5ElnPsPsn6U&e=3D


From nobody Mon Feb  2 03:01:21 2015
Return-Path: <athiasjerome@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D773F1A00CA for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 03:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 wA8CCpS1TrAZ for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 03:01:16 -0800 (PST)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 660ED1A00A9 for <sacm@ietf.org>; Mon,  2 Feb 2015 03:01:16 -0800 (PST)
Received: by mail-la0-f50.google.com with SMTP id hs14so39333196lab.9 for <sacm@ietf.org>; Mon, 02 Feb 2015 03:01:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gkNbWNTwZZvKNOW+p7FiWHfqRvD/GbfG1uZmOz1lnMM=; b=iJxCdAYHVsA+qB8AqF7v4DB0OyBkKKBIayZiX1Xf1s4CKGwgpgFAJ1H7pLUZMfppo4 YKFQ5t4DLxGpoR1vHDlbqUcEYmtp8r9MSQXCi1+DNm2YfGPhsQFlNs/khyuPUDHg+AUy JOjZNw54+ppskH/qxIAOCHoHDMjnuECR4Gfcdnz4Dmwui6tp9gm2yFkehU4wFDJpMggf pMRfJ/gprKw7SThFwjiQFGPP83gTKyKlA9uH9FLuuFeUsfapG0ZIF6au4wEi4d43X++U wbs5aoBRKZo6r6d7GSUdhmlMofJx2rqp0Vik1zA2NSvLebd9Kh18ZiqTpt4ww8ZZ8SEn j/+Q==
MIME-Version: 1.0
X-Received: by 10.112.220.36 with SMTP id pt4mr18252096lbc.15.1422874874669; Mon, 02 Feb 2015 03:01:14 -0800 (PST)
Received: by 10.25.209.5 with HTTP; Mon, 2 Feb 2015 03:01:14 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C97DDF1@AZ-FFEXMB04.global.avaya.com>
References: <CAA=AuEeUOkBQOMZPoxdQ3NuEr_Qe8GsGxe38uUQ7ajjrg8xaRw@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97DDF1@AZ-FFEXMB04.global.avaya.com>
Date: Mon, 2 Feb 2015 12:01:14 +0100
Message-ID: <CAA=AuEd7X7bdBgkNMejQxkPnyjf-COQOkeUxz4k-3dvvZr6RYQ@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/t-bv8Z3O7lwrbblyhuIIqjfdaoQ>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] ETSI Machine-to-Machine communications (M2M)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 11:01:19 -0000

Hi,

ETSI is the European Telecommunications Standards Institute,
officially responsible for standardization of Information and
Communication Technologies (ICT) within Europe.
ETSI SmartM2M (for machine-to-machine communications) group is a
technical group. Even is ETSI background is mainly 3GPP (mobile domain
[1]), I think SACM could benefit from ETSI work regarding:

Functional architecture for Machine-to-Machine communications (M2M)
ETSI TS 102 690 V1.1.1 (2011-10)
http://www.etsi.org/deliver/etsi_ts/102600_102699/102690/01.01.01_60/ts_102690v010101p.pdf

Identifiers

Subscription and Access Right mechanisms

Modelling and relationships

Procedures

Gateway/Broker architecture



Hope it makes sense
Best regards

[1] http://technical.openmobilealliance.org/Technical/release_program/docs/XDM/V2_0-20090810-C/OMA-TS-XDM_Core-V2_0-20090810-C.pdf

2015-02-02 11:18 GMT+01:00 Romascanu, Dan (Dan) <dromasca@avaya.com>:
> Hi Jerome,
>
> Can you shortly explain how this ETSI document is significant for SACM?
>
> Thanks and Regards,
>
> Dan
>
>
>> -----Original Message-----
>> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Jerome Athias
>> Sent: Sunday, February 01, 2015 11:49 AM
>> To: sacm@ietf.org
>> Subject: [sacm] ETSI Machine-to-Machine communications (M2M)
>>
>> Hi,
>>
>> for information, ETSI (European Telecommunications Standards
>> Institute) released a Technical Specification for Machine-to-Machine
>> communications (M2M); Interoperability Test Specification
>>
>> Ref: ETSI TS 103 315 V1.1.1 (2015-01)
>> https://urldefense.proofpoint.com/v2/url?u=http-
>> 3A__www.etsi.org_deliver_etsi-5Fts_103300-5F103399_103315_01.01.01-
>> 5F60_ts-
>> 5F103315v010101p.pdf&d=AwICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGx
>> R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=jtYVHqXpV3lDUHonGsit5-
>> cqB2WMJNnkHAMrmioym-Q&s=bgMgjNPQU3s_G-
>> QVupzTBN3hAatyRKcJ6Tlbusq0TUA&e=
>>
>> Best regards
>>
>> _______________________________________________
>> sacm mailing list
>> sacm@ietf.org
>> https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__www.ietf.org_mailman_listinfo_sacm&d=AwICAg&c=BFpWQw8bsuKpl
>> 1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=jtYVHq
>> XpV3lDUHonGsit5-cqB2WMJNnkHAMrmioym-
>> Q&s=OY8WxyApL98Uf1lgyTPbCCd_oER3UX6e5ElnPsPsn6U&e=
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm


From nobody Mon Feb  2 05:08:08 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87C61A039F for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 05:08:06 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 MzVdR9oXMdkp for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 05:08:05 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0073.outbound.protection.outlook.com [207.46.100.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFBD81A039A for <sacm@ietf.org>; Mon,  2 Feb 2015 05:08:04 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1353.namprd06.prod.outlook.com (25.161.212.11) with Microsoft SMTP Server (TLS) id 15.1.75.20; Mon, 2 Feb 2015 13:08:03 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Mon, 2 Feb 2015 13:08:03 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: Ira McDonald <blueroofmusic@gmail.com>
Thread-Topic: [sacm] New version of the information model diagram
Thread-Index: AdA+RMRU0inuW65EQle0W8iyZ0HKKwAAMNugAAafO4AAIlAdoA==
Date: Mon, 2 Feb 2015 13:08:02 +0000
Message-ID: <CY1PR0601MB135591C277AB97FC585B5BB6B73C0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com> <CAN40gSvxzgb8F6GTZJBw2YroxEensjAdtB3-ve-DYbbnVFhiSA@mail.gmail.com>
In-Reply-To: <CAN40gSvxzgb8F6GTZJBw2YroxEensjAdtB3-ve-DYbbnVFhiSA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1353;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1353; 
x-forefront-prvs: 0475418F50
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(164054003)(19609705001)(2656002)(62966003)(54206007)(19580395003)(110136001)(46102003)(87936001)(76576001)(66066001)(99286002)(86362001)(16236675004)(1411001)(54356999)(50986999)(76176999)(54606007)(99936001)(92566002)(102836002)(15975445007)(2950100001)(2900100001)(558084003)(19300405004)(77156002)(74316001)(40100003)(122556002)(19625215002)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1353; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/mixed; boundary="_004_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_"
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Feb 2015 13:08:02.6951 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1353
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/EoXU8oy5LzPuOIeogIXJx5qpodU>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 13:08:07 -0000

--_004_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_
Content-Type: multipart/alternative;
	boundary="_000_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_"

--_000_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhhbmtzLCBJcmEuIFNvcnJ5IGZvciB0aGUgcHJvYmxlbXMhIEhlcmUgaXMgdGhlIGRpYWdyYW0g
YXMgYW4gYXR0YWNobWVudC4NCg0KSSBzbmVha2VkIGluIG9uZSBjb3JyZWN0aW9uIHRvIG11bHRp
cGxpY2l0eS4NCg0KQmVzdCwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIENsaWZmDQo=

--_000_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0K
CW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4u
RW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1
bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0K
CW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhhbmtzLCBJcmEu
IFNvcnJ5IGZvciB0aGUgcHJvYmxlbXMhIEhlcmUgaXMgdGhlIGRpYWdyYW0gYXMgYW4gYXR0YWNo
bWVudC4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SSBzbmVh
a2VkIGluIG9uZSBjb3JyZWN0aW9uIHRvIG11bHRpcGxpY2l0eS4NCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+QmVzdCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IENsaWZmPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_--

--_004_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_
Content-Type: text/plain; name="info-model-diagram-2015-02-02.txt"
Content-Description: info-model-diagram-2015-02-02.txt
Content-Disposition: attachment;
	filename="info-model-diagram-2015-02-02.txt"; size=2810;
	creation-date="Sat, 31 Jan 2015 22:20:38 GMT";
	modification-date="Mon, 02 Feb 2015 13:00:36 GMT"
Content-Transfer-Encoding: base64

ICArLS0tLS0tLS0tKyArLS0tLS0tLS0tKyAgICAgICAgICAgICAgKy0tLS0tLS0tK19fX19fX19f
X19fX19fX19fX19fDQogIHxIYXJkd2FyZSB8IHxTb2Z0d2FyZSB8ICAgIF9fX19fX19fX198TG9j
YXRpb258Kl9fX19fX19fX19fX19fXyAgICB8DQogIHxDb21wb25lbnR8IHxDb21wb25lbnR8ICAg
fCAgICAgICAgICorLS0tLS0tLS0rKiAgICAgICAgICAgICAgIHwgICB8DQogICstLS0tLS0tLS0r
ICstLS0tLS0tLS0rICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICB8
DQogICAgICAgfDEgICAgICAgICAgfDEgICAgICAgfCAgICAgICAgICstLS0tLS0tLS0tKyAgICAg
ICAgICAgICAgIHwgICB8DQogICAgICAgfCogICAgICAgICAgfCogICAgICAgfCAgIF9fX19fX3xD
cmVkZW50aWFsfF9fX19fX19fX19fXyAgIHwgICB8DQogICstLS0tLS0tLS0rICstLS0tLS0tLSsg
ICAgfCAgfCAgICAgKistLS0tLS0tLS0tKyogICAgICAgICAgIHwqIHwqICB8DQogIHxIYXJkd2Fy
ZSB8IHxTb2Z0d2FyZXwgICAgfCAgfCAgICAgICAgICstLS0tLS0tLS0rICAgICAgICstLS0tLS0t
KyB8DQogIHxJbnN0YW5jZSB8IHxJbnN0YW5jZXwgICAgfCAgfCAgICAgICAgIHxOZXR3b3JrICB8
X19fX19fX3xBY2NvdW50fCB8DQogICstLS0tLS0tLS0rICstLS0tLS0tLSsgICAgfCAgfCAgICAg
ICAgIHxTZXNzaW9uICB8KiAgMC4uMSstLS0tLS0tKyB8DQogICAgICAgfCogICAgICB8KiAgICAg
ICAgICAqfCAqfCAgICAgICAgIHwtIC0gLSAtIC18ICAgICAgICAgICAgICAgICp8DQogICAgICAg
fCAgICAgICB8X19fXzErLS0tLS0tLS0tLSsxX19fX19fKnxOZXR3b3JrICB8X19fX19fX19fXyst
LS0tLS0tKw0KICAgICAgIHxfX19fX19fX19fX19ffCBFbmRwb2ludCB8X19fX18gICB8SW50ZXJm
YWNlfCogICAgIDEuLip8QWRkcmVzc3wNCiAgICAgICAgICAgICAgICAgICAgMXwgICAgICAgICAg
fDAuLjEgfCAgKy0tLS0tLS0tLSsgICAgICAgICAgKy0tLS0tLS0rDQogICAgICAgICAgICAgICAg
ICAgICArLS0tLS0tLS0tLSsgICAgIHwgICAgICAxfA0KICAgICAgICAgIF9fX19fX19fX19fX198
MSAgICB8KiAgICAgICB8ICAgICAgIHxfX19fXystLS0tLS0tLS0tLS0tKw0KICAgICAgICAgfCAg
ICAgICAgICAgICAgICAgICB8X19fX19fX198ICAgICAgICAgICAgKnxBdXRob3JpemF0aW9ufA0K
ICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgcGFydC1vZj4gICAgICAgICAgICAgICstLS0t
LS0tLS0tLS0tKw0KICAuLi4uLi4ufC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uDQogICAgICAgICB8ICAgICAgICAgICAgfDAuLjEg
ICAgICAgICAgICANCiAgICAgICAgIHwgICAgICAgICAgICB8ICAgICAgICAgICAgICAgDQogICAg
ICAgICB8ICAgICAgICAgICAgfCogICAgICAgICAgICAgIA0KICAgICAgICAgfCAgICAgICAgICst
LS0tLSsgICAgICAgICAgICArLS0tLS0tLS0tK19fX19fX19fX19fX19fX19fX18NCiAgICAgICAg
IHwgICAgICAgICB8IEFWUCB8X19fX19fX19fX19ffEVuZHBvaW50IHwqICAgICA8YmFzZWQtb24g
ICAgfA0KICAgICAgICBefCAgICAgICAgICstLS0tLSsxLi4qICAgICAgIDF8QXR0cmlidXRlfF9f
X19fX19fICAgICAgICAgICB8DQpob3N0ZWQtYnl8ICAgICAgICAgICAqfCAgICAgICAgICAgICAg
IHxBc3NlcnRpb258KiAgICAgICB8ICAgICAgICAgIHwNCiAgICAgICAgIHwgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgKy0tLS0tLS0tLSsgICAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAg
fCAgICAgICAgICAgIHxwcm9kdWNlZC11c2luZyAgIHwqICAgIHwqICAgICAgICAgfCAgICAgICAg
ICp8DQogICAgICAgICB8ICAgICAgICAgICAxfFYgICAgICAgICAgICAgICAgfCAgICAgfF9fX19f
X19fX198ICAgICArLS0tLS0tLSsNCiAgICAgICAgIHwgICAgICAgICstLS0tLS0tLSsgICAgICAg
ICAgICB8ICAgICAgIDxiYXNlZC1vbiAgICAgIHxTdW1tYXJ5fA0KICAgICAgICAgfCAgICAgICAg
fCBNZXRob2QgfCAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0rDQog
ICAgICAgICB8ICAgICAgICArLS0tLS0tLS0rICAgICAgICAgICAgfHByb2R1Y2VkLWJ5ICAgICAg
ICAgICAgICAgKnwgICAgICAgDQogICAgICAgICB8X19fX19fX19fX19fX19fX19fX18gICAgICAg
ICAgfFYgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHwqICAgICAgIDF8ICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICArLS0t
LS0tLS0rMV9fX19fX19fX19fXyorLS0tLS0tLS0tLS0rICAgICAgICAgICAgICAgICAgICAgICAg
ICB8DQogICAgIHwgICAgICAgIHwgICAgZ3VpZGVzPiAgIHwgU0FDTSAgICAgIHxfX19fX19fX19f
X19fX19fX19fX19fX19fX3wNCiAgICAgfEd1aWRhbmNlfCAgICAgICAgICAgICAgfCBDb21wb25l
bnQgfDEgICAgICA8cHJvZHVjZWQtYnkNCiAgICAgKy0tLS0tLS0tKypfX19fX19fX19fX18xKy0t
LS0tLS0tLS0tKw0KICAgICAgICAgICAgICAgIDxwcm9kdWNlZC1ieQ0KDQogICAgICAgICAtLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQogICAgICAgICAuLi4uLiBBYm92ZSB0aGlzIGxpbmUgaXMgdGhlIG1vbml0b3JhYmxlIHdvcmxk
DQogICAgICAgICAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQo=

--_004_CY1PR0601MB135591C277AB97FC585B5BB6B73C0CY1PR0601MB1355_--


From nobody Mon Feb  2 06:17:28 2015
Return-Path: <henk.birkholz@sit.fraunhofer.de>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC4D1A1B7C for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 06:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level: 
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 xrfCP0yHo2Zi for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 06:17:22 -0800 (PST)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B082D1A1B92 for <sacm@ietf.org>; Mon,  2 Feb 2015 06:14:43 -0800 (PST)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id t12EEd9K014425 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 2 Feb 2015 15:14:40 +0100
Received: from [192.168.0.71] (134.102.43.163) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.210.2; Mon, 2 Feb 2015 15:14:34 +0100
Message-ID: <54CF8541.7030300@sit.fraunhofer.de>
Date: Mon, 2 Feb 2015 15:10:09 +0100
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Clifford Kahn <cliffordk@pulsesecure.net>, "sacm@ietf.org" <sacm@ietf.org>
References: <54590118.9050702@sit.fraunhofer.de> <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080405000200090600020606"
X-Originating-IP: [134.102.43.163]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/AusESodrNdbWp7fwVxLul-YgOS4>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 14:17:25 -0000

--------------ms080405000200090600020606
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello Cliff,

In essence, 1.1.1.1:1433 could be seen as a sub-address of 1.1.1.1, and=20
if the inherent ambiguousness of IP-addresses cannot be addressed (e.g.=20
by associating an artificial identifier with each collected IP-address=20
TVP), a concept that combines both ports and addresses has to be used in =

parallel to the simpler concepts "IP-address" and "Port".

More thoughts on that in the next mail :)

Cheers,

Henk

On 02/01/2015 04:38 PM, Clifford Kahn wrote:
> Henk,
> First, a correction. I said, incorrectly, that you had proposed removin=
g the idea of "session". You actually proposed separating it from "interf=
ace". (I do suggest we remove "session" altogether.)
>
> Second, I like your suggestion of promoting section 4.10.1, "Address", =
to a 4.x section.
>
> Third, I like your addition to the "Address" section.
>
> Fourth, let's consider taking it further. In a side conversation you po=
inted out that a port number is really part of an address. The port numbe=
r matters for some purposes, but not for others. One place where it matte=
rs: you pointed out that compliance policies about network ingress make a=
 lot of sense. For example, a policy could disapprove of an endpoint list=
ening on the MSSQL port (1433). Many successful attacks have been made on=
 ports unintentionally left open, so this is well motivated.
>
> How would we model this? Is 1.1.1.1:1433 a sub-address of 1.1.1.1?
>
> Fifth, and most central: you write that we should capture the nested an=
d layered structure of interfaces to "address network centric security/mo=
nitoring processes, effectively". I don't understand yet how a network ba=
sed attribute collector (a "sensor") would know or care.  A sensor observ=
es or injects network traffic. It knows addresses. How can it be aware of=
 network interfaces? How can it discern whether one interface nests in an=
other?
>
> An attribute collector that runs on the endpoint, or that queries the e=
ndpoint using a management protocol, may discern the nesting. But it is n=
ot a sensor. Would information from the two kinds of collectors have to b=
e combined?
>
> Best,
> 			Cliff
>
> -----Original Message-----
> From: Clifford Kahn
> Sent: Sunday, February 01, 2015 9:39 AM
> To: 'Henk Birkholz'; sacm@ietf.org
> Subject: RE: [sacm] Comments on Network Interface
>
> Henk,
> Belated response here.
>
> As I understand you, you would remove the class "session", mentioned in=
 the diagram and in section 4.10 of draft-ietf-sacm-information-model. Is=
 that true?
>
> I realize there is more to your proposal. But I want to respond to remo=
ving "session". Let's consider why sessions were there.
>
> Suppose an endpoint's layer 2 interface comes online after a RADIUS exc=
hange. Some of us would say a layer 2 session has begun; that may be misu=
se of the word "session". Anyway, the RADIUS server knows:
> - the endpoint's MAC address
> - the credentials used in the RADIUS authentication
> - the authorization that it granted (VLAN, a filter-id denoting firewal=
l rules)
> - the endpoint's compliance, if NEA checking was done during the RADIUS=
 exchange
> - sometimes, an IP address (if the switch does DHCP snooping and report=
s its findings in RADIUS Accounting messages)
>
> That information is relevant for SACM. Authorization is relevant becaus=
e endpoints that have access to sensitive resources may be subject to mor=
e stringent compliance policies. (Hm. Do we have that in our use cases? S=
hould we?)
>
> Perhaps we don't need a session in the model. Perhaps the RADIUS server=
 can just make an endpoint attribute assertion stating the above attribut=
es. I like the simplification.
>
> Other kinds of network sessions (TCP connections, etc.) are certainly r=
elevant for security. But they seem to be outside of the SACM WG's charte=
r.
>
> In sum, I cannot see a reason to keep "session" in the information mode=
l.
>
> What do others think?
>
> Best,
> 			Cliff
>
> -----Original Message-----
> From: Henk Birkholz [mailto:henk.birkholz@sit.fraunhofer.de]
> Sent: Tuesday, November 04, 2014 11:39 AM
> To: sacm@ietf.org
> Subject: [sacm] Comments on Network Interface
>
> Hi all,
>
> the new draft (draft-ietf-sacm-information-model-00) now includes a com=
bined section for "Network Session" and "Network Interface" (4.10.).
>
> My recommendation is to divide the elements Network Session, Network In=
terface and potentially (Network) Address into separate sections of the s=
ame level (4.x).
>
> While both terms are related, of course, there are several (more or les=
s
> important) reasons for this:
> A session typically involves multiple participants (e.g. endpoints, or =
- broken down - eventually addresses or interfaces) and typically has a l=
imited life-time. An interface, in contrast, is a singular entity that ca=
n exist over the complete life-cycle of an endpoint (virtual interfaces c=
an have a foreseeable limited life-time). As Ira pointed out, an interfac=
e typically provides connectivity to a network on layer two to three, whi=
le a network session is typically associated with layers above those.
>
> Although closely related, they are quite different, semantically, and m=
ay even need separate representations in the SACM IM.
>
> My proposal for a separate "Network Interface" section:
>
> ---snip---
> Network Interface
>
> An endpoint is connected to a network via one or more interfaces.
> Interfaces can be physical or virtual. Interfaces of an endpoint can op=
erate on different layers, most prominently what is now commonly called l=
ayer 2 and 3. Within a layer, interfaces can be nested.
> On layer 2, a root interface is typically associated with a physical in=
terface port and nested interfaces are virtual interfaces. In the case of=
 a virtual endpoint, a root interface can be a virtual interface.
> Virtual layer 2 interfaces of one or more endpoints can also constitute=
 an aggregated group of links that act as one.
> On layer 3, nested interfaces typically constitute virtual tunnels or n=
etworks.
> Examples include: physical Ethernet port, layer 2 VLAN interface, a MC-=
LAG setup, layer 3 Point-to-Point tunnel ingress or egress.
> ---snap---
>
> A small addition to the "Address" section, analogously:
>
> ---snip---
> Network Address
>
> Network addresses are layer specific and follow layer specific address =
schemes. Each interface of a specific layer can be associated with one or=
 more addresses appropriate for that layer.
> There is no guarantee that an address is globally unique. In general, t=
here is a scope to an address in which it is intended to be unique.
> Examples include: physical Ethernet port with a MAC address, layer 2 VL=
AN interface with a MAC address, layer 3 interface with multiple IPv6 add=
resses, layer 3 tunnel ingress or egress with an IPv4 address.
> ---snap---
>
> Sometimes, the complexity a setup of interfaces can incorporate is a li=
ttle bit underestimated, IMHO. The proposed text above only includes the =
most common cases and does not touch emerging practices, such as physical=
 interface modules that provide a set of single physical interfaces, whic=
h are associated with multiple distinguishable endpoints at the same time=
=2E
>
> In order to address network centric security/monitoring processes, effe=
ctively, the SACM IM should be able to handle the complexity of applied c=
ommon practice in its definition of "Network Interface", I think.
>
> Best,
>
> Henk
>



--------------ms080405000200090600020606
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIUXDCC
BC4wggMWoAMCAQICAgEMMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNzEyMDUxNTE4NTha
Fw0xOTA2MzAyMzU5NTlaMGcxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpGcmF1bmhvZmVyMSEw
HwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQS0kxIDAeBgNVBAMTF0ZyYXVuaG9mZXIg
Um9vdCBDQSAyMDA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwz0eyWWNW4g3
9z7BIbZU3rA6VxsaHO6YCHQBWm+13zZXK0RFzvNGE2V2lZhUx6iFFW4SpBfoC+EhpzE9Kd3/
o9ZP0rSJ/WNK2qtT71kFtE/iOyqRmcDLZVeBozCTkA7Jvf0VMjIIpEh8VgXyuzaJ4kjCb0uS
DCVFvq0+1McB7bHIErQwCG6nb396IKe7tOU1gFQsGY/ZS8Adq0P4YRSU+7AdXbeR7GLAkdFe
3acLsy0fZjkYPK4EFOXSfTbZss2nE7DMRZ1WBFFxMzZcL11RE55PSJAOl1pLcNu5edmh1pTI
ktCl+2C/La2ecQAXhsD9SGadFEwFTkzRcUQL0HoPsQIDAQABo4HZMIHWMB8GA1UdIwQYMBaA
FDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUL0VCHjEF
gNVw2PgdV8tbetU9nPcwEgYDVR0TAQH/BAgwBgEB/wIBATBwBgNVHR8EaTBnMGWgY6Bhhl9o
dHRwOi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNy
bD8tY3JsX2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjANBgkqhkiG9w0BAQUF
AAOCAQEAGrdMejzl3cJjst6GJU5FYkz08o9fXdfljc4O1/WU4YuTMTanmiPnZ+FSwVoY1pnh
gGQ4D0o1M11meijcOH83cs1SdW4Qjmx9jPcp63fCuRkF1Lc9YbroBRLUUGJT7yJUYvxNAcNe
1A2DdGlR1TyerNukK3xthJbTcU3P1S1xo5LEP1XPmz0jdwdX6cjOHZe2M/uRl2CWD/f23m8l
kBKrGUfVRCOuwZI1KL8qQ14P6gdd0kTQhYLjErxH6iyt+PBBUn02uiKfeqAy70u8+ToHtinG
fThfNVV+OPI/fLPuLW4heF+5E8/v3mWAyCX1Zi1USq3O2S4OMM+AM6eLGXLqQTCCBMYwggOu
oAMCAQICCmEdMxkAAAAAAAMwDQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNV
BAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4G
A1UEAxMXRnJhdW5ob2ZlciBSb290IENBIDIwMDcwHhcNMDcxMjEyMTQ0OTM1WhcNMTkwNjMw
MjM1OTU5WjBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8GA1UECxMY
RnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVzZXIgQ0Eg
MjAwNzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMJ0EFHLddGB8Ss1nVqCOq+S
rs0C/K7I+yB3Dv9oEhWQSadnfGgkX/oOJhplPkqeCQrTh08zEYprVaJLTaVPVhvjx3h5+KML
3lVGZIfajA89TolhLwk+ml29VbqV5nLhNrSwdZy157b6dCu5JffxvpO5wXCn95Z/TLyLdeux
gVHs/MnhczvmBbBRS+Ow9UoKn+PZvyYmUEdOHg8cA5PGFaRP9q88q734VnlI+W4+y7BoN5wt
uqVrqWbbpOQ2sHYo9riv3b+x5WdsMrVieKGApQ/dNvgB5vuuAchRnsANZHgpAiPCzP7/QFYY
qk2undcxEXwPgo72oifB3uQZ3xHOV/cCAwEAAaOCAXIwggFuMBIGA1UdEwEB/wQIMAYBAf8C
AQAwHQYDVR0OBBYEFE8dr4jKbbiqHAn5xdER7Vm0k/oLMA4GA1UdDwEB/wQEAwIBBjAfBgNV
HSMEGDAWgBQvRUIeMQWA1XDY+B1Xy1t61T2c9zB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8v
Y3JsLnBraS5mcmF1bmhvZmVyLmRlL2ZoZy1yb290LWNhLTIwMDcuY3JshjFodHRwOi8vY3Js
LmZyYXVuaG9mZXItcGtpLmRlL2ZoZy1yb290LWNhLTIwMDcuY3JsMIGQBggrBgEFBQcBAQSB
gzCBgDA+BggrBgEFBQcwAoYyaHR0cDovL2NlcnQucGtpLmZyYXVuaG9mZXIuZGUvZmhnLXJv
b3QtY2EtMjAwNy5jZXIwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LmZyYXVuaG9mZXItcGtp
LmRlL2ZoZy1yb290LWNhLTIwMDcuY2VyMA0GCSqGSIb3DQEBBQUAA4IBAQAAd2yMM/nuVwQl
ysuIOeZOTKTOwpZLGYZNuERXwpWpEDfsMFUxX/Wetbu1a1qhd+x6SyXY4V1CzcFDOGF3wA7b
yIV/6dyC53I9luZTjy9zjUsjLZucD4jeNja3QEu39sQsYsuE3MTfFFJgr/NeAFMHVkkHGx3l
VXb+F3J3+9xeXHk/wB/yIKd/RIiMMTT4+a+ra2MTCsYAe4kgJ0vz2TXYGN8tujjCgsUUbwfJ
C9wrOiCJMNJM1i7sUVqVKIoswW7h5QpWUNu1E4RAsDEz7depXCYaAIwPprEIkr0dE63zqHhm
M4egS7iGmBfNQohUO6jJOWNcJ9dIxqc0c/4WUHg8MIIFpjCCBI6gAwIBAgIKFcglDgAAAAII
ozANBgkqhkiG9w0BAQUFADBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEh
MB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVy
IFVzZXIgQ0EgMjAwNzAeFw0xMzEyMTcxMjM1NDdaFw0xOTA2MzAyMzU5NTlaMFkxCzAJBgNV
BAYTAkRFMRMwEQYDVQQKEwpGcmF1bmhvZmVyMQwwCgYDVQQLEwNTSVQxDzANBgNVBAsTBlBl
b3BsZTEWMBQGA1UEAxMNSGVuayBCaXJraG9sejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAKsXgaAh0xiGvFnwWielNH0sAuapRSYZM2mzLEPl1Euoq/3VkbY2P1MbzIsb/8+Q
mKB64li7vParM+zPL7zjijzHRqgJYkOIDS1jA1CBqAQvDd1AUPmi9ZfwJ7dSX0kF6Z85bF6R
HkQZLps4HeTqC1tzexuplZUClTCTxCJu4FioaqEbeh4w117vEC/gEJlvr4t/jsHwgv4LwCY6
PT4iaCA6tCnpnwH+/acol7huFwA+KvDLiFZupdqt4P1wlVENq+GIAc/9TcND0wSICyI6ny74
tGvoV/RfroHM3oSUEGzRsWgq/InxQi9/I3ufqXVHxkMLRCJojN00Ovjrdi7qwpECAwEAAaOC
AmAwggJcMA4GA1UdDwEB/wQEAwIGwDAqBgNVHREEIzAhgR9oZW5rLmJpcmtob2x6QHNpdC5m
cmF1bmhvZmVyLmRlMB0GA1UdDgQWBBRQ1jZ98/8G4Zq4bKXRDy1tlI0JgjAfBgNVHSMEGDAW
gBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8vY3JsLnBr
aS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3JsLmZyYXVu
aG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEEgf0wgfow
PgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNh
LTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBraS5kZS9m
aGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2VyLWNhLTIw
MDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNl
ci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMBMGA1UdJQQMMAoGCCsGAQUFBwME
MEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYcaHR0cDovL3BraS5m
cmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEAlHj5O+ExJF+2q0FK+dRcWQb3
vcDAyaTXqotBwJgYRJVs6LV6kkw74CSDg1TPlr1FG9dEzS2MZbiPhtE1CqN3yEf40MJBLYFi
KG0DIJwX3YmmBmK5QbIE+1EQ0MzPKomYqDiBUuC7POBiTGRPpYCrvHEfVZ+BuVlsMsvCp9aK
6vn91k/pWHF0AU0tJVhOGCjlrJsCwn/nP/4qTNf/nSE8etykPvYvu799B4Tdljlvrt/WeaVo
yA1Jl9WPny96OCa4qJaDWUMnjTUt14NICuwGV9bype+q9dorsogyhnQEO4rDcaFdKxmjmoV+
agEy1JX4jR6iTaKmWYgIIXy6gMnHmTCCBbIwggSaoAMCAQICCkSGTToAAAAB174wDQYJKoZI
hvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsT
GEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENB
IDIwMDcwHhcNMTMwNzMwMTExNTA4WhcNMTkwNjMwMjM1OTU5WjBZMQswCQYDVQQGEwJERTET
MBEGA1UEChMKRnJhdW5ob2ZlcjEMMAoGA1UECxMDU0lUMQ8wDQYDVQQLEwZQZW9wbGUxFjAU
BgNVBAMTDUhlbmsgQmlya2hvbHowggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDj
tnr/To9XMlYudCBG2zL6U9stsuWyzIHvJ7al9p1tQakgTYiwTdX5/jsNA1JeHj+TJhzThxh7
nyBfONgy0EUgv835UJw5j4Tknlp5HdU39GMqEdAPd1791E50slOnKpGEjQwd8h6Cw73eF4YN
1QYlfbeoGPt+Tb1z+RUoauQto0atHhnU0rLX1mQ6tZXMMZ9FZcFgC7oVmwtwbK8URIVIlaHo
lGCgOfWfgHxSQICRr9j7kT25xHJ+oimXCb0lIyBuSKAJzo/OHFhIx9cNNGlAwzaynUhU8I1B
6vr9M580bCCEzRSOXzJOFxkhDaX+PinaHxa7SnQAgxlWvckXTEmPAgMBAAGjggJsMIICaDAO
BgNVHQ8BAf8EBAMCBDAwKgYDVR0RBCMwIYEfaGVuay5iaXJraG9sekBzaXQuZnJhdW5ob2Zl
ci5kZTAdBgNVHQ4EFgQUZTNsNue6lgNe5EoFiD4xR0w8XsIwHwYDVR0jBBgwFoAUTx2viMpt
uKocCfnF0RHtWbST+gswdQYDVR0fBG4wbDBqoGigZoYxaHR0cDovL2NybC5wa2kuZnJhdW5o
b2Zlci5kZS9maGctdXNlci1jYS0yMDA3LmNybIYxaHR0cDovL2NybC5mcmF1bmhvZmVyLXBr
aS5kZS9maGctdXNlci1jYS0yMDA3LmNybDCCAQoGCCsGAQUFBwEBBIH9MIH6MD4GCCsGAQUF
BzAChjJodHRwOi8vY2VydC5wa2kuZnJhdW5ob2Zlci5kZS9maGctdXNlci1jYS0yMDA3LmNl
cjA+BggrBgEFBQcwAoYyaHR0cDovL2NlcnQuZnJhdW5ob2Zlci1wa2kuZGUvZmhnLXVzZXIt
Y2EtMjAwNy5jZXIwOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNlci1jYS0yMDA3Lm9jc3Au
cGtpLmZyYXVuaG9mZXIuZGUvMDsGCCsGAQUFBzABhi9odHRwOi8vZmhnLXVzZXItY2EtMjAw
Ny5vY3NwLmZyYXVuaG9mZXItcGtpLmRlLzAfBgNVHSUEGDAWBgorBgEEAYI3CgMEBggrBgEF
BQcDBDBEBgNVHSAEPTA7MDkGCysGAQQBhgpQAwEBMCowKAYIKwYBBQUHAgEWHGh0dHA6Ly9w
a2kuZnJhdW5ob2Zlci5kZS9jcC8wDQYJKoZIhvcNAQEFBQADggEBACzw+XqMZ39YLL77+Pmq
ELSv8Ioyy9CXbsaYYsXEjKLGKvQix4o8MANvpoT6iyrDrqreaofsUd0YhdXd2PUJVZ92ujTA
BMq6fMJGvrty95zwW0lX0SWYqcSobX3mmW4D9nQpDEPEJGQ095kk3SzAFYO7ZHj9Srt1G2hq
UovZP5/aYk+CpYbml+uYlU4Ux/KtYD66k9I9YFCiHKpzNxgoKlzDlkZ2a2uRPYKBFqBqKRee
5TM1DB47l89K1xw3eUWcxcwjusZc2z6EZqk8CgyRXz+m+zK5LCnvSf+1nuR9T5OcmiPwJgpO
8qw3Yoer628t6NfTkz/a49vUgtSlq3kNURsxggN7MIIDdwIBATB1MGcxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpGcmF1bmhvZmVyMSEwHwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQ
S0kxIDAeBgNVBAMTF0ZyYXVuaG9mZXIgVXNlciBDQSAyMDA3AgoVyCUOAAAAAgijMAkGBSsO
AwIaBQCgggHbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MDIwMjE0MTAwOVowIwYJKoZIhvcNAQkEMRYEFHWpz0OBXvoS5qvCVNksBjdYLVL7MGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYQG
CSsGAQQBgjcQBDF3MHUwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAf
BgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBV
c2VyIENBIDIwMDcCCkSGTToAAAAB174wgYYGCyqGSIb3DQEJEAILMXegdTBnMQswCQYDVQQG
EwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3Jh
dGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVzZXIgQ0EgMjAwNwIKRIZNOgAAAAHXvjAN
BgkqhkiG9w0BAQEFAASCAQCFVWChWgTlUA6KT49lg8qNVUUWHhKcmlQdghHYzUhFd3Jb5LXk
yYwvtYFpyCZVZRS0wmNuS2izYKpzDlJ6mFw48/3Ww5GjqqMr4/iMVUNe8064D2OPH3SkJySJ
t91IYDmZZMZaY9SVoqPWvDBwxghMFMO5C1j3awxilRfy3BS5rPcvkUSBy/6PAA+K3BuyzYx2
axdBtb3gbPwh5/8fQ8ayVlUt+ZZDpbjKUT4pWIvKHo1G3DYPXr4mJ1jR71wcGRJqRRNuYhWm
FbPk600s9dFHGYQvU7BxdMgROV/eUCxDbzG/S7YaOAv/kO2Zc8pnYcDOAMbkS8i5LQc0Tewk
xWwiAAAAAAAA
--------------ms080405000200090600020606--


From nobody Mon Feb  2 06:44:18 2015
Return-Path: <henk.birkholz@sit.fraunhofer.de>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC4C61A1A5C for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 06:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level: 
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 lx30kk_1mmWF for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 06:44:11 -0800 (PST)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CD6C1A1A4F for <sacm@ietf.org>; Mon,  2 Feb 2015 06:44:10 -0800 (PST)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id t12Ei7kF015687 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 2 Feb 2015 15:44:08 +0100
Received: from [192.168.0.71] (134.102.43.163) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.210.2; Mon, 2 Feb 2015 15:44:02 +0100
Message-ID: <54CF8C29.3050307@sit.fraunhofer.de>
Date: Mon, 2 Feb 2015 15:39:37 +0100
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Clifford Kahn <cliffordk@pulsesecure.net>, "sacm@ietf.org" <sacm@ietf.org>
References: <54590118.9050702@sit.fraunhofer.de> <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030102060100000408080405"
X-Originating-IP: [134.102.43.163]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/I4o7IKpyqyeI65V4M9Vnk8O2AGY>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 14:44:17 -0000

--------------ms030102060100000408080405
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

And now a more detailed view on this:

Yes, a port number is effectively a layer 4 address, I think. Typically, =

ports are always active but are only used for services when an=20
application (this includes the OS in some occasions, or even a dedicated =

IPMI endpoint co-located on the endpoint itself), which runs on an=20
endpoint, binds them on a specific address. This includes, for example,=20
the very ambiguous loopback addresses. There is a strong relationship=20
between layer 4 port associations and endpoint security posture=20
regarding software/applications.

I think it is important to capture and incorporate three concepts here:
- active ports can be bound only to a subset of the layer 3 addresses=20
associated with an endpoint,
- addresses are always bound to specific interfaces, and
- interfaces (of various layers) have a relationships to each other=20
(e.g. nested, bridged/forwarding).

Regarding security posture of an endpoint, it might be considered "okay" =

that a vulnerable application running on it is providing a service=20
(thereby controlling a corresponding ingress listening port) via one of=20
the many layer 3 addresses of the endpoint, because this specific=20
address might be associated with an interface that is considered=20
connected to an "inside" or "securely managed" network (and not to,=20
e.g., an internet-facing interface). This is of course only true if=20
there is no sophisticated packet mangling or frame forwarding done on=20
the endpoint.

In essence, addresses (among other things) should be modeled in an=20
unambiguous way to correctly associate security related data with them.=20
Combining port and IP-address in an additional concept is one way to do=20
it, but I am not sure that will eliminate ambiguousness in every case.=20
Assigning artificially created identifiers to them would be an alternate =

route. We should discuss which further alternatives there are and which=20
would work best for SACM, I think.

Cheers,

Henk

p.s. in hindsight my expression "to address network centric=20
security/monitoring processes" seems to be quite misleading. It was not=20
my intend to refer to a "network based attribute collector" but to local =

endpoint attributes regarding the interconnected relationship of the=20
endpoint with its neighboring endpoints connected via the network.


On 02/01/2015 04:38 PM, Clifford Kahn wrote:
> Henk,
> First, a correction. I said, incorrectly, that you had proposed removin=
g the idea of "session". You actually proposed separating it from "interf=
ace". (I do suggest we remove "session" altogether.)
>
> Second, I like your suggestion of promoting section 4.10.1, "Address", =
to a 4.x section.
>
> Third, I like your addition to the "Address" section.
>
> Fourth, let's consider taking it further. In a side conversation you po=
inted out that a port number is really part of an address. The port numbe=
r matters for some purposes, but not for others. One place where it matte=
rs: you pointed out that compliance policies about network ingress make a=
 lot of sense. For example, a policy could disapprove of an endpoint list=
ening on the MSSQL port (1433). Many successful attacks have been made on=
 ports unintentionally left open, so this is well motivated.
>
> How would we model this? Is 1.1.1.1:1433 a sub-address of 1.1.1.1?
>
> Fifth, and most central: you write that we should capture the nested an=
d layered structure of interfaces to "address network centric security/mo=
nitoring processes, effectively". I don't understand yet how a network ba=
sed attribute collector (a "sensor") would know or care.  A sensor observ=
es or injects network traffic. It knows addresses. How can it be aware of=
 network interfaces? How can it discern whether one interface nests in an=
other?
>
> An attribute collector that runs on the endpoint, or that queries the e=
ndpoint using a management protocol, may discern the nesting. But it is n=
ot a sensor. Would information from the two kinds of collectors have to b=
e combined?
>
> Best,
> 			Cliff
>
> -----Original Message-----
> From: Clifford Kahn
> Sent: Sunday, February 01, 2015 9:39 AM
> To: 'Henk Birkholz'; sacm@ietf.org
> Subject: RE: [sacm] Comments on Network Interface
>
> Henk,
> Belated response here.
>
> As I understand you, you would remove the class "session", mentioned in=
 the diagram and in section 4.10 of draft-ietf-sacm-information-model. Is=
 that true?
>
> I realize there is more to your proposal. But I want to respond to remo=
ving "session". Let's consider why sessions were there.
>
> Suppose an endpoint's layer 2 interface comes online after a RADIUS exc=
hange. Some of us would say a layer 2 session has begun; that may be misu=
se of the word "session". Anyway, the RADIUS server knows:
> - the endpoint's MAC address
> - the credentials used in the RADIUS authentication
> - the authorization that it granted (VLAN, a filter-id denoting firewal=
l rules)
> - the endpoint's compliance, if NEA checking was done during the RADIUS=
 exchange
> - sometimes, an IP address (if the switch does DHCP snooping and report=
s its findings in RADIUS Accounting messages)
>
> That information is relevant for SACM. Authorization is relevant becaus=
e endpoints that have access to sensitive resources may be subject to mor=
e stringent compliance policies. (Hm. Do we have that in our use cases? S=
hould we?)
>
> Perhaps we don't need a session in the model. Perhaps the RADIUS server=
 can just make an endpoint attribute assertion stating the above attribut=
es. I like the simplification.
>
> Other kinds of network sessions (TCP connections, etc.) are certainly r=
elevant for security. But they seem to be outside of the SACM WG's charte=
r.
>
> In sum, I cannot see a reason to keep "session" in the information mode=
l.
>
> What do others think?
>
> Best,
> 			Cliff
>
> -----Original Message-----
> From: Henk Birkholz [mailto:henk.birkholz@sit.fraunhofer.de]
> Sent: Tuesday, November 04, 2014 11:39 AM
> To: sacm@ietf.org
> Subject: [sacm] Comments on Network Interface
>
> Hi all,
>
> the new draft (draft-ietf-sacm-information-model-00) now includes a com=
bined section for "Network Session" and "Network Interface" (4.10.).
>
> My recommendation is to divide the elements Network Session, Network In=
terface and potentially (Network) Address into separate sections of the s=
ame level (4.x).
>
> While both terms are related, of course, there are several (more or les=
s
> important) reasons for this:
> A session typically involves multiple participants (e.g. endpoints, or =
- broken down - eventually addresses or interfaces) and typically has a l=
imited life-time. An interface, in contrast, is a singular entity that ca=
n exist over the complete life-cycle of an endpoint (virtual interfaces c=
an have a foreseeable limited life-time). As Ira pointed out, an interfac=
e typically provides connectivity to a network on layer two to three, whi=
le a network session is typically associated with layers above those.
>
> Although closely related, they are quite different, semantically, and m=
ay even need separate representations in the SACM IM.
>
> My proposal for a separate "Network Interface" section:
>
> ---snip---
> Network Interface
>
> An endpoint is connected to a network via one or more interfaces.
> Interfaces can be physical or virtual. Interfaces of an endpoint can op=
erate on different layers, most prominently what is now commonly called l=
ayer 2 and 3. Within a layer, interfaces can be nested.
> On layer 2, a root interface is typically associated with a physical in=
terface port and nested interfaces are virtual interfaces. In the case of=
 a virtual endpoint, a root interface can be a virtual interface.
> Virtual layer 2 interfaces of one or more endpoints can also constitute=
 an aggregated group of links that act as one.
> On layer 3, nested interfaces typically constitute virtual tunnels or n=
etworks.
> Examples include: physical Ethernet port, layer 2 VLAN interface, a MC-=
LAG setup, layer 3 Point-to-Point tunnel ingress or egress.
> ---snap---
>
> A small addition to the "Address" section, analogously:
>
> ---snip---
> Network Address
>
> Network addresses are layer specific and follow layer specific address =
schemes. Each interface of a specific layer can be associated with one or=
 more addresses appropriate for that layer.
> There is no guarantee that an address is globally unique. In general, t=
here is a scope to an address in which it is intended to be unique.
> Examples include: physical Ethernet port with a MAC address, layer 2 VL=
AN interface with a MAC address, layer 3 interface with multiple IPv6 add=
resses, layer 3 tunnel ingress or egress with an IPv4 address.
> ---snap---
>
> Sometimes, the complexity a setup of interfaces can incorporate is a li=
ttle bit underestimated, IMHO. The proposed text above only includes the =
most common cases and does not touch emerging practices, such as physical=
 interface modules that provide a set of single physical interfaces, whic=
h are associated with multiple distinguishable endpoints at the same time=
=2E
>
> In order to address network centric security/monitoring processes, effe=
ctively, the SACM IM should be able to handle the complexity of applied c=
ommon practice in its definition of "Network Interface", I think.
>
> Best,
>
> Henk
>



--------------ms030102060100000408080405
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIUXDCC
BC4wggMWoAMCAQICAgEMMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNzEyMDUxNTE4NTha
Fw0xOTA2MzAyMzU5NTlaMGcxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpGcmF1bmhvZmVyMSEw
HwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQS0kxIDAeBgNVBAMTF0ZyYXVuaG9mZXIg
Um9vdCBDQSAyMDA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwz0eyWWNW4g3
9z7BIbZU3rA6VxsaHO6YCHQBWm+13zZXK0RFzvNGE2V2lZhUx6iFFW4SpBfoC+EhpzE9Kd3/
o9ZP0rSJ/WNK2qtT71kFtE/iOyqRmcDLZVeBozCTkA7Jvf0VMjIIpEh8VgXyuzaJ4kjCb0uS
DCVFvq0+1McB7bHIErQwCG6nb396IKe7tOU1gFQsGY/ZS8Adq0P4YRSU+7AdXbeR7GLAkdFe
3acLsy0fZjkYPK4EFOXSfTbZss2nE7DMRZ1WBFFxMzZcL11RE55PSJAOl1pLcNu5edmh1pTI
ktCl+2C/La2ecQAXhsD9SGadFEwFTkzRcUQL0HoPsQIDAQABo4HZMIHWMB8GA1UdIwQYMBaA
FDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUL0VCHjEF
gNVw2PgdV8tbetU9nPcwEgYDVR0TAQH/BAgwBgEB/wIBATBwBgNVHR8EaTBnMGWgY6Bhhl9o
dHRwOi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNy
bD8tY3JsX2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjANBgkqhkiG9w0BAQUF
AAOCAQEAGrdMejzl3cJjst6GJU5FYkz08o9fXdfljc4O1/WU4YuTMTanmiPnZ+FSwVoY1pnh
gGQ4D0o1M11meijcOH83cs1SdW4Qjmx9jPcp63fCuRkF1Lc9YbroBRLUUGJT7yJUYvxNAcNe
1A2DdGlR1TyerNukK3xthJbTcU3P1S1xo5LEP1XPmz0jdwdX6cjOHZe2M/uRl2CWD/f23m8l
kBKrGUfVRCOuwZI1KL8qQ14P6gdd0kTQhYLjErxH6iyt+PBBUn02uiKfeqAy70u8+ToHtinG
fThfNVV+OPI/fLPuLW4heF+5E8/v3mWAyCX1Zi1USq3O2S4OMM+AM6eLGXLqQTCCBMYwggOu
oAMCAQICCmEdMxkAAAAAAAMwDQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNV
BAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4G
A1UEAxMXRnJhdW5ob2ZlciBSb290IENBIDIwMDcwHhcNMDcxMjEyMTQ0OTM1WhcNMTkwNjMw
MjM1OTU5WjBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8GA1UECxMY
RnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVzZXIgQ0Eg
MjAwNzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMJ0EFHLddGB8Ss1nVqCOq+S
rs0C/K7I+yB3Dv9oEhWQSadnfGgkX/oOJhplPkqeCQrTh08zEYprVaJLTaVPVhvjx3h5+KML
3lVGZIfajA89TolhLwk+ml29VbqV5nLhNrSwdZy157b6dCu5JffxvpO5wXCn95Z/TLyLdeux
gVHs/MnhczvmBbBRS+Ow9UoKn+PZvyYmUEdOHg8cA5PGFaRP9q88q734VnlI+W4+y7BoN5wt
uqVrqWbbpOQ2sHYo9riv3b+x5WdsMrVieKGApQ/dNvgB5vuuAchRnsANZHgpAiPCzP7/QFYY
qk2undcxEXwPgo72oifB3uQZ3xHOV/cCAwEAAaOCAXIwggFuMBIGA1UdEwEB/wQIMAYBAf8C
AQAwHQYDVR0OBBYEFE8dr4jKbbiqHAn5xdER7Vm0k/oLMA4GA1UdDwEB/wQEAwIBBjAfBgNV
HSMEGDAWgBQvRUIeMQWA1XDY+B1Xy1t61T2c9zB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8v
Y3JsLnBraS5mcmF1bmhvZmVyLmRlL2ZoZy1yb290LWNhLTIwMDcuY3JshjFodHRwOi8vY3Js
LmZyYXVuaG9mZXItcGtpLmRlL2ZoZy1yb290LWNhLTIwMDcuY3JsMIGQBggrBgEFBQcBAQSB
gzCBgDA+BggrBgEFBQcwAoYyaHR0cDovL2NlcnQucGtpLmZyYXVuaG9mZXIuZGUvZmhnLXJv
b3QtY2EtMjAwNy5jZXIwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LmZyYXVuaG9mZXItcGtp
LmRlL2ZoZy1yb290LWNhLTIwMDcuY2VyMA0GCSqGSIb3DQEBBQUAA4IBAQAAd2yMM/nuVwQl
ysuIOeZOTKTOwpZLGYZNuERXwpWpEDfsMFUxX/Wetbu1a1qhd+x6SyXY4V1CzcFDOGF3wA7b
yIV/6dyC53I9luZTjy9zjUsjLZucD4jeNja3QEu39sQsYsuE3MTfFFJgr/NeAFMHVkkHGx3l
VXb+F3J3+9xeXHk/wB/yIKd/RIiMMTT4+a+ra2MTCsYAe4kgJ0vz2TXYGN8tujjCgsUUbwfJ
C9wrOiCJMNJM1i7sUVqVKIoswW7h5QpWUNu1E4RAsDEz7depXCYaAIwPprEIkr0dE63zqHhm
M4egS7iGmBfNQohUO6jJOWNcJ9dIxqc0c/4WUHg8MIIFpjCCBI6gAwIBAgIKFcglDgAAAAII
ozANBgkqhkiG9w0BAQUFADBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEh
MB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVy
IFVzZXIgQ0EgMjAwNzAeFw0xMzEyMTcxMjM1NDdaFw0xOTA2MzAyMzU5NTlaMFkxCzAJBgNV
BAYTAkRFMRMwEQYDVQQKEwpGcmF1bmhvZmVyMQwwCgYDVQQLEwNTSVQxDzANBgNVBAsTBlBl
b3BsZTEWMBQGA1UEAxMNSGVuayBCaXJraG9sejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAKsXgaAh0xiGvFnwWielNH0sAuapRSYZM2mzLEPl1Euoq/3VkbY2P1MbzIsb/8+Q
mKB64li7vParM+zPL7zjijzHRqgJYkOIDS1jA1CBqAQvDd1AUPmi9ZfwJ7dSX0kF6Z85bF6R
HkQZLps4HeTqC1tzexuplZUClTCTxCJu4FioaqEbeh4w117vEC/gEJlvr4t/jsHwgv4LwCY6
PT4iaCA6tCnpnwH+/acol7huFwA+KvDLiFZupdqt4P1wlVENq+GIAc/9TcND0wSICyI6ny74
tGvoV/RfroHM3oSUEGzRsWgq/InxQi9/I3ufqXVHxkMLRCJojN00Ovjrdi7qwpECAwEAAaOC
AmAwggJcMA4GA1UdDwEB/wQEAwIGwDAqBgNVHREEIzAhgR9oZW5rLmJpcmtob2x6QHNpdC5m
cmF1bmhvZmVyLmRlMB0GA1UdDgQWBBRQ1jZ98/8G4Zq4bKXRDy1tlI0JgjAfBgNVHSMEGDAW
gBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8vY3JsLnBr
aS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3JsLmZyYXVu
aG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEEgf0wgfow
PgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNh
LTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBraS5kZS9m
aGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2VyLWNhLTIw
MDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNl
ci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMBMGA1UdJQQMMAoGCCsGAQUFBwME
MEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYcaHR0cDovL3BraS5m
cmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEAlHj5O+ExJF+2q0FK+dRcWQb3
vcDAyaTXqotBwJgYRJVs6LV6kkw74CSDg1TPlr1FG9dEzS2MZbiPhtE1CqN3yEf40MJBLYFi
KG0DIJwX3YmmBmK5QbIE+1EQ0MzPKomYqDiBUuC7POBiTGRPpYCrvHEfVZ+BuVlsMsvCp9aK
6vn91k/pWHF0AU0tJVhOGCjlrJsCwn/nP/4qTNf/nSE8etykPvYvu799B4Tdljlvrt/WeaVo
yA1Jl9WPny96OCa4qJaDWUMnjTUt14NICuwGV9bype+q9dorsogyhnQEO4rDcaFdKxmjmoV+
agEy1JX4jR6iTaKmWYgIIXy6gMnHmTCCBbIwggSaoAMCAQICCkSGTToAAAAB174wDQYJKoZI
hvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsT
GEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENB
IDIwMDcwHhcNMTMwNzMwMTExNTA4WhcNMTkwNjMwMjM1OTU5WjBZMQswCQYDVQQGEwJERTET
MBEGA1UEChMKRnJhdW5ob2ZlcjEMMAoGA1UECxMDU0lUMQ8wDQYDVQQLEwZQZW9wbGUxFjAU
BgNVBAMTDUhlbmsgQmlya2hvbHowggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDj
tnr/To9XMlYudCBG2zL6U9stsuWyzIHvJ7al9p1tQakgTYiwTdX5/jsNA1JeHj+TJhzThxh7
nyBfONgy0EUgv835UJw5j4Tknlp5HdU39GMqEdAPd1791E50slOnKpGEjQwd8h6Cw73eF4YN
1QYlfbeoGPt+Tb1z+RUoauQto0atHhnU0rLX1mQ6tZXMMZ9FZcFgC7oVmwtwbK8URIVIlaHo
lGCgOfWfgHxSQICRr9j7kT25xHJ+oimXCb0lIyBuSKAJzo/OHFhIx9cNNGlAwzaynUhU8I1B
6vr9M580bCCEzRSOXzJOFxkhDaX+PinaHxa7SnQAgxlWvckXTEmPAgMBAAGjggJsMIICaDAO
BgNVHQ8BAf8EBAMCBDAwKgYDVR0RBCMwIYEfaGVuay5iaXJraG9sekBzaXQuZnJhdW5ob2Zl
ci5kZTAdBgNVHQ4EFgQUZTNsNue6lgNe5EoFiD4xR0w8XsIwHwYDVR0jBBgwFoAUTx2viMpt
uKocCfnF0RHtWbST+gswdQYDVR0fBG4wbDBqoGigZoYxaHR0cDovL2NybC5wa2kuZnJhdW5o
b2Zlci5kZS9maGctdXNlci1jYS0yMDA3LmNybIYxaHR0cDovL2NybC5mcmF1bmhvZmVyLXBr
aS5kZS9maGctdXNlci1jYS0yMDA3LmNybDCCAQoGCCsGAQUFBwEBBIH9MIH6MD4GCCsGAQUF
BzAChjJodHRwOi8vY2VydC5wa2kuZnJhdW5ob2Zlci5kZS9maGctdXNlci1jYS0yMDA3LmNl
cjA+BggrBgEFBQcwAoYyaHR0cDovL2NlcnQuZnJhdW5ob2Zlci1wa2kuZGUvZmhnLXVzZXIt
Y2EtMjAwNy5jZXIwOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNlci1jYS0yMDA3Lm9jc3Au
cGtpLmZyYXVuaG9mZXIuZGUvMDsGCCsGAQUFBzABhi9odHRwOi8vZmhnLXVzZXItY2EtMjAw
Ny5vY3NwLmZyYXVuaG9mZXItcGtpLmRlLzAfBgNVHSUEGDAWBgorBgEEAYI3CgMEBggrBgEF
BQcDBDBEBgNVHSAEPTA7MDkGCysGAQQBhgpQAwEBMCowKAYIKwYBBQUHAgEWHGh0dHA6Ly9w
a2kuZnJhdW5ob2Zlci5kZS9jcC8wDQYJKoZIhvcNAQEFBQADggEBACzw+XqMZ39YLL77+Pmq
ELSv8Ioyy9CXbsaYYsXEjKLGKvQix4o8MANvpoT6iyrDrqreaofsUd0YhdXd2PUJVZ92ujTA
BMq6fMJGvrty95zwW0lX0SWYqcSobX3mmW4D9nQpDEPEJGQ095kk3SzAFYO7ZHj9Srt1G2hq
UovZP5/aYk+CpYbml+uYlU4Ux/KtYD66k9I9YFCiHKpzNxgoKlzDlkZ2a2uRPYKBFqBqKRee
5TM1DB47l89K1xw3eUWcxcwjusZc2z6EZqk8CgyRXz+m+zK5LCnvSf+1nuR9T5OcmiPwJgpO
8qw3Yoer628t6NfTkz/a49vUgtSlq3kNURsxggN7MIIDdwIBATB1MGcxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpGcmF1bmhvZmVyMSEwHwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQ
S0kxIDAeBgNVBAMTF0ZyYXVuaG9mZXIgVXNlciBDQSAyMDA3AgoVyCUOAAAAAgijMAkGBSsO
AwIaBQCgggHbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MDIwMjE0MzkzN1owIwYJKoZIhvcNAQkEMRYEFP7aGbTFnTTMtQP6BYefLaTh7DJvMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYQG
CSsGAQQBgjcQBDF3MHUwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAf
BgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBV
c2VyIENBIDIwMDcCCkSGTToAAAAB174wgYYGCyqGSIb3DQEJEAILMXegdTBnMQswCQYDVQQG
EwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3Jh
dGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVzZXIgQ0EgMjAwNwIKRIZNOgAAAAHXvjAN
BgkqhkiG9w0BAQEFAASCAQCD4463ddKZuMADY48uiXsvMbn3wLs5QFdB+UnimOqQp9QIyLXN
mpygy7VxEBzcnUDJc4y5TCsW6QFxS4NdcTw/zDvyaliCXg0Ccs0EEl9kchqtWJmAo1elgYtP
tVgEOAtbUB37ZHKr16s9TufK5TXNAyCHJWOzkq4kqVypuPJrRxXJTshsyPXIDjpuOyVBowZj
ITJ8YdqlLtAZJvaR2pdbTOwBAgMVX4QVcRdD4mSlRtr6GTuC8MF2oqrnqP0FT0ysgFVsUj+3
e2bnWmI77NnqYsS7cYBJeuMpyE3s8Wd0YB7skHMV9Y6631sc/2pA4fUXKofUWaFpZ9kvMQca
6p2jAAAAAAAA
--------------ms030102060100000408080405--


From nobody Mon Feb  2 08:38:16 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9E271A6F5D for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 08:38:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 K1cbnuRkG1kN for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 08:38:13 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A1C1A8734 for <sacm@ietf.org>; Mon,  2 Feb 2015 08:38:05 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id kq14so84369128pab.0 for <sacm@ietf.org>; Mon, 02 Feb 2015 08:38:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=7RdfSHwLxqFUEqn9GIrZZEO4ptQigTJpwDnClm3tDyE=; b=c34CcevTCtE3JY27NnVubQ1W/jBDIHEV0Yl5C1Czvf20gaRQ5uSFjAvrXd/L75ju0r 2r3Emtc3BarC3pz2WQ/DgAcXTioMSPEVgyQ85e8ybyoNG7ByJueoTIuQ7VJFbV/6FL/9 bfgCGmXCCSVEBMDMMs2UbJ2ZVuWml7ue74oXh6SGz9Ebq1gpujyzGgproA8EU/+v9m4j 8+YYM7c8+XTqS7k8ivbPIq/0WMpzeZFEb0SVLlM4qEnMKst9aAffHmM+AMgdimc4r4OV OjUG62DUeWv0Ek1stjgmDgkUKrWIqNjxBF/J508G2Vxcyxk8FW5BIIoCLnzH6oIXfMOZ Pk9g==
X-Received: by 10.66.193.33 with SMTP id hl1mr30662883pac.141.1422895084717; Mon, 02 Feb 2015 08:38:04 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:1c3a:8355:af9e:9beb? ([2602:306:3406:4f00:1c3a:8355:af9e:9beb]) by mx.google.com with ESMTPSA id do2sm19280265pbc.23.2015.02.02.08.38.02 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 08:38:03 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <D52D17A9-5915-4EB0-BD4A-938C5B2BB5D7@gmail.com>
Date: Mon, 2 Feb 2015 10:37:53 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/I_es8Qx2oHTqcwkA81Zgp_j-eX8>
Subject: [sacm] Endpoint ID Design Team Notes: 2015-01-30
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 16:38:16 -0000

SACM Endpoint ID Design Team Notes
2015-01-30
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

Agenda:

	* Reminder:
		- WebEx Chat and SACM Jabber Room
		- Recording will be (is) enabled
	* Note takers?
	* Endpoint ID Example Continued
		- Review cryptographic information from Lisa, Cliff, =
Henk
		- Discuss ID information from BIOS software
		- Wrap up temporal data discussion, if needed
		- Providing prvenance information
	* Next Steps

Attendees:
	Adam Montville (SACM WG Host)
	David Waltermire
	Carolin Latze
	Charles Schmidt
	Chris Inacio
	Clifford Kahn
	Danny Haynes
	Henk Birkholz
	Jim Bieda (Call-in User_8)
	Lisa Lorenzin
	Ron Colvin (Call-in User_1)

Overview
=3D=3D=3D=3D=3D=3D=3D=3D
We changed up the priority of the agenda so that we could consider ID =
attribute "covered", so Lisa, Cliff, and Henk provided a five-minute =
(each) overview of the areas they were going to research.


Amended, Ongoing Notes
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Scenarios:

	- Scenario A: Software on an endpoint is asserting posture =
relating to the endpoint's software inventory and configuration.

Endpoint Identity Assertion
---------------------------

	* All endpoint attributes can be used to establish identity
	* We are defining a core set of (primary) attributes that can be =
used to assert identity in a consistent fashon
		- High level of assurance, attributes can be =
authenticated
	* Other (secondary) attributes can be used to check an identity =
assertion or to further define the endpoint's identity (e.g. =
configuration, software inventory, capability)


Attribute/value pairs
---------------------

	Identity attributes (used to determine what the endpoint is; to =
be provided regardless of other posture attributes):

		* Certificates (e.g., device, user, drive, other =
hardware)
			- Device mandatory if available on device; =
favored by consumers of the assertion
			- Others if available as associated with the =
session
			- Use whole cert or some aspect (e.g., public =
key)
	=09
		* Hostname(s) - configured on the device; may be =
multiple and possibly of different kinds
			- Consider how to specify type: multiple =
attributes for each type or type qualifier
	=09
		* FQDN(s) (if available); some hosts may have multiple; =
also list DNS aliases
			- Sourced from the DNS infrastructure
			- Think abou the security considerations of =
insecure DNS deployments
	=09
		* Interface(s) (comprehensive, if possible)
			- MAC address(es)
			- IP address(es)
				- Including additional IPs assigned to =
the interface
			- Interfaces may be nested (e.g., overlay =
networks - VLANs) - NOTE: Need to verify that standardized methods are =
available to do this.
	=09
		* Other cryptographic information (e.g., IPSec Key-hash, =
HIP-HIT (RFC4423, 5201), 802.1AR)
			- NOTE: Investigate options to determine if they =
should be included as primary attributes; post a summary of how to use =
these specs
				- Cliff: HIP-HIT
					- Experimental implementation at =
the moment; not a lot of adoption
					- ID is a public key; an =
endpoint can have more than one
					- A public key might be a good =
identifier type in general for SACM; public keys tend to exist, even =
when a certificate doesn't (e.g. SSH)
				- Lisa: IPSec Security Associations (SA)
					- The SA contains the IPSEC keys =
and what algorithms are in use
					- Unable to differentiate by =
source IP address
					- Keys can rotate, and may be =
less useful as a result				=09
					- Likely not a primary identity =
attribute, but likely useful to include as an aspect of posture.
				- Henk: 802.1AR
					- Appendix B in specification =
discusses use of TPM
					- The standard's intent is to =
support unattended operation
					- A strong, globally unique =
identifier (re: iDevID - preinstalled; lDevID - enterprise defined).
					- lDevID can be generated =
specifically for SACM uses
					- Any xDevID has to ahve a =
certificate.  Could a public key from the certificate be used as the =
identifier?
					- How would a SACM component =
know of the ID?  It could be collected from both the endpoint as well as =
the device making a network access control decision.
					- The secret (e.g. certificate) =
does not need to be hardware rooted
					- How widely is this =
implemented?  About 6 years old.  Many infrastructure vendors have =
implementations, but not much use has been seen.
				- Other notes:
					- To include public keys, we =
need to discuss: what algorithm was used and the intended use of the key =
as data points?  Need to consider authentication using private keys.
	=09
		* Tool-specific identitier - provided by the software =
making the assertion
			- SHOULD be provided
			- May be session scoped if the tool is not able =
to distinguish an endpoint across sessions
			- May be omitted if the tool is unable to =
distinguish the endpoint across multiple assertions

		* Identification information from bios/firmware (e.g., =
serial numbers, asset tags, VM id) that can be queried on the device =
using softare. NOTE: Need to discuss more.
			- Assets are compositional.  Some components may =
have specific identifiers.  It would be useful to indicate which =
component has a specific identifying attribute.
			- Information should be made available by all =
manufacturers
			- If available should be provided as an =
attribute


Temporal Data
-------------

A timestamp indicating when the observation is made for a given AVP:

	* If periodic, a timestamp at present time
	* If event-based, an interval last-change to present time
	* A timestamp is included on an attribute-by-attribute basis

For information that changes frequently having the ability to poll and =
represent the poll interval is beneficial. =20

Time to Live (TTL) values provide an indication of when a given aspect =
of state will change.  Provide when naturally occurring (e.g., a tool =
will know when the DHCP lease expires). MAY be provided if applicable.

	- Do not include in current model unless we have a good use =
case.



Provenance Data
---------------

	DISUCSS: Chain of custody considerations

		* A timestamp indicating when the assertion was received =
- consumer (e.g., collector, borker, repo)

		* Think about compositional model of assertions - =
Asserting additional details related to another assertion

	The SACM component that made the assertion - the identity of the =
software providing the information
		- An assertion of the identity of the software used =
(e.g., vendor, product, version, etc.)
		- The instance of the software (e.g., the device the =
software was run on, the installation of the software) - could be an =
endpoint identity assertion as well - may be the same as the endpoint or =
different if external to the endpoint
			- Reuse the identity information from the =
authentication to establish the identity of the reporter.
		- Cryptographic ifnormation that can be used to =
authenticate the provenance assertion
		- (FOR CONTINUED DISCUSSION) Some questions on the call =
about if providing provenance information is required in all cases; =
self-reported - may/should; other-reported - must
=09
	The endpoint attribute assertions (if any) on which the =
assertion is based
=09
	Information about the method used to derive the assertion


Other Data
----------

	Endpoint uniquely identified?  True or false; very subjective; =
ask larger WG


Other Considerations
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Write security considerations speaking to=20
		- uniqueness of any identifying attribute - address =
malicious or accidental cases where uniqueness may be compromised
		- Issues relating to compromise of endpoint attributes =
(lying endpoints) - Perhaps slandering other endpoints as a result

	* When authenticating as part ofa SACM posture exchange, the =
authentication information should be incorporated into an endpoint =
identity assertion.  Should be a MUST for any endpoint that has the =
capability to authenticate.

Future Discussion Points
------------------------

	* Discuss identification information from bios/firmware (e.g. =
serial numbers, asset tags, VM id) that can be queried on the device =
using software



NEXT STEPS (Agenda Items to track)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Coordinate Information Model updates on list
	* Provenance discussion at next meeting (February 6)





From nobody Mon Feb  2 08:39:11 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 293C11A6F5D for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 08:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 SfpBfhGKkdP2 for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 08:39:09 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6E6B1A1B95 for <sacm@ietf.org>; Mon,  2 Feb 2015 08:39:08 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id kx10so84223875pab.11 for <sacm@ietf.org>; Mon, 02 Feb 2015 08:39:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=75nV8eC4pNtghICue8lw49fcYCkcFsxwEakglp2fVTQ=; b=k5Jp996nZ4TYXyHIHE35dpf4rLDL4P2uYFM9UFdYRs02wk7WK0q/oNFYCeLVWO5PuV gTWvwzOkSX3ohHX5gY6cp7N7zVWzXzKBMKbhS2ikGa9lxgO2SiK0JKgBNwJs6ERVtAHI ms9ht2ACwjRhW7SpxvynwDWtSrxgalL3Q5xugJoJLd/AfeQWEgsJr0b/ZNfvF5tSVfv6 TmbIalcIQYEaalnF9rf98mBbT2xS45Oz4NFl66WKWkKD07HaQ1H1h+ucMWBhzcFZGfZn ghU/YxyQRAOdS+FGUIRhrUtm9dVoHmlmBNytGy6cQpR7zOCZQ8++f8yjkH7s8LywLNpa O22Q==
X-Received: by 10.68.190.101 with SMTP id gp5mr30735908pbc.30.1422895148116; Mon, 02 Feb 2015 08:39:08 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:1c3a:8355:af9e:9beb? ([2602:306:3406:4f00:1c3a:8355:af9e:9beb]) by mx.google.com with ESMTPSA id pp6sm19268044pdb.92.2015.02.02.08.39.06 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 08:39:07 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_039B23EC-9AAA-43F3-9DB8-7A965B99FD0F"
Message-Id: <BE86FA5E-AAB9-4FB5-BF2A-04AE9AC8CD7D@gmail.com>
Date: Mon, 2 Feb 2015 10:38:57 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/pKiNW-zXkCgeKOu4HCg5KHMo80M>
Subject: [sacm] Endpoint ID Design Team Recording Available: 2015-01-30
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 16:39:10 -0000

--Apple-Mail=_039B23EC-9AAA-43F3-9DB8-7A965B99FD0F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The recording from last Friday=E2=80=99s meeting is available:

=
https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0 =
<https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0>


Regards,

Adam=

--Apple-Mail=_039B23EC-9AAA-43F3-9DB8-7A965B99FD0F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">The recording from last Friday=E2=80=99s =
meeting is available:</div><div class=3D""><br class=3D""></div><a =
href=3D"https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu=
_a?dl=3D0" =
class=3D"">https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3=
bRu_a?dl=3D0</a><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Regards,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Adam</div></body></html>=

--Apple-Mail=_039B23EC-9AAA-43F3-9DB8-7A965B99FD0F--


From nobody Mon Feb  2 08:59:33 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3590D1A8724 for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 08:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 lqPDWWh4Pb33 for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 08:59:28 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E92361A8725 for <sacm@ietf.org>; Mon,  2 Feb 2015 08:59:27 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id lj1so84452518pab.6 for <sacm@ietf.org>; Mon, 02 Feb 2015 08:59:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=6KxHRESlnd/2ZZY0nr9goGuidWla51FkuA2UWSXBwEU=; b=xYkO07NKz89m5BEpaow2nayFcnCvm7tcA9ToQbcsBY5soluKo5BvkPYwbSgpRqOjkN dRzd2oYi60HLx6kO9FPZ1nP0C2g5gf308b/PLEWV94yptSB4iqycCpUsuzbUKXPW7Q6R KgZXMQcOlzfvRVG4t5hLc/Eag7OdnvoIgjz9NYP2ag2RIYewXTXzXFt76R5b9skQRQ3O DznnDMO1ufrUvWvdmxEC1grcZEhkrieygkYenheAVg+/M0DRZMKAHvmJmxWvCiIb+Bd5 PRoax9DGhB+Npknq3ry3MgnZ8ym4+fWYxZ4pyEzsIoxIKBXJA5h44xazT+wpfXvGytlk fkrA==
X-Received: by 10.66.186.208 with SMTP id fm16mr30529872pac.62.1422896366101;  Mon, 02 Feb 2015 08:59:26 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:1c3a:8355:af9e:9beb? ([2602:306:3406:4f00:1c3a:8355:af9e:9beb]) by mx.google.com with ESMTPSA id e16sm1989754pdk.29.2015.02.02.08.59.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 08:59:25 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9EA39291-666D-4ED5-98F0-E2E9598D25EC"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: "Adam W. Montville" <adam.w.montville@gmail.com>
In-Reply-To: <CY1PR0601MB1355D4BC01656A8B94FEFC0DB7340@CY1PR0601MB1355.namprd06.prod.outlook.com>
Date: Mon, 2 Feb 2015 10:59:14 -0600
Message-Id: <E0CAA254-FE9C-4235-AB1B-9211A0CE19B8@gmail.com>
References: <CY1PR0601MB1355D4BC01656A8B94FEFC0DB7340@CY1PR0601MB1355.namprd06.prod.outlook.com>
To: Clifford Kahn <cliffordk@pulsesecure.net>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/rXDcEo89Gcw1u-bJ2hzzExP4oTA>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] The W3C PROV model of provenance is relevant to SACM
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 16:59:30 -0000

--Apple-Mail=_9EA39291-666D-4ED5-98F0-E2E9598D25EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jan 25, 2015, at 10:28 AM, Clifford Kahn =
<cliffordk@pulsesecure.net> wrote:
>=20
> Process-Centered Provenance for SACM
> For PROV, process-centered provenance is the series of =
=E2=80=9Cactivities=E2=80=9D that produced an =E2=80=9Centity=E2=80=9D =
(an object). Process-centered provenance could be the revision history, =
for example. Each step in the revision history would be associated with =
an =E2=80=9Cagent=E2=80=9D that made the revision.=20
> =20
> In SACM conversations we have been using the term =E2=80=9Cmethod=E2=80=9D=
. It is a simplified version of process-centered provenance. I think it =
is enough for SACM, for the initial set of RFCs.
> =20
> Where PROV has a class Activity, I suggest that SACM have a class =
Method.
> =20
>                         +---------+______>______+-------+=20
>                         |Endpoint |*           1|Summary|
>                         |Attribute|             +-------+          =20
>      __________________1|Assertion|                 |1
>     | <was-generated-by +---------+                 |
>    1|                                               |
> +--------+__________________________________________|
> | Method |1          <was-generated-by
> +--------+
>=20
> An example of Method could be =E2=80=9CReporting all the SWID tags =
found on an endpoint, but with no attempt to make sure the list is =
accurate or complete=E2=80=9D.
> =20
> Why make Method be a class?=20
> (a)    Because in PROV, Activity is a class, and I believe in the =
=E2=80=9Cuse good stuff=E2=80=9D theory of progress. In the future, =
Method might be extended in potent ways. One might want to keep an audit =
trail of who devised and revised a method.
> (b)   Because if Method is a class, that suggests that the =
was-generated-by relations might be navigable in the reverse direction. =
A component might be able to ask questions like =E2=80=9CWho is using =
broken method X?=E2=80=9D or =E2=80=9CWhat methods are in use?=E2=80=9D
> (c)    Because it feels right.=20
>=20
> What do others think?

I very much like the idea of having a Method class.  This could very =
well be something that requires =E2=80=9Coperational curation=E2=80=9D =
post-specification, much like what we=E2=80=99ve been thinking =
capabilities would be like in the infrastructure.  In fact, Methods may =
well be closely linked to =E2=80=9Ccapabilities=E2=80=9D.=

--Apple-Mail=_9EA39291-666D-4ED5-98F0-E2E9598D25EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jan 25, 2015, at 10:28 AM, Clifford Kahn &lt;<a =
href=3D"mailto:cliffordk@pulsesecure.net" =
class=3D"">cliffordk@pulsesecure.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><h2 style=3D"margin: =
2pt 0in 0.0001pt; line-height: 18.373332977294922px; page-break-after: =
avoid; font-size: 13pt; font-family: 'Calibri Light', sans-serif; color: =
rgb(46, 116, 181); font-weight: normal; font-style: normal; =
font-variant: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D"">Process-Centered Provenance for SACM<o:p =
class=3D""></o:p></h2><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">For PROV, =
process-centered provenance is the series of =E2=80=9Cactivities=E2=80=9D =
that produced an =E2=80=9Centity=E2=80=9D (an object). Process-centered =
provenance could be the revision history, for example. Each step in the =
revision history would be associated with an =E2=80=9Cagent=E2=80=9D =
that made the revision.<span =
class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">In SACM conversations =
we have been using the term =E2=80=9Cmethod=E2=80=9D. It is a simplified =
version of process-centered provenance. I think it is enough for SACM, =
for the initial set of RFCs.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">Where PROV has a class =
Activity, I suggest that SACM have a class Method.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-size:=
 10pt; font-family: 'Courier New';" class=3D"">&nbsp;</span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-size: =
10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;+---------+______&gt;______+-------+&nbsp;<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-size:=
 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;|Endpoint =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1|Summary|<o:p class=3D""></o:p></span></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;|Attribute|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;<o:p class=3D""></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span=
 style=3D"font-size: 10pt; font-family: 'Courier New';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;__________________1|Assertion|&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; |1<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp;&nbsp; | =
&lt;was-generated-by =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p class=3D""></o:p></span></div><div=
 style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-size: =
10pt; font-family: 'Courier New';" class=3D"">&nbsp;&nbsp; =
1|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<br =
class=3D"">+--------+__________________________________________|<br =
class=3D"">| Method |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&lt;was-generated-by<br class=3D"">+--------+<br =
class=3D""><br class=3D""></span><o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D"">An example of Method could =
be =E2=80=9CReporting all the SWID tags found on an endpoint, but with =
no attempt to make sure the list is accurate or complete=E2=80=9D.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">Why make Method be a =
class?<span class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt 0.5in; =
line-height: 15.546667098999023px; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-indent: =
-0.25in;" class=3D""><span class=3D"">(a)<span style=3D"font-style: =
normal; font-variant: normal; font-weight: normal; font-size: 7pt; =
line-height: normal; font-family: 'Times New Roman';" =
class=3D"">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span>Because in =
PROV, Activity is a class, and I believe in the =E2=80=9Cuse good =
stuff=E2=80=9D theory of progress. In the future, Method might be =
extended in potent ways. One might want to keep an audit trail of who =
devised and revised a method.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt 0.5in; line-height: =
15.546667098999023px; font-size: 11pt; font-family: Calibri, sans-serif; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; text-indent: -0.25in;" =
class=3D""><span class=3D"">(b)<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';" class=3D"">&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span>Because if =
Method is a class, that suggests that the was-generated-by relations =
might be navigable in the reverse direction. A component might be able =
to ask questions like =E2=80=9CWho is using broken method X?=E2=80=9D or =
=E2=80=9CWhat methods are in use?=E2=80=9D<o:p class=3D""></o:p></div><p =
class=3D"MsoListParagraphCxSpLast" style=3D"margin: 0in 0in 8pt 0.5in; =
line-height: 15.546667098999023px; font-size: 11pt; font-family: =
Calibri, sans-serif; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-indent: =
-0.25in;"><span class=3D"">(c)<span style=3D"font-style: normal; =
font-variant: normal; font-weight: normal; font-size: 7pt; line-height: =
normal; font-family: 'Times New Roman';" =
class=3D"">&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span>Because it =
feels right.<span class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></p><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D"">What do others =
think?</div></div></blockquote></div><br class=3D""><div class=3D"">I =
very much like the idea of having a Method class. &nbsp;This could very =
well be something that requires =E2=80=9Coperational curation=E2=80=9D =
post-specification, much like what we=E2=80=99ve been thinking =
capabilities would be like in the infrastructure. &nbsp;In fact, Methods =
may well be closely linked to =E2=80=9Ccapabilities=E2=80=9D.</div></body>=
</html>=

--Apple-Mail=_9EA39291-666D-4ED5-98F0-E2E9598D25EC--


From nobody Mon Feb  2 10:57:02 2015
Return-Path: <gunnar.engelbach@threatguard.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8F31A882A for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 10:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 CbE5cFo_KURb for <sacm@ietfa.amsl.com>; Mon,  2 Feb 2015 10:56:57 -0800 (PST)
Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65A771A0372 for <sacm@ietf.org>; Mon,  2 Feb 2015 10:56:57 -0800 (PST)
Received: by mail-qc0-f178.google.com with SMTP id b13so31780047qcw.9 for <sacm@ietf.org>; Mon, 02 Feb 2015 10:56:56 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=mRNxAttME3NdLvAJ1hSpam5jZQVYbPhoSLpqnVaW79g=; b=YMZ+n4jWz5aAoPPlefu8iroE53wtfz+HVwxd09aJZ5ReerXkw49JZN8o3P9gtqMmDb /89QEEy2jFcbB5TO9R5cUeu/Cqi/PoZ4Y7jyam1DaCITCDS0y8rmxw++oFLt49pO4l1L VUppFOxKdPHJNmd0c7DmTlO52XfGS9t7dt5MWYRrKH3jDu6DjQInbX2BJiKp9YeXW35D qriy5KuOn6nmq1OIvL+ueq0ah1rSranWZn+wY8uGbNBA7Yu5HxHpeyetI9lUXTKVhBdY eppFbPs/cyXGrx1RX+DuoWvm4G9BWkRU2/XuHpimHMV6Y/hH3OdCl+5yRsXQfhze9OZh Kc/g==
X-Gm-Message-State: ALoCoQkAGvJGNpUkRqAnazVcvFQIF7J2Z2HYUnsyLLKJ2eVKvPmtCjS+n/6XPdek8CZs6LJVtyMm
X-Received: by 10.224.54.67 with SMTP id p3mr44672908qag.96.1422903416560; Mon, 02 Feb 2015 10:56:56 -0800 (PST)
Received: from [172.16.1.22] (h69-128-196-138.cntcnh.broadband.dynamic.tds.net. [69.128.196.138]) by mx.google.com with ESMTPSA id f5sm19084478qaf.5.2015.02.02.10.56.55 for <sacm@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Feb 2015 10:56:56 -0800 (PST)
From: Gunnar Engelbach <gunnar.engelbach@threatguard.com>
X-Google-Original-From: Gunnar Engelbach <Gunnar.Engelbach@ThreatGuard.com>
Message-ID: <54CFC879.8050504@ThreatGuard.com>
Date: Mon, 02 Feb 2015 13:56:57 -0500
Organization: ThreatGuard, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/e-978xb4li88LgN8moOVjEI1JAM>
Subject: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 18:57:00 -0000

As of late I haven't been as engaged in this working group so I have 
likely missed decision points that render the following observations 
moot, but there have been some things I've seen on the list that I felt 
I needed to pause to point out.


1) Scope creep.
There has been some good work going on with items that are important to 
security management, but I have to wonder how many of these are 
completely necessary to standardize the ability to automate a security 
assessment?

In the very simplest case an assessment requires have the ability to 
express the desired state of an endpoint in an automatable format, the 
ability to collect the set of attributes necessary for that computation, 
and the ability to unambiguously interpret the set of attributes values.


As an example, I will pick on I-D -- and the only reason I am using that 
one is because it's the most recent topic I read a message on.

Strictly speaking, it's not necessary to be able to positively identify 
and endpoint in order to automate a security assessment of it. 
Identification does because important when it comes to network management.

Now, recognizing that SACM exists in a world of enterprise management is 
reasonable, but so is the allowance that any component will be needed to 
be replaced with something better in the future.

So this really leads to two questions:

   A) What are the fundamental set of needs for addressing the charter 
of this working group?

   B) Will picking a particular solution now for any of the ancillary 
components lead to a design that makes it harder to replace them later?



2) Some comments I have seen recently imply that the idea that there is 
a known and finite set of endpoint attributes to be collected.  But this 
is only true within the scope of a particular policy[1].  The collection 
of all policies that are applicable to and endpoint determine the final 
set of attributes, and this set will change as the policies are updated 
and new policies are added.

With a couple of additional points:

   A) On any given day a new zero-day exploit can require the collection 
of an endpoint attribute that had not been previously known.

   B) The final set of attributes is not known until the set of 
applicable policies is known.

it seems apparent that security automation is an inherently top-down and 
dynamic process.


3) There has been quite a bit of talk about the data format and 
information model, and I think these conversations are premature.

What enables automated assessments is the ability to express the 
assessment goal in a machine-executable format.  I would go so far as to 
say that this top-level format is the most immutable item in the SACM 
ecosystem.  That is to say, replacing this format in the future will be 
more costly than updating any other part of SACM.

Starting with that assumption, the definition of that top-level format 
should be the starting point and addressing the needs of that is what 
will drive the data and information models.



Comments?


--gun




[1] For the sake of expediency I use the term "policy" to refer to any 
top-level security automation document.  It might be a security 
compliance policy, such as HIPAA or PCI, known vulnerability sweep, 
malware detection, etc.


From nobody Mon Feb  2 11:14:17 2015
Return-Path: <bjoernboesch@gmx.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 009A11A1A42; Mon,  2 Feb 2015 11:13:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level: 
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 VfQtoxJrRgGL; Mon,  2 Feb 2015 11:13:49 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC6DC1A1A46; Mon,  2 Feb 2015 11:13:38 -0800 (PST)
Received: from [192.168.2.105] ([79.246.19.23]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MOw4N-1YKqsp1qkh-006KeN; Mon, 02 Feb 2015 20:13:36 +0100
Message-ID: <54CFCC5F.6080709@gmx.net>
Date: Mon, 02 Feb 2015 20:13:35 +0100
From: "B.-C. Boesch" <bjoernboesch@gmx.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <54BB6D67.6010509@gmx.net> <23D534A9-90E7-45C0-AE78-419617965D15@comcast.net>
In-Reply-To: <23D534A9-90E7-45C0-AE78-419617965D15@comcast.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:D8XI1M81zqUQs/mD82mPNbovlVl+YhAB2M0BxmN6l+yef3I72Gm RBmqa8MIcSSPBmRuo7euT1KgU7SC6+22Hjsqb0m6UnLMWHWBoauPK3DMWFpN6c30gf3rJD9 wxDyLGVHK3wydOcPCfyFxUTkuudUJjmthFo7XtAwkYOgtjMustNP/mZQRiujTXbB4Ky9Six bzZn7HNj623gks1pjxXkw==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/Lg68u9bLAnlI2gbzfw6u5IBhqXk>
Cc: ietf@ietf.org, OPSAWG@ietf.org, Lime@ietf.org, sacm@ietf.org, saag@ietf.org
Subject: Re: [sacm] [OPSAWG] Internet Draft: Standardized Parameterization of Intrusion Detection Entities
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 19:13:51 -0000

Dear David,

thanks for your hint to the SACM WG. I have also posted it within the 
SACM community for any comments, feedback, suggestions, notations, 
hints, recommendations, etc. but haven´t  received any response or 
feedback to the Internet Draft so far. I hope this will change and a 
lively discussion is going to come up.

Kind regards

B.-C. Boesch


Am 02.02.2015 um 18:32 schrieb David Harrington:
> I think similar work is being addressed in the sacm wg.
>
> David Harrington
> ietfdbh@comcast.net
>
>
>
> On Jan 18, 2015, at 3:23 AM, B.-C. Boesch <bjoernboesch@gmx.net> wrote:
>
>> Dear Community,
>>
>> Efficiency of Intrusion Detection Systems (IDS) depends on their configuration and coverage of services. The coverage depends on used IDS with currently vendor-specific configurations. In case of usage of multiple systems the operations could become complex. Individual Communication between management interface and the IDS entities results that current multi-vendor IDS architectures do not interact with each other. They are independent coexistent.
>>
>> The Internet Draft defines data formats and exchange procedures to standardize parametrization information exchange into intrusion detection and response systems from a Manager to an Analyzer.
>>
>> The created Intrusion Detection Parametrization Exchange Format (IDPEF) is intended to be a standard data format to parametrize IDS. The development of this open standardized format and the Intrusion Detection Message Exchange Format (IDMEF) will be enable in combination interoperability among commercial, open source, and research systems, allowing users to mix-and-match the deployment of these systems according to their strong and weak points to obtain an optimal IDS implementation.
>>
>> The most obvious place to implement IDPEF is in the data channel between a Manager and an Analyzer of an IDS within this data channel where the Manager sends the configuration parameters to the Analyzers. But there are other places where the IDPEF can be useful:
>>
>> - Combination of specialized IDS like application-IDS with server-IDS, WLAN-IDS and network-IDS to one functional interacting meta-IDS.
>>
>> - Management of different IDS vendors with one central management interface.
>>
>> - Interaction of different IDS by using IDPEF and IDMEF.
>>
>> - Parametrization backups and restore of parametrized IDS entities.
>>
>> - For a communication between a Manager and a Manager in a multi-stage management architecture.
>>
>> I am happy to invite you to give me feedback, suggestions, notations, hints, recommendations, etc. to improve the Internet Draft. The initial version of the Internet Draft could be found at:
>>
>> http://www.ietf.org/id/draft-boesch-idxp-idpef-00.txt
>>
>> Kind regards,
>>
>> B.-C. Boesch
>>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg


From nobody Tue Feb  3 02:36:29 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5041A00AA for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 02:36:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ueeWKChX-OtV for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 02:36:27 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F3951A0097 for <sacm@ietf.org>; Tue,  3 Feb 2015 02:36:27 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao4FAG+j0FSHCzIm/2dsb2JhbABagmQigS+yOQEBAQEBAQaYLwKBHEMBAQEBAQF8hAwBAQEBAxIoSwQCAQgNCAEMFAkHMhQRAgQBEggaiAsBtHigfQEBAQEGAQEBAQEBARuGBIlDOIMWgRMFjwmKPIU8iEyDPSKDbm+BRH4BAQE
X-IronPort-AV: E=Sophos;i="5.09,512,1418101200"; d="scan'208";a="89915469"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 Feb 2015 05:36:24 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 03 Feb 2015 05:36:23 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Tue, 3 Feb 2015 05:36:22 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Gut Check?
Thread-Index: AQHQPxoIbInSvKW7zUyq9ZBKcrUMyJzeu3hg
Date: Tue, 3 Feb 2015 10:36:21 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com>
References: <54CFC879.8050504@ThreatGuard.com>
In-Reply-To: <54CFC879.8050504@ThreatGuard.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/bcKEaDxCdCK5FPSC5c12l5I4G4k>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 10:36:29 -0000

> -----Original Message-----
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Gunnar Engelbach
> Sent: Monday, February 02, 2015 8:57 PM
>=20
>=20
> 3) There has been quite a bit of talk about the data format and
> information model, and I think these conversations are premature.
>=20
> What enables automated assessments is the ability to express the
> assessment goal in a machine-executable format.  I would go so far as to
> say that this top-level format is the most immutable item in the SACM
> ecosystem.  That is to say, replacing this format in the future will be
> more costly than updating any other part of SACM.
>=20
> Starting with that assumption, the definition of that top-level format
> should be the starting point and addressing the needs of that is what
> will drive the data and information models.
>=20
>=20
>=20
> Comments?
>=20

Gunnar,

Thanks for your comments.=20

Can you clarify - what is the difference between 'that top level format' an=
d the Information Model? I thought (and I believe this was the consensus of=
 the WG) that the IM IS the (protocol-independent) top level format and dat=
a model (which can be expressed in different DMLs) derived from it. What am=
 I missing?=20

Regards,

Dan


From nobody Tue Feb  3 09:03:34 2015
Return-Path: <gunnar.engelbach@threatguard.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28DDF1A1B61 for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 09:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 9yiMA3zRy9Oi for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 09:03:28 -0800 (PST)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7BC21A1B62 for <sacm@ietf.org>; Tue,  3 Feb 2015 09:03:27 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id x3so12342557qcv.3 for <sacm@ietf.org>; Tue, 03 Feb 2015 09:03:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EaQ8q+LyqKwCSJeO5U238HEY3eEH6TEqSyKKLuSloHI=; b=ftZHGmpfUgvAgFx0o42Ya3pw+qfcvlDJq9mUOjLfGKMhG6UFGvs0BkcGuZw8vGCqDp WZbs6ufwFry2wkCMCuynjmL5n6cXc99y5UYFD97mN3hStFJUdzOyyMsEFl6YLrKa7fvh qC4Zx7XuC76sMyuGUoUd5IC0q22iIFG8sKCa7WdrHf3Lp3xsururBKWWn9j3EKmVwz2I i/ZYTootvfa3UImepHUjRADoRgj1ryVoarq8q+st/ngMzgpcwRrnN0MPi59G0R2T+O+h bRS/3qK4XiRuXLwmD7vFdgEHo30nN8/q2pR+vrVQgJYpzmkgi3Trq0yKfe70VxZ+pCjz XKsw==
X-Gm-Message-State: ALoCoQkuKmtKVOzXQZ/eeS+UtS8AqygdwIfphni5sxxqs2Msfxvdr4ss+pkYKuiOE4I5CL/UHJVm
X-Received: by 10.140.94.6 with SMTP id f6mr5513928qge.38.1422983007089; Tue, 03 Feb 2015 09:03:27 -0800 (PST)
Received: from [172.16.1.22] (h69-128-196-138.cntcnh.broadband.dynamic.tds.net. [69.128.196.138]) by mx.google.com with ESMTPSA id e13sm14329582qaw.8.2015.02.03.09.03.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Feb 2015 09:03:26 -0800 (PST)
From: Gunnar Engelbach <gunnar.engelbach@threatguard.com>
X-Google-Original-From: Gunnar Engelbach <Gunnar.Engelbach@ThreatGuard.com>
Message-ID: <54D0FF61.8060608@ThreatGuard.com>
Date: Tue, 03 Feb 2015 12:03:29 -0500
Organization: ThreatGuard, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,  "sacm@ietf.org" <sacm@ietf.org>
References: <54CFC879.8050504@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/FmBxIDpIQ5HRv-CSetaVghHrzZY>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 17:03:31 -0000

On 2/3/2015 5:36 AM, Romascanu, Dan (Dan) wrote:
>
>
>> -----Original Message-----
>> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Gunnar Engelbach
>> Sent: Monday, February 02, 2015 8:57 PM
>>
>>
>> 3) There has been quite a bit of talk about the data format and
>> information model, and I think these conversations are premature.
>>
>> What enables automated assessments is the ability to express the
>> assessment goal in a machine-executable format.  I would go so far as to
>> say that this top-level format is the most immutable item in the SACM
>> ecosystem.  That is to say, replacing this format in the future will be
>> more costly than updating any other part of SACM.
>>
>> Starting with that assumption, the definition of that top-level format
>> should be the starting point and addressing the needs of that is what
>> will drive the data and information models.
>>
>>
>>
>> Comments?
>>
>
> Gunnar,
>
> Thanks for your comments.
>
> Can you clarify - what is the difference between 'that top level format' and the Information Model? I thought (and I believe this was the consensus of the WG) that the IM IS the (protocol-independent) top level format and data model (which can be expressed in different DMLs) derived from it. What am I missing?


Sure, maybe that is the intent.  If so, I totally missed it.

I read every message that comes across this list, and the impression I 
have been getting is that the Information Model and Data Model apply to 
the collection and distribution of endpoint attributes and not to a 
higher level goal that they are in service to.


--gun


>
> Regards,
>
> Dan
>


From nobody Tue Feb  3 09:53:44 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 311DF1A7113 for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 09:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YwrtsZMFhaeZ for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 09:53:40 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5A411A6FFF for <sacm@ietf.org>; Tue,  3 Feb 2015 09:53:40 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEGAJUK0VTGmAcV/2dsb2JhbABagmQigSsEsjwBAQEBAQEGmC8CgR5DAQEBAQEBfIQMAQEBAQMSKEsEAgEIDQQEAQEBChQJBzIUCQgCBAESCBqICwG2JaERAQEBAQEFAQEBAQEBARuGBIlDOAaDEIETBY8MhVyEYYU9C4hDgz0ig25vgUR+AQEB
X-IronPort-AV: E=Sophos;i="5.09,514,1418101200"; d="scan'208";a="102499628"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Feb 2015 12:53:39 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 03 Feb 2015 12:53:39 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Tue, 3 Feb 2015 18:53:37 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Gut Check?
Thread-Index: AQHQPxoIbInSvKW7zUyq9ZBKcrUMyJzeu3hggADAz4D//7ndQA==
Date: Tue, 3 Feb 2015 17:53:37 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C980385@AZ-FFEXMB04.global.avaya.com>
References: <54CFC879.8050504@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com> <54D0FF61.8060608@ThreatGuard.com>
In-Reply-To: <54D0FF61.8060608@ThreatGuard.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/hE1pv_gMrtzk2rH4AhNnsQZ8JXA>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 17:53:42 -0000

> -----Original Message-----
> From: Gunnar Engelbach [mailto:gunnar.engelbach@threatguard.com]
> Sent: Tuesday, February 03, 2015 7:03 PM
> To: Romascanu, Dan (Dan); sacm@ietf.org
> Subject: Re: [sacm] Gut Check?
>=20
>=20
>=20
> On 2/3/2015 5:36 AM, Romascanu, Dan (Dan) wrote:
> >
> >
> >> -----Original Message-----
> >> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Gunnar
> >> Engelbach
> >> Sent: Monday, February 02, 2015 8:57 PM
> >>
> >>
> >> 3) There has been quite a bit of talk about the data format and
> >> information model, and I think these conversations are premature.
> >>
> >> What enables automated assessments is the ability to express the
> >> assessment goal in a machine-executable format.  I would go so far as
> >> to say that this top-level format is the most immutable item in the
> >> SACM ecosystem.  That is to say, replacing this format in the future
> >> will be more costly than updating any other part of SACM.
> >>
> >> Starting with that assumption, the definition of that top-level
> >> format should be the starting point and addressing the needs of that
> >> is what will drive the data and information models.
> >>
> >>
> >>
> >> Comments?
> >>
> >
> > Gunnar,
> >
> > Thanks for your comments.
> >
> > Can you clarify - what is the difference between 'that top level format=
' and
> the Information Model? I thought (and I believe this was the consensus of
> the WG) that the IM IS the (protocol-independent) top level format and da=
ta
> model (which can be expressed in different DMLs) derived from it. What am=
 I
> missing?
>=20
>=20
> Sure, maybe that is the intent.  If so, I totally missed it.
>=20
> I read every message that comes across this list, and the impression I ha=
ve
> been getting is that the Information Model and Data Model apply to the
> collection and distribution of endpoint attributes and not to a higher le=
vel
> goal that they are in service to.
>=20
>=20

Let me try to focus better my question. What is missing from the current IM=
 proposal in order to reach that 'higher level goal'?

Thanks and Regards,

Dan


From nobody Tue Feb  3 10:01:29 2015
Return-Path: <david.waltermire@nist.gov>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDB9C1A711A for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 10:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ji8yPEzzZC5z for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 10:01:20 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0755.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:755]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0C701A1BFF for <sacm@ietf.org>; Tue,  3 Feb 2015 10:01:19 -0800 (PST)
Received: from DM2PR09MB0224.namprd09.prod.outlook.com (25.160.92.146) by DM2PR09MB0223.namprd09.prod.outlook.com (25.160.92.145) with Microsoft SMTP Server (TLS) id 15.1.75.20; Tue, 3 Feb 2015 18:00:56 +0000
Received: from DM2PR09MB0224.namprd09.prod.outlook.com ([25.160.92.146]) by DM2PR09MB0224.namprd09.prod.outlook.com ([25.160.92.146]) with mapi id 15.01.0075.002; Tue, 3 Feb 2015 18:00:56 +0000
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Gut Check?
Thread-Index: AQHQPxoNneoM+vHjgUy6Mmpx/pZCDJzevEuAgABsKoCAAA4CgIAAAZPw
Date: Tue, 3 Feb 2015 18:00:56 +0000
Message-ID: <DM2PR09MB0224E36C3B7EC76F5F65A652F03D0@DM2PR09MB0224.namprd09.prod.outlook.com>
References: <54CFC879.8050504@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com> <54D0FF61.8060608@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C980385@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C980385@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.227.107]
authentication-results: avaya.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0223;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0223;
x-forefront-prvs: 0476D4AB88
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(51704005)(377454003)(24454002)(35774003)(479174004)(2900100001)(2950100001)(2501002)(107886001)(15975445007)(102836002)(19580395003)(19580405001)(40100003)(122556002)(76176999)(74316001)(87936001)(33656002)(561944003)(86362001)(93886004)(62966003)(76576001)(92566002)(99286002)(54356999)(77156002)(46102003)(66066001)(50986999)(106116001)(2656002)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0223; H:DM2PR09MB0224.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2015 18:00:56.2233 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0223
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/6CggN9iXkZ4Im1E8yoP7asBYA-Q>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 18:01:26 -0000

Comments inline.

-----Original Message-----
From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Tuesday, February 03, 2015 12:54 PM
To: Gunnar Engelbach; sacm@ietf.org
Subject: Re: [sacm] Gut Check?



> -----Original Message-----
> From: Gunnar Engelbach [mailto:gunnar.engelbach@threatguard.com]
> Sent: Tuesday, February 03, 2015 7:03 PM
> To: Romascanu, Dan (Dan); sacm@ietf.org
> Subject: Re: [sacm] Gut Check?
>=20
>=20
>=20
> On 2/3/2015 5:36 AM, Romascanu, Dan (Dan) wrote:
> >
> >
> >> -----Original Message-----
> >> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Gunnar=20
> >> Engelbach
> >> Sent: Monday, February 02, 2015 8:57 PM
> >>
> >>
> >> 3) There has been quite a bit of talk about the data format and=20
> >> information model, and I think these conversations are premature.
> >>
> >> What enables automated assessments is the ability to express the=20
> >> assessment goal in a machine-executable format.  I would go so far=20
> >> as to say that this top-level format is the most immutable item in=20
> >> the SACM ecosystem.  That is to say, replacing this format in the=20
> >> future will be more costly than updating any other part of SACM.
> >>
> >> Starting with that assumption, the definition of that top-level=20
> >> format should be the starting point and addressing the needs of=20
> >> that is what will drive the data and information models.
> >>
> >>
> >>
> >> Comments?
> >>
> >
> > Gunnar,
> >
> > Thanks for your comments.
> >
> > Can you clarify - what is the difference between 'that top level=20
> > format' and
> the Information Model? I thought (and I believe this was the consensus=20
> of the WG) that the IM IS the (protocol-independent) top level format=20
> and data model (which can be expressed in different DMLs) derived from=20
> it. What am I missing?
>=20
>=20
> Sure, maybe that is the intent.  If so, I totally missed it.
>=20
> I read every message that comes across this list, and the impression I=20
> have been getting is that the Information Model and Data Model apply=20
> to the collection and distribution of endpoint attributes and not to a=20
> higher level goal that they are in service to.
>=20
>=20

Let me try to focus better my question. What is missing from the current IM=
 proposal in order to reach that 'higher level goal'?

[daw: I would also like to know what is missing from the charter, use cases=
, and requirements to define these higher-level goals?]

Thanks and Regards,

Dan

_______________________________________________
sacm mailing list
sacm@ietf.org
https://www.ietf.org/mailman/listinfo/sacm


From nobody Tue Feb  3 11:59:03 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7F941A87F1 for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 11:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 6ocs96Kydv9r for <sacm@ietfa.amsl.com>; Tue,  3 Feb 2015 11:58:45 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0644.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::644]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B38771A882E for <sacm@ietf.org>; Tue,  3 Feb 2015 11:58:44 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) with Microsoft SMTP Server (TLS) id 15.1.75.20; Tue, 3 Feb 2015 19:58:14 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Tue, 3 Feb 2015 19:58:14 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Comments on Network Interface
Thread-Index: AQHP+GodCKGp54AXtUubmJnUXWgtPpzcZT1QgAAFQFCAAZDRgIAB53NQ
Date: Tue, 3 Feb 2015 19:58:14 +0000
Message-ID: <CY1PR0601MB1355A2CEE12A57BD5DABACF4B73D0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <54590118.9050702@sit.fraunhofer.de> <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com> <54CF8C29.3050307@sit.fraunhofer.de>
In-Reply-To: <54CF8C29.3050307@sit.fraunhofer.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.255.184.225]
authentication-results: sit.fraunhofer.de; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1355;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1355; 
x-forefront-prvs: 0476D4AB88
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(13464003)(51704005)(164054003)(24454002)(52314003)(53754006)(377454003)(479174004)(2900100001)(46102003)(2950100001)(2656002)(87936001)(77156002)(62966003)(102836002)(33656002)(561944003)(54356999)(50986999)(76176999)(76576001)(122556002)(40100003)(19580395003)(92566002)(19580405001)(2501002)(66066001)(106116001)(86362001)(74316001)(107886001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1355; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2015 19:58:14.2137 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1355
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/r4A67ReXlSsIcYryEMKBoSWzr_I>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 19:58:53 -0000

SGVuaywgDQpDb3VsZCB5b3UgcHJvdmlkZSBhIHNtYWxsIFVNTCBjbGFzcyBkaWFncmFtIHRoYXQg
d2lsbCBtb2RlbCBhY3RpdmUgcG9ydHMsIGFkZHJlc3NlcywgaW50ZXJmYWNlcywgYW5kIHRoZSBy
ZWxhdGlvbnNoaXBzIGFtb25nIHRoZW0gdGhhdCB5b3Ugd291bGQgbGlrZSB0byBzZWUgbW9kZWxl
ZD8gIA0KDQpDb3VsZCB5b3UgcHJvdmlkZSBhIHNob3J0IGxpc3Qgb2YgY29tcGxpYW5jZSBtb25p
dG9yaW5nIGdvYWxzIHNlcnZlZCBieSB0aGlzIG1pbmktbW9kZWw/IA0KDQpJJ2QgcmF0aGVyIGVy
ciB3aXRoIHNpbXBsaWNpdHkgcmF0aGVyIHRoYW4gd2l0aCBjb21wbGV4aXR5LiBBIHNpbXBsZXIg
bW9kZWwgd291bGQgaGF2ZSBubyBzZXNzaW9ucyBhbmQgbm8gaW50ZXJmYWNlcywganVzdDoNCg0K
ICAgICAgICAgIEVuZHBvaW50IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gQWRkcmVzcw0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAgICAqDQoNCkFuIEFkZHJl
c3MgaW5zdGFuY2UgY291bGQgYmUgYSBsYXllciAyIGFkZHJlc3MgKHVzdWFsbHkgTUFDKSwgYSBs
YXllciAzIGFkZHJlc3MgKHVzdWFsbHkgSVApLCBhIGxheWVyIDQgYWRkcmVzcyAodXN1YWxseSBJ
UDpwb3J0KSwgZXRjLiANCg0KSSBhbSB0cnlpbmcgdG8gbGVhcm4gdGhlIGFkdmFudGFnZXMgeW91
IHNlZSBmb3IgU0FDTSBpbiB5b3VyIG1vcmUgc29waGlzdGljYXRlZCBtb2RlbC4gIA0KDQpUaGFu
a3MsDQoJCQlDbGlmZg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSGVuayBC
aXJraG9seiBbbWFpbHRvOmhlbmsuYmlya2hvbHpAc2l0LmZyYXVuaG9mZXIuZGVdIA0KU2VudDog
TW9uZGF5LCBGZWJydWFyeSAwMiwgMjAxNSA5OjQwIEFNDQpUbzogQ2xpZmZvcmQgS2Fobjsgc2Fj
bUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtzYWNtXSBDb21tZW50cyBvbiBOZXR3b3JrIEludGVy
ZmFjZQ0KDQpBbmQgbm93IGEgbW9yZSBkZXRhaWxlZCB2aWV3IG9uIHRoaXM6DQoNClllcywgYSBw
b3J0IG51bWJlciBpcyBlZmZlY3RpdmVseSBhIGxheWVyIDQgYWRkcmVzcywgSSB0aGluay4gVHlw
aWNhbGx5LCANCnBvcnRzIGFyZSBhbHdheXMgYWN0aXZlIGJ1dCBhcmUgb25seSB1c2VkIGZvciBz
ZXJ2aWNlcyB3aGVuIGFuIA0KYXBwbGljYXRpb24gKHRoaXMgaW5jbHVkZXMgdGhlIE9TIGluIHNv
bWUgb2NjYXNpb25zLCBvciBldmVuIGEgZGVkaWNhdGVkIA0KSVBNSSBlbmRwb2ludCBjby1sb2Nh
dGVkIG9uIHRoZSBlbmRwb2ludCBpdHNlbGYpLCB3aGljaCBydW5zIG9uIGFuIA0KZW5kcG9pbnQs
IGJpbmRzIHRoZW0gb24gYSBzcGVjaWZpYyBhZGRyZXNzLiBUaGlzIGluY2x1ZGVzLCBmb3IgZXhh
bXBsZSwgDQp0aGUgdmVyeSBhbWJpZ3VvdXMgbG9vcGJhY2sgYWRkcmVzc2VzLiBUaGVyZSBpcyBh
IHN0cm9uZyByZWxhdGlvbnNoaXAgDQpiZXR3ZWVuIGxheWVyIDQgcG9ydCBhc3NvY2lhdGlvbnMg
YW5kIGVuZHBvaW50IHNlY3VyaXR5IHBvc3R1cmUgDQpyZWdhcmRpbmcgc29mdHdhcmUvYXBwbGlj
YXRpb25zLg0KDQpJIHRoaW5rIGl0IGlzIGltcG9ydGFudCB0byBjYXB0dXJlIGFuZCBpbmNvcnBv
cmF0ZSB0aHJlZSBjb25jZXB0cyBoZXJlOg0KLSBhY3RpdmUgcG9ydHMgY2FuIGJlIGJvdW5kIG9u
bHkgdG8gYSBzdWJzZXQgb2YgdGhlIGxheWVyIDMgYWRkcmVzc2VzIA0KYXNzb2NpYXRlZCB3aXRo
IGFuIGVuZHBvaW50LA0KLSBhZGRyZXNzZXMgYXJlIGFsd2F5cyBib3VuZCB0byBzcGVjaWZpYyBp
bnRlcmZhY2VzLCBhbmQNCi0gaW50ZXJmYWNlcyAob2YgdmFyaW91cyBsYXllcnMpIGhhdmUgYSBy
ZWxhdGlvbnNoaXBzIHRvIGVhY2ggb3RoZXIgDQooZS5nLiBuZXN0ZWQsIGJyaWRnZWQvZm9yd2Fy
ZGluZykuDQoNClJlZ2FyZGluZyBzZWN1cml0eSBwb3N0dXJlIG9mIGFuIGVuZHBvaW50LCBpdCBt
aWdodCBiZSBjb25zaWRlcmVkICJva2F5IiANCnRoYXQgYSB2dWxuZXJhYmxlIGFwcGxpY2F0aW9u
IHJ1bm5pbmcgb24gaXQgaXMgcHJvdmlkaW5nIGEgc2VydmljZSANCih0aGVyZWJ5IGNvbnRyb2xs
aW5nIGEgY29ycmVzcG9uZGluZyBpbmdyZXNzIGxpc3RlbmluZyBwb3J0KSB2aWEgb25lIG9mIA0K
dGhlIG1hbnkgbGF5ZXIgMyBhZGRyZXNzZXMgb2YgdGhlIGVuZHBvaW50LCBiZWNhdXNlIHRoaXMg
c3BlY2lmaWMgDQphZGRyZXNzIG1pZ2h0IGJlIGFzc29jaWF0ZWQgd2l0aCBhbiBpbnRlcmZhY2Ug
dGhhdCBpcyBjb25zaWRlcmVkIA0KY29ubmVjdGVkIHRvIGFuICJpbnNpZGUiIG9yICJzZWN1cmVs
eSBtYW5hZ2VkIiBuZXR3b3JrIChhbmQgbm90IHRvLCANCmUuZy4sIGFuIGludGVybmV0LWZhY2lu
ZyBpbnRlcmZhY2UpLiBUaGlzIGlzIG9mIGNvdXJzZSBvbmx5IHRydWUgaWYgDQp0aGVyZSBpcyBu
byBzb3BoaXN0aWNhdGVkIHBhY2tldCBtYW5nbGluZyBvciBmcmFtZSBmb3J3YXJkaW5nIGRvbmUg
b24gDQp0aGUgZW5kcG9pbnQuDQoNCkluIGVzc2VuY2UsIGFkZHJlc3NlcyAoYW1vbmcgb3RoZXIg
dGhpbmdzKSBzaG91bGQgYmUgbW9kZWxlZCBpbiBhbiANCnVuYW1iaWd1b3VzIHdheSB0byBjb3Jy
ZWN0bHkgYXNzb2NpYXRlIHNlY3VyaXR5IHJlbGF0ZWQgZGF0YSB3aXRoIHRoZW0uIA0KQ29tYmlu
aW5nIHBvcnQgYW5kIElQLWFkZHJlc3MgaW4gYW4gYWRkaXRpb25hbCBjb25jZXB0IGlzIG9uZSB3
YXkgdG8gZG8gDQppdCwgYnV0IEkgYW0gbm90IHN1cmUgdGhhdCB3aWxsIGVsaW1pbmF0ZSBhbWJp
Z3VvdXNuZXNzIGluIGV2ZXJ5IGNhc2UuIA0KQXNzaWduaW5nIGFydGlmaWNpYWxseSBjcmVhdGVk
IGlkZW50aWZpZXJzIHRvIHRoZW0gd291bGQgYmUgYW4gYWx0ZXJuYXRlIA0Kcm91dGUuIFdlIHNo
b3VsZCBkaXNjdXNzIHdoaWNoIGZ1cnRoZXIgYWx0ZXJuYXRpdmVzIHRoZXJlIGFyZSBhbmQgd2hp
Y2ggDQp3b3VsZCB3b3JrIGJlc3QgZm9yIFNBQ00sIEkgdGhpbmsuDQoNCkNoZWVycywNCg0KSGVu
aw0KDQpwLnMuIGluIGhpbmRzaWdodCBteSBleHByZXNzaW9uICJ0byBhZGRyZXNzIG5ldHdvcmsg
Y2VudHJpYyANCnNlY3VyaXR5L21vbml0b3JpbmcgcHJvY2Vzc2VzIiBzZWVtcyB0byBiZSBxdWl0
ZSBtaXNsZWFkaW5nLiBJdCB3YXMgbm90IA0KbXkgaW50ZW5kIHRvIHJlZmVyIHRvIGEgIm5ldHdv
cmsgYmFzZWQgYXR0cmlidXRlIGNvbGxlY3RvciIgYnV0IHRvIGxvY2FsIA0KZW5kcG9pbnQgYXR0
cmlidXRlcyByZWdhcmRpbmcgdGhlIGludGVyY29ubmVjdGVkIHJlbGF0aW9uc2hpcCBvZiB0aGUg
DQplbmRwb2ludCB3aXRoIGl0cyBuZWlnaGJvcmluZyBlbmRwb2ludHMgY29ubmVjdGVkIHZpYSB0
aGUgbmV0d29yay4NCg0KDQpPbiAwMi8wMS8yMDE1IDA0OjM4IFBNLCBDbGlmZm9yZCBLYWhuIHdy
b3RlOg0KPiBIZW5rLA0KPiBGaXJzdCwgYSBjb3JyZWN0aW9uLiBJIHNhaWQsIGluY29ycmVjdGx5
LCB0aGF0IHlvdSBoYWQgcHJvcG9zZWQgcmVtb3ZpbmcgdGhlIGlkZWEgb2YgInNlc3Npb24iLiBZ
b3UgYWN0dWFsbHkgcHJvcG9zZWQgc2VwYXJhdGluZyBpdCBmcm9tICJpbnRlcmZhY2UiLiAoSSBk
byBzdWdnZXN0IHdlIHJlbW92ZSAic2Vzc2lvbiIgYWx0b2dldGhlci4pDQo+DQo+IFNlY29uZCwg
SSBsaWtlIHlvdXIgc3VnZ2VzdGlvbiBvZiBwcm9tb3Rpbmcgc2VjdGlvbiA0LjEwLjEsICJBZGRy
ZXNzIiwgdG8gYSA0Lnggc2VjdGlvbi4NCj4NCj4gVGhpcmQsIEkgbGlrZSB5b3VyIGFkZGl0aW9u
IHRvIHRoZSAiQWRkcmVzcyIgc2VjdGlvbi4NCj4NCj4gRm91cnRoLCBsZXQncyBjb25zaWRlciB0
YWtpbmcgaXQgZnVydGhlci4gSW4gYSBzaWRlIGNvbnZlcnNhdGlvbiB5b3UgcG9pbnRlZCBvdXQg
dGhhdCBhIHBvcnQgbnVtYmVyIGlzIHJlYWxseSBwYXJ0IG9mIGFuIGFkZHJlc3MuIFRoZSBwb3J0
IG51bWJlciBtYXR0ZXJzIGZvciBzb21lIHB1cnBvc2VzLCBidXQgbm90IGZvciBvdGhlcnMuIE9u
ZSBwbGFjZSB3aGVyZSBpdCBtYXR0ZXJzOiB5b3UgcG9pbnRlZCBvdXQgdGhhdCBjb21wbGlhbmNl
IHBvbGljaWVzIGFib3V0IG5ldHdvcmsgaW5ncmVzcyBtYWtlIGEgbG90IG9mIHNlbnNlLiBGb3Ig
ZXhhbXBsZSwgYSBwb2xpY3kgY291bGQgZGlzYXBwcm92ZSBvZiBhbiBlbmRwb2ludCBsaXN0ZW5p
bmcgb24gdGhlIE1TU1FMIHBvcnQgKDE0MzMpLiBNYW55IHN1Y2Nlc3NmdWwgYXR0YWNrcyBoYXZl
IGJlZW4gbWFkZSBvbiBwb3J0cyB1bmludGVudGlvbmFsbHkgbGVmdCBvcGVuLCBzbyB0aGlzIGlz
IHdlbGwgbW90aXZhdGVkLg0KPg0KPiBIb3cgd291bGQgd2UgbW9kZWwgdGhpcz8gSXMgMS4xLjEu
MToxNDMzIGEgc3ViLWFkZHJlc3Mgb2YgMS4xLjEuMT8NCj4NCj4gRmlmdGgsIGFuZCBtb3N0IGNl
bnRyYWw6IHlvdSB3cml0ZSB0aGF0IHdlIHNob3VsZCBjYXB0dXJlIHRoZSBuZXN0ZWQgYW5kIGxh
eWVyZWQgc3RydWN0dXJlIG9mIGludGVyZmFjZXMgdG8gImFkZHJlc3MgbmV0d29yayBjZW50cmlj
IHNlY3VyaXR5L21vbml0b3JpbmcgcHJvY2Vzc2VzLCBlZmZlY3RpdmVseSIuIEkgZG9uJ3QgdW5k
ZXJzdGFuZCB5ZXQgaG93IGEgbmV0d29yayBiYXNlZCBhdHRyaWJ1dGUgY29sbGVjdG9yIChhICJz
ZW5zb3IiKSB3b3VsZCBrbm93IG9yIGNhcmUuICBBIHNlbnNvciBvYnNlcnZlcyBvciBpbmplY3Rz
IG5ldHdvcmsgdHJhZmZpYy4gSXQga25vd3MgYWRkcmVzc2VzLiBIb3cgY2FuIGl0IGJlIGF3YXJl
IG9mIG5ldHdvcmsgaW50ZXJmYWNlcz8gSG93IGNhbiBpdCBkaXNjZXJuIHdoZXRoZXIgb25lIGlu
dGVyZmFjZSBuZXN0cyBpbiBhbm90aGVyPw0KPg0KPiBBbiBhdHRyaWJ1dGUgY29sbGVjdG9yIHRo
YXQgcnVucyBvbiB0aGUgZW5kcG9pbnQsIG9yIHRoYXQgcXVlcmllcyB0aGUgZW5kcG9pbnQgdXNp
bmcgYSBtYW5hZ2VtZW50IHByb3RvY29sLCBtYXkgZGlzY2VybiB0aGUgbmVzdGluZy4gQnV0IGl0
IGlzIG5vdCBhIHNlbnNvci4gV291bGQgaW5mb3JtYXRpb24gZnJvbSB0aGUgdHdvIGtpbmRzIG9m
IGNvbGxlY3RvcnMgaGF2ZSB0byBiZSBjb21iaW5lZD8NCj4NCj4gQmVzdCwNCj4gCQkJQ2xpZmYN
Cj4NCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQ2xpZmZvcmQgS2Fobg0K
PiBTZW50OiBTdW5kYXksIEZlYnJ1YXJ5IDAxLCAyMDE1IDk6MzkgQU0NCj4gVG86ICdIZW5rIEJp
cmtob2x6Jzsgc2FjbUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSRTogW3NhY21dIENvbW1lbnRzIG9u
IE5ldHdvcmsgSW50ZXJmYWNlDQo+DQo+IEhlbmssDQo+IEJlbGF0ZWQgcmVzcG9uc2UgaGVyZS4N
Cj4NCj4gQXMgSSB1bmRlcnN0YW5kIHlvdSwgeW91IHdvdWxkIHJlbW92ZSB0aGUgY2xhc3MgInNl
c3Npb24iLCBtZW50aW9uZWQgaW4gdGhlIGRpYWdyYW0gYW5kIGluIHNlY3Rpb24gNC4xMCBvZiBk
cmFmdC1pZXRmLXNhY20taW5mb3JtYXRpb24tbW9kZWwuIElzIHRoYXQgdHJ1ZT8NCj4NCj4gSSBy
ZWFsaXplIHRoZXJlIGlzIG1vcmUgdG8geW91ciBwcm9wb3NhbC4gQnV0IEkgd2FudCB0byByZXNw
b25kIHRvIHJlbW92aW5nICJzZXNzaW9uIi4gTGV0J3MgY29uc2lkZXIgd2h5IHNlc3Npb25zIHdl
cmUgdGhlcmUuDQo+DQo+IFN1cHBvc2UgYW4gZW5kcG9pbnQncyBsYXllciAyIGludGVyZmFjZSBj
b21lcyBvbmxpbmUgYWZ0ZXIgYSBSQURJVVMgZXhjaGFuZ2UuIFNvbWUgb2YgdXMgd291bGQgc2F5
IGEgbGF5ZXIgMiBzZXNzaW9uIGhhcyBiZWd1bjsgdGhhdCBtYXkgYmUgbWlzdXNlIG9mIHRoZSB3
b3JkICJzZXNzaW9uIi4gQW55d2F5LCB0aGUgUkFESVVTIHNlcnZlciBrbm93czoNCj4gLSB0aGUg
ZW5kcG9pbnQncyBNQUMgYWRkcmVzcw0KPiAtIHRoZSBjcmVkZW50aWFscyB1c2VkIGluIHRoZSBS
QURJVVMgYXV0aGVudGljYXRpb24NCj4gLSB0aGUgYXV0aG9yaXphdGlvbiB0aGF0IGl0IGdyYW50
ZWQgKFZMQU4sIGEgZmlsdGVyLWlkIGRlbm90aW5nIGZpcmV3YWxsIHJ1bGVzKQ0KPiAtIHRoZSBl
bmRwb2ludCdzIGNvbXBsaWFuY2UsIGlmIE5FQSBjaGVja2luZyB3YXMgZG9uZSBkdXJpbmcgdGhl
IFJBRElVUyBleGNoYW5nZQ0KPiAtIHNvbWV0aW1lcywgYW4gSVAgYWRkcmVzcyAoaWYgdGhlIHN3
aXRjaCBkb2VzIERIQ1Agc25vb3BpbmcgYW5kIHJlcG9ydHMgaXRzIGZpbmRpbmdzIGluIFJBRElV
UyBBY2NvdW50aW5nIG1lc3NhZ2VzKQ0KPg0KPiBUaGF0IGluZm9ybWF0aW9uIGlzIHJlbGV2YW50
IGZvciBTQUNNLiBBdXRob3JpemF0aW9uIGlzIHJlbGV2YW50IGJlY2F1c2UgZW5kcG9pbnRzIHRo
YXQgaGF2ZSBhY2Nlc3MgdG8gc2Vuc2l0aXZlIHJlc291cmNlcyBtYXkgYmUgc3ViamVjdCB0byBt
b3JlIHN0cmluZ2VudCBjb21wbGlhbmNlIHBvbGljaWVzLiAoSG0uIERvIHdlIGhhdmUgdGhhdCBp
biBvdXIgdXNlIGNhc2VzPyBTaG91bGQgd2U/KQ0KPg0KPiBQZXJoYXBzIHdlIGRvbid0IG5lZWQg
YSBzZXNzaW9uIGluIHRoZSBtb2RlbC4gUGVyaGFwcyB0aGUgUkFESVVTIHNlcnZlciBjYW4ganVz
dCBtYWtlIGFuIGVuZHBvaW50IGF0dHJpYnV0ZSBhc3NlcnRpb24gc3RhdGluZyB0aGUgYWJvdmUg
YXR0cmlidXRlcy4gSSBsaWtlIHRoZSBzaW1wbGlmaWNhdGlvbi4NCj4NCj4gT3RoZXIga2luZHMg
b2YgbmV0d29yayBzZXNzaW9ucyAoVENQIGNvbm5lY3Rpb25zLCBldGMuKSBhcmUgY2VydGFpbmx5
IHJlbGV2YW50IGZvciBzZWN1cml0eS4gQnV0IHRoZXkgc2VlbSB0byBiZSBvdXRzaWRlIG9mIHRo
ZSBTQUNNIFdHJ3MgY2hhcnRlci4NCj4NCj4gSW4gc3VtLCBJIGNhbm5vdCBzZWUgYSByZWFzb24g
dG8ga2VlcCAic2Vzc2lvbiIgaW4gdGhlIGluZm9ybWF0aW9uIG1vZGVsLg0KPg0KPiBXaGF0IGRv
IG90aGVycyB0aGluaz8NCj4NCj4gQmVzdCwNCj4gCQkJQ2xpZmYNCj4NCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSGVuayBCaXJraG9seiBbbWFpbHRvOmhlbmsuYmlya2hv
bHpAc2l0LmZyYXVuaG9mZXIuZGVdDQo+IFNlbnQ6IFR1ZXNkYXksIE5vdmVtYmVyIDA0LCAyMDE0
IDExOjM5IEFNDQo+IFRvOiBzYWNtQGlldGYub3JnDQo+IFN1YmplY3Q6IFtzYWNtXSBDb21tZW50
cyBvbiBOZXR3b3JrIEludGVyZmFjZQ0KPg0KPiBIaSBhbGwsDQo+DQo+IHRoZSBuZXcgZHJhZnQg
KGRyYWZ0LWlldGYtc2FjbS1pbmZvcm1hdGlvbi1tb2RlbC0wMCkgbm93IGluY2x1ZGVzIGEgY29t
YmluZWQgc2VjdGlvbiBmb3IgIk5ldHdvcmsgU2Vzc2lvbiIgYW5kICJOZXR3b3JrIEludGVyZmFj
ZSIgKDQuMTAuKS4NCj4NCj4gTXkgcmVjb21tZW5kYXRpb24gaXMgdG8gZGl2aWRlIHRoZSBlbGVt
ZW50cyBOZXR3b3JrIFNlc3Npb24sIE5ldHdvcmsgSW50ZXJmYWNlIGFuZCBwb3RlbnRpYWxseSAo
TmV0d29yaykgQWRkcmVzcyBpbnRvIHNlcGFyYXRlIHNlY3Rpb25zIG9mIHRoZSBzYW1lIGxldmVs
ICg0LngpLg0KPg0KPiBXaGlsZSBib3RoIHRlcm1zIGFyZSByZWxhdGVkLCBvZiBjb3Vyc2UsIHRo
ZXJlIGFyZSBzZXZlcmFsIChtb3JlIG9yIGxlc3MNCj4gaW1wb3J0YW50KSByZWFzb25zIGZvciB0
aGlzOg0KPiBBIHNlc3Npb24gdHlwaWNhbGx5IGludm9sdmVzIG11bHRpcGxlIHBhcnRpY2lwYW50
cyAoZS5nLiBlbmRwb2ludHMsIG9yIC0gYnJva2VuIGRvd24gLSBldmVudHVhbGx5IGFkZHJlc3Nl
cyBvciBpbnRlcmZhY2VzKSBhbmQgdHlwaWNhbGx5IGhhcyBhIGxpbWl0ZWQgbGlmZS10aW1lLiBB
biBpbnRlcmZhY2UsIGluIGNvbnRyYXN0LCBpcyBhIHNpbmd1bGFyIGVudGl0eSB0aGF0IGNhbiBl
eGlzdCBvdmVyIHRoZSBjb21wbGV0ZSBsaWZlLWN5Y2xlIG9mIGFuIGVuZHBvaW50ICh2aXJ0dWFs
IGludGVyZmFjZXMgY2FuIGhhdmUgYSBmb3Jlc2VlYWJsZSBsaW1pdGVkIGxpZmUtdGltZSkuIEFz
IElyYSBwb2ludGVkIG91dCwgYW4gaW50ZXJmYWNlIHR5cGljYWxseSBwcm92aWRlcyBjb25uZWN0
aXZpdHkgdG8gYSBuZXR3b3JrIG9uIGxheWVyIHR3byB0byB0aHJlZSwgd2hpbGUgYSBuZXR3b3Jr
IHNlc3Npb24gaXMgdHlwaWNhbGx5IGFzc29jaWF0ZWQgd2l0aCBsYXllcnMgYWJvdmUgdGhvc2Uu
DQo+DQo+IEFsdGhvdWdoIGNsb3NlbHkgcmVsYXRlZCwgdGhleSBhcmUgcXVpdGUgZGlmZmVyZW50
LCBzZW1hbnRpY2FsbHksIGFuZCBtYXkgZXZlbiBuZWVkIHNlcGFyYXRlIHJlcHJlc2VudGF0aW9u
cyBpbiB0aGUgU0FDTSBJTS4NCj4NCj4gTXkgcHJvcG9zYWwgZm9yIGEgc2VwYXJhdGUgIk5ldHdv
cmsgSW50ZXJmYWNlIiBzZWN0aW9uOg0KPg0KPiAtLS1zbmlwLS0tDQo+IE5ldHdvcmsgSW50ZXJm
YWNlDQo+DQo+IEFuIGVuZHBvaW50IGlzIGNvbm5lY3RlZCB0byBhIG5ldHdvcmsgdmlhIG9uZSBv
ciBtb3JlIGludGVyZmFjZXMuDQo+IEludGVyZmFjZXMgY2FuIGJlIHBoeXNpY2FsIG9yIHZpcnR1
YWwuIEludGVyZmFjZXMgb2YgYW4gZW5kcG9pbnQgY2FuIG9wZXJhdGUgb24gZGlmZmVyZW50IGxh
eWVycywgbW9zdCBwcm9taW5lbnRseSB3aGF0IGlzIG5vdyBjb21tb25seSBjYWxsZWQgbGF5ZXIg
MiBhbmQgMy4gV2l0aGluIGEgbGF5ZXIsIGludGVyZmFjZXMgY2FuIGJlIG5lc3RlZC4NCj4gT24g
bGF5ZXIgMiwgYSByb290IGludGVyZmFjZSBpcyB0eXBpY2FsbHkgYXNzb2NpYXRlZCB3aXRoIGEg
cGh5c2ljYWwgaW50ZXJmYWNlIHBvcnQgYW5kIG5lc3RlZCBpbnRlcmZhY2VzIGFyZSB2aXJ0dWFs
IGludGVyZmFjZXMuIEluIHRoZSBjYXNlIG9mIGEgdmlydHVhbCBlbmRwb2ludCwgYSByb290IGlu
dGVyZmFjZSBjYW4gYmUgYSB2aXJ0dWFsIGludGVyZmFjZS4NCj4gVmlydHVhbCBsYXllciAyIGlu
dGVyZmFjZXMgb2Ygb25lIG9yIG1vcmUgZW5kcG9pbnRzIGNhbiBhbHNvIGNvbnN0aXR1dGUgYW4g
YWdncmVnYXRlZCBncm91cCBvZiBsaW5rcyB0aGF0IGFjdCBhcyBvbmUuDQo+IE9uIGxheWVyIDMs
IG5lc3RlZCBpbnRlcmZhY2VzIHR5cGljYWxseSBjb25zdGl0dXRlIHZpcnR1YWwgdHVubmVscyBv
ciBuZXR3b3Jrcy4NCj4gRXhhbXBsZXMgaW5jbHVkZTogcGh5c2ljYWwgRXRoZXJuZXQgcG9ydCwg
bGF5ZXIgMiBWTEFOIGludGVyZmFjZSwgYSBNQy1MQUcgc2V0dXAsIGxheWVyIDMgUG9pbnQtdG8t
UG9pbnQgdHVubmVsIGluZ3Jlc3Mgb3IgZWdyZXNzLg0KPiAtLS1zbmFwLS0tDQo+DQo+IEEgc21h
bGwgYWRkaXRpb24gdG8gdGhlICJBZGRyZXNzIiBzZWN0aW9uLCBhbmFsb2dvdXNseToNCj4NCj4g
LS0tc25pcC0tLQ0KPiBOZXR3b3JrIEFkZHJlc3MNCj4NCj4gTmV0d29yayBhZGRyZXNzZXMgYXJl
IGxheWVyIHNwZWNpZmljIGFuZCBmb2xsb3cgbGF5ZXIgc3BlY2lmaWMgYWRkcmVzcyBzY2hlbWVz
LiBFYWNoIGludGVyZmFjZSBvZiBhIHNwZWNpZmljIGxheWVyIGNhbiBiZSBhc3NvY2lhdGVkIHdp
dGggb25lIG9yIG1vcmUgYWRkcmVzc2VzIGFwcHJvcHJpYXRlIGZvciB0aGF0IGxheWVyLg0KPiBU
aGVyZSBpcyBubyBndWFyYW50ZWUgdGhhdCBhbiBhZGRyZXNzIGlzIGdsb2JhbGx5IHVuaXF1ZS4g
SW4gZ2VuZXJhbCwgdGhlcmUgaXMgYSBzY29wZSB0byBhbiBhZGRyZXNzIGluIHdoaWNoIGl0IGlz
IGludGVuZGVkIHRvIGJlIHVuaXF1ZS4NCj4gRXhhbXBsZXMgaW5jbHVkZTogcGh5c2ljYWwgRXRo
ZXJuZXQgcG9ydCB3aXRoIGEgTUFDIGFkZHJlc3MsIGxheWVyIDIgVkxBTiBpbnRlcmZhY2Ugd2l0
aCBhIE1BQyBhZGRyZXNzLCBsYXllciAzIGludGVyZmFjZSB3aXRoIG11bHRpcGxlIElQdjYgYWRk
cmVzc2VzLCBsYXllciAzIHR1bm5lbCBpbmdyZXNzIG9yIGVncmVzcyB3aXRoIGFuIElQdjQgYWRk
cmVzcy4NCj4gLS0tc25hcC0tLQ0KPg0KPiBTb21ldGltZXMsIHRoZSBjb21wbGV4aXR5IGEgc2V0
dXAgb2YgaW50ZXJmYWNlcyBjYW4gaW5jb3Jwb3JhdGUgaXMgYSBsaXR0bGUgYml0IHVuZGVyZXN0
aW1hdGVkLCBJTUhPLiBUaGUgcHJvcG9zZWQgdGV4dCBhYm92ZSBvbmx5IGluY2x1ZGVzIHRoZSBt
b3N0IGNvbW1vbiBjYXNlcyBhbmQgZG9lcyBub3QgdG91Y2ggZW1lcmdpbmcgcHJhY3RpY2VzLCBz
dWNoIGFzIHBoeXNpY2FsIGludGVyZmFjZSBtb2R1bGVzIHRoYXQgcHJvdmlkZSBhIHNldCBvZiBz
aW5nbGUgcGh5c2ljYWwgaW50ZXJmYWNlcywgd2hpY2ggYXJlIGFzc29jaWF0ZWQgd2l0aCBtdWx0
aXBsZSBkaXN0aW5ndWlzaGFibGUgZW5kcG9pbnRzIGF0IHRoZSBzYW1lIHRpbWUuDQo+DQo+IElu
IG9yZGVyIHRvIGFkZHJlc3MgbmV0d29yayBjZW50cmljIHNlY3VyaXR5L21vbml0b3JpbmcgcHJv
Y2Vzc2VzLCBlZmZlY3RpdmVseSwgdGhlIFNBQ00gSU0gc2hvdWxkIGJlIGFibGUgdG8gaGFuZGxl
IHRoZSBjb21wbGV4aXR5IG9mIGFwcGxpZWQgY29tbW9uIHByYWN0aWNlIGluIGl0cyBkZWZpbml0
aW9uIG9mICJOZXR3b3JrIEludGVyZmFjZSIsIEkgdGhpbmsuDQo+DQo+IEJlc3QsDQo+DQo+IEhl
bmsNCj4NCg0KDQo=


From nobody Wed Feb  4 01:06:01 2015
Return-Path: <henk.birkholz@sit.fraunhofer.de>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2EC41A8704 for <sacm@ietfa.amsl.com>; Wed,  4 Feb 2015 01:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level: 
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 XoXgZK4YuQyc for <sacm@ietfa.amsl.com>; Wed,  4 Feb 2015 01:05:53 -0800 (PST)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D08201A86FF for <sacm@ietf.org>; Wed,  4 Feb 2015 01:05:51 -0800 (PST)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id t1495mcI013701 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 4 Feb 2015 10:05:49 +0100
Received: from [192.168.0.71] (134.102.43.163) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.210.2; Wed, 4 Feb 2015 10:05:43 +0100
Message-ID: <54D1DFDC.7080100@sit.fraunhofer.de>
Date: Wed, 4 Feb 2015 10:01:16 +0100
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Clifford Kahn <cliffordk@pulsesecure.net>, "sacm@ietf.org" <sacm@ietf.org>
References: <54590118.9050702@sit.fraunhofer.de> <CY1PR0601MB13551089FC3E03AC2476B912B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com> <54CF8C29.3050307@sit.fraunhofer.de> <CY1PR0601MB1355A2CEE12A57BD5DABACF4B73D0@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB1355A2CEE12A57BD5DABACF4B73D0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020904070901010307060604"
X-Originating-IP: [134.102.43.163]
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/FA2e6xU7h2AGYHrFjODJlBoEyN8>
Subject: Re: [sacm] Comments on Network Interface
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 09:05:59 -0000

--------------ms020904070901010307060604
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

First of all, I have to say that it was not my initial intend to include =

Layer 4 addresses into the model at this point. That's why I did not=20
include that concept in the small addition to section 4.10. My goal was=20
simply to add some text that highlights the inherent complexity of the=20
"class" Network Interface (and Network Address, analogously).

The first two examples below will show two simple scenarios that refer=20
to the proposed additions to 4.10. The third example is intended as a=20
first step towards answering and discussing your question about layer 4=20
addresses, Cliff. It uses terminology from SCAP-AI. In general, the=20
examples use instantiations of "classes" (the elements in the diagram)=20
and only show the values of the TVP.

The representation used in the current draft:

       Endpoint----N.Interface----Address
               1  *           1  *

And a small (new) addition to represent nested interfaces corresponding=20
to the proposed text:

                      +---+
                      |*  |1
       Endpoint----N.Interface----Address
               1  *           1  *



Example 1: "An endpoint for 'office use' must not forward frames from=20
one network segment (l2 broadcast domain) to another" This is a common=20
network security rule regarding network separation.

Endpoint attributes collected from a target endpoint (endpoint under=20
assessment) in the current representation (I omitted the L2 addresses to =

keep it simple):

       L2Interface1
         |
         |
       EndpointA---BridgingVirtualInterface(BVI)
         |
         |
       L2Interface2

While the collected security posture attributes show that there is a=20
virtual bridging interface, there is no data to show if this interface=20
is actually bridging the two physical Interfaces. The existence of a=20
virtual bridging interface on an "office endpoint" might be interpreted=20
as potentially not "compliant".

Endpoint attributes collected from an endpoint under assessment with the =

addition of relationships between interfaces in the representation:

       L2Interface1
         |
         |
       EndpointA---BridgingVirtualInterface(BVI)
         |                |
         |                |
       L2Interface2-------+

While Interface2 is part of the bridge, Interface1 is not, and the=20
endpoint is therefore "compliant". It might still also be a suspicious=20
"office" endpoint due the uncommon use of a virtual bridging interface=20
that has already one associated physical interface.




Example 2: "192.0.2.0/24 is an internal network using public addresses=20
that must not be exposed to an 'outside' interface". This is also a=20
common network security rule regarding network separation.

Endpoint attributes collected from a target endpoint in the current=20
representation (I omitted the L2 addresses and L3 interfaces to keep it=20
simple). L2Interface1 is the 'outside' interface:

       L2Interface1-----------123.123.12.12
         |
         | +----VLAN1 ID 10---192.0.2.114
         | |
         | | +--VLAN2 ID 20---203.0.113.1
         | | |
       EndpointA
         | | |
         | | +--VLAN3 ID 30---198.51.100.1
         | |
         | +----VLAN4 ID 40---172.21.11.114
         |
       L2Interface2-----------10.112.0.1

The collected endpoint attributes do not contain information about how=20
the interfaces are associated with each other and it is not possible to=20
discern if the virtual interface with the address in 192.0.2.0/24 is=20
facing the 'outside' or the 'inside' network.

Endpoint attributes collected from a target endpoint with the addition=20
of relationships between interfaces in the representation:

            +--VLAN2 ID 20----203.0.113.1
            |
       L2Interface1-----------123.123.12.12
         |  |
         |  +--VLAN4 ID 40----172.21.11.114
         |
       EndpointA
         |
         |  +--VLAN1 ID 10----192.0.2.114
         |  |
       L2Interface2-----------10.112.0.1
            |
            +--VLAN3 ID 30----198.51.100.1

In this endpoint attribute collection, virtual interfaces are now always =

associated with their corresponding physical interfaces. The endpoint is =

"compliant" due to VLAN3 ID 10 being associated with the inside=20
interface and there being no virtual bridging interface that might=20
forward frames to the 'outside' interface.




Example 3: "A proxy service must not be reachable from an outside=20
network". This is a variation of Example 1 based on the following=20
extended model, which - please mind - is not by any means meant to be a=20
final proposal.

Active Ports could be modeled as attributes of the "class" Service,=20
which is associated with the "class" Software Instance similar to=20
SCAP-AI (this still ignores the ambiguousness of addresses):

                    +---+
                    |*  |1
       Endpoint----Interface----Address
          |1   1  *         1  *   |1
          |*                       |
       Software                    |*
       Instance-----------------Service
               1               *

Endpoint attributes collected from a target endpoint with the addition=20
of relationships between interfaces and also the "class" Services in the =

representation (I omitted the L2 addresses and L3 interfaces to keep it=20
simple), L2Interface2 is the 'outside' interface:

                          +-------------------------------Squid_Instance
                          |                                 |
                          |                                 |
       L2Interface1----EndpointA----BVI----192.0.2.114----Proxy_at_8080
                          |          |
                          |          |
                    L2Interface2-----+

The collected set of associated attributes shows that the only=20
IP-address of the target endpoint is associated with the virtual=20
bridging interface. The endpoint is not "compliant", because the proxy=20
service provided by a running squid instance is reachable via the=20
'outside' interface.


You could alternatively call the new element Port instead of Service, or =

include every active port of an l3 address in one instance of Service.=20
Some might consider the introduction of Service scope creep.

In any case, I hope this - rather long, please excuse me - illustration=20
conveys why a simplified abstraction of endpoint-addresses associations=20
will not be able to correctly express desired states about network=20
configuration.


IHTH,

Henk


On 02/03/2015 08:58 PM, Clifford Kahn wrote:
> Henk,
> Could you provide a small UML class diagram that will model active port=
s, addresses, interfaces, and the relationships among them that you would=
 like to see modeled?
>
> Could you provide a short list of compliance monitoring goals served by=
 this mini-model?
>
> I'd rather err with simplicity rather than with complexity. A simpler m=
odel would have no sessions and no interfaces, just:
>
>            Endpoint ---------------------- Address
>                             1                      *
>
> An Address instance could be a layer 2 address (usually MAC), a layer 3=
 address (usually IP), a layer 4 address (usually IP:port), etc.
>
> I am trying to learn the advantages you see for SACM in your more sophi=
sticated model.
>
> Thanks,
> 			Cliff
>
> -----Original Message-----
> From: Henk Birkholz [mailto:henk.birkholz@sit.fraunhofer.de]
> Sent: Monday, February 02, 2015 9:40 AM
> To: Clifford Kahn; sacm@ietf.org
> Subject: Re: [sacm] Comments on Network Interface
>
> And now a more detailed view on this:
>
> Yes, a port number is effectively a layer 4 address, I think. Typically=
,
> ports are always active but are only used for services when an
> application (this includes the OS in some occasions, or even a dedicate=
d
> IPMI endpoint co-located on the endpoint itself), which runs on an
> endpoint, binds them on a specific address. This includes, for example,=

> the very ambiguous loopback addresses. There is a strong relationship
> between layer 4 port associations and endpoint security posture
> regarding software/applications.
>
> I think it is important to capture and incorporate three concepts here:=

> - active ports can be bound only to a subset of the layer 3 addresses
> associated with an endpoint,
> - addresses are always bound to specific interfaces, and
> - interfaces (of various layers) have a relationships to each other
> (e.g. nested, bridged/forwarding).
>
> Regarding security posture of an endpoint, it might be considered "okay=
"
> that a vulnerable application running on it is providing a service
> (thereby controlling a corresponding ingress listening port) via one of=

> the many layer 3 addresses of the endpoint, because this specific
> address might be associated with an interface that is considered
> connected to an "inside" or "securely managed" network (and not to,
> e.g., an internet-facing interface). This is of course only true if
> there is no sophisticated packet mangling or frame forwarding done on
> the endpoint.
>
> In essence, addresses (among other things) should be modeled in an
> unambiguous way to correctly associate security related data with them.=

> Combining port and IP-address in an additional concept is one way to do=

> it, but I am not sure that will eliminate ambiguousness in every case.
> Assigning artificially created identifiers to them would be an alternat=
e
> route. We should discuss which further alternatives there are and which=

> would work best for SACM, I think.
>
> Cheers,
>
> Henk
>
> p.s. in hindsight my expression "to address network centric
> security/monitoring processes" seems to be quite misleading. It was not=

> my intend to refer to a "network based attribute collector" but to loca=
l
> endpoint attributes regarding the interconnected relationship of the
> endpoint with its neighboring endpoints connected via the network.
>
>
> On 02/01/2015 04:38 PM, Clifford Kahn wrote:
>> Henk,
>> First, a correction. I said, incorrectly, that you had proposed removi=
ng the idea of "session". You actually proposed separating it from "inter=
face". (I do suggest we remove "session" altogether.)
>>
>> Second, I like your suggestion of promoting section 4.10.1, "Address",=
 to a 4.x section.
>>
>> Third, I like your addition to the "Address" section.
>>
>> Fourth, let's consider taking it further. In a side conversation you p=
ointed out that a port number is really part of an address. The port numb=
er matters for some purposes, but not for others. One place where it matt=
ers: you pointed out that compliance policies about network ingress make =
a lot of sense. For example, a policy could disapprove of an endpoint lis=
tening on the MSSQL port (1433). Many successful attacks have been made o=
n ports unintentionally left open, so this is well motivated.
>>
>> How would we model this? Is 1.1.1.1:1433 a sub-address of 1.1.1.1?
>>
>> Fifth, and most central: you write that we should capture the nested a=
nd layered structure of interfaces to "address network centric security/m=
onitoring processes, effectively". I don't understand yet how a network b=
ased attribute collector (a "sensor") would know or care.  A sensor obser=
ves or injects network traffic. It knows addresses. How can it be aware o=
f network interfaces? How can it discern whether one interface nests in a=
nother?
>>
>> An attribute collector that runs on the endpoint, or that queries the =
endpoint using a management protocol, may discern the nesting. But it is =
not a sensor. Would information from the two kinds of collectors have to =
be combined?
>>
>> Best,
>> 			Cliff
>>
>> -----Original Message-----
>> From: Clifford Kahn
>> Sent: Sunday, February 01, 2015 9:39 AM
>> To: 'Henk Birkholz'; sacm@ietf.org
>> Subject: RE: [sacm] Comments on Network Interface
>>
>> Henk,
>> Belated response here.
>>
>> As I understand you, you would remove the class "session", mentioned i=
n the diagram and in section 4.10 of draft-ietf-sacm-information-model. I=
s that true?
>>
>> I realize there is more to your proposal. But I want to respond to rem=
oving "session". Let's consider why sessions were there.
>>
>> Suppose an endpoint's layer 2 interface comes online after a RADIUS ex=
change. Some of us would say a layer 2 session has begun; that may be mis=
use of the word "session". Anyway, the RADIUS server knows:
>> - the endpoint's MAC address
>> - the credentials used in the RADIUS authentication
>> - the authorization that it granted (VLAN, a filter-id denoting firewa=
ll rules)
>> - the endpoint's compliance, if NEA checking was done during the RADIU=
S exchange
>> - sometimes, an IP address (if the switch does DHCP snooping and repor=
ts its findings in RADIUS Accounting messages)
>>
>> That information is relevant for SACM. Authorization is relevant becau=
se endpoints that have access to sensitive resources may be subject to mo=
re stringent compliance policies. (Hm. Do we have that in our use cases? =
Should we?)
>>
>> Perhaps we don't need a session in the model. Perhaps the RADIUS serve=
r can just make an endpoint attribute assertion stating the above attribu=
tes. I like the simplification.
>>
>> Other kinds of network sessions (TCP connections, etc.) are certainly =
relevant for security. But they seem to be outside of the SACM WG's chart=
er.
>>
>> In sum, I cannot see a reason to keep "session" in the information mod=
el.
>>
>> What do others think?
>>
>> Best,
>> 			Cliff
>>
>> -----Original Message-----
>> From: Henk Birkholz [mailto:henk.birkholz@sit.fraunhofer.de]
>> Sent: Tuesday, November 04, 2014 11:39 AM
>> To: sacm@ietf.org
>> Subject: [sacm] Comments on Network Interface
>>
>> Hi all,
>>
>> the new draft (draft-ietf-sacm-information-model-00) now includes a co=
mbined section for "Network Session" and "Network Interface" (4.10.).
>>
>> My recommendation is to divide the elements Network Session, Network I=
nterface and potentially (Network) Address into separate sections of the =
same level (4.x).
>>
>> While both terms are related, of course, there are several (more or le=
ss
>> important) reasons for this:
>> A session typically involves multiple participants (e.g. endpoints, or=
 - broken down - eventually addresses or interfaces) and typically has a =
limited life-time. An interface, in contrast, is a singular entity that c=
an exist over the complete life-cycle of an endpoint (virtual interfaces =
can have a foreseeable limited life-time). As Ira pointed out, an interfa=
ce typically provides connectivity to a network on layer two to three, wh=
ile a network session is typically associated with layers above those.
>>
>> Although closely related, they are quite different, semantically, and =
may even need separate representations in the SACM IM.
>>
>> My proposal for a separate "Network Interface" section:
>>
>> ---snip---
>> Network Interface
>>
>> An endpoint is connected to a network via one or more interfaces.
>> Interfaces can be physical or virtual. Interfaces of an endpoint can o=
perate on different layers, most prominently what is now commonly called =
layer 2 and 3. Within a layer, interfaces can be nested.
>> On layer 2, a root interface is typically associated with a physical i=
nterface port and nested interfaces are virtual interfaces. In the case o=
f a virtual endpoint, a root interface can be a virtual interface.
>> Virtual layer 2 interfaces of one or more endpoints can also constitut=
e an aggregated group of links that act as one.
>> On layer 3, nested interfaces typically constitute virtual tunnels or =
networks.
>> Examples include: physical Ethernet port, layer 2 VLAN interface, a MC=
-LAG setup, layer 3 Point-to-Point tunnel ingress or egress.
>> ---snap---
>>
>> A small addition to the "Address" section, analogously:
>>
>> ---snip---
>> Network Address
>>
>> Network addresses are layer specific and follow layer specific address=
 schemes. Each interface of a specific layer can be associated with one o=
r more addresses appropriate for that layer.
>> There is no guarantee that an address is globally unique. In general, =
there is a scope to an address in which it is intended to be unique.
>> Examples include: physical Ethernet port with a MAC address, layer 2 V=
LAN interface with a MAC address, layer 3 interface with multiple IPv6 ad=
dresses, layer 3 tunnel ingress or egress with an IPv4 address.
>> ---snap---
>>
>> Sometimes, the complexity a setup of interfaces can incorporate is a l=
ittle bit underestimated, IMHO. The proposed text above only includes the=
 most common cases and does not touch emerging practices, such as physica=
l interface modules that provide a set of single physical interfaces, whi=
ch are associated with multiple distinguishable endpoints at the same tim=
e.
>>
>> In order to address network centric security/monitoring processes, eff=
ectively, the SACM IM should be able to handle the complexity of applied =
common practice in its definition of "Network Interface", I think.
>>
>> Best,
>>
>> Henk
>>
>
>



--------------ms020904070901010307060604
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIUXDCC
BC4wggMWoAMCAQICAgEMMA0GCSqGSIb3DQEBBQUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVy
MSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0wNzEyMDUxNTE4NTha
Fw0xOTA2MzAyMzU5NTlaMGcxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpGcmF1bmhvZmVyMSEw
HwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQS0kxIDAeBgNVBAMTF0ZyYXVuaG9mZXIg
Um9vdCBDQSAyMDA3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwz0eyWWNW4g3
9z7BIbZU3rA6VxsaHO6YCHQBWm+13zZXK0RFzvNGE2V2lZhUx6iFFW4SpBfoC+EhpzE9Kd3/
o9ZP0rSJ/WNK2qtT71kFtE/iOyqRmcDLZVeBozCTkA7Jvf0VMjIIpEh8VgXyuzaJ4kjCb0uS
DCVFvq0+1McB7bHIErQwCG6nb396IKe7tOU1gFQsGY/ZS8Adq0P4YRSU+7AdXbeR7GLAkdFe
3acLsy0fZjkYPK4EFOXSfTbZss2nE7DMRZ1WBFFxMzZcL11RE55PSJAOl1pLcNu5edmh1pTI
ktCl+2C/La2ecQAXhsD9SGadFEwFTkzRcUQL0HoPsQIDAQABo4HZMIHWMB8GA1UdIwQYMBaA
FDHDeRu69VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUL0VCHjEF
gNVw2PgdV8tbetU9nPcwEgYDVR0TAQH/BAgwBgEB/wIBATBwBgNVHR8EaTBnMGWgY6Bhhl9o
dHRwOi8vcGtpLnRlbGVzZWMuZGUvY2dpLWJpbi9zZXJ2aWNlL2FmX0Rvd25sb2FkQVJMLmNy
bD8tY3JsX2Zvcm1hdD1YXzUwOSYtaXNzdWVyPURUX1JPT1RfQ0FfMjANBgkqhkiG9w0BAQUF
AAOCAQEAGrdMejzl3cJjst6GJU5FYkz08o9fXdfljc4O1/WU4YuTMTanmiPnZ+FSwVoY1pnh
gGQ4D0o1M11meijcOH83cs1SdW4Qjmx9jPcp63fCuRkF1Lc9YbroBRLUUGJT7yJUYvxNAcNe
1A2DdGlR1TyerNukK3xthJbTcU3P1S1xo5LEP1XPmz0jdwdX6cjOHZe2M/uRl2CWD/f23m8l
kBKrGUfVRCOuwZI1KL8qQ14P6gdd0kTQhYLjErxH6iyt+PBBUn02uiKfeqAy70u8+ToHtinG
fThfNVV+OPI/fLPuLW4heF+5E8/v3mWAyCX1Zi1USq3O2S4OMM+AM6eLGXLqQTCCBMYwggOu
oAMCAQICCmEdMxkAAAAAAAMwDQYJKoZIhvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNV
BAoTCkZyYXVuaG9mZXIxITAfBgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4G
A1UEAxMXRnJhdW5ob2ZlciBSb290IENBIDIwMDcwHhcNMDcxMjEyMTQ0OTM1WhcNMTkwNjMw
MjM1OTU5WjBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8GA1UECxMY
RnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVzZXIgQ0Eg
MjAwNzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMJ0EFHLddGB8Ss1nVqCOq+S
rs0C/K7I+yB3Dv9oEhWQSadnfGgkX/oOJhplPkqeCQrTh08zEYprVaJLTaVPVhvjx3h5+KML
3lVGZIfajA89TolhLwk+ml29VbqV5nLhNrSwdZy157b6dCu5JffxvpO5wXCn95Z/TLyLdeux
gVHs/MnhczvmBbBRS+Ow9UoKn+PZvyYmUEdOHg8cA5PGFaRP9q88q734VnlI+W4+y7BoN5wt
uqVrqWbbpOQ2sHYo9riv3b+x5WdsMrVieKGApQ/dNvgB5vuuAchRnsANZHgpAiPCzP7/QFYY
qk2undcxEXwPgo72oifB3uQZ3xHOV/cCAwEAAaOCAXIwggFuMBIGA1UdEwEB/wQIMAYBAf8C
AQAwHQYDVR0OBBYEFE8dr4jKbbiqHAn5xdER7Vm0k/oLMA4GA1UdDwEB/wQEAwIBBjAfBgNV
HSMEGDAWgBQvRUIeMQWA1XDY+B1Xy1t61T2c9zB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8v
Y3JsLnBraS5mcmF1bmhvZmVyLmRlL2ZoZy1yb290LWNhLTIwMDcuY3JshjFodHRwOi8vY3Js
LmZyYXVuaG9mZXItcGtpLmRlL2ZoZy1yb290LWNhLTIwMDcuY3JsMIGQBggrBgEFBQcBAQSB
gzCBgDA+BggrBgEFBQcwAoYyaHR0cDovL2NlcnQucGtpLmZyYXVuaG9mZXIuZGUvZmhnLXJv
b3QtY2EtMjAwNy5jZXIwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LmZyYXVuaG9mZXItcGtp
LmRlL2ZoZy1yb290LWNhLTIwMDcuY2VyMA0GCSqGSIb3DQEBBQUAA4IBAQAAd2yMM/nuVwQl
ysuIOeZOTKTOwpZLGYZNuERXwpWpEDfsMFUxX/Wetbu1a1qhd+x6SyXY4V1CzcFDOGF3wA7b
yIV/6dyC53I9luZTjy9zjUsjLZucD4jeNja3QEu39sQsYsuE3MTfFFJgr/NeAFMHVkkHGx3l
VXb+F3J3+9xeXHk/wB/yIKd/RIiMMTT4+a+ra2MTCsYAe4kgJ0vz2TXYGN8tujjCgsUUbwfJ
C9wrOiCJMNJM1i7sUVqVKIoswW7h5QpWUNu1E4RAsDEz7depXCYaAIwPprEIkr0dE63zqHhm
M4egS7iGmBfNQohUO6jJOWNcJ9dIxqc0c/4WUHg8MIIFpjCCBI6gAwIBAgIKFcglDgAAAAII
ozANBgkqhkiG9w0BAQUFADBnMQswCQYDVQQGEwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEh
MB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3JhdGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVy
IFVzZXIgQ0EgMjAwNzAeFw0xMzEyMTcxMjM1NDdaFw0xOTA2MzAyMzU5NTlaMFkxCzAJBgNV
BAYTAkRFMRMwEQYDVQQKEwpGcmF1bmhvZmVyMQwwCgYDVQQLEwNTSVQxDzANBgNVBAsTBlBl
b3BsZTEWMBQGA1UEAxMNSGVuayBCaXJraG9sejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAKsXgaAh0xiGvFnwWielNH0sAuapRSYZM2mzLEPl1Euoq/3VkbY2P1MbzIsb/8+Q
mKB64li7vParM+zPL7zjijzHRqgJYkOIDS1jA1CBqAQvDd1AUPmi9ZfwJ7dSX0kF6Z85bF6R
HkQZLps4HeTqC1tzexuplZUClTCTxCJu4FioaqEbeh4w117vEC/gEJlvr4t/jsHwgv4LwCY6
PT4iaCA6tCnpnwH+/acol7huFwA+KvDLiFZupdqt4P1wlVENq+GIAc/9TcND0wSICyI6ny74
tGvoV/RfroHM3oSUEGzRsWgq/InxQi9/I3ufqXVHxkMLRCJojN00Ovjrdi7qwpECAwEAAaOC
AmAwggJcMA4GA1UdDwEB/wQEAwIGwDAqBgNVHREEIzAhgR9oZW5rLmJpcmtob2x6QHNpdC5m
cmF1bmhvZmVyLmRlMB0GA1UdDgQWBBRQ1jZ98/8G4Zq4bKXRDy1tlI0JgjAfBgNVHSMEGDAW
gBRPHa+Iym24qhwJ+cXREe1ZtJP6CzB1BgNVHR8EbjBsMGqgaKBmhjFodHRwOi8vY3JsLnBr
aS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JshjFodHRwOi8vY3JsLmZyYXVu
aG9mZXItcGtpLmRlL2ZoZy11c2VyLWNhLTIwMDcuY3JsMIIBCgYIKwYBBQUHAQEEgf0wgfow
PgYIKwYBBQUHMAKGMmh0dHA6Ly9jZXJ0LnBraS5mcmF1bmhvZmVyLmRlL2ZoZy11c2VyLWNh
LTIwMDcuY2VyMD4GCCsGAQUFBzAChjJodHRwOi8vY2VydC5mcmF1bmhvZmVyLXBraS5kZS9m
aGctdXNlci1jYS0yMDA3LmNlcjA7BggrBgEFBQcwAYYvaHR0cDovL2ZoZy11c2VyLWNhLTIw
MDcub2NzcC5wa2kuZnJhdW5ob2Zlci5kZS8wOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNl
ci1jYS0yMDA3Lm9jc3AuZnJhdW5ob2Zlci1wa2kuZGUvMBMGA1UdJQQMMAoGCCsGAQUFBwME
MEQGA1UdIAQ9MDswOQYLKwYBBAGGClADAQEwKjAoBggrBgEFBQcCARYcaHR0cDovL3BraS5m
cmF1bmhvZmVyLmRlL2NwLzANBgkqhkiG9w0BAQUFAAOCAQEAlHj5O+ExJF+2q0FK+dRcWQb3
vcDAyaTXqotBwJgYRJVs6LV6kkw74CSDg1TPlr1FG9dEzS2MZbiPhtE1CqN3yEf40MJBLYFi
KG0DIJwX3YmmBmK5QbIE+1EQ0MzPKomYqDiBUuC7POBiTGRPpYCrvHEfVZ+BuVlsMsvCp9aK
6vn91k/pWHF0AU0tJVhOGCjlrJsCwn/nP/4qTNf/nSE8etykPvYvu799B4Tdljlvrt/WeaVo
yA1Jl9WPny96OCa4qJaDWUMnjTUt14NICuwGV9bype+q9dorsogyhnQEO4rDcaFdKxmjmoV+
agEy1JX4jR6iTaKmWYgIIXy6gMnHmTCCBbIwggSaoAMCAQICCkSGTToAAAAB174wDQYJKoZI
hvcNAQEFBQAwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAfBgNVBAsT
GEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBVc2VyIENB
IDIwMDcwHhcNMTMwNzMwMTExNTA4WhcNMTkwNjMwMjM1OTU5WjBZMQswCQYDVQQGEwJERTET
MBEGA1UEChMKRnJhdW5ob2ZlcjEMMAoGA1UECxMDU0lUMQ8wDQYDVQQLEwZQZW9wbGUxFjAU
BgNVBAMTDUhlbmsgQmlya2hvbHowggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDj
tnr/To9XMlYudCBG2zL6U9stsuWyzIHvJ7al9p1tQakgTYiwTdX5/jsNA1JeHj+TJhzThxh7
nyBfONgy0EUgv835UJw5j4Tknlp5HdU39GMqEdAPd1791E50slOnKpGEjQwd8h6Cw73eF4YN
1QYlfbeoGPt+Tb1z+RUoauQto0atHhnU0rLX1mQ6tZXMMZ9FZcFgC7oVmwtwbK8URIVIlaHo
lGCgOfWfgHxSQICRr9j7kT25xHJ+oimXCb0lIyBuSKAJzo/OHFhIx9cNNGlAwzaynUhU8I1B
6vr9M580bCCEzRSOXzJOFxkhDaX+PinaHxa7SnQAgxlWvckXTEmPAgMBAAGjggJsMIICaDAO
BgNVHQ8BAf8EBAMCBDAwKgYDVR0RBCMwIYEfaGVuay5iaXJraG9sekBzaXQuZnJhdW5ob2Zl
ci5kZTAdBgNVHQ4EFgQUZTNsNue6lgNe5EoFiD4xR0w8XsIwHwYDVR0jBBgwFoAUTx2viMpt
uKocCfnF0RHtWbST+gswdQYDVR0fBG4wbDBqoGigZoYxaHR0cDovL2NybC5wa2kuZnJhdW5o
b2Zlci5kZS9maGctdXNlci1jYS0yMDA3LmNybIYxaHR0cDovL2NybC5mcmF1bmhvZmVyLXBr
aS5kZS9maGctdXNlci1jYS0yMDA3LmNybDCCAQoGCCsGAQUFBwEBBIH9MIH6MD4GCCsGAQUF
BzAChjJodHRwOi8vY2VydC5wa2kuZnJhdW5ob2Zlci5kZS9maGctdXNlci1jYS0yMDA3LmNl
cjA+BggrBgEFBQcwAoYyaHR0cDovL2NlcnQuZnJhdW5ob2Zlci1wa2kuZGUvZmhnLXVzZXIt
Y2EtMjAwNy5jZXIwOwYIKwYBBQUHMAGGL2h0dHA6Ly9maGctdXNlci1jYS0yMDA3Lm9jc3Au
cGtpLmZyYXVuaG9mZXIuZGUvMDsGCCsGAQUFBzABhi9odHRwOi8vZmhnLXVzZXItY2EtMjAw
Ny5vY3NwLmZyYXVuaG9mZXItcGtpLmRlLzAfBgNVHSUEGDAWBgorBgEEAYI3CgMEBggrBgEF
BQcDBDBEBgNVHSAEPTA7MDkGCysGAQQBhgpQAwEBMCowKAYIKwYBBQUHAgEWHGh0dHA6Ly9w
a2kuZnJhdW5ob2Zlci5kZS9jcC8wDQYJKoZIhvcNAQEFBQADggEBACzw+XqMZ39YLL77+Pmq
ELSv8Ioyy9CXbsaYYsXEjKLGKvQix4o8MANvpoT6iyrDrqreaofsUd0YhdXd2PUJVZ92ujTA
BMq6fMJGvrty95zwW0lX0SWYqcSobX3mmW4D9nQpDEPEJGQ095kk3SzAFYO7ZHj9Srt1G2hq
UovZP5/aYk+CpYbml+uYlU4Ux/KtYD66k9I9YFCiHKpzNxgoKlzDlkZ2a2uRPYKBFqBqKRee
5TM1DB47l89K1xw3eUWcxcwjusZc2z6EZqk8CgyRXz+m+zK5LCnvSf+1nuR9T5OcmiPwJgpO
8qw3Yoer628t6NfTkz/a49vUgtSlq3kNURsxggN7MIIDdwIBATB1MGcxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpGcmF1bmhvZmVyMSEwHwYDVQQLExhGcmF1bmhvZmVyIENvcnBvcmF0ZSBQ
S0kxIDAeBgNVBAMTF0ZyYXVuaG9mZXIgVXNlciBDQSAyMDA3AgoVyCUOAAAAAgijMAkGBSsO
AwIaBQCgggHbMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE1
MDIwNDA5MDExNlowIwYJKoZIhvcNAQkEMRYEFNoglbSPifps/xRbPUjKLWKtZyiOMGwGCSqG
SIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggq
hkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYQG
CSsGAQQBgjcQBDF3MHUwZzELMAkGA1UEBhMCREUxEzARBgNVBAoTCkZyYXVuaG9mZXIxITAf
BgNVBAsTGEZyYXVuaG9mZXIgQ29ycG9yYXRlIFBLSTEgMB4GA1UEAxMXRnJhdW5ob2ZlciBV
c2VyIENBIDIwMDcCCkSGTToAAAAB174wgYYGCyqGSIb3DQEJEAILMXegdTBnMQswCQYDVQQG
EwJERTETMBEGA1UEChMKRnJhdW5ob2ZlcjEhMB8GA1UECxMYRnJhdW5ob2ZlciBDb3Jwb3Jh
dGUgUEtJMSAwHgYDVQQDExdGcmF1bmhvZmVyIFVzZXIgQ0EgMjAwNwIKRIZNOgAAAAHXvjAN
BgkqhkiG9w0BAQEFAASCAQAt3EwHaEZOisD/MAneb2axK2M74IiS80SadzaWPy7Vh5T0+PCf
HBII9RSs9h6yasbqvuZJMfSzHK7+E9GCmmylBfObbYdQkQbdQ/T2nGUiUZxRAM1a6fZmL+GO
QTiWFUdeXblap9eVzm+lUd6/Yi3qPojSM94psm+zMmOcdJjwF20M5+P2xplx0ST8iCgUJRtf
er0rYYJcOKzMKxtoCLKdm0k9JVZoOTFtGruBQGFfM8P4+aohXFpE+EF8O+3iTQgBA7aAQjwb
K4iuRVReExrDDJVgTj7vmp1ztvBSS+Bq6qpeW3ytLQ+z/Nt4Y7HfOJ6b8qP7DawcVWQBLqgZ
eTgEAAAAAAAA
--------------ms020904070901010307060604--


From nobody Wed Feb  4 11:57:28 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8797C1A1B61 for <sacm@ietfa.amsl.com>; Wed,  4 Feb 2015 11:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 BWkmTKhyDAdH for <sacm@ietfa.amsl.com>; Wed,  4 Feb 2015 11:57:25 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EC711A6FF5 for <sacm@ietf.org>; Wed,  4 Feb 2015 11:57:24 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigGACp50lSHCzIm/2dsb2JhbABAFwOCQyEiIjBZBIUCqnMFBpIXHQEIhXICgSFDAQEBAQEBfIQOAQEBAhIbOSUBFQUQCgQMPBcNAgEEGwEZiAsBDDewHYR/j3aREAEKAQEBHoYEiTATCxYMHAeCFQxAHYETBY8Qg1CGcDaCTYI7iFGDPSKBW4FFTm8BAQGBQX4BAQE
X-IronPort-AV: E=Sophos;i="5.09,519,1418101200";  d="scan'208,217";a="105479814"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 04 Feb 2015 14:57:23 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 04 Feb 2015 14:57:22 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Wed, 4 Feb 2015 20:57:21 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Feb 9 SACM WG Interim - Agenda and Logistics
Thread-Index: AdBAtMW029kzuqTPRDuZpgSbZxggdQ==
Date: Wed, 4 Feb 2015 19:57:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C981A80@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A80AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/odehmH3gUnB_3-_AOGkGPKPgV7U>
Subject: [sacm] Feb 9 SACM WG Interim - Agenda and Logistics
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 19:57:27 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A80AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Our next WG virtual interim is scheduled for Monday 2/9, 10AM to noon EST.

The preliminary agenda is posted at http://www.ietf.org/proceedings/interim=
/2015/02/09/sacm/agenda/agenda-interim-2015-sacm-2. Unless updates will be =
posted before Monday (will they be?) I expect the Requirements and Architec=
ture slots to be rather short and to deal mainly with comments received sin=
ce the previous virtual interim. We shall spend most of our time discussing=
 the design team status and open issues.

Bashing the agenda can start right now.

As always we will need two volunteers to take notes. Please do not be timid=
.

The logistic of the call are as follows:


SACM

Monday, January 5, 2015

7:00 am  |  Pacific Standard Time (San Francisco, GMT-08:00)  |  2 hr

Join WebEx meeting:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_j.php-3FMTID-3Dmbd5c89b8b5118b478637e1f934838939&d=3DAAICaQ&c=3DB=
FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D-=
iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&s=3D3h9hmHCJ61OxHdpuSSFLbMqlb33t=
kpAovQxY9WwSUPM&e=3D

Meeting number: 827 426 527

Meeting password: 1234

Join by phone

1-877-668-4490 Call-in toll-free number (US/Canada)

1-408-792-6300 Call-in toll number (US/Canada) Access code: 827 426 527 Glo=
bal call-in numbers:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_globalcallin.php-3FserviceType-3DMC-26ED-3D291916977-26tollFree-3=
D1&d=3DAAICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXR=
ucPvdrphpBsFA&m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&s=3D9guoNkXRd=
vJy_41LP_rBUECzDwTfu4Nn-Z13r7LJMVY&e=3D

Toll-free calling restrictions:

https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.webex.com_pdf_tol=
lfree-5Frestrictions.pdf&d=3DAAICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR3=
1OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazS=
jegpEw7M&s=3D_8inPJarrr9B73XErB2bUtxCPsbf3LXnUmR8oFkR6q8&e=3D



Add this meeting to your calendar:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_j.php-3FMTID-3Dm92cdb6e414ef4f94e76fcf895ff398a1&d=3DAAICaQ&c=3DB=
FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D-=
iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&s=3D1mZU6LHn4eKpAhjn3QMjVJJcWyIH=
dejEmgUYfQKm6uU&e=3D



Can't join the meeting? Contact support:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_mc&d=3DAAICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvl=
siLQfucBXRucPvdrphpBsFA&m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&s=
=3D0DwlQg1cLsF6_B0g8MMRaeUijQFDq-pFa1Z6QC5MSsc&e=3D



Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A80AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Our next WG virtual interim is scheduled for Monday =
2/9, 10AM to noon EST.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The preliminary agenda is posted at <a href=3D"http:=
//www.ietf.org/proceedings/interim/2015/02/09/sacm/agenda/agenda-interim-20=
15-sacm-2">
http://www.ietf.org/proceedings/interim/2015/02/09/sacm/agenda/agenda-inter=
im-2015-sacm-2</a>. Unless updates will be posted before Monday (will they =
be?) I expect the Requirements and Architecture slots to be rather short an=
d to deal mainly with comments received
 since the previous virtual interim. We shall spend most of our time discus=
sing the design team status and open issues.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Bashing the agenda can start right now. <o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As always we will need two volunteers to take notes.=
 Please do not be timid.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The logistic of the call are as follows: <o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">SACM<o:p></o:p></p>
<p class=3D"MsoPlainText">Monday, January 5, 2015<o:p></o:p></p>
<p class=3D"MsoPlainText">7:00 am&nbsp; |&nbsp; Pacific Standard Time (San =
Francisco, GMT-08:00)&nbsp; |&nbsp; 2 hr<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Join WebEx meeting:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_j.php-3FMTID-3Dmbd5c89b8b511=
8b478637e1f934838939&amp;d=3DAAICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3D=
I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4vZ1ya7Y=
bUMb90kAuazSjegpEw7M&amp;s=3D3h9hmHCJ61OxHdpuSSFLbMqlb33tkpAovQxY9WwSUPM&am=
p;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex=
.com_workgreen_j.php-3FMTID-3Dmbd5c89b8b5118b478637e1f934838939&amp;d=3DAAI=
CaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRuc=
PvdrphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D3h9=
hmHCJ61OxHdpuSSFLbMqlb33tkpAovQxY9WwSUPM&amp;e</a>=3D<o:p></o:p></p>
<p class=3D"MsoPlainText">Meeting number: 827 426 527<o:p></o:p></p>
<p class=3D"MsoPlainText">Meeting password: 1234<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Join by phone<o:p></o:p></p>
<p class=3D"MsoPlainText">1-877-668-4490 Call-in toll-free number (US/Canad=
a)<o:p></o:p></p>
<p class=3D"MsoPlainText">1-408-792-6300 Call-in toll number (US/Canada) Ac=
cess code: 827 426 527 Global call-in numbers:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_globalcallin.php-3FserviceTy=
pe-3DMC-26ED-3D291916977-26tollFree-3D1&amp;d=3DAAICaQ&amp;c=3DBFpWQw8bsuKp=
l1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D-iT3=
ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D9guoNkXRdvJy_41LP_rBUECzDwT=
fu4Nn-Z13r7LJMVY&amp;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=
3A__workgreen.webex.com_workgreen_globalcallin.php-3FserviceType-3DMC-26ED-=
3D291916977-26tollFree-3D1&amp;d=3DAAICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&am=
p;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4v=
Z1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D9guoNkXRdvJy_41LP_rBUECzDwTfu4Nn-Z13r7LJ=
MVY&amp;e</a>=3D<o:p></o:p></p>
<p class=3D"MsoPlainText">Toll-free calling restrictions: <o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttp-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&amp;d=3DAAICa=
Q&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPv=
drphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D_8inP=
Jarrr9B73XErB2bUtxCPsbf3LXnUmR8oFkR6q8&amp;e">https://urldefense.proofpoint=
.com/v2/url?u=3Dhttp-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&amp;=
d=3DAAICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQf=
ucBXRucPvdrphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;=
s=3D_8inPJarrr9B73XErB2bUtxCPsbf3LXnUmR8oFkR6q8&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Add this meeting to your calendar:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_j.php-3FMTID-3Dm92cdb6e414ef=
4f94e76fcf895ff398a1&amp;d=3DAAICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3D=
I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4vZ1ya7Y=
bUMb90kAuazSjegpEw7M&amp;s=3D1mZU6LHn4eKpAhjn3QMjVJJcWyIHdejEmgUYfQKm6uU&am=
p;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex=
.com_workgreen_j.php-3FMTID-3Dm92cdb6e414ef4f94e76fcf895ff398a1&amp;d=3DAAI=
CaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRuc=
PvdrphpBsFA&amp;m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D1mZ=
U6LHn4eKpAhjn3QMjVJJcWyIHdejEmgUYfQKm6uU&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Can't join the meeting? Contact support:<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_mc&amp;d=3DAAICaQ&amp;c=3DBF=
pWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&am=
p;m=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D0DwlQg1cLsF6_B0g8=
MMRaeUijQFDq-pFa1Z6QC5MSsc&amp;e">https://urldefense.proofpoint.com/v2/url?=
u=3Dhttps-3A__workgreen.webex.com_workgreen_mc&amp;d=3DAAICaQ&amp;c=3DBFpWQ=
w8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=
=3D-iT3ty2kAuvLWRH4vZ1ya7YbUMb90kAuazSjegpEw7M&amp;s=3D0DwlQg1cLsF6_B0g8MMR=
aeUijQFDq-pFa1Z6QC5MSsc&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A80AZFFEXMB04globa_--


From nobody Wed Feb  4 11:59:09 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2247F1A1B61 for <sacm@ietfa.amsl.com>; Wed,  4 Feb 2015 11:59:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qrwseTtI1VWk for <sacm@ietfa.amsl.com>; Wed,  4 Feb 2015 11:59:06 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38D081A6F22 for <sacm@ietf.org>; Wed,  4 Feb 2015 11:59:05 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigGAOF40lSHCzIm/2dsb2JhbABAFwOCQyEiIjBZBIUCqnMFBpIXHQEIhXICgSFDAQEBAQEBfIQOAQEBAhIbOSUBFQUQCgQMPBcNAgEEGwEZiAsBDDewHIR/j3aREAEBCAEBAQEBHYYEiTATCxYMHAeCFQxAHYETBY8Qg1CDYIMQECaCTYI7iFGDPSKBW4FFTm8BAQGBQX4BAQE
X-IronPort-AV: E=Sophos; i="5.09,519,1418101200"; d="scan'208,217"; a="90175356"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Feb 2015 14:59:02 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 04 Feb 2015 14:58:58 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Wed, 4 Feb 2015 14:58:56 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Feb 9 SACM WG Interim - Agenda and Logistics
Thread-Index: AdBAtP7NuUADCkt8RSqyWUNHVCDl5w==
Date: Wed, 4 Feb 2015 19:58:56 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C981A93@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A93AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/u8S0v-XhdoTCww7mfO5FzUNZ5MI>
Subject: [sacm] Feb 9 SACM WG Interim - Agenda and Logistics
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 19:59:08 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A93AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

(corrected meeting information)

Hi,

Our next WG virtual interim is scheduled for Monday 2/9, 10AM to noon EST.

The preliminary agenda is posted at http://www.ietf.org/proceedings/interim=
/2015/02/09/sacm/agenda/agenda-interim-2015-sacm-2. Unless updates will be =
posted before Monday (will they be?) I expect the Requirements and Architec=
ture slots to be rather short and to deal mainly with comments received sin=
ce the previous virtual interim. We shall spend most of our time discussing=
 the design team status and open issues.

Bashing the agenda can start right now.

As always we will need two volunteers to take notes. Please do not be timid=
.

The logistic of the call are as follows:


SACM

Monday, February 9, 2015

7:00 am  |  Pacific Standard Time (San Francisco, GMT-08:00)  |  2 hr

Join WebEx meeting:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_j.php-3FMTID-3Dme6b5c19af8bff57de91bc774f18e7a65&d=3DAwICaQ&c=3DB=
FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D7=
2SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=3DySgHiH7hFrs_CQYgzNtlD78hOucw=
RjHL-oly2jqMUGU&e=3D

Meeting number:            823 993 527

Meeting password:         1234

Join by phone

1-877-668-4490 Call-in toll-free number (US/Canada)

1-408-792-6300 Call-in toll number (US/Canada) Access code: 823 993 527 Glo=
bal call-in numbers:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_globalcallin.php-3FserviceType-3DMC-26ED-3D291916977-26tollFree-3=
D1&d=3DAwICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXR=
ucPvdrphpBsFA&m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=3DzgDMqD2XB=
0x668uu2QfIbYiKA7wsPlPblgGu-ISvN_0&e=3D

Toll-free calling restrictions:

https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.webex.com_pdf_tol=
lfree-5Frestrictions.pdf&d=3DAwICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR3=
1OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2Y=
lhtGKPJ4&s=3DhHC4-eS62JH4Ty76TkJx5-UHx0aBwsZmF3j3y9Rugu4&e=3D



Add this meeting to your calendar:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_j.php-3FMTID-3Dme411e7e4ea3e92dbc6dee600a6175a14&d=3DAwICaQ&c=3DB=
FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D7=
2SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=3D_EwxJYlPScIkjYFUMrM2-UdpUTB3=
SK2Iqiiu3IH7TLI&e=3D



Can't join the meeting? Contact support:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_mc&d=3DAwICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvl=
siLQfucBXRucPvdrphpBsFA&m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=
=3D98IZc36v-aaM9CjBosIfYrQcytz_63JdN8a4HmoDhPM&e=3D



IMPORTANT NOTICE: Please note that this WebEx service allows audio and othe=
r information sent during the session to be recorded, which may be discover=
able in a legal matter. By joining this session, you automatically consent =
to such recordings. If you do not consent to being recorded, discuss your c=
oncerns with the host or do not join the session.



Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A93AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">(corrected meeting information)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Our next WG virtual interim is scheduled for Monday =
2/9, 10AM to noon EST.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The preliminary agenda is posted at <a href=3D"http:=
//www.ietf.org/proceedings/interim/2015/02/09/sacm/agenda/agenda-interim-20=
15-sacm-2">
http://www.ietf.org/proceedings/interim/2015/02/09/sacm/agenda/agenda-inter=
im-2015-sacm-2</a>. Unless updates will be posted before Monday (will they =
be?) I expect the Requirements and Architecture slots to be rather short an=
d to deal mainly with comments received
 since the previous virtual interim. We shall spend most of our time discus=
sing the design team status and open issues.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Bashing the agenda can start right now. <o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As always we will need two volunteers to take notes.=
 Please do not be timid.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The logistic of the call are as follows: <o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">SACM<o:p></o:p></p>
<p class=3D"MsoPlainText">Monday, February 9, 2015<o:p></o:p></p>
<p class=3D"MsoPlainText">7:00 am&nbsp; |&nbsp; Pacific Standard Time (San =
Francisco, GMT-08:00)&nbsp; |&nbsp; 2 hr<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Join WebEx meeting:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_j.php-3FMTID-3Dme6b5c19af8bf=
f57de91bc774f18e7a65&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3D=
I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB=
4Lse-epbFq2YlhtGKPJ4&amp;s=3DySgHiH7hFrs_CQYgzNtlD78hOucwRjHL-oly2jqMUGU&am=
p;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex=
.com_workgreen_j.php-3FMTID-3Dme6b5c19af8bff57de91bc774f18e7a65&amp;d=3DAwI=
CaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRuc=
PvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DySg=
HiH7hFrs_CQYgzNtlD78hOucwRjHL-oly2jqMUGU&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">Meeting number:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 823 993 527<o:p></o:p></p>
<p class=3D"MsoPlainText">Meeting password:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; 1234<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p></o:p></p>
<p class=3D"MsoPlainText">Join by phone<o:p></o:p></p>
<p class=3D"MsoPlainText">1-877-668-4490 Call-in toll-free number (US/Canad=
a)<o:p></o:p></p>
<p class=3D"MsoPlainText">1-408-792-6300 Call-in toll number (US/Canada) Ac=
cess code: 823 993 527 Global call-in numbers:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_globalcallin.php-3FserviceTy=
pe-3DMC-26ED-3D291916977-26tollFree-3D1&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKp=
l1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72Sa=
mZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DzgDMqD2XB0x668uu2QfIbYiKA7w=
sPlPblgGu-ISvN_0&amp;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=
3A__workgreen.webex.com_workgreen_globalcallin.php-3FserviceType-3DMC-26ED-=
3D291916977-26tollFree-3D1&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&am=
p;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiyw=
YAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DzgDMqD2XB0x668uu2QfIbYiKA7wsPlPblgGu-ISv=
N_0&amp;e</a>=3D<o:p></o:p></p>
<p class=3D"MsoPlainText">Toll-free calling restrictions: <o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttp-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&amp;d=3DAwICa=
Q&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPv=
drphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DhHC4-=
eS62JH4Ty76TkJx5-UHx0aBwsZmF3j3y9Rugu4&amp;e">https://urldefense.proofpoint=
.com/v2/url?u=3Dhttp-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&amp;=
d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQf=
ucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;=
s=3DhHC4-eS62JH4Ty76TkJx5-UHx0aBwsZmF3j3y9Rugu4&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Add this meeting to your calendar:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_j.php-3FMTID-3Dme411e7e4ea3e=
92dbc6dee600a6175a14&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3D=
I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB=
4Lse-epbFq2YlhtGKPJ4&amp;s=3D_EwxJYlPScIkjYFUMrM2-UdpUTB3SK2Iqiiu3IH7TLI&am=
p;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex=
.com_workgreen_j.php-3FMTID-3Dme411e7e4ea3e92dbc6dee600a6175a14&amp;d=3DAwI=
CaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRuc=
PvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3D_Ew=
xJYlPScIkjYFUMrM2-UdpUTB3SK2Iqiiu3IH7TLI&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Can't join the meeting? Contact support:<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_mc&amp;d=3DAwICaQ&amp;c=3DBF=
pWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&am=
p;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3D98IZc36v-aaM9CjBo=
sIfYrQcytz_63JdN8a4HmoDhPM&amp;e">https://urldefense.proofpoint.com/v2/url?=
u=3Dhttps-3A__workgreen.webex.com_workgreen_mc&amp;d=3DAwICaQ&amp;c=3DBFpWQ=
w8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=
=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3D98IZc36v-aaM9CjBosIf=
YrQcytz_63JdN8a4HmoDhPM&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">IMPORTANT NOTICE: Please note that this WebEx ser=
vice allows audio and other information sent during the session to be recor=
ded, which may be discoverable in a legal matter. By joining this session, =
you automatically consent to such
 recordings. If you do not consent to being recorded, discuss your concerns=
 with the host or do not join the session.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C981A93AZFFEXMB04globa_--


From nobody Thu Feb  5 10:46:56 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 434E51A1B04 for <sacm@ietfa.amsl.com>; Thu,  5 Feb 2015 10:46:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 IkiSwFWN4sSm for <sacm@ietfa.amsl.com>; Thu,  5 Feb 2015 10:46:53 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0660.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:660]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5A691A1A95 for <sacm@ietf.org>; Thu,  5 Feb 2015 10:46:52 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1354.namprd06.prod.outlook.com (25.161.212.12) with Microsoft SMTP Server (TLS) id 15.1.75.20; Thu, 5 Feb 2015 18:46:29 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Thu, 5 Feb 2015 18:46:29 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Gut Check?
Thread-Index: AQHQP+vgWwCAp9C20E+mP3X8UKCHIJziTlgw
Date: Thu, 5 Feb 2015 18:46:28 +0000
Message-ID: <CY1PR0601MB135559CAF4238A5F27567755B73B0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <54CFC879.8050504@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: avaya.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1354;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1354; 
x-forefront-prvs: 0478C23FE0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(51444003)(52604005)(102836002)(15975445007)(33656002)(76576001)(2501002)(106116001)(86362001)(122556002)(2900100001)(2950100001)(92566002)(40100003)(77156002)(62966003)(19580395003)(99286002)(66066001)(76176999)(46102003)(50986999)(74316001)(87936001)(107886001)(54356999)(2656002)(7059030); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1354; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2015 18:46:28.7893 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1354
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/pibX0WCHCNQsvEdeaENvxVZLMAQ>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 18:46:55 -0000

Gunnar,
Thanks for raising this. I find it clarifying. Some of us have been down in=
 the weeds, with caterpillars.=20

You write:

> What enables automated assessments is the ability to express the=20
> assessment goal in a machine-executable format. =20

In the SACM model, assessment goals would be expressed as Guidance objects.=
=20
We have not talked much about what is in a Guidance object. Gunnar, I think
that is your concern -- am I right?

However, there are existing standards for expressing assessment goals, incl=
uding:
	- OVAL (http://oval.mitre.org/)=20
	- XCCDF (http://scap.nist.gov/specifications/xccdf/)=20
	- Other members of the SCAP family

I think SACM should complement these standards. I think it makes sense to u=
se such notations in Guidance instances. If so, we should make sure that wo=
uld work: for example, that the information model expresses the inputs that=
 an XCCDF engine needs.

I don't think SACM is about creating a new standard for assessment goals. I=
 think SACM is largely about  *assessment agility*. In response to an emerg=
ent threat:

	- One can update guidance, and the new guidance will take immediate effect=
 everywhere it needs to, so that the right attributes are collected and the=
 evaluators check the right things.

	- If that isn't sufficient, one can deploy a new evaluator, an antidote cr=
eated for the threat. It's not necessary that this new evaluator take its g=
uidance in a standard notation. For agility, we need to encourage both inno=
vation and standardization.=20

Today, evaluators are largely bound up with collectors. If I want to apply =
a new evaluator to my 100,000 endpoints, I need to install it on 100,000 en=
dpoints. That's a massive deployment effort. Because of the variety of plat=
forms in use, I may need a Windows version, a Mac version, an Android versi=
on, etc. That's a big software development effort. Some of these platforms =
accept updates only from app stores. Getting software into an app store tak=
es time. The current reality is far from agile. Decoupling evaluators from =
collectors will help.=20

In conclusion, a good standard for collecting and communicating endpoint at=
tributes will fill a gap.=20

But as you say, we need to keep our eye on the higher level goal they are i=
n service to. And so, it would be good to check what endpoint attributes an=
 XCCDF engine (for example) needs, and make sure our model has them.=20

Best,
			Cliff


From nobody Thu Feb  5 12:02:04 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91261A8ABB for <sacm@ietfa.amsl.com>; Thu,  5 Feb 2015 12:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 bdXifk7_cylg for <sacm@ietfa.amsl.com>; Thu,  5 Feb 2015 12:01:52 -0800 (PST)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A321A8ABD for <sacm@ietf.org>; Thu,  5 Feb 2015 12:01:44 -0800 (PST)
Received: by mail-lb0-f181.google.com with SMTP id u14so4638003lbd.12 for <sacm@ietf.org>; Thu, 05 Feb 2015 12:01:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NpC2sdOKgFQeiDM7DdzmIF5dYNYDy8cCOhESkj9sIsA=; b=U9I3OtSh7qjQEMhzkjM7X40CcbpbetJJsHj2VG90n2vaC+5mqZPKBIXbFuge5RGu27 3+oR3mSYfvHs7zDzM86aJbINKZezIDRSLTlOh3I3H1vulEgZ6CTMfM3VFvHCuqqDSx3Y 6ok1LM8wqdrWLeQvKokqPtu2NYqNrL1U2uhBLRLNPruXy7oBTIlbto2+qfXdbzQr/to0 wX8u2oFJ7vWBYSr08BTOQ5xxktR45S0TzPt8+qpImMfREibrUdXcd8jv+fK7hYScOjl8 6S3D0AhtcBnhJOwRvCjeqYeBGegA3gHD2+8qpXTpHu3oeClD1yzqk9Bl5GWYKTNhGljS 3xUg==
MIME-Version: 1.0
X-Received: by 10.152.204.97 with SMTP id kx1mr5710254lac.75.1423166502946; Thu, 05 Feb 2015 12:01:42 -0800 (PST)
Received: by 10.112.167.134 with HTTP; Thu, 5 Feb 2015 12:01:42 -0800 (PST)
In-Reply-To: <CY1PR0601MB135559CAF4238A5F27567755B73B0@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <54CFC879.8050504@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com> <CY1PR0601MB135559CAF4238A5F27567755B73B0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Date: Thu, 5 Feb 2015 15:01:42 -0500
Message-ID: <CAHbuEH7x07FsOtTFhoXqHn5+MaeY5yv2FNQTHsnS800awxjYXw@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Clifford Kahn <cliffordk@pulsesecure.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/bHtl41qoXh6RAxgMKaSMUNUX2Zg>
Cc: Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 20:01:56 -0000

On Thu, Feb 5, 2015 at 1:46 PM, Clifford Kahn <cliffordk@pulsesecure.net> w=
rote:
> Gunnar,
> Thanks for raising this. I find it clarifying. Some of us have been down =
in the weeds, with caterpillars.
>
> You write:
>
>> What enables automated assessments is the ability to express the
>> assessment goal in a machine-executable format.
>
> In the SACM model, assessment goals would be expressed as Guidance object=
s.
> We have not talked much about what is in a Guidance object. Gunnar, I thi=
nk
> that is your concern -- am I right?
>
> However, there are existing standards for expressing assessment goals, in=
cluding:
>         - OVAL (http://oval.mitre.org/)
>         - XCCDF (http://scap.nist.gov/specifications/xccdf/)
>         - Other members of the SCAP family

YANG modules are another possibility and are used everywhere else.
There is a bit of an explosion of them in the IETF and in the open
source community at the moment.  If YANG can be used, it should be
considered.  Not all devices will want to support SCAP.

-Kathleen
contributor hat
>
> I think SACM should complement these standards. I think it makes sense to=
 use such notations in Guidance instances. If so, we should make sure that =
would work: for example, that the information model expresses the inputs th=
at an XCCDF engine needs.
>
> I don't think SACM is about creating a new standard for assessment goals.=
 I think SACM is largely about  *assessment agility*. In response to an eme=
rgent threat:
>
>         - One can update guidance, and the new guidance will take immedia=
te effect everywhere it needs to, so that the right attributes are collecte=
d and the evaluators check the right things.
>
>         - If that isn't sufficient, one can deploy a new evaluator, an an=
tidote created for the threat. It's not necessary that this new evaluator t=
ake its guidance in a standard notation. For agility, we need to encourage =
both innovation and standardization.
>
> Today, evaluators are largely bound up with collectors. If I want to appl=
y a new evaluator to my 100,000 endpoints, I need to install it on 100,000 =
endpoints. That's a massive deployment effort. Because of the variety of pl=
atforms in use, I may need a Windows version, a Mac version, an Android ver=
sion, etc. That's a big software development effort. Some of these platform=
s accept updates only from app stores. Getting software into an app store t=
akes time. The current reality is far from agile. Decoupling evaluators fro=
m collectors will help.
>
> In conclusion, a good standard for collecting and communicating endpoint =
attributes will fill a gap.
>
> But as you say, we need to keep our eye on the higher level goal they are=
 in service to. And so, it would be good to check what endpoint attributes =
an XCCDF engine (for example) needs, and make sure our model has them.
>
> Best,
>                         Cliff
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm



--=20

Best regards,
Kathleen


From nobody Thu Feb  5 13:40:27 2015
Return-Path: <gunnar.engelbach@threatguard.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA7D1A6F22 for <sacm@ietfa.amsl.com>; Thu,  5 Feb 2015 13:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 VXsQJA7qMvlU for <sacm@ietfa.amsl.com>; Thu,  5 Feb 2015 13:40:18 -0800 (PST)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01E601A6F0E for <sacm@ietf.org>; Thu,  5 Feb 2015 13:40:17 -0800 (PST)
Received: by mail-qc0-f182.google.com with SMTP id l6so8692377qcy.13 for <sacm@ietf.org>; Thu, 05 Feb 2015 13:40:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ldo7v93FAHEJKASaZxDhILQXIqoDonP4aaRy9vSBHGA=; b=SVpv+QXitOb1g+s/AYinLKTFqeZtIc+ObkZ2Xv9u9Uk4ofmAEj2b4by72+Xi2f/s1Z nGS3pixwl5TnrCTCHx4pwfRDu8T2Zn6cklsd/Ha1Rz0Rns6ZXcI6ix9Xl4SIj6hjLzwX JbQzG8tryKs2X43VcdjIXuhmUWMg/ryzHU/KHMqNZMCWQWEoXJUiMXF7agPaThmYvbLy R5L+7TNhf497l4J0hI8kBPW9f1qGdg4+ysAAmZzZMuF3mob9CsI0+uWwX3nZQY/H4hIO pQUKhiKKrokUVG02+ONjiIrDXmxkQ9yZaB/hHAz4JQRpU/kq3Tz2SeTR1XCYCukOs4K+ 8uyA==
X-Gm-Message-State: ALoCoQmfEIGZtZcOuQFyfROGF6uiwaZdCopSZB1y2bsPz4ulfdKAK6p0sN/UUu39+eQ2aomFhwM0
X-Received: by 10.229.83.196 with SMTP id g4mr593536qcl.18.1423172417145; Thu, 05 Feb 2015 13:40:17 -0800 (PST)
Received: from [172.16.1.22] (h69-128-196-138.cntcnh.broadband.dynamic.tds.net. [69.128.196.138]) by mx.google.com with ESMTPSA id e2sm404557qaf.49.2015.02.05.13.40.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 13:40:16 -0800 (PST)
From: Gunnar Engelbach <gunnar.engelbach@threatguard.com>
X-Google-Original-From: Gunnar Engelbach <Gunnar.Engelbach@ThreatGuard.com>
Message-ID: <54D3C728.7040304@ThreatGuard.com>
Date: Thu, 05 Feb 2015 14:40:24 -0500
Organization: ThreatGuard, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Clifford Kahn <cliffordk@pulsesecure.net>,  "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "sacm@ietf.org" <sacm@ietf.org>
References: <54CFC879.8050504@ThreatGuard.com> <9904FB1B0159DA42B0B887B7FA8119CA5C97F5B6@AZ-FFEXMB04.global.avaya.com> <CY1PR0601MB135559CAF4238A5F27567755B73B0@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB135559CAF4238A5F27567755B73B0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/eqbUbZhkbRi-yO8bIS7d9oEzDZU>
Subject: Re: [sacm] Gut Check?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 21:40:23 -0000

Yes, XCCDF and OVAL are examples of what I am referring to, but I don't 
want to presuppose that those are the best way to solve this problem.

We have a nice set of requirements -- let's talk about those and let 
them drive us toward the best solution.

My point is that that decision needs to be made before we talk about 
collection in any detail -- otherwise you don't know how to respond to 
collection requests, what format the collected attributes need to be in 
so they can be properly interpreted, and how to unambiguously identify 
those attributes.


Something else I will point out about OVAL.  It doesn't just specify a 
flat list of attributes to collect, it can also contain logic structures 
that use a collected values to determine what to collect.

As a simple example, if you are interested in what minimal password 
length is being enforced by an endpoint, the correct place to look for 
that setting depends on whether the endpoint is using local 
authentication, YP, NIS/NIS+, Kerberos, etc.

If you develop a collector that is not aware of OVAL as the collection 
language, then it will not be capable of doing that collection.



As far as the cost of updating software on the endpoints goes, I 
entirely agree, and that's why starting at the top before moving down to 
the attributes is so important.

The set of attributes to collect is not a finite known set.  The list 
will change as new vulnerabilities are discovered, new software 
installed, the role of the endpoint changes, and so on.  In order to 
minimize the frequency with which the collection software needs to be 
updated, collection needs to be able to be done in a dynamic manner 
where what to collect and how to collect it is driven by the Guidance.

A secondary factor in that process is accuracy.  Collectors will be 
built by multiple vendors and their results can easily be different if 
the "what and how" of collection is not kept consistent.  If that "what 
and how" is a set of instructions provided by the Guidance, consistency 
between implementations becomes much less of an issue.




On 2/5/2015 1:46 PM, Clifford Kahn wrote:
> Gunnar,
> Thanks for raising this. I find it clarifying. Some of us have been down in the weeds, with caterpillars.
>
> You write:
>
>> What enables automated assessments is the ability to express the
>> assessment goal in a machine-executable format.
>
> In the SACM model, assessment goals would be expressed as Guidance objects.
> We have not talked much about what is in a Guidance object. Gunnar, I think
> that is your concern -- am I right?
>
> However, there are existing standards for expressing assessment goals, including:
> 	- OVAL (http://oval.mitre.org/)
> 	- XCCDF (http://scap.nist.gov/specifications/xccdf/)
> 	- Other members of the SCAP family
>
> I think SACM should complement these standards. I think it makes sense to use such notations in Guidance instances. If so, we should make sure that would work: for example, that the information model expresses the inputs that an XCCDF engine needs.
>
> I don't think SACM is about creating a new standard for assessment goals. I think SACM is largely about  *assessment agility*. In response to an emergent threat:
>
> 	- One can update guidance, and the new guidance will take immediate effect everywhere it needs to, so that the right attributes are collected and the evaluators check the right things.
>
> 	- If that isn't sufficient, one can deploy a new evaluator, an antidote created for the threat. It's not necessary that this new evaluator take its guidance in a standard notation. For agility, we need to encourage both innovation and standardization.
>
> Today, evaluators are largely bound up with collectors. If I want to apply a new evaluator to my 100,000 endpoints, I need to install it on 100,000 endpoints. That's a massive deployment effort. Because of the variety of platforms in use, I may need a Windows version, a Mac version, an Android version, etc. That's a big software development effort. Some of these platforms accept updates only from app stores. Getting software into an app store takes time. The current reality is far from agile. Decoupling evaluators from collectors will help.
>
> In conclusion, a good standard for collecting and communicating endpoint attributes will fill a gap.
>
> But as you say, we need to keep our eye on the higher level goal they are in service to. And so, it would be good to check what endpoint attributes an XCCDF engine (for example) needs, and make sure our model has them.
>
> Best,
> 			Cliff
>


From nobody Thu Feb  5 15:26:56 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0611A0BE8; Thu,  5 Feb 2015 15:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 slnKCIf5mQgx; Thu,  5 Feb 2015 15:26:43 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C41661A0016; Thu,  5 Feb 2015 15:26:42 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id l4so12821552lbv.13; Thu, 05 Feb 2015 15:26:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=kPg3WXcOqhy6w9vxqceCZEXE/E+i2/wslEFOgaLNbv8=; b=r9QmVriD5uoftSahxLHb8qf+HwObqnJi+zoD8yevPqpDCTcIqGfAerdByS6EJbe746 xCY6VU9FZgHFmUKGndLeb3LwLLS7w6BGqjjishBFpZRk5CfVej3FXZWoSDkI3bz6jLUG QB3ltDu2xHXfbwrxV5gl4BMhUuesgVLDoGQViqDFK0DE4neT8L/+8pXMjy2J9G+qHrZq 0NkEIjN73ivXIHdUgaSvK9P4LmvhWMSj2AIhVNOUsKXMnpoYzig0zJLIYi6Jy56HxM5u Q8yyvaclrhAWSOy67q9Higucg4kz6H8XxJU4+pm0ig5gzSByOMeZFfJmLwERQ4/vewxo Nufg==
MIME-Version: 1.0
X-Received: by 10.152.7.38 with SMTP id g6mr428710laa.65.1423178801288; Thu, 05 Feb 2015 15:26:41 -0800 (PST)
Received: by 10.112.167.134 with HTTP; Thu, 5 Feb 2015 15:26:41 -0800 (PST)
Date: Thu, 5 Feb 2015 18:26:41 -0500
Message-ID: <CAHbuEH43VZEFGFQQqBAYsoGTmhod+sZ-7p3QAP6rF6pscxPSbQ@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "ace@ietf.org" <ace@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c2906ce71a98050e5fa2db
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/IxEVhzSHH6UiMpxez4z5H0GxlhI>
Subject: [sacm] Use Case drafts - should they be published summary
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2015 23:26:49 -0000

--001a11c2906ce71a98050e5fa2db
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,

Sorry for the cross post, both WGs helped develop a list of arguments on
why their use case draft should be published.  I didn't get many messages
(and the chairs didn't either in private), so it seems most are in favor of
publishing use cases drafts.

I'll plan to chat about this with the IESG next week and wanted to share my
summary of reasons.  I ordered them, but didn't spend too much time
editing, as this won't be a living document (at least in this state).

Thanks again for your assistance!

----

*Use Case Drafts: Should they be published?*

*Reasons in favor:*


   1. If this is part of the WGs charter and a milestone, the work has
   already been agreed to be done and there is an expectation from those
   working on it that it will be published.  The WG has probably already
   sucked up this time if it's on the charter.  It would be unfair to pull =
it
   now.
   2. The IESG is here to serve the IETF.  If there is consensus to publish
   a use case draft, it should go forward.
   3. If the WG wants it published, it ought to be darn well be published.
   There=E2=80=99s no prohibition against uc/req drafts that I=E2=80=99m aw=
are of *AND* it=E2=80=99s
   an Informational RFC after all it=E2=80=99s *NOT* a standards track RFC.=
  There
   ought to be a lower bar for informational vs standards track and if ther=
e
   isn=E2=80=99t one then that=E2=80=99s really the IESG=E2=80=99s fault.
   4. The use cases draft helps to frame the problem(s) being addressed by
   the WG proposals and is important for guiding future development as well=
 as
   recording the history of consensus about the scope of work.
   5. Allows WGs to get cross-area review and IESG input earlier in the
   process on the whole WG concept.  That might be possible with just an IE=
TF
   LC, but that seems like a bit of a waste of time and probably wouldn=E2=
=80=99t be
   taken seriously by the reviewers without a =E2=80=9Cthreat=E2=80=9D of p=
ublication.
   6. They are usually informational with no RFC2119 language and should be
   easier to process.
   7. It is desirable to have a published document that can be found later
   to better understand the scope of work produced by a WG or can be used t=
o
   get a newcomer up-to-speed.  While an expired draft can technically be
   found, it's existence may not be known by those interested to read the
   draft. Dave Crocker's dependency graph off the WG page in the data track=
er
   include expires drafts.  Some expired drafts should go away, how would o=
ne
   distinguish in a traceable and helpful way?  You can't rely on wiki's to=
 be
   maintained after WGs disappear.
   8. A wiki to maintain this type of data is too dynamic and can't be
   trusted.  How do you distinguish versions and changes over time even if =
it
   isn't published as an RFC until the solutions are closer to final?
   9. In most scientific publications, referencing a weblink (like e.g. a
   wiki) is strongly discouraged due to their ephemeral nature. Having an R=
FC
   number is not only nice to have, it is quite essential if one is to refe=
r
   to this document in any serious article.
   10. The process of getting it published usually supplies a final jolt of
   energy that can make the document even better (and increase the focus of
   the WG in the process).  It is hard to overestimate this effect.
   11. From the ACE WG: One obvious reason for having this as a WG draft
   (published or not) is that some felt their input wasn't considered when =
it
   was an individual draft.
   12. People might be more motivated to contribute to a WG draft than to
   an individual draft.  People will also be more motivated to contribute i=
f
   the final result is a published document that they can point to when
   someone (employer, sponsor) asks them what the result of their work was.
   13. Publishing the draft as (informational) RFC also helps to valorize
   the work that the authors put into this document.  If the draft is just
   published as a wiki, this sends the message to many readers that IETF
   didn't consider this a worthy enough contribution for a real publication=
.
   This would also discourage future contributions to such documents
   (especially by scientists).
   14. WGs still have the energy*, and want to get this off the table so
   they can use it (as intended) as input for the specification-level
   discussion of the WG. Note: this may be especially true for newcomers to
   the IETF, it will help for them to see a progression of drafts and that
   work can move along.
   15. Diversity: If we want to encourage customer participation, this is
   one of the key areas in which they can contribute and have a positive
   impact on the work.  This may also help researchers who may be involved =
in
   use cases or subsequent phases where they raise awareness of existing wo=
rk
   to solve the problems discussed in the scope of work.


*Opposition:*


   1. It's time consuming for the IETF and ideally would have been
   completed prior to WG formation.  By the time use cases are complete, fo=
lks
   interested in solutions may have walked away already to go do something
   real, develop code.
   2. This process doesn't keep pace with the open source community and
   should be a pre-cursor to WG formation.  We need to figure out how to sp=
eed
   up.
   3. Use cases may be a moving target and may evolve over the course of
   the WG life.


----

Best regards,
Kathleen

--001a11c2906ce71a98050e5fa2db
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<br><br>Sorry for the cross post, both WGs helped de=
velop a list of arguments on why their use case draft should be published.=
=C2=A0 I didn&#39;t get many messages (and the chairs didn&#39;t either in =
private), so it seems most are in favor of publishing use cases drafts.<br>=
<br>I&#39;ll plan to chat about this with the IESG next week and wanted to =
share my summary of reasons.=C2=A0 I ordered them, but didn&#39;t spend too=
 much time editing, as this won&#39;t be a living document (at least in thi=
s state).<br><br>Thanks again for your assistance!<br><br>----<br><br><b>Us=
e Case Drafts: Should they be published?</b><br><br><b>Reasons in favor:</b=
><br><br><ol><li>If this is part of the WGs charter and a milestone, the wo=
rk has already been agreed to be done and there is an expectation from thos=
e working on it that it will be published.=C2=A0 The WG has probably alread=
y sucked up this time if it&#39;s on the charter.=C2=A0 It would be unfair =
to pull it now.<br></li><li>The IESG is here to serve the IETF.=C2=A0 If th=
ere is consensus to publish a use case draft, it should go forward.<br></li=
><li>If the WG wants it published, it ought to be darn well be published. T=
here=E2=80=99s no prohibition against uc/req drafts that I=E2=80=99m aware =
of *AND* it=E2=80=99s an Informational RFC after all it=E2=80=99s *NOT* a s=
tandards track RFC.=C2=A0 There ought to be a lower bar for informational v=
s standards track and if there isn=E2=80=99t one then that=E2=80=99s really=
 the IESG=E2=80=99s fault.<br></li><li>The use cases draft helps to frame t=
he problem(s) being addressed by the WG proposals and is important for guid=
ing future development as well as recording the history of consensus about =
the scope of work.<br></li><li>Allows WGs to get cross-area review and IESG=
 input earlier in the process on the whole WG concept.=C2=A0 That might be =
possible with just an IETF LC, but that seems like a bit of a waste of time=
 and probably wouldn=E2=80=99t be taken seriously by the reviewers without =
a =E2=80=9Cthreat=E2=80=9D of publication.<br></li><li>They are usually inf=
ormational with no RFC2119 language and should be easier to process.<br></l=
i><li>It is desirable to have a published document that can be found later =
to better understand the scope of work produced by a WG or can be used to g=
et a newcomer up-to-speed.=C2=A0 While an expired draft can technically be =
found, it&#39;s existence may not be known by those interested to read the =
draft. Dave Crocker&#39;s dependency graph off the WG page in the data trac=
ker include expires drafts.=C2=A0 Some expired drafts should go away, how w=
ould one distinguish in a traceable and helpful way?=C2=A0 You can&#39;t re=
ly on wiki&#39;s to be maintained after WGs disappear.<br></li><li>A wiki t=
o maintain this type of data is too dynamic and can&#39;t be trusted.=C2=A0=
 How do you distinguish versions and changes over time even if it isn&#39;t=
 published as an RFC until the solutions are closer to final?<br></li><li>I=
n most scientific publications, referencing a weblink (like e.g. a wiki) is=
 strongly discouraged due to their ephemeral nature. Having an RFC number i=
s not only nice to have, it is quite essential if one is to refer to this d=
ocument in any serious article.<br></li><li>The process of getting it publi=
shed usually supplies a final jolt of energy that can make the document eve=
n better (and increase the focus of the WG in the process).=C2=A0 It is har=
d to overestimate this effect.<br></li><li>From the ACE WG: One obvious rea=
son for having this as a WG draft (published or not) is that some felt thei=
r input wasn&#39;t considered when it was an individual draft.<br></li><li>=
People might be more motivated to contribute to a WG draft than to an indiv=
idual draft.=C2=A0 People will also be more motivated to contribute if the =
final result is a published document that they can point to when someone (e=
mployer, sponsor) asks them what the result of their work was.<br></li><li>=
Publishing the draft as (informational) RFC also helps to valorize the work=
 that the authors put into this document.=C2=A0 If the draft is just publis=
hed as a wiki, this sends the message to many readers that IETF didn&#39;t =
consider this a worthy enough contribution for a real publication. This wou=
ld also discourage future contributions to such documents (especially by sc=
ientists).<br></li><li>WGs still have the energy*, and want to get this off=
 the table so they can use it (as intended) as input for the specification-=
level discussion of the WG. Note: this may be especially true for newcomers=
 to the IETF, it will help for them to see a progression of drafts and that=
 work can move along.<br></li><li>Diversity: If we want to encourage custom=
er participation, this is one of the key areas in which they can contribute=
 and have a positive impact on the work.=C2=A0 This may also help researche=
rs who may be involved in use cases or subsequent phases where they raise a=
wareness of existing work to solve the problems discussed in the scope of w=
ork.<br></li></ol><div><br><b>Opposition:</b><br><br><ol><li>It&#39;s time =
consuming for the IETF and ideally would have been completed prior to WG fo=
rmation.=C2=A0 By the time use cases are complete, folks interested in solu=
tions may have walked away already to go do something real, develop code.</=
li><li>This process doesn&#39;t keep pace with the open source community an=
d should be a pre-cursor to WG formation.=C2=A0 We need to figure out how t=
o speed up.</li><li>Use cases may be a moving target and may evolve over th=
e course of the WG life.<br></li></ol><br>---- <br><br>Best regards,<br>Kat=
hleen</div></div>

--001a11c2906ce71a98050e5fa2db--


From nobody Thu Feb  5 16:11:27 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B1C1A0011; Thu,  5 Feb 2015 16:11:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 y5P5gn6e3KKc; Thu,  5 Feb 2015 16:11:04 -0800 (PST)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1081A0029; Thu,  5 Feb 2015 16:10:50 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id w7so13184656lbi.1; Thu, 05 Feb 2015 16:10:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XMb3q3ErYIsAVOW9W7kJk1N2W3d3LJwp6s9duEBaEU4=; b=Ku7ASdDvy73q2l1i0BZ4pFtwJ66WtyL4+RkRA07ctFeGgnZvg7HPOFd7K1EA2zWK95 JHm2jcRK1g1krUlsKSIec7yXI0m3LHiDQ4W7+CY5U0Fdiwmeg+2yHly1sZcQTOBe1U4b 6J0lv6Giqs0pcdBC64n1tW+eJbr/GrNEplsfYpsxtHeiiYPbwP8ovUCPm0v17kiXYXeY rFPcaJex8vnnf1svhsVkzsVdpcHGgUNUMbTON3IvNNHgcadTiYpkQkXewWaj1ozC5iZV ZEAI0JoMINxuaaoTj7OiSSSXiGzmzUSAobQwKMW9zDoTEekgpAKCNErdO5B3pd7PHW+Q JrAQ==
MIME-Version: 1.0
X-Received: by 10.112.118.144 with SMTP id km16mr506204lbb.75.1423181449242; Thu, 05 Feb 2015 16:10:49 -0800 (PST)
Received: by 10.112.167.134 with HTTP; Thu, 5 Feb 2015 16:10:49 -0800 (PST)
In-Reply-To: <CAHbuEH43VZEFGFQQqBAYsoGTmhod+sZ-7p3QAP6rF6pscxPSbQ@mail.gmail.com>
References: <CAHbuEH43VZEFGFQQqBAYsoGTmhod+sZ-7p3QAP6rF6pscxPSbQ@mail.gmail.com>
Date: Thu, 5 Feb 2015 19:10:49 -0500
Message-ID: <CAHbuEH7SnKnvKOF4azVXCtr-bmw-SsvDJqu7y2K=MgcGdED-bg@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "ace@ietf.org" <ace@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bfd07e6bbadce050e604082
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/a-8trIrT27JdLxELMAjMbWsY6u0>
Subject: Re: [sacm] Use Case drafts - should they be published summary
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 00:11:09 -0000

--047d7bfd07e6bbadce050e604082
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I;m just going to amend #2 so it's not misunderstood, this is specific to
use case drafts.  If a draft is harmful to the Internet and it gets to the
IESG, it probably won't get published even if there is consensus.

On Thu, Feb 5, 2015 at 6:26 PM, Kathleen Moriarty <
kathleen.moriarty.ietf@gmail.com> wrote:

> Hello,
>
> Sorry for the cross post, both WGs helped develop a list of arguments on
> why their use case draft should be published.  I didn't get many messages
> (and the chairs didn't either in private), so it seems most are in favor =
of
> publishing use cases drafts.
>
> I'll plan to chat about this with the IESG next week and wanted to share
> my summary of reasons.  I ordered them, but didn't spend too much time
> editing, as this won't be a living document (at least in this state).
>
> Thanks again for your assistance!
>
> ----
>
> *Use Case Drafts: Should they be published?*
>
> *Reasons in favor:*
>
>
>    1. If this is part of the WGs charter and a milestone, the work has
>    already been agreed to be done and there is an expectation from those
>    working on it that it will be published.  The WG has probably already
>    sucked up this time if it's on the charter.  It would be unfair to pul=
l it
>    now.
>    2. The IESG is here to serve the IETF.  If there is consensus to
>    publish a use case draft, it should go forward.  Cross area review may=
 help
>    identify early problems with the work or things that could be harmful =
to
>    the Internet.
>    3. If the WG wants it published, it ought to be darn well be
>    published. There=E2=80=99s no prohibition against uc/req drafts that I=
=E2=80=99m aware of
>    *AND* it=E2=80=99s an Informational RFC after all it=E2=80=99s *NOT* a=
 standards track
>    RFC.  There ought to be a lower bar for informational vs standards tra=
ck
>    and if there isn=E2=80=99t one then that=E2=80=99s really the IESG=E2=
=80=99s fault.
>    4. The use cases draft helps to frame the problem(s) being addressed
>    by the WG proposals and is important for guiding future development as=
 well
>    as recording the history of consensus about the scope of work.
>    5. Allows WGs to get cross-area review and IESG input earlier in the
>    process on the whole WG concept.  That might be possible with just an =
IETF
>    LC, but that seems like a bit of a waste of time and probably wouldn=
=E2=80=99t be
>    taken seriously by the reviewers without a =E2=80=9Cthreat=E2=80=9D of=
 publication.
>    6. They are usually informational with no RFC2119 language and should
>    be easier to process.
>    7. It is desirable to have a published document that can be found
>    later to better understand the scope of work produced by a WG or can b=
e
>    used to get a newcomer up-to-speed.  While an expired draft can techni=
cally
>    be found, it's existence may not be known by those interested to read =
the
>    draft. Dave Crocker's dependency graph off the WG page in the data tra=
cker
>    include expires drafts.  Some expired drafts should go away, how would=
 one
>    distinguish in a traceable and helpful way?  You can't rely on wiki's =
to be
>    maintained after WGs disappear.
>    8. A wiki to maintain this type of data is too dynamic and can't be
>    trusted.  How do you distinguish versions and changes over time even i=
f it
>    isn't published as an RFC until the solutions are closer to final?
>    9. In most scientific publications, referencing a weblink (like e.g. a
>    wiki) is strongly discouraged due to their ephemeral nature. Having an=
 RFC
>    number is not only nice to have, it is quite essential if one is to re=
fer
>    to this document in any serious article.
>    10. The process of getting it published usually supplies a final jolt
>    of energy that can make the document even better (and increase the foc=
us of
>    the WG in the process).  It is hard to overestimate this effect.
>    11. From the ACE WG: One obvious reason for having this as a WG draft
>    (published or not) is that some felt their input wasn't considered whe=
n it
>    was an individual draft.
>    12. People might be more motivated to contribute to a WG draft than to
>    an individual draft.  People will also be more motivated to contribute=
 if
>    the final result is a published document that they can point to when
>    someone (employer, sponsor) asks them what the result of their work wa=
s.
>    13. Publishing the draft as (informational) RFC also helps to valorize
>    the work that the authors put into this document.  If the draft is jus=
t
>    published as a wiki, this sends the message to many readers that IETF
>    didn't consider this a worthy enough contribution for a real publicati=
on.
>    This would also discourage future contributions to such documents
>    (especially by scientists).
>    14. WGs still have the energy*, and want to get this off the table so
>    they can use it (as intended) as input for the specification-level
>    discussion of the WG. Note: this may be especially true for newcomers =
to
>    the IETF, it will help for them to see a progression of drafts and tha=
t
>    work can move along.
>    15. Diversity: If we want to encourage customer participation, this is
>    one of the key areas in which they can contribute and have a positive
>    impact on the work.  This may also help researchers who may be involve=
d in
>    use cases or subsequent phases where they raise awareness of existing =
work
>    to solve the problems discussed in the scope of work.
>
>
> *Opposition:*
>
>
>    1. It's time consuming for the IETF and ideally would have been
>    completed prior to WG formation.  By the time use cases are complete, =
folks
>    interested in solutions may have walked away already to go do somethin=
g
>    real, develop code.
>    2. This process doesn't keep pace with the open source community and
>    should be a pre-cursor to WG formation.  We need to figure out how to =
speed
>    up.
>    3. Use cases may be a moving target and may evolve over the course of
>    the WG life.
>
>
> ----
>
> Best regards,
> Kathleen
>



--=20

Best regards,
Kathleen

--047d7bfd07e6bbadce050e604082
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I;m just going to amend #2 so it&#39;s not misunderstood, =
this is specific to use case drafts.=C2=A0 If a draft is harmful to the Int=
ernet and it gets to the IESG, it probably won&#39;t get published even if =
there is consensus.<div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Thu, Feb 5, 2015 at 6:26 PM, Kathleen Moriarty <span dir=3D"ltr">&lt;<=
a href=3D"mailto:kathleen.moriarty.ietf@gmail.com" target=3D"_blank">kathle=
en.moriarty.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div dir=3D"ltr">Hello,<br><br>Sorry for the cross post, both WGs h=
elped develop a list of arguments on why their use case draft should be pub=
lished.=C2=A0 I didn&#39;t get many messages (and the chairs didn&#39;t eit=
her in private), so it seems most are in favor of publishing use cases draf=
ts.<br><br>I&#39;ll plan to chat about this with the IESG next week and wan=
ted to share my summary of reasons.=C2=A0 I ordered them, but didn&#39;t sp=
end too much time editing, as this won&#39;t be a living document (at least=
 in this state).<br><br>Thanks again for your assistance!<br><br>----<br><b=
r><b>Use Case Drafts: Should they be published?</b><br><br><b>Reasons in fa=
vor:</b><br><br><ol><li>If this is part of the WGs charter and a milestone,=
 the work has already been agreed to be done and there is an expectation fr=
om those working on it that it will be published.=C2=A0 The WG has probably=
 already sucked up this time if it&#39;s on the charter.=C2=A0 It would be =
unfair to pull it now.<br></li><li>The IESG is here to serve the IETF.=C2=
=A0 If there is consensus to publish a use case draft, it should go forward=
.=C2=A0 Cross area review may help identify early problems with the work or=
 things that could be harmful to the Internet.<br></li><li>If the WG wants =
it published, it ought to be darn well be published. There=E2=80=99s no pro=
hibition against uc/req drafts that I=E2=80=99m aware of *AND* it=E2=80=99s=
 an Informational RFC after all it=E2=80=99s *NOT* a standards track RFC.=
=C2=A0 There ought to be a lower bar for informational vs standards track a=
nd if there isn=E2=80=99t one then that=E2=80=99s really the IESG=E2=80=99s=
 fault.<br></li><li>The use cases draft helps to frame the problem(s) being=
 addressed by the WG proposals and is important for guiding future developm=
ent as well as recording the history of consensus about the scope of work.<=
br></li><li>Allows WGs to get cross-area review and IESG input earlier in t=
he process on the whole WG concept.=C2=A0 That might be possible with just =
an IETF LC, but that seems like a bit of a waste of time and probably would=
n=E2=80=99t be taken seriously by the reviewers without a =E2=80=9Cthreat=
=E2=80=9D of publication.<br></li><li>They are usually informational with n=
o RFC2119 language and should be easier to process.<br></li><li>It is desir=
able to have a published document that can be found later to better underst=
and the scope of work produced by a WG or can be used to get a newcomer up-=
to-speed.=C2=A0 While an expired draft can technically be found, it&#39;s e=
xistence may not be known by those interested to read the draft. Dave Crock=
er&#39;s dependency graph off the WG page in the data tracker include expir=
es drafts.=C2=A0 Some expired drafts should go away, how would one distingu=
ish in a traceable and helpful way?=C2=A0 You can&#39;t rely on wiki&#39;s =
to be maintained after WGs disappear.<br></li><li>A wiki to maintain this t=
ype of data is too dynamic and can&#39;t be trusted.=C2=A0 How do you disti=
nguish versions and changes over time even if it isn&#39;t published as an =
RFC until the solutions are closer to final?<br></li><li>In most scientific=
 publications, referencing a weblink (like e.g. a wiki) is strongly discour=
aged due to their ephemeral nature. Having an RFC number is not only nice t=
o have, it is quite essential if one is to refer to this document in any se=
rious article.<br></li><li>The process of getting it published usually supp=
lies a final jolt of energy that can make the document even better (and inc=
rease the focus of the WG in the process).=C2=A0 It is hard to overestimate=
 this effect.<br></li><li>From the ACE WG: One obvious reason for having th=
is as a WG draft (published or not) is that some felt their input wasn&#39;=
t considered when it was an individual draft.<br></li><li>People might be m=
ore motivated to contribute to a WG draft than to an individual draft.=C2=
=A0 People will also be more motivated to contribute if the final result is=
 a published document that they can point to when someone (employer, sponso=
r) asks them what the result of their work was.<br></li><li>Publishing the =
draft as (informational) RFC also helps to valorize the work that the autho=
rs put into this document.=C2=A0 If the draft is just published as a wiki, =
this sends the message to many readers that IETF didn&#39;t consider this a=
 worthy enough contribution for a real publication. This would also discour=
age future contributions to such documents (especially by scientists).<br><=
/li><li>WGs still have the energy*, and want to get this off the table so t=
hey can use it (as intended) as input for the specification-level discussio=
n of the WG. Note: this may be especially true for newcomers to the IETF, i=
t will help for them to see a progression of drafts and that work can move =
along.<br></li><li>Diversity: If we want to encourage customer participatio=
n, this is one of the key areas in which they can contribute and have a pos=
itive impact on the work.=C2=A0 This may also help researchers who may be i=
nvolved in use cases or subsequent phases where they raise awareness of exi=
sting work to solve the problems discussed in the scope of work.<br></li></=
ol><div><br><b>Opposition:</b><br><br><ol><li>It&#39;s time consuming for t=
he IETF and ideally would have been completed prior to WG formation.=C2=A0 =
By the time use cases are complete, folks interested in solutions may have =
walked away already to go do something real, develop code.</li><li>This pro=
cess doesn&#39;t keep pace with the open source community and should be a p=
re-cursor to WG formation.=C2=A0 We need to figure out how to speed up.</li=
><li>Use cases may be a moving target and may evolve over the course of the=
 WG life.<br></li></ol><br>---- <br><br>Best regards,<br>Kathleen</div></di=
v>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div><div>Kath=
leen</div></div></div>
</div></div>

--047d7bfd07e6bbadce050e604082--


From nobody Fri Feb  6 04:56:26 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4F531A1AAC for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 04:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level: 
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 n0BNZjk7FCFD for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 04:56:20 -0800 (PST)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 065751A1A81 for <sacm@ietf.org>; Fri,  6 Feb 2015 04:56:19 -0800 (PST)
Received: by pdbfl12 with SMTP id fl12so14619541pdb.6 for <sacm@ietf.org>; Fri, 06 Feb 2015 04:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=C2IT3neMNM0TykIdhJO8oBFMiay08RCjU3UO4doXKI8=; b=j8LqxGqofHtRuXFDuh7iXSoZ/6XyAEiZcuE79LOgwcdLim59IRX3+9MP1zSkSbMBQe UL8p/VoDXBQQMNRqfnh55ywv3z5tzT5EsCSBvlHR9kXF/x/mvtLuMiS6IsMNP6dPrNz0 ZnqoOL0aSY2gPDwH9I834VCHyEUHvO5niWPa0BM0MVG39QV1qLX/huazNPqHA43Z5N3Y 099/2U2ZTcFnL1IeJC4fLMBlvdi+SCm31l43y6K5yXE7DUBLHHrTLsTQ+S+Opdm7xNiI Xq/+o2mPi3AwjQb2Ei9bKBbIUjN49ZX6gedcq1YkCYW6Mq70jdywNB50THpNxiy7aNeN h7aQ==
X-Received: by 10.68.68.131 with SMTP id w3mr5680422pbt.132.1423227378670; Fri, 06 Feb 2015 04:56:18 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:39d0:5d74:64ec:a241? ([2602:306:3406:4f00:39d0:5d74:64ec:a241]) by mx.google.com with ESMTPSA id kg2sm8018772pbc.72.2015.02.06.04.56.16 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Feb 2015 04:56:17 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <C595A8D6-BE18-4E57-AFBF-B167DF049CF1@gmail.com>
Date: Fri, 6 Feb 2015 06:56:00 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/wtwHfAkfdpcPlmvkAobGf8ChGA0>
Subject: [sacm] Endpoint ID Design Team Meeting
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 12:56:21 -0000

All:

There is an Endpoint ID Design Team meeting scheduled to begin in just =
over two hours from now.  Dave W. has indicated that he=E2=80=99s unable =
to join the first half of the meeting, and I have an unforeseen schedule =
conflict that will cause me to be about 10-15 minutes late to the start.

If I can get the WebEx started, is there anyone who would be willing to =
kick off the meeting?  We are slated to discuss two topic areas: 1) get =
a brief update on information model updates, if any, and 2) start =
discussing provenance.

I can get the WebEx started about 15 minutes early and pass the ball to =
someone, or we can simply plan to start about 10 minutes later than =
usual.  If I don=E2=80=99t hear from anyone willing to help start the =
meeting, I=E2=80=99ll assume we=E2=80=99re all OK starting 10 minutes =
behind schedule.  I apologize for the inconvenience. =20

Kind regards,

Adam=


From nobody Fri Feb  6 08:40:17 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D503B1A6F30 for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 08:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 yoULK9bMtgnl for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 08:40:05 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52A0F1A6F29 for <sacm@ietf.org>; Fri,  6 Feb 2015 08:40:05 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id lj1so18266879pab.6 for <sacm@ietf.org>; Fri, 06 Feb 2015 08:40:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=IuuCCntudOUpoPES+dIDfDzrPpvGbqDUbgL5LWga0gY=; b=m5oiCbvZiqGPwgAGX6+E6O23aLxNCtRjejMc3FCwWzoY5w6tnEXO5gAc6SKbvWQ39z Bb09ccPI4Vw6PCQsdpURaoifZ2JX6NP3g/A76HZttesvy6jgMw9GyXas2MS8ZYCEnguu MV4rytfAR0z7Dy4c7u5AHKxvsqhb02bWqf0yZeh/x+oJsfwC5hYGDPXaD0a7bZxwpOp4 4DcybiqlkiPj6WMVkJLK5xUAprfA+bGF8beBcwTOwxO+iSX4knmIqSrp9dmHqhOIfcAL h8sO36RCJ1uT+PbV80KmYM2jl3M8HykLIFjt5eED6OZUk3q5Iav2pzZci7xq3DIMTR9t T7tw==
X-Received: by 10.68.232.130 with SMTP id to2mr7118325pbc.169.1423240804509; Fri, 06 Feb 2015 08:40:04 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:39d0:5d74:64ec:a241? ([2602:306:3406:4f00:39d0:5d74:64ec:a241]) by mx.google.com with ESMTPSA id n2sm8582812pdo.0.2015.02.06.08.40.02 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Feb 2015 08:40:03 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <F14B7304-5214-4651-BB16-CA8FB1660F07@gmail.com>
Date: Fri, 6 Feb 2015 10:39:45 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/Ht_EsfDpKswaAoq6b41Lhv4mPmE>
Subject: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-06
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 16:40:09 -0000

SACM Endpoint ID Design Team Notes
2015-02-06
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

Agenda:

	* Reminder:
		- WebEx Chat and SACM Jabber Room
		- Recording will be (is) enabled
	* Note takers?
	* Endpoint ID Example Continued
		- Update on updating Information Model draft
		- Providing prvenance information
	* Next Steps

Attendees:
	Carolin Latze
	Clifford Kahn
	Danny Haynes
	Henk Birkholz
	Lisa Lorenzin
	Ron Colvin
	Dave Waltermire

Overview
=3D=3D=3D=3D=3D=3D=3D=3D
We changed up the priority of the agenda so that we could consider ID =
attribute "covered", so Lisa, Cliff, and Henk provided a five-minute =
(each) overview of the areas they were going to research.


Amended, Ongoing Notes
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Scenarios:

	- Scenario A: Software on an endpoint is asserting posture =
relating to the endpoint's software inventory and configuration.

Endpoint Identity Assertion
---------------------------

	* All endpoint attributes can be used to establish identity
	* We are defining a core set of (primary) attributes that can be =
used to assert identity in a consistent fashon
		- High level of assurance, attributes can be =
authenticated
	* Other (secondary) attributes can be used to check an identity =
assertion or to further define the endpoint's identity (e.g. =
configuration, software inventory, capability)


Attribute/value pairs
---------------------

	Identity attributes (used to determine what the endpoint is; to =
be provided regardless of other posture attributes):

		* Certificates (e.g., device, user, drive, other =
hardware)
			- Device mandatory if available on device; =
favored by consumers of the assertion
			- Others if available as associated with the =
session
			- Use whole cert or some aspect (e.g., public =
key)
	=09
		* Hostname(s) - configured on the device; may be =
multiple and possibly of different kinds
			- Consider how to specify type: multiple =
attributes for each type or type qualifier
	=09
		* FQDN(s) (if available); some hosts may have multiple; =
also list DNS aliases
			- Sourced from the DNS infrastructure
			- Think abou the security considerations of =
insecure DNS deployments
	=09
		* Interface(s) (comprehensive, if possible)
			- MAC address(es)
			- IP address(es)
				- Including additional IPs assigned to =
the interface
			- Interfaces may be nested (e.g., overlay =
networks - VLANs) - NOTE: Need to verify that standardized methods are =
available to do this.
	=09
		* Other cryptographic information (e.g., IPSec Key-hash, =
HIP-HIT (RFC4423, 5201), 802.1AR)
			- NOTE: Investigate options to determine if they =
should be included as primary attributes; post a summary of how to use =
these specs
				- Cliff: HIP-HIT
					- Experimental implementation at =
the moment; not a lot of adoption
					- ID is a public key; an =
endpoint can have more than one
					- A public key might be a good =
identifier type in general for SACM; public keys tend to exist, even =
when a certificate doesn't (e.g. SSH)
				- Lisa: IPSec Security Associations (SA)
					- The SA contains the IPSEC keys =
and what algorithms are in use
					- Unable to differentiate by =
source IP address
					- Keys can rotate, and may be =
less useful as a result				=09
					- Likely not a primary identity =
attribute, but likely useful to include as an aspect of posture.
				- Henk: 802.1AR
					- Appendix B in specification =
discusses use of TPM
					- The standard's intent is to =
support unattended operation
					- A strong, globally unique =
identifier (re: iDevID - preinstalled; lDevID - enterprise defined).
					- lDevID can be generated =
specifically for SACM uses
					- Any xDevID has to ahve a =
certificate.  Could a public key from the certificate be used as the =
identifier?
					- How would a SACM component =
know of the ID?  It could be collected from both the endpoint as well as =
the device making a network access control decision.
					- The secret (e.g. certificate) =
does not need to be hardware rooted
					- How widely is this =
implemented?  About 6 years old.  Many infrastructure vendors have =
implementations, but not much use has been seen.
				- Other notes:
					- To include public keys, we =
need to discuss: what algorithm was used and the intended use of the key =
as data points?  Need to consider authentication using private keys.
	=09
		* Tool-specific identitier - provided by the software =
making the assertion
			- SHOULD be provided
			- May be session scoped if the tool is not able =
to distinguish an endpoint across sessions
			- May be omitted if the tool is unable to =
distinguish the endpoint across multiple assertions

		* Identification information from bios/firmware (e.g., =
serial numbers, asset tags, VM id) that can be queried on the device =
using softare. NOTE: Need to discuss more.
			- Assets are compositional.  Some components may =
have specific identifiers.  It would be useful to indicate which =
component has a specific identifying attribute.
			- Information should be made available by all =
manufacturers
			- If available should be provided as an =
attribute


Temporal Data
-------------

A timestamp indicating when the observation is made for a given AVP:

	* If periodic, a timestamp at present time
	* If event-based, an interval last-change to present time
	* A timestamp is included on an attribute-by-attribute basis

For information that changes frequently having the ability to poll and =
represent the poll interval is beneficial. =20

Time to Live (TTL) values provide an indication of when a given aspect =
of state will change.  Provide when naturally occurring (e.g., a tool =
will know when the DHCP lease expires). MAY be provided if applicable.

	- Do not include in current model unless we have a good use =
case.



Provenance Data
---------------

	What constitutes provenance:
		* Assessing confidence
			* Identity of the reporter itself (possibly =
endpoint identity but may be software component identity)
			* Have some idea of what that thing is
			* Have some sort of timestamp
			* Is entity aware that it=E2=80=99s =E2=80=9Cself =
reporting=E2=80=9D or =E2=80=9Cother reporting=E2=80=9D

	3 Aspects of Provenance from W3C:
	1. Chain of Custody:
		* Who said the information
		* Who handles the information
		* Endpoint is in chain
		* SACM component is in chain
		* Should include how information was transported

	2. Method (=E2=80=9CProcess=E2=80=9D in W3C terminology)
		* How did you go about harvesting

	3. Basis

	We should provide enough information for the consumer to =
determine degree of confidence.  May require guidance about what may or =
may not constitute some degree of confidence (perhaps an informational =
draft?). TODO: Need to recruit people to write this informational draft =
(certain areas in this set of notes could be used as a basis for such a =
draft).

	Reporter=E2=80=99s identity and the timestamp should be a MUST =
in all instances.  Others may lean toward SHOULD, because they may not =
always be possible. =20


	Example: IP address of an endpoint
		Goal is to associate IP address with Unique endpoint ID.
			Endpoint self-report
			Third-party assigns IP address reporting (e.g. =
IP address mgt sys)
			Third-party observer (e.g. profiler, =
infrastructure witnessing traffic)

		We want provenance for that IP address attribute to tell =
us from where the information came.  If it=E2=80=99s observed, is it =
authoritative, or is it simply passive?  We want to know the observation =
timestamp.

		CoC is who is doing the reporting.
		Process is how observation was made/communicated.
		Object-oriented Provenance is the source of the =
observation

	Note that endpoints can=E2=80=99t really =E2=80=9Clie=E2=80=9D =
about third-party observations; caution if the observer is not in a =
position to see the accurate observation (e.g. NAT=E2=80=99d =
environments).

	Other observations from discussion:
		It=E2=80=99s valuable to capture time auth/observation =
occurred
		Every AVP should have its own timestamp. =20
			Wouldn=E2=80=99t that be the timestamp of the =
attribute itself?

	TODO: Gap analysis for tying in W3C work to SACM - how do we =
hook into that work in a way that doesn=E2=80=99t bring in the whole =
elephant when we need only the trunk and the leg?  Cliff will iterate =
one more time, people will review and comment as appropriate before next =
meeting (2/13). Need to investigate the W3C concepts a bit further to =
determine how they might apply to SACM - find an example of how =
provenance would be generated/used.

	FUTURE WORK: Consider the =E2=80=9Ccomment=E2=80=9D mechanism as =
in IF-MAP - possibly something that can come later (subsequent SACM =
=E2=80=9Cphase=E2=80=9D).

	DISCUSS: Transport security considerations may apply to Chain of =
Custody and Method, is there a =E2=80=9Cplace=E2=80=9D better than =
others to include this type of information in the model?

	DISCUSS: Is there any way to generalize the notion of chain of =
custody, method, basis, to then generalize =E2=80=9Cconfidence=E2=80=9D? =
=20

	DISUCSS: Chain of custody considerations

	Notes previous to 2/6 conversation:

		* A timestamp indicating when the assertion was received =
- consumer (e.g., collector, borker, repo)

		* Think about compositional model of assertions - =
Asserting additional details related to another assertion

		The SACM component that made the assertion - the =
identity of the software providing the information
			- An assertion of the identity of the software =
used (e.g., vendor, product, version, etc.)
			- The instance of the software (e.g., the device =
the software was run on, the installation of the software) - could be an =
endpoint identity assertion as well - may be the same as the endpoint or =
different if external to the endpoint
				- Reuse the identity information from =
the authentication to establish the identity of the reporter.
			- Cryptographic ifnormation that can be used to =
authenticate the provenance assertion
			- (FOR CONTINUED DISCUSSION) Some questions on =
the call about if providing provenance information is required in all =
cases; self-reported - may/should; other-reported - must
	=09
		The endpoint attribute assertions (if any) on which the =
assertion is based
	=09
		Information about the method used to derive the =
assertion


Other Data
----------

	Endpoint uniquely identified?  True or false; very subjective; =
ask larger WG


Other Considerations
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Write security considerations speaking to=20
		- uniqueness of any identifying attribute - address =
malicious or accidental cases where uniqueness may be compromised
		- Issues relating to compromise of endpoint attributes =
(lying endpoints) - Perhaps slandering other endpoints as a result

	* When authenticating as part ofa SACM posture exchange, the =
authentication information should be incorporated into an endpoint =
identity assertion.  Should be a MUST for any endpoint that has the =
capability to authenticate.

Future Discussion Points
------------------------

	* Discuss identification information from bios/firmware (e.g. =
serial numbers, asset tags, VM id) that can be queried on the device =
using software



NEXT STEPS (Agenda Items to track)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Coordinate Information Model updates on list
	* Endpoint ID Design Team overview at Virtual Interim
	* Continued Provenance discussion at next meeting (February 13)





From nobody Fri Feb  6 12:35:13 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E8A1A1EEA for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 12:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 mXNl3xpgBz66 for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 12:35:10 -0800 (PST)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8376E1A00C6 for <sacm@ietf.org>; Fri,  6 Feb 2015 12:35:10 -0800 (PST)
Received: by mail-pa0-f48.google.com with SMTP id ey11so19495768pad.7 for <sacm@ietf.org>; Fri, 06 Feb 2015 12:35:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=dgFbuBHzgMqxaUH8K56BL8EtH5/0PmlxZrLWq4ehCWc=; b=UKpEZ81K4P3ns1umat+CU/URTDRZzg25SptN5QpKczu2TlxbZRApX11ujzPHxg41rK bZ4EJ0OJWAI2otIQkuiwjHIVtwVnjDz0VeEhfrj9jtT8CosK5UMWqMpWzeS14XzEvAbm YU710FD0uzO5obcURCtQTXoQHukiXvNGN8gK4h6xbnYtyapjyze7Uz7b9dDOkqpMDxwY lpdkh4Y1K7evOJ5bXt2gKGaFLp3pK65JaLeoYV4LRLmXdbfXTq3eNu58Bo43KsbDR3DW DEPN30Cuc/wT7S4xP+UgtVjQ9Ynpvg5JKd5MG/m2Iz01W/KqsK0MA0KyiFRzlFU2hxzu /E5w==
X-Received: by 10.70.27.33 with SMTP id q1mr8781498pdg.84.1423254909383; Fri, 06 Feb 2015 12:35:09 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:39d0:5d74:64ec:a241? ([2602:306:3406:4f00:39d0:5d74:64ec:a241]) by mx.google.com with ESMTPSA id ex3sm5194168pdb.23.2015.02.06.12.35.07 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Feb 2015 12:35:08 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EB7ACE1D-37DD-4544-B402-0906F56C04C8"
Message-Id: <A8A32EA7-0EEB-4B5E-8DB9-7F81D76A9BE2@gmail.com>
Date: Fri, 6 Feb 2015 14:34:50 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/NedMnYEP1FWNvjkUSWoufjA1QEs>
Subject: [sacm] Terminology Draft XML for -05
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 20:35:12 -0000

--Apple-Mail=_EB7ACE1D-37DD-4544-B402-0906F56C04C8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Does anyone have the XML file for the -05 version of =
http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/ =
<http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/> ??

Please send to me if you can.

Thanks!=

--Apple-Mail=_EB7ACE1D-37DD-4544-B402-0906F56C04C8
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Does anyone have the XML file for the -05 version of&nbsp;<a href="http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/" class="">http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/</a>&nbsp;??<div class=""><br class=""></div><div class="">Please send to me if you can.</div><div class=""><br class=""></div><div class="">Thanks!</div></body></html>
--Apple-Mail=_EB7ACE1D-37DD-4544-B402-0906F56C04C8--


From nobody Fri Feb  6 13:09:52 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791A31A885F for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 13:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 WZub-29m2g8D for <sacm@ietfa.amsl.com>; Fri,  6 Feb 2015 13:09:47 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76BE41A8775 for <sacm@ietf.org>; Fri,  6 Feb 2015 13:09:38 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id hz1so15003993pad.10 for <sacm@ietf.org>; Fri, 06 Feb 2015 13:09:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=Eje0s5crVQcQ15dGlo32r3Nl5VRivhmstkRcew6Rat4=; b=Z/6p1VLz0X1+aiVtEusU1p9ETHMyg9gwx9rkk0ueGiUympcWN7lOLr8Du/6SgRxh1K lVKCj3wUXAZV3krN4nZUI07Wo2gR9WTC/1ot+S1L7kwRFGBzcOVKySjVWMiN3sUu+HAp ROl3LWRN52444rPtlt1wGMbACcazchkHV3FqXKnASzLNfWSyvEPw4OGGrcLGJO4Gkewv DNuxoLKaoeHXIIE4NlUUFScYkCcOhXdY6WZ91GsF2KjMiMDQQcetgLmWOPZmcQUrpQII 6b42nTcM1bAtqZQQ3cqz1TggxWexLBAyX+BrqAGy1bIzQUvQXHbdqbHMP2icJXLqw0+x yRug==
X-Received: by 10.68.192.101 with SMTP id hf5mr8734441pbc.117.1423256977766; Fri, 06 Feb 2015 13:09:37 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:39d0:5d74:64ec:a241? ([2602:306:3406:4f00:39d0:5d74:64ec:a241]) by mx.google.com with ESMTPSA id l3sm8961492pdc.46.2015.02.06.13.09.35 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Feb 2015 13:09:36 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0694724C-12BC-4C2D-B261-F22382C96BEB"
Message-Id: <37EB46B7-73D4-4053-B385-30CBABC43B8F@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Date: Fri, 6 Feb 2015 15:09:19 -0600
References: <A8A32EA7-0EEB-4B5E-8DB9-7F81D76A9BE2@gmail.com>
To: sacm@ietf.org
In-Reply-To: <A8A32EA7-0EEB-4B5E-8DB9-7F81D76A9BE2@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/VjsirrZu5XmWDGg7rcfmM1pqr0o>
Subject: Re: [sacm] Terminology Draft XML for -05
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 21:09:49 -0000

--Apple-Mail=_0694724C-12BC-4C2D-B261-F22382C96BEB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Cancel this request - I found it.

> On Feb 6, 2015, at 2:34 PM, Adam W. Montville =
<adam.w.montville@gmail.com> wrote:
>=20
> Does anyone have the XML file for the -05 version of =
http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/ =
<http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/> ??
>=20
> Please send to me if you can.
>=20
> Thanks!


--Apple-Mail=_0694724C-12BC-4C2D-B261-F22382C96BEB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Cancel this request - I found it.<div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Feb 6, 2015, at 2:34 PM, Adam W. Montville &lt;<a =
href=3D"mailto:adam.w.montville@gmail.com" =
class=3D"">adam.w.montville@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html charset=3Dus-ascii" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D"">Does anyone =
have the XML file for the -05 version of&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/" =
class=3D"">http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/</a=
>&nbsp;??<div class=3D""><br class=3D""></div><div class=3D"">Please =
send to me if you can.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks!</div></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_0694724C-12BC-4C2D-B261-F22382C96BEB--


From nobody Sun Feb  8 08:13:52 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E271A1B43 for <sacm@ietfa.amsl.com>; Sun,  8 Feb 2015 08:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 uIE15b9KHSFh for <sacm@ietfa.amsl.com>; Sun,  8 Feb 2015 08:13:47 -0800 (PST)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AECF81A886C for <sacm@ietf.org>; Sun,  8 Feb 2015 08:13:47 -0800 (PST)
Received: by mail-qa0-f52.google.com with SMTP id v10so3290890qac.11 for <sacm@ietf.org>; Sun, 08 Feb 2015 08:13:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yWJZrBKWlDI7CwQzH26m57U/Sw7wFYC5epw/rTk8W/s=; b=n53B3+Z7GCc6ql5GOJr+DGMmAMitmEUbFZhiWOHTPG2Hv+i7w6yrqfHqgqJhYJBLct 1YaNGTBt/IiFOuOlLUbIOeXO0kLskmewoCimKSK/p/7KUI+V6LS3tj7mnJzxgRSWZ3wv nU/dqvgal90TasXIMOJZQUYj0CO6IHFPSC6FMmAQPPxWqFKCRFgXUIofTRSJyU+I6sEY Yaqidi5Pwa8wOkFaahjkx6jCTjdIi7L9CvpfO43Jtgny0BrPhLgUIOWI0qF4U6Vdqnuy Y3wP45qk34cHo94ztf7Gspfp6efY6MEMCSSUoalgIXeY/Q4Vz2ZUXwE3decuFS/DLhvS qqKg==
X-Received: by 10.224.86.74 with SMTP id r10mr17628334qal.45.1423412026885; Sun, 08 Feb 2015 08:13:46 -0800 (PST)
Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id q3sm4195817qac.48.2015.02.08.08.13.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Feb 2015 08:13:45 -0800 (PST)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <BN1PR06MB437C9E753C08DC0FF3FFB7CA8310@BN1PR06MB437.namprd06.prod.outlook.com>
Date: Sun, 8 Feb 2015 11:13:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <721096E7-B0BA-4F70-9176-7A76BCF9E013@gmail.com>
References: <BN1PR06MB437C9E753C08DC0FF3FFB7CA8310@BN1PR06MB437.namprd06.prod.outlook.com>
To: "Lorenzin, Lisa" <llorenzin@pulsesecure.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/cLlNmsNW4vmWlWL2Z7FRKYRvvL8>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] IPsec SA overview
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Feb 2015 16:13:50 -0000

Sorry, this was sitting in my outbox unsent.

Hello,

Sent from my iPhone

> On Jan 30, 2015, at 7:39 AM, "Lorenzin, Lisa" <llorenzin@pulsesecure.net> w=
rote:
>=20
> Greetings!
>=20
> Henk's note on 802.1AR (which is very clear and concise - thank you, Henk!=
) reminds me that I had the action item to summarize an IPsec SA.
>=20
> An IPsec security association (SA) is composed of a collection of paramete=
rs - including destination address, keys, IPsec transforms, etc.) - that des=
cribe how to set up an IPsec tunnel between two endpoints. SAs are one-way, s=
o in order to establish an IPsec tunnel between two peers, each peer must cr=
eate an SA representing its communication with the other.

If the WG chooses to use IPsec SAs, please use existing definitions for this=
 term since IPsec is an IETF protocol.  I'm on a plane, so I can't look up t=
he reference at the moment.  It may be in RFC4949 or I'm sure you'll find it=
 in an IPsec RFC.

Thanks,
Kathleen
>=20
> The reason I suggested IPsec SA as a possible endpoint identity attribute i=
s because Pulse Secure & Juniper use IPsec SAs as one way to identify endpoi=
nt traffic passing through a firewall acting as an L3 enforcement point.  Th=
e simplest way to identify the sending endpoint is by source IP address; how=
ever, this breaks if there is a NAT between endpoint and policy server, or b=
etween endpoint and enforcer firewall.  Using an IPsec SA (which the client c=
ommunicates to the policy server, and the endpoint uses to form an IPsec tun=
nel with the firewall) ensures that the policy server and firewall can mutua=
lly identify the same endpoint even if the endpoint communicates with the po=
licy server on a different IP address than it communicates with the firewall=
.
>=20
> Upon reflection, I don't think that an IPsec SA is suitable as a primary e=
ndpoint identity attribute for SACM because it is session-specific, not endp=
oint specific.  However, it could still be a useful endpoint attribute to ca=
pture (if possible) since it does reflect a unique characteristic of the end=
point.
>=20
> Regards,
> Lisa
>=20
> --=20
> Lisa Lorenzin    /    Principal Solutions Architect
> llorenzin@pulsesecure.net    /    919-384-7275
> Pulse Secure    /    https://www.pulsesecure.net
>=20
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm


From nobody Sun Feb  8 08:15:25 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D231ACCC7 for <sacm@ietfa.amsl.com>; Sun,  8 Feb 2015 08:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 tMK2zg2SV1LU for <sacm@ietfa.amsl.com>; Sun,  8 Feb 2015 08:13:59 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 435401A1B43 for <sacm@ietf.org>; Sun,  8 Feb 2015 08:13:59 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id v8so17687120qal.8 for <sacm@ietf.org>; Sun, 08 Feb 2015 08:13:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NPPahhUSl982KncZxm8oer7XbRzc+GcZKjGd5qKJwlY=; b=OV1H501WV8YqbMraP9AcW/pjwoJPjtpDcpfSvfuaD8Jy5YWYaaFnEYW4opcSUSiOAx hLX8qloIQyGp81xbG39IrpM0KIneoXYjdqcsTCkKxZDgYNGAlnLAG7X+LL7bQciVRQpO x+Pbz72kuDKTBNYS1ZQLAvCypCQ5/q8GIYIrzebkBtIdcqYR07xxMQPy9P44ds9MBWk2 3V4a1/LkaSEl5ktNhi/ALBBUdre9cEh0bmzE+butCBLB/9wvXmVlrtZIBujElaXgJJm6 nQ1dyNEyd+zkMRGfEq2TPrrBF+f7O4tbvkfwH9L/b01XvIWuwKcMHxLT5KFw/yo27t7q pkJg==
X-Received: by 10.140.106.228 with SMTP id e91mr29534776qgf.19.1423412038541;  Sun, 08 Feb 2015 08:13:58 -0800 (PST)
Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id t36sm9040948qgt.31.2015.02.08.08.13.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Feb 2015 08:13:57 -0800 (PST)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com>
Date: Sun, 8 Feb 2015 11:13:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com>
To: Sean Turner <turners@ieca.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/ojENuI4m4IKgokM2wNSQTfuAG9E>
Cc: Dan Romascanu <dromasca@avaya.com>, "sacm@ietf.org" <sacm@ietf.org>, "Lorenzin, Lisa" <llorenzin@pulsesecure.net>
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Feb 2015 16:14:01 -0000

Sent from my iPhone

>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
>>=20
>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa <llorenzin@pulsesecure.net> wro=
te:
>>=20
>> If it was just me, I'd use Trac because it seems simpler to me. But if th=
e rest of the group prefers Github, I will endeavor to wrap my head around i=
t. :)
>=20
> I=E2=80=99ve got some links to some pointers for GitHub that Martin Thomps=
on provided when I had to get my head around GitHub too.
>=20
> For ID authors there=E2=80=99s:
> https://github.com/martinthomson/i-d-template
>=20
> If the chairs make a WG repo (and make you a contributor) then it=E2=80=99=
ll look slightly more official - and they can add note well and the like.
>=20
> Personally, I like github because there=E2=80=99s a whole lotta open sourc=
e folks using it.

+1. I believe the WG is only talking about issue tracking right now, but WGs=
 using this for document editing seem to really prefer the ability to see up=
dates/draft management in between IETF versions.

Kathleen
No hat
>=20
> spt
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm


From nobody Mon Feb  9 02:10:47 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5451A0181 for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 02:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.509
X-Spam-Level: 
X-Spam-Status: No, score=-5.509 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 SKK7mOS8wZmK for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 02:10:43 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ABC81A01F4 for <sacm@ietf.org>; Mon,  9 Feb 2015 02:10:39 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnEGAG2G2FSHCzIm/2dsb2JhbABCFwOCQyEiUk8LBIUDqxkBAQEBAQaSJR0BCIVyAoEUQwEBAQEBAXyEDAEBAQEBAhIbOSMCAQgNBAEDAQELCgQMAwcyFAMGBwEBAQQBEggBGYgLAQw3pU+PdpBZAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4YEiTATCxYMCgERB4IVTB2BFAWPG4NQg2ODERAmgk2CO4hcgz4igVuBRU5vAQEBgUF+AQEB
X-IronPort-AV: E=Sophos;i="5.09,542,1418101200";  d="scan'208,217";a="106008459"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 09 Feb 2015 05:10:37 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 09 Feb 2015 05:10:38 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Mon, 9 Feb 2015 05:10:36 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Feb 9 SACM WG Interim - Agenda and Logistics
Thread-Index: AdBAtP7NuUADCkt8RSqyWUNHVCDl5wDm2Jpw
Date: Mon, 9 Feb 2015 10:10:36 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C98EBF7@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C981A93@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C981A93@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C98EBF7AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/HVfbyh9SP_ZQBNVTtZgULbohYcU>
Subject: Re: [sacm] Feb 9 SACM WG Interim - Agenda and Logistics
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2015 10:10:45 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C98EBF7AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We are still looking for volunteers to help us with taking notes.

If there are any presentations that need to be used during the meeting, ple=
ase send them to the chairs.

Thanks and Regards,

Dan


From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Wednesday, February 04, 2015 9:59 PM
To: sacm@ietf.org
Subject: [sacm] Feb 9 SACM WG Interim - Agenda and Logistics

(corrected meeting information)

Hi,

Our next WG virtual interim is scheduled for Monday 2/9, 10AM to noon EST.

The preliminary agenda is posted at http://www.ietf.org/proceedings/interim=
/2015/02/09/sacm/agenda/agenda-interim-2015-sacm-2<https://urldefense.proof=
point.com/v2/url?u=3Dhttp-3A__www.ietf.org_proceedings_interim_2015_02_09_s=
acm_agenda_agenda-2Dinterim-2D2015-2Dsacm-2D2&d=3DAwMFAg&c=3DBFpWQw8bsuKpl1=
SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DuuAXOM7SCSGRsw=
kdr2vI7TChNas_VUd3c-pFs8GjrcU&s=3DAP4M7d3-MpMZGQ59VZZuoSyH6OS_hgItn2Ow2Wjt2=
7w&e=3D>. Unless updates will be posted before Monday (will they be?) I exp=
ect the Requirements and Architecture slots to be rather short and to deal =
mainly with comments received since the previous virtual interim. We shall =
spend most of our time discussing the design team status and open issues.

Bashing the agenda can start right now.

As always we will need two volunteers to take notes. Please do not be timid=
.

The logistic of the call are as follows:


SACM

Monday, February 9, 2015

7:00 am  |  Pacific Standard Time (San Francisco, GMT-08:00)  |  2 hr



Join WebEx meeting:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_j.php-3FMTID-3Dme6b5c19af8bff57de91bc774f18e7a65&d=3DAwICaQ&c=3DB=
FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D7=
2SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=3DySgHiH7hFrs_CQYgzNtlD78hOucw=
RjHL-oly2jqMUGU&e=3D

Meeting number:            823 993 527

Meeting password:         1234



Join by phone

1-877-668-4490 Call-in toll-free number (US/Canada)

1-408-792-6300 Call-in toll number (US/Canada) Access code: 823 993 527 Glo=
bal call-in numbers:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_globalcallin.php-3FserviceType-3DMC-26ED-3D291916977-26tollFree-3=
D1&d=3DAwICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXR=
ucPvdrphpBsFA&m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=3DzgDMqD2XB=
0x668uu2QfIbYiKA7wsPlPblgGu-ISvN_0&e=3D

Toll-free calling restrictions:

https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.webex.com_pdf_tol=
lfree-5Frestrictions.pdf&d=3DAwICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR3=
1OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2Y=
lhtGKPJ4&s=3DhHC4-eS62JH4Ty76TkJx5-UHx0aBwsZmF3j3y9Rugu4&e=3D



Add this meeting to your calendar:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_j.php-3FMTID-3Dme411e7e4ea3e92dbc6dee600a6175a14&d=3DAwICaQ&c=3DB=
FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3D7=
2SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=3D_EwxJYlPScIkjYFUMrM2-UdpUTB3=
SK2Iqiiu3IH7TLI&e=3D



Can't join the meeting? Contact support:

https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex.com_=
workgreen_mc&d=3DAwICaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvl=
siLQfucBXRucPvdrphpBsFA&m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&s=
=3D98IZc36v-aaM9CjBosIfYrQcytz_63JdN8a4HmoDhPM&e=3D



IMPORTANT NOTICE: Please note that this WebEx service allows audio and othe=
r information sent during the session to be recorded, which may be discover=
able in a legal matter. By joining this session, you automatically consent =
to such recordings. If you do not consent to being recorded, discuss your c=
oncerns with the host or do not join the session.



Regards,

Dan


--_000_9904FB1B0159DA42B0B887B7FA8119CA5C98EBF7AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi, <o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We are still looking f=
or volunteers to help us with taking notes.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If there are any prese=
ntations that need to be used during the meeting, please send them to the c=
hairs.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks and Regards,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dan<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> sacm [ma=
ilto:sacm-bounces@ietf.org]
<b>On Behalf Of </b>Romascanu, Dan (Dan)<br>
<b>Sent:</b> Wednesday, February 04, 2015 9:59 PM<br>
<b>To:</b> sacm@ietf.org<br>
<b>Subject:</b> [sacm] Feb 9 SACM WG Interim - Agenda and Logistics<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">(corrected meeting information)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Our next WG virtual interim is scheduled for Monday =
2/9, 10AM to noon EST.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The preliminary agenda is posted at <a href=3D"https=
://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__www.ietf.org_proceedings_i=
nterim_2015_02_09_sacm_agenda_agenda-2Dinterim-2D2015-2Dsacm-2D2&amp;d=3DAw=
MFAg&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRu=
cPvdrphpBsFA&amp;m=3DuuAXOM7SCSGRswkdr2vI7TChNas_VUd3c-pFs8GjrcU&amp;s=3DAP=
4M7d3-MpMZGQ59VZZuoSyH6OS_hgItn2Ow2Wjt27w&amp;e=3D">
http://www.ietf.org/proceedings/interim/2015/02/09/sacm/agenda/agenda-inter=
im-2015-sacm-2</a>. Unless updates will be posted before Monday (will they =
be?) I expect the Requirements and Architecture slots to be rather short an=
d to deal mainly with comments received
 since the previous virtual interim. We shall spend most of our time discus=
sing the design team status and open issues.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Bashing the agenda can start right now. <o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As always we will need two volunteers to take notes.=
 Please do not be timid.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The logistic of the call are as follows: <o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">SACM<o:p></o:p></p>
<p class=3D"MsoPlainText">Monday, February 9, 2015<o:p></o:p></p>
<p class=3D"MsoPlainText">7:00 am&nbsp; |&nbsp; Pacific Standard Time (San =
Francisco, GMT-08:00)&nbsp; |&nbsp; 2 hr<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Join WebEx meeting:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_j.php-3FMTID-3Dme6b5c19af8bf=
f57de91bc774f18e7a65&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3D=
I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB=
4Lse-epbFq2YlhtGKPJ4&amp;s=3DySgHiH7hFrs_CQYgzNtlD78hOucwRjHL-oly2jqMUGU&am=
p;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex=
.com_workgreen_j.php-3FMTID-3Dme6b5c19af8bff57de91bc774f18e7a65&amp;d=3DAwI=
CaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRuc=
PvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DySg=
HiH7hFrs_CQYgzNtlD78hOucwRjHL-oly2jqMUGU&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">Meeting number:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 823 993 527<o:p></o:p></p>
<p class=3D"MsoPlainText">Meeting password:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; 1234<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Join by phone<o:p></o:p></p>
<p class=3D"MsoPlainText">1-877-668-4490 Call-in toll-free number (US/Canad=
a)<o:p></o:p></p>
<p class=3D"MsoPlainText">1-408-792-6300 Call-in toll number (US/Canada) Ac=
cess code: 823 993 527 Global call-in numbers:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_globalcallin.php-3FserviceTy=
pe-3DMC-26ED-3D291916977-26tollFree-3D1&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKp=
l1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72Sa=
mZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DzgDMqD2XB0x668uu2QfIbYiKA7w=
sPlPblgGu-ISvN_0&amp;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=
3A__workgreen.webex.com_workgreen_globalcallin.php-3FserviceType-3DMC-26ED-=
3D291916977-26tollFree-3D1&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&am=
p;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiyw=
YAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DzgDMqD2XB0x668uu2QfIbYiKA7wsPlPblgGu-ISv=
N_0&amp;e</a>=3D<o:p></o:p></p>
<p class=3D"MsoPlainText">Toll-free calling restrictions: <o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttp-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&amp;d=3DAwICa=
Q&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPv=
drphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3DhHC4-=
eS62JH4Ty76TkJx5-UHx0aBwsZmF3j3y9Rugu4&amp;e">https://urldefense.proofpoint=
.com/v2/url?u=3Dhttp-3A__www.webex.com_pdf_tollfree-5Frestrictions.pdf&amp;=
d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQf=
ucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;=
s=3DhHC4-eS62JH4Ty76TkJx5-UHx0aBwsZmF3j3y9Rugu4&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Add this meeting to your calendar:<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_j.php-3FMTID-3Dme411e7e4ea3e=
92dbc6dee600a6175a14&amp;d=3DAwICaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3D=
I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB=
4Lse-epbFq2YlhtGKPJ4&amp;s=3D_EwxJYlPScIkjYFUMrM2-UdpUTB3SK2Iqiiu3IH7TLI&am=
p;e">https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__workgreen.webex=
.com_workgreen_j.php-3FMTID-3Dme411e7e4ea3e92dbc6dee600a6175a14&amp;d=3DAwI=
CaQ&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRuc=
PvdrphpBsFA&amp;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3D_Ew=
xJYlPScIkjYFUMrM2-UdpUTB3SK2Iqiiu3IH7TLI&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Can't join the meeting? Contact support:<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><a href=3D"https://urldefense.proofpoint.com/v2/u=
rl?u=3Dhttps-3A__workgreen.webex.com_workgreen_mc&amp;d=3DAwICaQ&amp;c=3DBF=
pWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&am=
p;m=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3D98IZc36v-aaM9CjBo=
sIfYrQcytz_63JdN8a4HmoDhPM&amp;e">https://urldefense.proofpoint.com/v2/url?=
u=3Dhttps-3A__workgreen.webex.com_workgreen_mc&amp;d=3DAwICaQ&amp;c=3DBFpWQ=
w8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=
=3D72SamZu_O6lLzyiywYAARkB4Lse-epbFq2YlhtGKPJ4&amp;s=3D98IZc36v-aaM9CjBosIf=
YrQcytz_63JdN8a4HmoDhPM&amp;e</a>=3D
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">IMPORTANT NOTICE: Please note that this WebEx ser=
vice allows audio and other information sent during the session to be recor=
ded, which may be discoverable in a legal matter. By joining this session, =
you automatically consent to such
 recordings. If you do not consent to being recorded, discuss your concerns=
 with the host or do not join the session.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C98EBF7AZFFEXMB04globa_--


From nobody Mon Feb  9 07:20:14 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C07271A1A20 for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:03:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
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 UOj5mw2aquUO for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:02:59 -0800 (PST)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0B721A079D for <sacm@ietf.org>; Mon,  9 Feb 2015 07:02:16 -0800 (PST)
Received: by pdbnh10 with SMTP id nh10so29035150pdb.0 for <sacm@ietf.org>; Mon, 09 Feb 2015 07:02:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=from:content-type:subject:message-id:date:to:mime-version; bh=PZZRJ9u0i5ZTSN3LbI6WoRoGsiFDgIB2v5YvUCP+XhQ=; b=BPGMuXt/yRL76O0DerDngpuA6d4vvTzoaLTDqsdEteeH/AbmOp98l9RSyx1Bhfx5yA Dqi7ZtS4STTPsG+sOaMDyAeQn154elU5z+6dKW93j581wSknOysmjSx0jZ3ge+R31X5i XvwJ5d3uCBfHh8uogUHwWsicUh4FLVJyMYaoDE2jts079OGm8s39WpCD9ek816q2mn2k /CURzQhbUYVGITB6FKeIXr2HiJN6Cy7m1Rs2lPsl3+GY9E51SFEABYGaxy4UGwxG6A01 JEysUs34y3M0vbR9dqkqVENZuoW4dYtyKyhoR1NtqN2qv9Fzkon6Bz95MEzrZ83cdsob 0k9g==
X-Received: by 10.70.44.7 with SMTP id a7mr29508838pdm.107.1423494136468; Mon, 09 Feb 2015 07:02:16 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:adb1:3120:9a0d:b49f? ([2602:306:3406:4f00:adb1:3120:9a0d:b49f]) by mx.google.com with ESMTPSA id pr2sm16570502pbb.88.2015.02.09.07.02.14 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Feb 2015 07:02:15 -0800 (PST)
From: Adam W. Montville <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B318FA9C-1592-478A-9DA7-C3F4B8EF569E"
Message-Id: <AFBD2C0C-B446-4FF8-B7DE-425C16C03B1A@gmail.com>
Date: Mon, 9 Feb 2015 09:01:53 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/GGoTNrdY5KjOPa8XCuog9349oCk>
Subject: [sacm] Endpoint ID Design Team Meeting Recording Available: 2015-02-06
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2015 15:03:00 -0000

--Apple-Mail=_B318FA9C-1592-478A-9DA7-C3F4B8EF569E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The recording from last week=E2=80=99s Endpoint ID Design Team meeting =
is now available here: =
https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0 =
<https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0>

Kind regards,

Adam=

--Apple-Mail=_B318FA9C-1592-478A-9DA7-C3F4B8EF569E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">The recording from last week=E2=80=99s Endpoint ID Design =
Team meeting is now available here:&nbsp;<a =
href=3D"https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu=
_a?dl=3D0" =
class=3D"">https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3=
bRu_a?dl=3D0</a><div class=3D""><br class=3D""></div><div class=3D"">Kind =
regards,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Adam</div></body></html>=

--Apple-Mail=_B318FA9C-1592-478A-9DA7-C3F4B8EF569E--


From nobody Mon Feb  9 07:48:06 2015
Return-Path: <inacio@cert.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 315B81A1A42 for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 w9f-t9Tjlw-i for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:45:05 -0800 (PST)
Received: from plainfield.sei.cmu.edu (plainfield.sei.cmu.edu [192.58.107.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DAC51A1A03 for <sacm@ietf.org>; Mon,  9 Feb 2015 07:45:05 -0800 (PST)
Received: from pawpaw.sei.cmu.edu (pawpaw.sei.cmu.edu [10.64.21.22]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id t19Fj09Z021521; Mon, 9 Feb 2015 10:45:00 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1423496700; bh=iZE7IW+QQi8PG/tLIe0pvcq4o/Y/A211LtHM3IJ26yo=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-ID:Content-Transfer-Encoding:MIME-Version: Sender:Reply-To; b=K7HYgVMvMYaapB0we5/tM946aY7Itj+KmzOtyttCzuymhzy4uju+1EHsqj2np31mO qodOSieijLusMAVHRbrQAK2trJ24WEqcHDPPkslTl0tFRJsO7+INVKEBkREMmsUyqM TubOovCEmClo/q/9zQbaoHxvhrCdAI54JAtrOhGk=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by pawpaw.sei.cmu.edu (8.14.4/8.14.4/1456) with ESMTP id t19FipeQ024371; Mon, 9 Feb 2015 10:44:51 -0500
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0210.002; Mon, 9 Feb 2015 10:44:49 -0500
From: Chris Inacio <inacio@cert.org>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: [sacm] poll: Trac or GitHub or None?
Thread-Index: AdApqhdYROeqYVY8RmKRvukEhGRi8wMr+24AAEC2J8ABMZUrAAHwPQWAADFGIYA=
Date: Mon, 9 Feb 2015 15:44:49 +0000
Message-ID: <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com> <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com>
In-Reply-To: <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.51.97]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D8009F75ED4C134BB06331D5D6501607@sei.cmu.edu>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/wTBUSCqDOEgtQ5Mz9L8vQyyQmZw>
Cc: Dan Romascanu <dromasca@avaya.com>, Sean Turner <turners@ieca.com>, "sacm@ietf.org" <sacm@ietf.org>, "Lorenzin, Lisa" <llorenzin@pulsesecure.net>
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2015 15:45:08 -0000

KzEgZm9yIEdpdEh1Yi4NCg0KDQotLQ0KQ2hyaXMgSW5hY2lvDQppbmFjaW9AY2VydC5vcmcNCg0K
DQoNCj4gT24gRmViIDgsIDIwMTUsIGF0IDExOjEzIEFNLCBLYXRobGVlbiBNb3JpYXJ0eSA8a2F0
aGxlZW4ubW9yaWFydHkuaWV0ZkBnbWFpbC5jb20+IHdyb3RlOg0KPiANCj4gDQo+IA0KPiBTZW50
IGZyb20gbXkgaVBob25lDQo+IA0KPj4+IE9uIEphbiAyOSwgMjAxNSwgYXQgMjoyNSBQTSwgU2Vh
biBUdXJuZXIgPHR1cm5lcnNAaWVjYS5jb20+IHdyb3RlOg0KPj4+IA0KPj4+IE9uIEphbiAyMywg
MjAxNSwgYXQgMjA6MjksIExvcmVuemluLCBMaXNhIDxsbG9yZW56aW5AcHVsc2VzZWN1cmUubmV0
PiB3cm90ZToNCj4+PiANCj4+PiBJZiBpdCB3YXMganVzdCBtZSwgSSdkIHVzZSBUcmFjIGJlY2F1
c2UgaXQgc2VlbXMgc2ltcGxlciB0byBtZS4gQnV0IGlmIHRoZSByZXN0IG9mIHRoZSBncm91cCBw
cmVmZXJzIEdpdGh1YiwgSSB3aWxsIGVuZGVhdm9yIHRvIHdyYXAgbXkgaGVhZCBhcm91bmQgaXQu
IDopDQo+PiANCj4+IEnigJl2ZSBnb3Qgc29tZSBsaW5rcyB0byBzb21lIHBvaW50ZXJzIGZvciBH
aXRIdWIgdGhhdCBNYXJ0aW4gVGhvbXBzb24gcHJvdmlkZWQgd2hlbiBJIGhhZCB0byBnZXQgbXkg
aGVhZCBhcm91bmQgR2l0SHViIHRvby4NCj4+IA0KPj4gRm9yIElEIGF1dGhvcnMgdGhlcmXigJlz
Og0KPj4gaHR0cHM6Ly9naXRodWIuY29tL21hcnRpbnRob21zb24vaS1kLXRlbXBsYXRlDQo+PiAN
Cj4+IElmIHRoZSBjaGFpcnMgbWFrZSBhIFdHIHJlcG8gKGFuZCBtYWtlIHlvdSBhIGNvbnRyaWJ1
dG9yKSB0aGVuIGl04oCZbGwgbG9vayBzbGlnaHRseSBtb3JlIG9mZmljaWFsIC0gYW5kIHRoZXkg
Y2FuIGFkZCBub3RlIHdlbGwgYW5kIHRoZSBsaWtlLg0KPj4gDQo+PiBQZXJzb25hbGx5LCBJIGxp
a2UgZ2l0aHViIGJlY2F1c2UgdGhlcmXigJlzIGEgd2hvbGUgbG90dGEgb3BlbiBzb3VyY2UgZm9s
a3MgdXNpbmcgaXQuDQo+IA0KPiArMS4gSSBiZWxpZXZlIHRoZSBXRyBpcyBvbmx5IHRhbGtpbmcg
YWJvdXQgaXNzdWUgdHJhY2tpbmcgcmlnaHQgbm93LCBidXQgV0dzIHVzaW5nIHRoaXMgZm9yIGRv
Y3VtZW50IGVkaXRpbmcgc2VlbSB0byByZWFsbHkgcHJlZmVyIHRoZSBhYmlsaXR5IHRvIHNlZSB1
cGRhdGVzL2RyYWZ0IG1hbmFnZW1lbnQgaW4gYmV0d2VlbiBJRVRGIHZlcnNpb25zLg0KPiANCj4g
S2F0aGxlZW4NCj4gTm8gaGF0DQo+PiANCj4+IHNwdA0KPj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IHNhY20gbWFpbGluZyBsaXN0DQo+PiBzYWNt
QGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NhY20N
Cj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
IHNhY20gbWFpbGluZyBsaXN0DQo+IHNhY21AaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9zYWNtDQoNCg==


From nobody Mon Feb  9 07:55:05 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E25F01A1A25 for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:51:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 hqFdxSVTs-aw for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:51:21 -0800 (PST)
Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02D531A1A1B for <sacm@ietf.org>; Mon,  9 Feb 2015 07:51:21 -0800 (PST)
Received: by labgq15 with SMTP id gq15so476577lab.3 for <sacm@ietf.org>; Mon, 09 Feb 2015 07:51:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=U6OWGqJbyIz3f+nbkpkpLYxM4D2TB9bpkP5liE+RViY=; b=QfDut7g1iuZxc1lHBE0coUmpJU7ZYQKsf/+e276vBO9mzn+edIIOVZXSfGtUuECMq+ S9CoGRtuebp6nwdvQsQDK/ej/iV6dzYqmKcm07NS5Nce4ftNhYElgRvSyHbpCoERvtPp 104Q4rrNr5dHoSVdO1Zd34fzvgx4oxPtwnKvMjsWtjpZOlkzMOjVagV/kVfzB2tgsWTl HKWBsMk2lMySHRG24G1AfLvtp2kHTm7DQecF6o+n+/ZvM5L905aY9o+N/lvZzwOfg2CQ J8uFU6ItL/yGAMyqcFz+pQKaNKDn+3RilRREsBfI+O6qWdOJc+zPabS/Z+KhwCbfq92l SFgQ==
MIME-Version: 1.0
X-Received: by 10.112.9.38 with SMTP id w6mr17840084lba.113.1423497079462; Mon, 09 Feb 2015 07:51:19 -0800 (PST)
Received: by 10.112.167.134 with HTTP; Mon, 9 Feb 2015 07:51:19 -0800 (PST)
In-Reply-To: <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com> <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com> <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org>
Date: Mon, 9 Feb 2015 10:51:19 -0500
Message-ID: <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Chris Inacio <inacio@cert.org>
Content-Type: multipart/alternative; boundary=001a1134deb8c2a212050ea9bd86
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/HlJsZ1-p3PnRT788nUHH2pFZHP4>
Cc: Dan Romascanu <dromasca@avaya.com>, Sean Turner <turners@ieca.com>, "sacm@ietf.org" <sacm@ietf.org>, "Lorenzin, Lisa" <llorenzin@pulsesecure.net>
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2015 15:51:24 -0000

--001a1134deb8c2a212050ea9bd86
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Is the WG interested in editing drafts via GitHub as well or just tracking
issues?  Other WGs find editing drafts via GitHub very helpful.  I believe
both Sean and I have sent links for examples and how to do this.

Thanks.

On Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio <inacio@cert.org> wrote:

> +1 for GitHub.
>
>
> --
> Chris Inacio
> inacio@cert.org
>
>
>
> > On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty <
> kathleen.moriarty.ietf@gmail.com> wrote:
> >
> >
> >
> > Sent from my iPhone
> >
> >>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
> >>>
> >>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa <llorenzin@pulsesecure.net>
> wrote:
> >>>
> >>> If it was just me, I'd use Trac because it seems simpler to me. But i=
f
> the rest of the group prefers Github, I will endeavor to wrap my head
> around it. :)
> >>
> >> I=E2=80=99ve got some links to some pointers for GitHub that Martin Th=
ompson
> provided when I had to get my head around GitHub too.
> >>
> >> For ID authors there=E2=80=99s:
> >> https://github.com/martinthomson/i-d-template
> >>
> >> If the chairs make a WG repo (and make you a contributor) then it=E2=
=80=99ll
> look slightly more official - and they can add note well and the like.
> >>
> >> Personally, I like github because there=E2=80=99s a whole lotta open s=
ource
> folks using it.
> >
> > +1. I believe the WG is only talking about issue tracking right now, bu=
t
> WGs using this for document editing seem to really prefer the ability to
> see updates/draft management in between IETF versions.
> >
> > Kathleen
> > No hat
> >>
> >> spt
> >> _______________________________________________
> >> sacm mailing list
> >> sacm@ietf.org
> >> https://www.ietf.org/mailman/listinfo/sacm
> >
> > _______________________________________________
> > sacm mailing list
> > sacm@ietf.org
> > https://www.ietf.org/mailman/listinfo/sacm
>
>


--=20

Best regards,
Kathleen

--001a1134deb8c2a212050ea9bd86
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Is the WG interested in editing drafts via GitHub as well =
or just tracking issues?=C2=A0 Other WGs find editing drafts via GitHub ver=
y helpful.=C2=A0 I believe both Sean and I have sent links for examples and=
 how to do this.<div><br></div><div>Thanks.</div></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Mon, Feb 9, 2015 at 10:44 AM, Chri=
s Inacio <span dir=3D"ltr">&lt;<a href=3D"mailto:inacio@cert.org" target=3D=
"_blank">inacio@cert.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">+1 for GitHub.<br>
<br>
<br>
--<br>
Chris Inacio<br>
<a href=3D"mailto:inacio@cert.org">inacio@cert.org</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
&gt; On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty &lt;<a href=3D"mailto:k=
athleen.moriarty.ietf@gmail.com">kathleen.moriarty.ietf@gmail.com</a>&gt; w=
rote:<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Sent from my iPhone<br>
&gt;<br>
&gt;&gt;&gt; On Jan 29, 2015, at 2:25 PM, Sean Turner &lt;<a href=3D"mailto=
:turners@ieca.com">turners@ieca.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Jan 23, 2015, at 20:29, Lorenzin, Lisa &lt;<a href=3D"mailt=
o:llorenzin@pulsesecure.net">llorenzin@pulsesecure.net</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If it was just me, I&#39;d use Trac because it seems simpler t=
o me. But if the rest of the group prefers Github, I will endeavor to wrap =
my head around it. :)<br>
&gt;&gt;<br>
&gt;&gt; I=E2=80=99ve got some links to some pointers for GitHub that Marti=
n Thompson provided when I had to get my head around GitHub too.<br>
&gt;&gt;<br>
&gt;&gt; For ID authors there=E2=80=99s:<br>
&gt;&gt; <a href=3D"https://github.com/martinthomson/i-d-template" target=
=3D"_blank">https://github.com/martinthomson/i-d-template</a><br>
&gt;&gt;<br>
&gt;&gt; If the chairs make a WG repo (and make you a contributor) then it=
=E2=80=99ll look slightly more official - and they can add note well and th=
e like.<br>
&gt;&gt;<br>
&gt;&gt; Personally, I like github because there=E2=80=99s a whole lotta op=
en source folks using it.<br>
&gt;<br>
&gt; +1. I believe the WG is only talking about issue tracking right now, b=
ut WGs using this for document editing seem to really prefer the ability to=
 see updates/draft management in between IETF versions.<br>
&gt;<br>
&gt; Kathleen<br>
&gt; No hat<br>
&gt;&gt;<br>
&gt;&gt; spt<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; sacm mailing list<br>
&gt;&gt; <a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; sacm mailing list<br>
&gt; <a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/sacm</a><br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div=
><div>Kathleen</div></div></div>
</div>

--001a1134deb8c2a212050ea9bd86--


From nobody Mon Feb  9 08:03:30 2015
Return-Path: <athiasjerome@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5D521A1A59 for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 a-WteogDdbgk for <sacm@ietfa.amsl.com>; Mon,  9 Feb 2015 07:57:31 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D5371A1A51 for <sacm@ietf.org>; Mon,  9 Feb 2015 07:57:31 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id u10so17260779lbd.7 for <sacm@ietf.org>; Mon, 09 Feb 2015 07:57:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=VRKvgR1qYTlGb9uP918fXZvg2bssZjCWupCZzDCsfws=; b=l8WHwWuMduGqe8FO4J+dUktzmafhqY2poRI9acndkuPNbcf3uCXM0eFvfB7cvd49f+ yYPeI2NW354+ck1mwi5tsHFSExldpo/A/pnQ7Us8LAAaFYgthwiSGlFyl5FuY2DSAZ5g UQ8V8kA9IpViA0iUNlv4A6OdtpundEKZuHs26nWUSekwj/vU85lXWlY2h3SXWnuTfXZs S1et6b9eqLsTsjctZRxKi2i5XDmu/e2y/SFgPILeqoJuPE1gMB2uYC+JkPH2aA4mOG9U rNs3lu6QSa3/d42TnIneqpySiIau0Q03zzIQQbndBiLbmuqHbbvqS+BaTVLTfhfb2Y6K gfMQ==
MIME-Version: 1.0
X-Received: by 10.112.132.67 with SMTP id os3mr18044150lbb.90.1423497449326; Mon, 09 Feb 2015 07:57:29 -0800 (PST)
Received: by 10.25.209.5 with HTTP; Mon, 9 Feb 2015 07:57:29 -0800 (PST)
In-Reply-To: <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com> <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com> <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org> <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com>
Date: Mon, 9 Feb 2015 16:57:29 +0100
Message-ID: <CAA=AuEf_V0HO-41s72cN14WgBqRqaV9Zcqh-Zs7j3vd0xDtCXg@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/qEdPcVMcRoE4xdyjegVZZq_jaeQ>
Cc: Dan Romascanu <dromasca@avaya.com>, Chris Inacio <inacio@cert.org>, "Lorenzin, Lisa" <llorenzin@pulsesecure.net>, Sean Turner <turners@ieca.com>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2015 15:57:33 -0000

+1 for GitHub for issues, and drafts
Could we also track an actions plan/risks register?

Best regards

2015-02-09 16:51 GMT+01:00 Kathleen Moriarty <kathleen.moriarty.ietf@gmail.=
com>:
> Is the WG interested in editing drafts via GitHub as well or just trackin=
g
> issues?  Other WGs find editing drafts via GitHub very helpful.  I believ=
e
> both Sean and I have sent links for examples and how to do this.
>
> Thanks.
>
> On Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio <inacio@cert.org> wrote:
>>
>> +1 for GitHub.
>>
>>
>> --
>> Chris Inacio
>> inacio@cert.org
>>
>>
>>
>> > On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty
>> > <kathleen.moriarty.ietf@gmail.com> wrote:
>> >
>> >
>> >
>> > Sent from my iPhone
>> >
>> >>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
>> >>>
>> >>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa <llorenzin@pulsesecure.net=
>
>> >>> wrote:
>> >>>
>> >>> If it was just me, I'd use Trac because it seems simpler to me. But =
if
>> >>> the rest of the group prefers Github, I will endeavor to wrap my hea=
d around
>> >>> it. :)
>> >>
>> >> I=E2=80=99ve got some links to some pointers for GitHub that Martin T=
hompson
>> >> provided when I had to get my head around GitHub too.
>> >>
>> >> For ID authors there=E2=80=99s:
>> >> https://github.com/martinthomson/i-d-template
>> >>
>> >> If the chairs make a WG repo (and make you a contributor) then it=E2=
=80=99ll
>> >> look slightly more official - and they can add note well and the like=
.
>> >>
>> >> Personally, I like github because there=E2=80=99s a whole lotta open =
source
>> >> folks using it.
>> >
>> > +1. I believe the WG is only talking about issue tracking right now, b=
ut
>> > WGs using this for document editing seem to really prefer the ability =
to see
>> > updates/draft management in between IETF versions.
>> >
>> > Kathleen
>> > No hat
>> >>
>> >> spt
>> >> _______________________________________________
>> >> sacm mailing list
>> >> sacm@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/sacm
>> >
>> > _______________________________________________
>> > sacm mailing list
>> > sacm@ietf.org
>> > https://www.ietf.org/mailman/listinfo/sacm
>>
>
>
>
> --
>
> Best regards,
> Kathleen
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>


From nobody Tue Feb 10 09:42:31 2015
Return-Path: <ietf@augustcellars.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C15A1A1A7B for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 09:42:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level: 
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 uKSxrlsumEpF for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 09:42:23 -0800 (PST)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990011A1A1F for <sacm@ietf.org>; Tue, 10 Feb 2015 09:42:23 -0800 (PST)
Received: from Philemon (75-150-47-141-Oregon.hfc.comcastbusiness.net [75.150.47.141]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 3ECF538F0D; Tue, 10 Feb 2015 09:42:22 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Clifford Kahn'" <cliffordk@pulsesecure.net>, <sacm@ietf.org>
References: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com>
Date: Tue, 10 Feb 2015 09:41:35 -0800
Message-ID: <04d501d04558$d0cba530$7262ef90$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04D6_01D04515.C2B00650"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQIN6nU/jFI7HXVdapy3OgjjDorzM5xu2zsw
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/SuBZ5m_62AN6jKxnaat85itRIwE>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 17:42:28 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04D6_01D04515.C2B00650
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am having a problem with the picture when dealing with the two pairs
Hardware Component/Hardware Instance and Software Component/Software
Instance.  If I understand the picture correct there is a single component
with multiple instances that are mapped into an end point.  However this
does not seem to reflect the reality that there are actually multiple
components that should be mapped to the end point.

 

I believe that these two pairs of components needs to be separated from the
main diagram and two new objects created Hardware Asset and Software Asset
(based on the description in 4.8.2 Asset is probably not correct as it does
not include the "evil" software side).   There would then be a multi to one
mapping from Hardware Asset and Software Asset to the end point.

 

Jim

 

 

From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Clifford Kahn
Sent: Sunday, February 01, 2015 9:37 AM
To: sacm@ietf.org
Subject: Re: [sacm] New version of the information model diagram

 

With glitches in the figure fixed (sorry)

 

From: Clifford Kahn 
Sent: Sunday, February 01, 2015 12:33 PM
To: 'sacm@ietf.org'
Subject: New version of the information model diagram

 

All,

I reference draft-ietf-sacm-information-model-00. 

 

I would eliminate figure 1. It's redundant.

 

I would change

                "Figure 2 depicts an instance of the information model."

to

                "Figure 1 depicts the information model."

 

Here is a new version of the figure.  (View the figure using a fixed-width
font, such as Courier.)

 

  +---------+ +---------+              +--------+____________________

  |Hardware | |Software |    __________|Location|*_______________    |

  |Component| |Component|   |         *+--------+*               |   |

  +---------+ +---------+   |                                    |   |

       |1          |1       |         +----------+               |   |

       |*          |*       |   ______|Credential|____________   |   |

  +---------+ +--------+    |  |     *+----------+*           |* |*  |

  |Hardware | |Software|    |  |         +---------+       +-------+ |

  |Instance | |Instance|    |  |         |Network  |_______|Account| |

  +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |

       |*      |*          *| *|         |- - - - -|                *|

       |       |____1+----------+1______*|Network  |__________+-------+

       |_____________| Endpoint |_____   |Interface|*     1..*|Address|

                    1|          |0..1 |  +---------+          +-------+

                     +----------+     |      1|

          _____________|1    |*       |       |_____+-------------+

         |                   |________|            *|Authorization|

         |                    part-of>              +-------------+

  .......|..............................................................

         |            |0..1            

         |            |               

         |            |*              

         |         +-----+            +---------+___________________

         |         | AVP |____________|Endpoint |1..*   <based-on   |

        ^|         +-----+1..*       1|Attribute|________           |

hosted-by|           *|               |Assertion|*       |          |

         |            |               +---------+        |          |

         |            |produced-using   |*    |*         |         *|

         |           1|V                |     |__________|     +-------+

         |        +--------+            |       <based-on      |Summary|

         |        | Method |            |                      +-------+

         |        +--------+            |produced-by               *|       

         |____________________          |V                          |

                              |*       1|                           |

    +--------+1____________*+-----------+                           |

    |        |    guides>   | SACM      |___________________________|

    |Guidance|              | Component |1       <produced-by

    +--------+*____________1+-----------+

               <produced-by

 

         -------------------------------------------------------------

         ..... Above this line is the monitorable world

         -------------------------------------------------------------

 

The figure has additions for provenance:

.         A class "Method"

.         The produced-using relationship between an AVP and  a Method

.         The produced-by relationship between a Guidance and a SACM
Component

.         The hosted-by relationship between a SACM Component and an
Endpoint

 

The figure has other changes:

.         asserted-by and summarized-by have been renamed to produced-by.

.         "User" is now "Account". If a user has different credentials, SACM
cannot know that they belong to the same user. But, per Kim W, many
organizations do have accounts that associate credentials. 

.         The multiplicity of the based-on relationships have been
corrected. 

.         More relationships now have labels, per UML convention. 

.         I got rid of the causal arrows, which had become redundant and
were nonstandard and clutter. 

 

Still to come:

.         We are still discussing network sessions and network interfaces
and how to model them. I left that part of the figure alone for now.

.         More provenance. 

.         Should Level of Assurance be a class? 

.         If an endpoint provides information about itself to an external
attribute collector, which turns the information into SACM notation, how do
we model the endpoint's and the collector's parts in the chain of custody? 

.         Will a SACM controller ever add an AVP to an endpoint attribute
assertion? If so, how will we model that? 

.         Coverage. I know Kim is interested in capturing enough information
so that gaps in coverage can be found. (Is this in our requirements? It
should be, I think.) She has suggested something like, each SACM component
should publish a description of what it covers. The "guides" relationship
might look sufficient, but it isn't. If a piece of guidance says "Capture
the SWID tag inventory", a SACM component can heed that, but only for some
endpoints.

 

 

Clifford Kahn

Principal Engineeer, Technical Lead

 


------=_NextPart_000_04D6_01D04515.C2B00650
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am having a problem =
with the picture when dealing with the two pairs Hardware =
Component/Hardware Instance and Software Component/Software =
Instance.&nbsp; If I understand the picture correct there is a single =
component with multiple instances that are mapped into an end =
point.&nbsp; However this does not seem to reflect the reality that =
there are actually multiple components that should be mapped to the end =
point.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I believe that these two =
pairs of components needs to be separated from the main diagram and two =
new objects created Hardware Asset and Software Asset&nbsp; (based on =
the description in 4.8.2 Asset is probably not correct as it does not =
include the &#8220;evil&#8221; software side).&nbsp;&nbsp; There would =
then be a multi to one mapping from Hardware Asset and Software Asset to =
the end point.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
sacm [mailto:sacm-bounces@ietf.org] <b>On Behalf Of </b>Clifford =
Kahn<br><b>Sent:</b> Sunday, February 01, 2015 9:37 AM<br><b>To:</b> =
sacm@ietf.org<br><b>Subject:</b> Re: [sacm] New version of the =
information model diagram<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>With glitches in the figure fixed =
(sorry)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> Clifford Kahn =
<br><b>Sent:</b> Sunday, February 01, 2015 12:33 PM<br><b>To:</b> =
'sacm@ietf.org'<br><b>Subject:</b> New version of the information model =
diagram<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>All,<o:p></o:p></p><p class=3DMsoNormal>I reference =
draft-ietf-sacm-information-model-00. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would =
eliminate figure 1. It's redundant.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would =
change<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 2 depicts an instance =
of the information model.&#8221;<o:p></o:p></p><p =
class=3DMsoNormal>to<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 1 depicts the =
information model.&#8221;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Here is a =
new version of the figure. &nbsp;(View the figure using a fixed-width =
font, such as Courier.)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; +---------+ =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; +--------+____________________<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
|Hardware | |Software |&nbsp;&nbsp;&nbsp; =
__________|Location|*_______________&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; |Component| =
|Component|&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*+--------+*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
+---------+ +---------+&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; |<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;+----------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; =
______|Credential|____________&nbsp;&nbsp; |&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; +---------+ =
+--------+&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp; =
&nbsp;&nbsp;*+----------+*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; |* |*&nbsp; |<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
|Hardware | |Software|&nbsp;&nbsp;&nbsp; |&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +-------+ =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; |Instance | =
|Instance|&nbsp;&nbsp;&nbsp; |&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Network&nbsp; =
|_______|Account| |<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; +---------+ =
+--------+&nbsp;&nbsp;&nbsp; |&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Session&nbsp; =
|*&nbsp; 0..1+-------+ |<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *| =
*|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |- - - - =
-|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; *|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|____1+----------+1______*|Network&nbsp; =
|__________+-------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____________| Endpoint |_____&nbsp;&nbsp; =
|Interface|*&nbsp;&nbsp;&nbsp;&nbsp; =
1..*|Address|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;1|&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1 |&nbsp; =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;+----------+&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________|1&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____+-------------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|________|&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*|Authorization|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;part-of&gt;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; =
.......|..............................................................<o:=
p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;+-----+&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+---------+______________=
_____<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| AVP |____________|Endpoint =
|1..* &nbsp;&nbsp;&lt;based-on &nbsp;&nbsp;|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;^| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+-----+1..* =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|Attribute|________&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>hosted-by| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&nbsp;&nbsp=
; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|=
Assertion|*&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-using =
&nbsp;&nbsp;|* =
&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|V&nbsp;&nbsp;&nbs=
p; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|=
 &nbsp;&nbsp;&nbsp;&nbsp;|__________| =
&nbsp;&nbsp;&nbsp;&nbsp;+-------+<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--------+ =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;based-on&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;|Summary|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| Method | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;=
&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+-------+<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--------+ =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produc=
ed-by =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;*|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|____________=
________&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|V&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|* =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;+--------+1____________*+-----------+&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 |&nbsp;&nbsp;&nbsp; guides&gt;&nbsp;&nbsp; | =
SACM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |__________________<span =
style=3D'color:#1F497D'>_</span>________|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;|Guidance|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Component |1&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;+--------+*____________1+-----------+<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-------------------------------------------------------------<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ..... Above this =
line is the monitorable world<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-------------------------------------------------------------<o:p></o:p><=
/span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The figure has additions for =
provenance:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>A class &quot;Method&quot;<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The produced-using relationship between an AVP and&nbsp; a =
Method<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The produced-by relationship between a Guidance and a SACM =
Component<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The hosted-by relationship between a SACM Component and an =
Endpoint<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The figure has other changes:<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>asserted-by and summarized-by have been renamed to =
produced-by.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>&quot;User&quot; is now &quot;Account&quot;. If a user has =
different credentials, SACM cannot know that they belong to the same =
user. But, per Kim W, many organizations do have accounts that associate =
credentials. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The multiplicity of the based-on relationships have been =
corrected. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>More relationships now have labels, per UML convention. =
<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>I got rid of the causal arrows, which had become redundant and =
were nonstandard and clutter. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Still to =
come:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>We are still discussing network sessions and network interfaces =
and how to model them. I left that part of the figure alone for =
now.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>More provenance. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>Should Level of Assurance be a class? <o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>If an endpoint provides information about itself to an external =
attribute collector, which turns the information into SACM notation, how =
do we model the endpoint's and the collector's parts in the chain of =
custody? <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>Will a SACM controller ever add an AVP to an endpoint attribute =
assertion? If so, how will we model that? <o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>Coverage. I know Kim is interested in capturing enough =
information so that gaps in coverage can be found. (Is this in our =
requirements? It should be, I think.) She has suggested something like, =
each SACM component should publish a description of what it covers. The =
&quot;guides&quot; relationship might look sufficient, but it isn't. If =
a piece of guidance says &quot;Capture the SWID tag inventory&quot;, a =
SACM component can heed that, but only for some =
endpoints.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Clifford =
Kahn<o:p></o:p></p><p class=3DMsoNormal>Principal Engineeer, Technical =
Lead<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_04D6_01D04515.C2B00650--


From nobody Tue Feb 10 09:59:59 2015
Return-Path: <cliffordk@pulsesecure.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B44BC1A009E for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 09:59:56 -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, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 q-pqvs99N9PJ for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 09:59:51 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0678.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:678]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C29251A1ADA for <sacm@ietf.org>; Tue, 10 Feb 2015 09:59:50 -0800 (PST)
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com (25.161.212.13) by CY1PR0601MB1353.namprd06.prod.outlook.com (25.161.212.11) with Microsoft SMTP Server (TLS) id 15.1.87.18; Tue, 10 Feb 2015 17:59:26 +0000
Received: from CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) by CY1PR0601MB1355.namprd06.prod.outlook.com ([25.161.212.13]) with mapi id 15.01.0075.002; Tue, 10 Feb 2015 17:59:26 +0000
From: Clifford Kahn <cliffordk@pulsesecure.net>
To: Jim Schaad <ietf@augustcellars.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] New version of the information model diagram
Thread-Index: AdA+RMRU0inuW65EQle0W8iyZ0HKKwAAMNugAcTSK4AAAFuEEA==
Date: Tue, 10 Feb 2015 17:59:26 +0000
Message-ID: <CY1PR0601MB1355363B99C748CCD784F569B7240@CY1PR0601MB1355.namprd06.prod.outlook.com>
References: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com> <04d501d04558$d0cba530$7262ef90$@augustcellars.com>
In-Reply-To: <04d501d04558$d0cba530$7262ef90$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.60.254.166]
authentication-results: augustcellars.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:CY1PR0601MB1353;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:CY1PR0601MB1353; 
x-forefront-prvs: 048396AFA0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(164054003)(377454003)(40100003)(2950100001)(15975445007)(102836002)(2900100001)(2656002)(122556002)(19300405004)(77156002)(62966003)(46102003)(87936001)(76576001)(33656002)(107886001)(2501002)(19625215002)(66066001)(86362001)(74316001)(99286002)(16236675004)(76176999)(50986999)(54356999)(19580405001)(19580395003)(92566002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR0601MB1353; H:CY1PR0601MB1355.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_CY1PR0601MB1355363B99C748CCD784F569B7240CY1PR0601MB1355_"
MIME-Version: 1.0
X-OriginatorOrg: pulsesecure.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Feb 2015 17:59:26.1488 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3290a917-9dd6-43db-843b-a3e376f9f96c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0601MB1353
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/q1bI7JMVSrAwN0_2P77LW37u2C4>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 17:59:57 -0000

--_000_CY1PR0601MB1355363B99C748CCD784F569B7240CY1PR0601MB1355_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks, Jim.

I'll take the pair Hardware Component/Hardware Instance.

The UML diagram doesn't say that Hardware Instance is a singleton.

The diagram says that the relationship between an endpoint and a hardware i=
nstance is 1:* (one-to-many).
   - An endpoint can have many hardware instances.
   - A hardware instance belongs to exactly one endpoint.

It says that the relationship between a hardware instance and a hardware co=
mponent is *:1 (many-to-one).
    - A hardware instance is an instance of one hardware component.
    - A hardware component has many instances.

Does that address your concern?

Best,
                                                Cliff

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Tuesday, February 10, 2015 12:42 PM
To: Clifford Kahn; sacm@ietf.org
Subject: RE: [sacm] New version of the information model diagram

I am having a problem with the picture when dealing with the two pairs Hard=
ware Component/Hardware Instance and Software Component/Software Instance. =
 If I understand the picture correct there is a single component with multi=
ple instances that are mapped into an end point.  However this does not see=
m to reflect the reality that there are actually multiple components that s=
hould be mapped to the end point.

I believe that these two pairs of components needs to be separated from the=
 main diagram and two new objects created Hardware Asset and Software Asset=
  (based on the description in 4.8.2 Asset is probably not correct as it do=
es not include the "evil" software side).   There would then be a multi to =
one mapping from Hardware Asset and Software Asset to the end point.

Jim


From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Clifford Kahn
Sent: Sunday, February 01, 2015 9:37 AM
To: sacm@ietf.org<mailto:sacm@ietf.org>
Subject: Re: [sacm] New version of the information model diagram

With glitches in the figure fixed (sorry)

From: Clifford Kahn
Sent: Sunday, February 01, 2015 12:33 PM
To: 'sacm@ietf.org'
Subject: New version of the information model diagram

All,
I reference draft-ietf-sacm-information-model-00.

I would eliminate figure 1. It's redundant.

I would change
                "Figure 2 depicts an instance of the information model."
to
                "Figure 1 depicts the information model."

Here is a new version of the figure.  (View the figure using a fixed-width =
font, such as Courier.)

  +---------+ +---------+              +--------+____________________
  |Hardware | |Software |    __________|Location|*_______________    |
  |Component| |Component|   |         *+--------+*               |   |
  +---------+ +---------+   |                                    |   |
       |1          |1       |         +----------+               |   |
       |*          |*       |   ______|Credential|____________   |   |
  +---------+ +--------+    |  |     *+----------+*           |* |*  |
  |Hardware | |Software|    |  |         +---------+       +-------+ |
  |Instance | |Instance|    |  |         |Network  |_______|Account| |
  +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |
       |*      |*          *| *|         |- - - - -|                *|
       |       |____1+----------+1______*|Network  |__________+-------+
       |_____________| Endpoint |_____   |Interface|*     1..*|Address|
                    1|          |0..1 |  +---------+          +-------+
                     +----------+     |      1|
          _____________|1    |*       |       |_____+-------------+
         |                   |________|            *|Authorization|
         |                    part-of>              +-------------+
  .......|..............................................................
         |            |0..1
         |            |
         |            |*
         |         +-----+            +---------+___________________
         |         | AVP |____________|Endpoint |1..*   <based-on   |
        ^|         +-----+1..*       1|Attribute|________           |
hosted-by|           *|               |Assertion|*       |          |
         |            |               +---------+        |          |
         |            |produced-using   |*    |*         |         *|
         |           1|V                |     |__________|     +-------+
         |        +--------+            |       <based-on      |Summary|
         |        | Method |            |                      +-------+
         |        +--------+            |produced-by               *|
         |____________________          |V                          |
                              |*       1|                           |
    +--------+1____________*+-----------+                           |
    |        |    guides>   | SACM      |___________________________|
    |Guidance|              | Component |1       <produced-by
    +--------+*____________1+-----------+
               <produced-by

         -------------------------------------------------------------
         ..... Above this line is the monitorable world
         -------------------------------------------------------------

The figure has additions for provenance:

*         A class "Method"

*         The produced-using relationship between an AVP and  a Method

*         The produced-by relationship between a Guidance and a SACM Compon=
ent

*         The hosted-by relationship between a SACM Component and an Endpoi=
nt

The figure has other changes:

*         asserted-by and summarized-by have been renamed to produced-by.

*         "User" is now "Account". If a user has different credentials, SAC=
M cannot know that they belong to the same user. But, per Kim W, many organ=
izations do have accounts that associate credentials.

*         The multiplicity of the based-on relationships have been correcte=
d.

*         More relationships now have labels, per UML convention.

*         I got rid of the causal arrows, which had become redundant and we=
re nonstandard and clutter.

Still to come:

*         We are still discussing network sessions and network interfaces a=
nd how to model them. I left that part of the figure alone for now.

*         More provenance.

*         Should Level of Assurance be a class?

*         If an endpoint provides information about itself to an external a=
ttribute collector, which turns the information into SACM notation, how do =
we model the endpoint's and the collector's parts in the chain of custody?

*         Will a SACM controller ever add an AVP to an endpoint attribute a=
ssertion? If so, how will we model that?

*         Coverage. I know Kim is interested in capturing enough informatio=
n so that gaps in coverage can be found. (Is this in our requirements? It s=
hould be, I think.) She has suggested something like, each SACM component s=
hould publish a description of what it covers. The "guides" relationship mi=
ght look sufficient, but it isn't. If a piece of guidance says "Capture the=
 SWID tag inventory", a SACM component can heed that, but only for some end=
points.


Clifford Kahn
Principal Engineeer, Technical Lead


--_000_CY1PR0601MB1355363B99C748CCD784F569B7240CY1PR0601MB1355_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma",sans-serif;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks, Jim.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I&#8217;ll take the pa=
ir Hardware Component/Hardware Instance.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The UML diagram doesn&=
#8217;t say that Hardware Instance is a singleton.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The diagram says that =
the relationship between an endpoint and a hardware instance is 1:* (one-to=
-many).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;- An=
 endpoint can have many hardware instances.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;- A =
hardware instance belongs to exactly one endpoint.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">It says that the relat=
ionship between a hardware instance and a hardware component is *:1 (many-t=
o-one).&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;- A hardware instance is an instance of one hardware component.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;- A hardware component has many instances.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Does that address your=
 concern? <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cliff<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Jim Schaad [mailto:ietf@augustcellars.c=
om] <br>
<b>Sent:</b> Tuesday, February 10, 2015 12:42 PM<br>
<b>To:</b> Clifford Kahn; sacm@ietf.org<br>
<b>Subject:</b> RE: [sacm] New version of the information model diagram<o:p=
></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I am having a problem =
with the picture when dealing with the two pairs Hardware Component/Hardwar=
e Instance and Software Component/Software Instance.&nbsp; If I understand =
the picture correct there is a single component
 with multiple instances that are mapped into an end point.&nbsp; However t=
his does not seem to reflect the reality that there are actually multiple c=
omponents that should be mapped to the end point.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I believe that these t=
wo pairs of components needs to be separated from the main diagram and two =
new objects created Hardware Asset and Software Asset&nbsp; (based on the d=
escription in 4.8.2 Asset is probably not
 correct as it does not include the &#8220;evil&#8221; software side).&nbsp=
;&nbsp; There would then be a multi to one mapping from Hardware Asset and =
Software Asset to the end point.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jim<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,sans-serif">From:</span></b><span style=3D"font-size:10.0pt;f=
ont-family:&quot;Tahoma&quot;,sans-serif"> sacm [<a href=3D"mailto:sacm-bou=
nces@ietf.org">mailto:sacm-bounces@ietf.org</a>]
<b>On Behalf Of </b>Clifford Kahn<br>
<b>Sent:</b> Sunday, February 01, 2015 9:37 AM<br>
<b>To:</b> <a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
<b>Subject:</b> Re: [sacm] New version of the information model diagram<o:p=
></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">With glitches in the f=
igure fixed (sorry)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Clifford Kahn <br>
<b>Sent:</b> Sunday, February 01, 2015 12:33 PM<br>
<b>To:</b> 'sacm@ietf.org'<br>
<b>Subject:</b> New version of the information model diagram<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">All,<o:p></o:p></p>
<p class=3D"MsoNormal">I reference draft-ietf-sacm-information-model-00. <o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would eliminate figure 1. It's redundant.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would change<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 2 depicts an instance =
of the information model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal">to<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 1 depicts the informat=
ion model.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is a new version of the figure. &nbsp;(View the=
 figure using a fixed-width font, such as Courier.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;--------&#43;_______=
_____________<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software |&nbsp;&nbsp;&nbsp; __________|Location|*_____=
__________&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Component| |Component|&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; *&#43;--------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;---------&#43;&nbsp;&nbsp; |&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp=
; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; ___=
___|Credential|____________&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp; &nbsp;&nbsp;*&#43;----------&#43;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |* |*&nbsp; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Hardware | |Software|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; &#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; |Instance | |Instance|&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Network&nbsp; |_______|Account| |<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &#43;---------&#43; &#43;--------&#43;&nbsp;&nbsp;&nbsp; |&nbsp; |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Session&nbsp; |*&nbsp; 0..1=
&#43;-------&#43; |<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |*&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *| *|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |- - - - -|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *|<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|____1&#43;----------&#43;1______*|Network&nbsp; |__________&#43;-------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_____________| Endpoint |_____&nbsp;&=
nbsp; |Interface|*&nbsp;&nbsp;&nbsp;&nbsp; 1..*|Address|<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;1|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|0..1 |&nbsp; &#43;---------&#43;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&#43;----------&#43;&nbsp;&nb=
sp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; _____________|1&nbsp=
;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; |_____&#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|________|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; *|Authorization|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;part-of&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; .......|............................................................=
..<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp;&nbsp;&nbsp;&nbsp;&#43;-----&#43;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;---------&#43;___________________<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;| AVP |____________|Endpoint |1..* &nbsp;&nbsp;&lt;=
based-on &nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;^| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&#43;-----&#43;1..* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
1|Attribute|________&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
hosted-by| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&n=
bsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;|Assertion|*&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&#43;---------&#43;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-using &nbsp;&nbsp;|* &nbsp;&n=
bsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;1|V&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;|_____=
_____| &nbsp;&nbsp;&nbsp;&nbsp;&#43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;based-on&nbsp; &nbsp;&n=
bsp;&nbsp;&nbsp;|Summary|<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;| Method | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#=
43;-------&#43;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|&nbsp; &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&#43;--------&#43; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-by &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|____________________=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|V&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;|* &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;1____________*&#43;-----------&#4=
3;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D"color:#1F497D">
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;=
&nbsp;&nbsp; guides&gt;&nbsp;&nbsp; | SACM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |_=
_________________<span style=3D"color:#1F497D">_</span>________|<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;|Guidance|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Component |1&nbsp;&nbsp; &nbsp;&nbs=
p;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&#43;--------&#43;*____________1&#43;-----------&#4=
3;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
<o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ..... Above this line is t=
he monitorable world<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; --------------------------=
-----------------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has additions for provenance:<o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>A class &quot;Method&quot;<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>The produced-using relationship between an AVP and&nbsp; a Method<o:=
p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>The produced-by relationship between a Guidance and a SACM Component=
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>The hosted-by relationship between a SACM Component and an Endpoint<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The figure has other changes:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>asserted-by and summarized-by have been renamed to produced-by.<o:p>=
</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>&quot;User&quot; is now &quot;Account&quot;. If a user has different=
 credentials, SACM cannot know that they belong to the same user. But, per =
Kim W, many organizations do have accounts that associate credentials.
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>The multiplicity of the based-on relationships have been corrected. =
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>More relationships now have labels, per UML convention. <o:p></o:p><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>I got rid of the causal arrows, which had become redundant and were =
nonstandard and clutter.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Still to come:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>We are still discussing network sessions and network interfaces and =
how to model them. I left that part of the figure alone for now.<o:p></o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>More provenance. <o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
"><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-siz=
e:7.0pt;font-family:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Should Level of Assurance be a class? <o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
"><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-siz=
e:7.0pt;font-family:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>If an endpoint provides information about itself to an external attr=
ibute collector, which turns the information into SACM notation, how do we =
model the endpoint's and the collector's parts in the chain of custody?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
"><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-siz=
e:7.0pt;font-family:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Will a SACM controller ever add an AVP to an endpoint attribute asse=
rtion? If so, how will we model that?
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"f=
ont-family:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-famil=
y:&quot;Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
</span>Coverage. I know Kim is interested in capturing enough information s=
o that gaps in coverage can be found. (Is this in our requirements? It shou=
ld be, I think.) She has suggested something like, each SACM component shou=
ld publish a description of what
 it covers. The &quot;guides&quot; relationship might look sufficient, but =
it isn't. If a piece of guidance says &quot;Capture the SWID tag inventory&=
quot;, a SACM component can heed that, but only for some endpoints.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Clifford Kahn<o:p></o:p></p>
<p class=3D"MsoNormal">Principal Engineeer, Technical Lead<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_CY1PR0601MB1355363B99C748CCD784F569B7240CY1PR0601MB1355_--


From nobody Tue Feb 10 10:09:11 2015
Return-Path: <ietf@augustcellars.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2031A02F1 for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 10:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 UpDLAMVmOyg1 for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 10:09:04 -0800 (PST)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 169BA1A06FD for <sacm@ietf.org>; Tue, 10 Feb 2015 10:09:04 -0800 (PST)
Received: from Philemon (75-150-47-141-Oregon.hfc.comcastbusiness.net [75.150.47.141]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id C3C2138EE9; Tue, 10 Feb 2015 10:09:02 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Clifford Kahn'" <cliffordk@pulsesecure.net>, <sacm@ietf.org>
References: <CY1PR0601MB1355A0219D54FB93A0421236B73F0@CY1PR0601MB1355.namprd06.prod.outlook.com> <04d501d04558$d0cba530$7262ef90$@augustcellars.com> <CY1PR0601MB1355363B99C748CCD784F569B7240@CY1PR0601MB1355.namprd06.prod.outlook.com>
In-Reply-To: <CY1PR0601MB1355363B99C748CCD784F569B7240@CY1PR0601MB1355.namprd06.prod.outlook.com>
Date: Tue, 10 Feb 2015 10:08:15 -0800
Message-ID: <04e901d0455c$8ac7c4c0$a0574e40$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04EA_01D04519.7CAA9F40"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQIN6nU/jFI7HXVdapy3OgjjDorzMwGF+GKTAgLmkwmcUp0KUA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/BxxM39Afo9tzqIrLR_zYmtfZ4sA>
Subject: Re: [sacm] New version of the information model diagram
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 18:09:10 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04EA_01D04519.7CAA9F40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Yes, but from the picture I don't understand that an endpoint can have
multiple hardware components

 

Jim

 

From: Clifford Kahn [mailto:cliffordk@pulsesecure.net] 
Sent: Tuesday, February 10, 2015 9:59 AM
To: Jim Schaad; sacm@ietf.org
Subject: RE: [sacm] New version of the information model diagram

 

Thanks, Jim.

 

I'll take the pair Hardware Component/Hardware Instance.

 

The UML diagram doesn't say that Hardware Instance is a singleton. 

 

The diagram says that the relationship between an endpoint and a hardware
instance is 1:* (one-to-many). 

   - An endpoint can have many hardware instances. 

   - A hardware instance belongs to exactly one endpoint. 

 

It says that the relationship between a hardware instance and a hardware
component is *:1 (many-to-one).  

    - A hardware instance is an instance of one hardware component. 

    - A hardware component has many instances. 

 

Does that address your concern? 

 

Best,

                                                Cliff

 

From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Tuesday, February 10, 2015 12:42 PM
To: Clifford Kahn; sacm@ietf.org
Subject: RE: [sacm] New version of the information model diagram

 

I am having a problem with the picture when dealing with the two pairs
Hardware Component/Hardware Instance and Software Component/Software
Instance.  If I understand the picture correct there is a single component
with multiple instances that are mapped into an end point.  However this
does not seem to reflect the reality that there are actually multiple
components that should be mapped to the end point.

 

I believe that these two pairs of components needs to be separated from the
main diagram and two new objects created Hardware Asset and Software Asset
(based on the description in 4.8.2 Asset is probably not correct as it does
not include the "evil" software side).   There would then be a multi to one
mapping from Hardware Asset and Software Asset to the end point.

 

Jim

 

 

From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Clifford Kahn
Sent: Sunday, February 01, 2015 9:37 AM
To: sacm@ietf.org
Subject: Re: [sacm] New version of the information model diagram

 

With glitches in the figure fixed (sorry)

 

From: Clifford Kahn 
Sent: Sunday, February 01, 2015 12:33 PM
To: 'sacm@ietf.org'
Subject: New version of the information model diagram

 

All,

I reference draft-ietf-sacm-information-model-00. 

 

I would eliminate figure 1. It's redundant.

 

I would change

                "Figure 2 depicts an instance of the information model."

to

                "Figure 1 depicts the information model."

 

Here is a new version of the figure.  (View the figure using a fixed-width
font, such as Courier.)

 

  +---------+ +---------+              +--------+____________________

  |Hardware | |Software |    __________|Location|*_______________    |

  |Component| |Component|   |         *+--------+*               |   |

  +---------+ +---------+   |                                    |   |

       |1          |1       |         +----------+               |   |

       |*          |*       |   ______|Credential|____________   |   |

  +---------+ +--------+    |  |     *+----------+*           |* |*  |

  |Hardware | |Software|    |  |         +---------+       +-------+ |

  |Instance | |Instance|    |  |         |Network  |_______|Account| |

  +---------+ +--------+    |  |         |Session  |*  0..1+-------+ |

       |*      |*          *| *|         |- - - - -|                *|

       |       |____1+----------+1______*|Network  |__________+-------+

       |_____________| Endpoint |_____   |Interface|*     1..*|Address|

                    1|          |0..1 |  +---------+          +-------+

                     +----------+     |      1|

          _____________|1    |*       |       |_____+-------------+

         |                   |________|            *|Authorization|

         |                    part-of>              +-------------+

  .......|..............................................................

         |            |0..1            

         |            |               

         |            |*              

         |         +-----+            +---------+___________________

         |         | AVP |____________|Endpoint |1..*   <based-on   |

        ^|         +-----+1..*       1|Attribute|________           |

hosted-by|           *|               |Assertion|*       |          |

         |            |               +---------+        |          |

         |            |produced-using   |*    |*         |         *|

         |           1|V                |     |__________|     +-------+

         |        +--------+            |       <based-on      |Summary|

         |        | Method |            |                      +-------+

         |        +--------+            |produced-by               *|       

         |____________________          |V                          |

                              |*       1|                           |

    +--------+1____________*+-----------+                           |

    |        |    guides>   | SACM      |___________________________|

    |Guidance|              | Component |1       <produced-by

    +--------+*____________1+-----------+

               <produced-by

 

         -------------------------------------------------------------

         ..... Above this line is the monitorable world

         -------------------------------------------------------------

 

The figure has additions for provenance:

.         A class "Method"

.         The produced-using relationship between an AVP and  a Method

.         The produced-by relationship between a Guidance and a SACM
Component

.         The hosted-by relationship between a SACM Component and an
Endpoint

 

The figure has other changes:

.         asserted-by and summarized-by have been renamed to produced-by.

.         "User" is now "Account". If a user has different credentials, SACM
cannot know that they belong to the same user. But, per Kim W, many
organizations do have accounts that associate credentials. 

.         The multiplicity of the based-on relationships have been
corrected. 

.         More relationships now have labels, per UML convention. 

.         I got rid of the causal arrows, which had become redundant and
were nonstandard and clutter. 

 

Still to come:

.         We are still discussing network sessions and network interfaces
and how to model them. I left that part of the figure alone for now.

.         More provenance. 

.         Should Level of Assurance be a class? 

.         If an endpoint provides information about itself to an external
attribute collector, which turns the information into SACM notation, how do
we model the endpoint's and the collector's parts in the chain of custody? 

.         Will a SACM controller ever add an AVP to an endpoint attribute
assertion? If so, how will we model that? 

.         Coverage. I know Kim is interested in capturing enough information
so that gaps in coverage can be found. (Is this in our requirements? It
should be, I think.) She has suggested something like, each SACM component
should publish a description of what it covers. The "guides" relationship
might look sufficient, but it isn't. If a piece of guidance says "Capture
the SWID tag inventory", a SACM component can heed that, but only for some
endpoints.

 

 

Clifford Kahn

Principal Engineeer, Technical Lead

 


------=_NextPart_000_04EA_01D04519.7CAA9F40
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Yes, but from the =
picture I don&#8217;t understand that an endpoint can have multiple =
hardware components<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Clifford Kahn [mailto:cliffordk@pulsesecure.net] <br><b>Sent:</b> =
Tuesday, February 10, 2015 9:59 AM<br><b>To:</b> Jim Schaad; =
sacm@ietf.org<br><b>Subject:</b> RE: [sacm] New version of the =
information model diagram<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks, Jim.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I&#8217;ll take the pair =
Hardware Component/Hardware Instance.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>The UML diagram =
doesn&#8217;t say that Hardware Instance is a singleton. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>The diagram says that =
the relationship between an endpoint and a hardware instance is 1:* =
(one-to-many). <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;- An endpoint can have many =
hardware instances. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;- A hardware instance belongs =
to exactly one endpoint. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>It says that the =
relationship between a hardware instance and a hardware component is *:1 =
(many-to-one).&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;- A hardware instance is =
an instance of one hardware component. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;- A hardware component =
has many instances. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Does that address your =
concern? <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Best,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Cliff<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br><b>Sent:</b> Tuesday, February 10, 2015 12:42 PM<br><b>To:</b> =
Clifford Kahn; <a =
href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br><b>Subject:</b> RE: =
[sacm] New version of the information model =
diagram<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I am having a problem with the picture when =
dealing with the two pairs Hardware Component/Hardware Instance and =
Software Component/Software Instance.&nbsp; If I understand the picture =
correct there is a single component with multiple instances that are =
mapped into an end point.&nbsp; However this does not seem to reflect =
the reality that there are actually multiple components that should be =
mapped to the end point.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I believe that these two =
pairs of components needs to be separated from the main diagram and two =
new objects created Hardware Asset and Software Asset&nbsp; (based on =
the description in 4.8.2 Asset is probably not correct as it does not =
include the &#8220;evil&#8221; software side).&nbsp;&nbsp; There would =
then be a multi to one mapping from Hardware Asset and Software Asset to =
the end point.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
sacm [<a =
href=3D"mailto:sacm-bounces@ietf.org">mailto:sacm-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Clifford Kahn<br><b>Sent:</b> Sunday, February 01, =
2015 9:37 AM<br><b>To:</b> <a =
href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br><b>Subject:</b> Re: =
[sacm] New version of the information model =
diagram<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>With glitches in the figure fixed =
(sorry)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> Clifford Kahn =
<br><b>Sent:</b> Sunday, February 01, 2015 12:33 PM<br><b>To:</b> =
'sacm@ietf.org'<br><b>Subject:</b> New version of the information model =
diagram<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>All,<o:p></o:p></p><p class=3DMsoNormal>I reference =
draft-ietf-sacm-information-model-00. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would =
eliminate figure 1. It's redundant.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would =
change<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 2 depicts an instance =
of the information model.&#8221;<o:p></o:p></p><p =
class=3DMsoNormal>to<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;Figure 1 depicts the =
information model.&#8221;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Here is a =
new version of the figure. &nbsp;(View the figure using a fixed-width =
font, such as Courier.)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; +---------+ =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; +--------+____________________<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
|Hardware | |Software |&nbsp;&nbsp;&nbsp; =
__________|Location|*_______________&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; |Component| =
|Component|&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*+--------+*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; |<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
+---------+ +---------+&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; |<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;+----------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; =
______|Credential|____________&nbsp;&nbsp; |&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; +---------+ =
+--------+&nbsp;&nbsp;&nbsp; |&nbsp; |&nbsp;&nbsp; =
&nbsp;&nbsp;*+----------+*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; |* |*&nbsp; |<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
|Hardware | |Software|&nbsp;&nbsp;&nbsp; |&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +-------+ =
|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; |Instance | =
|Instance|&nbsp;&nbsp;&nbsp; |&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Network&nbsp; =
|_______|Account| |<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; +---------+ =
+--------+&nbsp;&nbsp;&nbsp; |&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Session&nbsp; =
|*&nbsp; 0..1+-------+ |<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *| =
*|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |- - - - =
-|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; *|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|____1+----------+1______*|Network&nbsp; =
|__________+-------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____________| Endpoint |_____&nbsp;&nbsp; =
|Interface|*&nbsp;&nbsp;&nbsp;&nbsp; =
1..*|Address|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;1|&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1 |&nbsp; =
+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;+----------+&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
_____________|1&nbsp;&nbsp;&nbsp; |*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|_____+-------------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|________|&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
*|Authorization|<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;part-of&gt;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-------------+<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp; =
.......|..............................................................<o:=
p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|0..1&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
 =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;=
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;+-----+&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+---------+______________=
_____<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| AVP |____________|Endpoint =
|1..* &nbsp;&nbsp;&lt;based-on &nbsp;&nbsp;|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;^| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+-----+1..* =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|Attribute|________&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>hosted-by| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|&nbsp;&nbsp=
; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|=
Assertion|*&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;+---------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produced-using =
&nbsp;&nbsp;|* =
&nbsp;&nbsp;&nbsp;|*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*|<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|V&nbsp;&nbsp;&nbs=
p; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|=
 &nbsp;&nbsp;&nbsp;&nbsp;|__________| =
&nbsp;&nbsp;&nbsp;&nbsp;+-------+<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;<span style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--------+ =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;based-on&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;|Summary|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| Method | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;=
&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+-------+<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+--------+ =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|produc=
ed-by =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;*|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|____________=
________&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|V&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier New"'>&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|* =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;+--------+1____________*+-----------+&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
style=3D'color:#1F497D'> =
</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 |&nbsp;&nbsp;&nbsp; guides&gt;&nbsp;&nbsp; | =
SACM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |__________________<span =
style=3D'color:#1F497D'>_</span>________|<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;|Guidance|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Component |1&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;+--------+*____________1+-----------+<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&lt;produced-by<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-------------------------------------------------------------<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ..... Above this =
line is the monitorable world<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-------------------------------------------------------------<o:p></o:p><=
/span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The figure has additions for =
provenance:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>A class &quot;Method&quot;<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The produced-using relationship between an AVP and&nbsp; a =
Method<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The produced-by relationship between a Guidance and a SACM =
Component<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The hosted-by relationship between a SACM Component and an =
Endpoint<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The figure has other changes:<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>asserted-by and summarized-by have been renamed to =
produced-by.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>&quot;User&quot; is now &quot;Account&quot;. If a user has =
different credentials, SACM cannot know that they belong to the same =
user. But, per Kim W, many organizations do have accounts that associate =
credentials. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>The multiplicity of the based-on relationships have been =
corrected. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>More relationships now have labels, per UML convention. =
<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>I got rid of the causal arrows, which had become redundant and =
were nonstandard and clutter. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Still to =
come:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>We are still discussing network sessions and network interfaces =
and how to model them. I left that part of the figure alone for =
now.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>More provenance. <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>Should Level of Assurance be a class? <o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>If an endpoint provides information about itself to an external =
attribute collector, which turns the information into SACM notation, how =
do we model the endpoint's and the collector's parts in the chain of =
custody? <o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>Will a SACM controller ever add an AVP to an endpoint attribute =
assertion? If so, how will we model that? <o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in'><span =
style=3D'font-family:Symbol'>&middot;</span><span =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>Coverage. I know Kim is interested in capturing enough =
information so that gaps in coverage can be found. (Is this in our =
requirements? It should be, I think.) She has suggested something like, =
each SACM component should publish a description of what it covers. The =
&quot;guides&quot; relationship might look sufficient, but it isn't. If =
a piece of guidance says &quot;Capture the SWID tag inventory&quot;, a =
SACM component can heed that, but only for some =
endpoints.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Clifford =
Kahn<o:p></o:p></p><p class=3DMsoNormal>Principal Engineeer, Technical =
Lead<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_04EA_01D04519.7CAA9F40--



From nobody Tue Feb 10 10:14:34 2015
Return-Path: <ietf@augustcellars.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 541E51A1B15 for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 10:14:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 EWl2oETKh62m for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 10:14:26 -0800 (PST)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A44D1A1B18 for <sacm@ietf.org>; Tue, 10 Feb 2015 10:14:24 -0800 (PST)
Received: from Philemon (75-150-47-141-Oregon.hfc.comcastbusiness.net [75.150.47.141]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id F394738F12 for <sacm@ietf.org>; Tue, 10 Feb 2015 10:14:23 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <sacm@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com> <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com> <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org> <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com>
In-Reply-To: <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com>
Date: Tue, 10 Feb 2015 10:13:36 -0800
Message-ID: <04ee01d0455d$4a305160$de90f420$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04EF_01D0451A.3C101EA0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQJ4wrunq6R6ZS66ZLN1emTQE5gGmAH4VKNbAfcl/sUBfXR77QHRRa6LAXWIhjkCYhJr2ZtAgLoA
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/o9gEtnmvJ4V-VJE9odAHswwn1t4>
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 18:14:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04EF_01D0451A.3C101EA0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

One of the issues that was not discussed on the call is the structure =
that is going to be used for the repository.

=20

TLS has a project which is the working group and then a different =
repository for each different document https://github.com/tlswg

=20

I have also seen a single repository with a different subdirectory for =
each different=20

=20

One could also I suppose have a single repository with different files =
in that repository for each draft.

=20

The choice makes a difference in terms of how issues are going to be =
tracked.  The first means that each different draft has its own issue =
tracker.  There is no easy way to look at all of the issues in a single =
view.  It can also be a problem if an issue is attached to two different =
drafts as the issue either needs to cross point to the other one or be =
duplicated. =20

=20

The first is easier if you are using all of the fancy makefiles that =
have been created for doing releases and automatic building of files =
during merges.   I don=E2=80=99t know that doing tagging works well for =
doing tags on different directories of different strings.

=20

Jim

=20

=20

From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Kathleen Moriarty
Sent: Monday, February 09, 2015 7:51 AM
To: Chris Inacio
Cc: Dan Romascanu; Sean Turner; sacm@ietf.org; Lorenzin, Lisa
Subject: Re: [sacm] poll: Trac or GitHub or None?

=20

Is the WG interested in editing drafts via GitHub as well or just =
tracking issues?  Other WGs find editing drafts via GitHub very helpful. =
 I believe both Sean and I have sent links for examples and how to do =
this.

=20

Thanks.

=20

On Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio <inacio@cert.org> wrote:

+1 for GitHub.


--
Chris Inacio
inacio@cert.org




> On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty =
<kathleen.moriarty.ietf@gmail.com> wrote:
>
>
>
> Sent from my iPhone
>
>>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
>>>
>>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa =
<llorenzin@pulsesecure.net> wrote:
>>>
>>> If it was just me, I'd use Trac because it seems simpler to me. But =
if the rest of the group prefers Github, I will endeavor to wrap my head =
around it. :)
>>
>> I=E2=80=99ve got some links to some pointers for GitHub that Martin =
Thompson provided when I had to get my head around GitHub too.
>>
>> For ID authors there=E2=80=99s:
>> https://github.com/martinthomson/i-d-template
>>
>> If the chairs make a WG repo (and make you a contributor) then =
it=E2=80=99ll look slightly more official - and they can add note well =
and the like.
>>
>> Personally, I like github because there=E2=80=99s a whole lotta open =
source folks using it.
>
> +1. I believe the WG is only talking about issue tracking right now, =
but WGs using this for document editing seem to really prefer the =
ability to see updates/draft management in between IETF versions.
>
> Kathleen
> No hat
>>
>> spt
>> _______________________________________________
>> sacm mailing list
>> sacm@ietf.org
>> https://www.ietf.org/mailman/listinfo/sacm
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm





=20

--=20

=20

Best regards,

Kathleen


------=_NextPart_000_04EF_01D0451A.3C101EA0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>One of the issues that was not discussed on the call is the structure =
that is going to be used for the repository.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>TLS has a project which is the working group and then a different =
repository for each different document <a =
href=3D"https://github.com/tlswg">https://github.com/tlswg</a><o:p></o:p>=
</span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have also seen a single repository with a different subdirectory =
for each different <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>One could also I suppose have a single repository with different =
files in that repository for each draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The choice makes a difference in terms of how issues are going to be =
tracked.=C2=A0 The first means that each different draft has its own =
issue tracker.=C2=A0 There is no easy way to look at all of the issues =
in a single view.=C2=A0 It can also be a problem if an issue is attached =
to two different drafts as the issue either needs to cross point to the =
other one or be duplicated.=C2=A0 <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The first is easier if you are using all of the fancy makefiles that =
have been created for doing releases and automatic building of files =
during merges.=C2=A0=C2=A0 I don=E2=80=99t know that doing tagging works =
well for doing tags on different directories of different =
strings.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
sacm [mailto:sacm-bounces@ietf.org] <b>On Behalf Of </b>Kathleen =
Moriarty<br><b>Sent:</b> Monday, February 09, 2015 7:51 AM<br><b>To:</b> =
Chris Inacio<br><b>Cc:</b> Dan Romascanu; Sean Turner; sacm@ietf.org; =
Lorenzin, Lisa<br><b>Subject:</b> Re: [sacm] poll: Trac or GitHub or =
None?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Is the =
WG interested in editing drafts via GitHub as well or just tracking =
issues?&nbsp; Other WGs find editing drafts via GitHub very =
helpful.&nbsp; I believe both Sean and I have sent links for examples =
and how to do this.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks.<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Mon, =
Feb 9, 2015 at 10:44 AM, Chris Inacio &lt;<a =
href=3D"mailto:inacio@cert.org" =
target=3D"_blank">inacio@cert.org</a>&gt; wrote:<o:p></o:p></p><p =
class=3DMsoNormal>+1 for GitHub.<br><br><br>--<br>Chris Inacio<br><a =
href=3D"mailto:inacio@cert.org">inacio@cert.org</a><o:p></o:p></p><div><d=
iv><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br><br><br>&gt; =
On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty &lt;<a =
href=3D"mailto:kathleen.moriarty.ietf@gmail.com">kathleen.moriarty.ietf@g=
mail.com</a>&gt; wrote:<br>&gt;<br>&gt;<br>&gt;<br>&gt; Sent from my =
iPhone<br>&gt;<br>&gt;&gt;&gt; On Jan 29, 2015, at 2:25 PM, Sean Turner =
&lt;<a href=3D"mailto:turners@ieca.com">turners@ieca.com</a>&gt; =
wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; On Jan 23, 2015, at 20:29, =
Lorenzin, Lisa &lt;<a =
href=3D"mailto:llorenzin@pulsesecure.net">llorenzin@pulsesecure.net</a>&g=
t; wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; If it was just me, I'd use =
Trac because it seems simpler to me. But if the rest of the group =
prefers Github, I will endeavor to wrap my head around it. =
:)<br>&gt;&gt;<br>&gt;&gt; I=E2=80=99ve got some links to some pointers =
for GitHub that Martin Thompson provided when I had to get my head =
around GitHub too.<br>&gt;&gt;<br>&gt;&gt; For ID authors =
there=E2=80=99s:<br>&gt;&gt; <a =
href=3D"https://github.com/martinthomson/i-d-template" =
target=3D"_blank">https://github.com/martinthomson/i-d-template</a><br>&g=
t;&gt;<br>&gt;&gt; If the chairs make a WG repo (and make you a =
contributor) then it=E2=80=99ll look slightly more official - and they =
can add note well and the like.<br>&gt;&gt;<br>&gt;&gt; Personally, I =
like github because there=E2=80=99s a whole lotta open source folks =
using it.<br>&gt;<br>&gt; +1. I believe the WG is only talking about =
issue tracking right now, but WGs using this for document editing seem =
to really prefer the ability to see updates/draft management in between =
IETF versions.<br>&gt;<br>&gt; Kathleen<br>&gt; No =
hat<br>&gt;&gt;<br>&gt;&gt; spt<br>&gt;&gt; =
_______________________________________________<br>&gt;&gt; sacm mailing =
list<br>&gt;&gt; <a =
href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/sacm" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>&gt;<=
br>&gt; _______________________________________________<br>&gt; sacm =
mailing list<br>&gt; <a =
href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/sacm" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><o:p></o:=
p></p></div></div></div><p class=3DMsoNormal><br><br =
clear=3Dall><o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>-- =
<o:p></o:p></p><div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Best =
regards,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Kathleen<o:p></o:p></p></div></div></div></div></div></=
div></body></html>
------=_NextPart_000_04EF_01D0451A.3C101EA0--


From nobody Tue Feb 10 10:43:12 2015
Return-Path: <a.mohaisen@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6EB41A1BA2 for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 10:42:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 AUi3mnx3sz0K for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 10:42:09 -0800 (PST)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D68AB1A02F1 for <sacm@ietf.org>; Tue, 10 Feb 2015 10:42:08 -0800 (PST)
Received: by iebtr6 with SMTP id tr6so26903163ieb.4 for <sacm@ietf.org>; Tue, 10 Feb 2015 10:42:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3pqaAY8qm+nBILUEAKSdALOPKjOql2cK6OXVjZd1Ytg=; b=KRbcUMpzhMZy9Ed6wQCEKNt+6oZ1Ilxk7xszw7PgyzZgqg3mt7E5pwtaG759WalSXP w8cJ4NflAk8Rac27xzLdF/dOI/MTMdPlTM5ilK5KNul3nLq89wu/YYV3PTP79Y4Fi0QW H7DptpdmAIUcJc8B5QH+7ySveqMuT7w4Na3PK73hqR9WTFsn6gd6gDannemo09/Nz8lH Qs+PTOD81Wde63M6J4/6Z6thSfWUOjf2r+WuM+WESETjR367F9ogSjeS8KIq1lxEx2+i Luepne/e8npxpYzoaIlf1cqmBMPc3oLp1pN73xG/vsIaA9jf9eRMUtgZKqsBPyX4UPEB gVlQ==
MIME-Version: 1.0
X-Received: by 10.107.131.83 with SMTP id f80mr3039643iod.50.1423593728299; Tue, 10 Feb 2015 10:42:08 -0800 (PST)
Received: by 10.50.43.68 with HTTP; Tue, 10 Feb 2015 10:42:08 -0800 (PST)
In-Reply-To: <04ee01d0455d$4a305160$de90f420$@augustcellars.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com> <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com> <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org> <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com> <04ee01d0455d$4a305160$de90f420$@augustcellars.com>
Date: Tue, 10 Feb 2015 13:42:08 -0500
Message-ID: <CAMjhxSePkURr8TuS4sW=+oYJoYH-K0APfMXg-kmkysP72aAA6w@mail.gmail.com>
From: Aziz Mohaisen <a.mohaisen@gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a113f998a7ad88e050ec03e1b
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/hQe1V1GGrAlywsBxoEq27vgBUKs>
X-Mailman-Approved-At: Tue, 10 Feb 2015 10:43:11 -0800
Cc: sacm@ietf.org
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 18:42:12 -0000

--001a113f998a7ad88e050ec03e1b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That is perhaps something that the working group or chairs have to decide.
I am not sure if the TLS WG is using GitHub for issue tracking, editing
documents, or both, so cannot speak for their choice.

If we are going to use GitHub for issue tracking only, I think it would be
reasonable to have all document in a single repository for cross-reference
of issues -- just the way Jim explained it.

However, if we are to use GitHub for tracking and authoring -- contributing
to documents, it becomes infeasible to have a single repository with a
directory structure for documents.

As of now, I have created a single repository for each document that's
posted on the WG page:

https://github.com/sacm

I need everyone who wants to be a collaborator on any document to send me
their user id on github.

Thanks,
Aziz


---------
Aziz Mohaisen
www.mohaisen.net

On Tue, Feb 10, 2015 at 1:13 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> One of the issues that was not discussed on the call is the structure tha=
t
> is going to be used for the repository.
>
>
>
> TLS has a project which is the working group and then a different
> repository for each different document https://github.com/tlswg
>
>
>
> I have also seen a single repository with a different subdirectory for
> each different
>
>
>
> One could also I suppose have a single repository with different files in
> that repository for each draft.
>
>
>
> The choice makes a difference in terms of how issues are going to be
> tracked.  The first means that each different draft has its own issue
> tracker.  There is no easy way to look at all of the issues in a single
> view.  It can also be a problem if an issue is attached to two different
> drafts as the issue either needs to cross point to the other one or be
> duplicated.
>
>
>
> The first is easier if you are using all of the fancy makefiles that have
> been created for doing releases and automatic building of files during
> merges.   I don=E2=80=99t know that doing tagging works well for doing ta=
gs on
> different directories of different strings.
>
>
>
> Jim
>
>
>
>
>
> *From:* sacm [mailto:sacm-bounces@ietf.org] *On Behalf Of *Kathleen
> Moriarty
> *Sent:* Monday, February 09, 2015 7:51 AM
> *To:* Chris Inacio
> *Cc:* Dan Romascanu; Sean Turner; sacm@ietf.org; Lorenzin, Lisa
> *Subject:* Re: [sacm] poll: Trac or GitHub or None?
>
>
>
> Is the WG interested in editing drafts via GitHub as well or just trackin=
g
> issues?  Other WGs find editing drafts via GitHub very helpful.  I believ=
e
> both Sean and I have sent links for examples and how to do this.
>
>
>
> Thanks.
>
>
>
> On Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio <inacio@cert.org> wrote:
>
> +1 for GitHub.
>
>
> --
> Chris Inacio
> inacio@cert.org
>
>
>
>
> > On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty <
> kathleen.moriarty.ietf@gmail.com> wrote:
> >
> >
> >
> > Sent from my iPhone
> >
> >>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
> >>>
> >>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa <llorenzin@pulsesecure.net>
> wrote:
> >>>
> >>> If it was just me, I'd use Trac because it seems simpler to me. But i=
f
> the rest of the group prefers Github, I will endeavor to wrap my head
> around it. :)
> >>
> >> I=E2=80=99ve got some links to some pointers for GitHub that Martin Th=
ompson
> provided when I had to get my head around GitHub too.
> >>
> >> For ID authors there=E2=80=99s:
> >> https://github.com/martinthomson/i-d-template
> >>
> >> If the chairs make a WG repo (and make you a contributor) then it=E2=
=80=99ll
> look slightly more official - and they can add note well and the like.
> >>
> >> Personally, I like github because there=E2=80=99s a whole lotta open s=
ource
> folks using it.
> >
> > +1. I believe the WG is only talking about issue tracking right now, bu=
t
> WGs using this for document editing seem to really prefer the ability to
> see updates/draft management in between IETF versions.
> >
> > Kathleen
> > No hat
> >>
> >> spt
> >> _______________________________________________
> >> sacm mailing list
> >> sacm@ietf.org
> >> https://www.ietf.org/mailman/listinfo/sacm
> >
> > _______________________________________________
> > sacm mailing list
> > sacm@ietf.org
> > https://www.ietf.org/mailman/listinfo/sacm
>
>
>
>
>
> --
>
>
>
> Best regards,
>
> Kathleen
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>
>

--001a113f998a7ad88e050ec03e1b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>That is perhaps something that the wor=
king group or chairs have to decide. I am not sure if the TLS WG is using G=
itHub for issue tracking, editing documents, or both, so cannot speak for t=
heir choice. <br><br></div>If we are going to use GitHub for issue tracking=
 only, I think it would be reasonable to have all document in a single repo=
sitory for cross-reference of issues -- just the way Jim explained it. <br>=
<br></div>However, if we are to use GitHub for tracking and authoring -- co=
ntributing to documents, it becomes infeasible to have a single repository =
with a directory structure for documents. <br><br></div>As of now, I have c=
reated a single repository for each document that&#39;s posted on the WG pa=
ge:<br><br><a href=3D"https://github.com/sacm">https://github.com/sacm</a><=
br><br></div>I need everyone who wants to be a collaborator on any document=
 to send me their user id on github.<br><br>Thanks,<br>Aziz<br></div><div c=
lass=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature">=
<div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr"><div><div><div><div><br>---------<br></div><div>Aziz Mohaisen<br><=
/div></div></div></div><a href=3D"http://www.mohaisen.net/" target=3D"_blan=
k">www.mohaisen.net</a><br></div></div></div></div></div></div></div></div>=
</div>
<br><div class=3D"gmail_quote">On Tue, Feb 10, 2015 at 1:13 PM, Jim Schaad =
<span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_=
blank">ietf@augustcellars.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div><p class=
=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">One of the issues that was not di=
scussed on the call is the structure that is going to be used for the repos=
itory.<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f=
497d"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span style=3D"=
font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:#1f497d">TLS has a project which is the working group and then a differe=
nt repository for each different document <a href=3D"https://github.com/tls=
wg" target=3D"_blank">https://github.com/tlswg</a><u></u><u></u></span></p>=
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I have also seen a =
single repository with a different subdirectory for each different <u></u><=
u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=
=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">O=
ne could also I suppose have a single repository with different files in th=
at repository for each draft.<u></u><u></u></span></p><p class=3D"MsoNormal=
"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"Mso=
Normal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1f497d">The choice makes a difference in terms o=
f how issues are going to be tracked.=C2=A0 The first means that each diffe=
rent draft has its own issue tracker.=C2=A0 There is no easy way to look at=
 all of the issues in a single view.=C2=A0 It can also be a problem if an i=
ssue is attached to two different drafts as the issue either needs to cross=
 point to the other one or be duplicated.=C2=A0 <u></u><u></u></span></p><p=
 class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span>=
</p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">The first is easier i=
f you are using all of the fancy makefiles that have been created for doing=
 releases and automatic building of files during merges.=C2=A0=C2=A0 I don=
=E2=80=99t know that doing tagging works well for doing tags on different d=
irectories of different strings.<u></u><u></u></span></p><p class=3D"MsoNor=
mal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"=
MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></span></p><p class=
=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p=
 class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span>=
</p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;pa=
dding:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size=
:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span>=
</b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sa=
ns-serif&quot;"> sacm [mailto:<a href=3D"mailto:sacm-bounces@ietf.org" targ=
et=3D"_blank">sacm-bounces@ietf.org</a>] <b>On Behalf Of </b>Kathleen Moria=
rty<br><b>Sent:</b> Monday, February 09, 2015 7:51 AM<br><b>To:</b> Chris I=
nacio<br><b>Cc:</b> Dan Romascanu; Sean Turner; <a href=3D"mailto:sacm@ietf=
.org" target=3D"_blank">sacm@ietf.org</a>; Lorenzin, Lisa<span class=3D""><=
br><b>Subject:</b> Re: [sacm] poll: Trac or GitHub or None?<u></u><u></u></=
span></span></p></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>=
<div><p class=3D"MsoNormal">Is the WG interested in editing drafts via GitH=
ub as well or just tracking issues?=C2=A0 Other WGs find editing drafts via=
 GitHub very helpful.=C2=A0 I believe both Sean and I have sent links for e=
xamples and how to do this.<u></u><u></u></p><div><p class=3D"MsoNormal"><u=
></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">Thanks.<u></u><u></=
u></p></div></div><div><div class=3D"h5"><div><p class=3D"MsoNormal"><u></u=
>=C2=A0<u></u></p><div><p class=3D"MsoNormal">On Mon, Feb 9, 2015 at 10:44 =
AM, Chris Inacio &lt;<a href=3D"mailto:inacio@cert.org" target=3D"_blank">i=
nacio@cert.org</a>&gt; wrote:<u></u><u></u></p><p class=3D"MsoNormal">+1 fo=
r GitHub.<br><br><br>--<br>Chris Inacio<br><a href=3D"mailto:inacio@cert.or=
g" target=3D"_blank">inacio@cert.org</a><u></u><u></u></p><div><div><p clas=
s=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br><br><br>&gt; On Feb 8, 2=
015, at 11:13 AM, Kathleen Moriarty &lt;<a href=3D"mailto:kathleen.moriarty=
.ietf@gmail.com" target=3D"_blank">kathleen.moriarty.ietf@gmail.com</a>&gt;=
 wrote:<br>&gt;<br>&gt;<br>&gt;<br>&gt; Sent from my iPhone<br>&gt;<br>&gt;=
&gt;&gt; On Jan 29, 2015, at 2:25 PM, Sean Turner &lt;<a href=3D"mailto:tur=
ners@ieca.com" target=3D"_blank">turners@ieca.com</a>&gt; wrote:<br>&gt;&gt=
;&gt;<br>&gt;&gt;&gt; On Jan 23, 2015, at 20:29, Lorenzin, Lisa &lt;<a href=
=3D"mailto:llorenzin@pulsesecure.net" target=3D"_blank">llorenzin@pulsesecu=
re.net</a>&gt; wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; If it was just me, I&=
#39;d use Trac because it seems simpler to me. But if the rest of the group=
 prefers Github, I will endeavor to wrap my head around it. :)<br>&gt;&gt;<=
br>&gt;&gt; I=E2=80=99ve got some links to some pointers for GitHub that Ma=
rtin Thompson provided when I had to get my head around GitHub too.<br>&gt;=
&gt;<br>&gt;&gt; For ID authors there=E2=80=99s:<br>&gt;&gt; <a href=3D"htt=
ps://github.com/martinthomson/i-d-template" target=3D"_blank">https://githu=
b.com/martinthomson/i-d-template</a><br>&gt;&gt;<br>&gt;&gt; If the chairs =
make a WG repo (and make you a contributor) then it=E2=80=99ll look slightl=
y more official - and they can add note well and the like.<br>&gt;&gt;<br>&=
gt;&gt; Personally, I like github because there=E2=80=99s a whole lotta ope=
n source folks using it.<br>&gt;<br>&gt; +1. I believe the WG is only talki=
ng about issue tracking right now, but WGs using this for document editing =
seem to really prefer the ability to see updates/draft management in betwee=
n IETF versions.<br>&gt;<br>&gt; Kathleen<br>&gt; No hat<br>&gt;&gt;<br>&gt=
;&gt; spt<br>&gt;&gt; _______________________________________________<br>&g=
t;&gt; sacm mailing list<br>&gt;&gt; <a href=3D"mailto:sacm@ietf.org" targe=
t=3D"_blank">sacm@ietf.org</a><br>&gt;&gt; <a href=3D"https://www.ietf.org/=
mailman/listinfo/sacm" target=3D"_blank">https://www.ietf.org/mailman/listi=
nfo/sacm</a><br>&gt;<br>&gt; ______________________________________________=
_<br>&gt; sacm mailing list<br>&gt; <a href=3D"mailto:sacm@ietf.org" target=
=3D"_blank">sacm@ietf.org</a><br>&gt; <a href=3D"https://www.ietf.org/mailm=
an/listinfo/sacm" target=3D"_blank">https://www.ietf.org/mailman/listinfo/s=
acm</a><u></u><u></u></p></div></div></div><p class=3D"MsoNormal"><br><br c=
lear=3D"all"><u></u><u></u></p><div><p class=3D"MsoNormal"><u></u>=C2=A0<u>=
</u></p></div><p class=3D"MsoNormal">-- <u></u><u></u></p><div><div><p clas=
s=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNormal">Best re=
gards,<u></u><u></u></p></div><div><p class=3D"MsoNormal">Kathleen<u></u><u=
></u></p></div></div></div></div></div></div></div></div></div><br>________=
_______________________________________<br>
sacm mailing list<br>
<a href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/sacm</a><br>
<br></blockquote></div><br></div>

--001a113f998a7ad88e050ec03e1b--


From nobody Tue Feb 10 14:37:17 2015
Return-Path: <ietf@augustcellars.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C891A871D for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 14:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 32LPdp00rIS1 for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 14:37:11 -0800 (PST)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20AAB1A86FA for <sacm@ietf.org>; Tue, 10 Feb 2015 14:37:11 -0800 (PST)
Received: from Philemon (75-150-47-141-Oregon.hfc.comcastbusiness.net [75.150.47.141]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id C0BB538F16; Tue, 10 Feb 2015 14:37:09 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Aziz Mohaisen'" <a.mohaisen@gmail.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com>	<9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com>	<BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com>	<D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com>	<794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com>	<82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org>	<CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com>	<04ee01d0455d$4a305160$de90f420$@augustcellars.com> <CAMjhxSePkURr8TuS4sW=+oYJoYH-K0APfMXg-kmkysP72aAA6w@mail.gmail.com>
In-Reply-To: <CAMjhxSePkURr8TuS4sW=+oYJoYH-K0APfMXg-kmkysP72aAA6w@mail.gmail.com>
Date: Tue, 10 Feb 2015 14:36:22 -0800
Message-ID: <057a01d04581$ff75c3b0$fe614b10$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_057B_01D0453E.F156F080"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQJ4wrunq6R6ZS66ZLN1emTQE5gGmAH4VKNbAfcl/sUBfXR77QHRRa6LAXWIhjkCYhJr2QE/l2/pAbRx81ibKS+PUA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/xF7OY4pL0FTCCuPwl_UaDhUe8Zc>
Cc: sacm@ietf.org
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 22:37:15 -0000

This is a multipart message in MIME format.

------=_NextPart_000_057B_01D0453E.F156F080
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Note =E2=80=93 You don=E2=80=99t need to be a collaborator on a document =
in order to=20

1)      Open issues

2)      Clone and make pull requests

=20

The collaborators should be the main document editors.

=20

Jim

=20

=20

From: Aziz Mohaisen [mailto:a.mohaisen@gmail.com]=20
Sent: Tuesday, February 10, 2015 10:42 AM
To: Jim Schaad
Cc: sacm@ietf.org
Subject: Re: [sacm] poll: Trac or GitHub or None?

=20

That is perhaps something that the working group or chairs have to =
decide. I am not sure if the TLS WG is using GitHub for issue tracking, =
editing documents, or both, so cannot speak for their choice.=20

If we are going to use GitHub for issue tracking only, I think it would =
be reasonable to have all document in a single repository for =
cross-reference of issues -- just the way Jim explained it.=20

However, if we are to use GitHub for tracking and authoring -- =
contributing to documents, it becomes infeasible to have a single =
repository with a directory structure for documents.=20

As of now, I have created a single repository for each document that's =
posted on the WG page:

https://github.com/sacm

I need everyone who wants to be a collaborator on any document to send =
me their user id on github.

Thanks,
Aziz





---------

Aziz Mohaisen

www.mohaisen.net <http://www.mohaisen.net/>=20

=20

On Tue, Feb 10, 2015 at 1:13 PM, Jim Schaad <ietf@augustcellars.com> =
wrote:

One of the issues that was not discussed on the call is the structure =
that is going to be used for the repository.

=20

TLS has a project which is the working group and then a different =
repository for each different document https://github.com/tlswg

=20

I have also seen a single repository with a different subdirectory for =
each different=20

=20

One could also I suppose have a single repository with different files =
in that repository for each draft.

=20

The choice makes a difference in terms of how issues are going to be =
tracked.  The first means that each different draft has its own issue =
tracker.  There is no easy way to look at all of the issues in a single =
view.  It can also be a problem if an issue is attached to two different =
drafts as the issue either needs to cross point to the other one or be =
duplicated. =20

=20

The first is easier if you are using all of the fancy makefiles that =
have been created for doing releases and automatic building of files =
during merges.   I don=E2=80=99t know that doing tagging works well for =
doing tags on different directories of different strings.

=20

Jim

=20

=20

From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Kathleen Moriarty
Sent: Monday, February 09, 2015 7:51 AM
To: Chris Inacio
Cc: Dan Romascanu; Sean Turner; sacm@ietf.org; Lorenzin, Lisa
Subject: Re: [sacm] poll: Trac or GitHub or None?

=20

Is the WG interested in editing drafts via GitHub as well or just =
tracking issues?  Other WGs find editing drafts via GitHub very helpful. =
 I believe both Sean and I have sent links for examples and how to do =
this.

=20

Thanks.

=20

On Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio <inacio@cert.org> wrote:

+1 for GitHub.


--
Chris Inacio
inacio@cert.org




> On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty =
<kathleen.moriarty.ietf@gmail.com> wrote:
>
>
>
> Sent from my iPhone
>
>>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
>>>
>>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa =
<llorenzin@pulsesecure.net> wrote:
>>>
>>> If it was just me, I'd use Trac because it seems simpler to me. But =
if the rest of the group prefers Github, I will endeavor to wrap my head =
around it. :)
>>
>> I=E2=80=99ve got some links to some pointers for GitHub that Martin =
Thompson provided when I had to get my head around GitHub too.
>>
>> For ID authors there=E2=80=99s:
>> https://github.com/martinthomson/i-d-template
>>
>> If the chairs make a WG repo (and make you a contributor) then =
it=E2=80=99ll look slightly more official - and they can add note well =
and the like.
>>
>> Personally, I like github because there=E2=80=99s a whole lotta open =
source folks using it.
>
> +1. I believe the WG is only talking about issue tracking right now, =
but WGs using this for document editing seem to really prefer the =
ability to see updates/draft management in between IETF versions.
>
> Kathleen
> No hat
>>
>> spt
>> _______________________________________________
>> sacm mailing list
>> sacm@ietf.org
>> https://www.ietf.org/mailman/listinfo/sacm
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm





=20

--=20

=20

Best regards,

Kathleen


_______________________________________________
sacm mailing list
sacm@ietf.org
https://www.ietf.org/mailman/listinfo/sacm

=20


------=_NextPart_000_057B_01D0453E.F156F080
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1066075309;
	mso-list-type:hybrid;
	mso-list-template-ids:691822290 67698705 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Note =E2=80=93 You don=E2=80=99t need to be a collaborator on a =
document in order to <o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>1)<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Open issues<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>2)<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Clone and make pull requests<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The collaborators should be the main document =
editors.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Aziz Mohaisen [mailto:a.mohaisen@gmail.com] <br><b>Sent:</b> Tuesday, =
February 10, 2015 10:42 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
sacm@ietf.org<br><b>Subject:</b> Re: [sacm] poll: Trac or GitHub or =
None?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>That is perhaps =
something that the working group or chairs have to decide. I am not sure =
if the TLS WG is using GitHub for issue tracking, editing documents, or =
both, so cannot speak for their choice. <o:p></o:p></p></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>If we are going to use =
GitHub for issue tracking only, I think it would be reasonable to have =
all document in a single repository for cross-reference of issues -- =
just the way Jim explained it. <o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>However, if we are to use GitHub for =
tracking and authoring -- contributing to documents, it becomes =
infeasible to have a single repository with a directory structure for =
documents. <o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>As of now, I have created a single =
repository for each document that's posted on the WG page:<br><br><a =
href=3D"https://github.com/sacm">https://github.com/sacm</a><o:p></o:p></=
p></div><p class=3DMsoNormal>I need everyone who wants to be a =
collaborator on any document to send me their user id on =
github.<br><br>Thanks,<br>Aziz<o:p></o:p></p></div><div><p =
class=3DMsoNormal><br =
clear=3Dall><o:p></o:p></p><div><div><div><div><div><div><div><div><div><=
div><div><div><div><p =
class=3DMsoNormal><br>---------<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Aziz Mohaisen<o:p></o:p></p></div></div></div></div><p =
class=3DMsoNormal><a href=3D"http://www.mohaisen.net/" =
target=3D"_blank">www.mohaisen.net</a><o:p></o:p></p></div></div></div></=
div></div></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Tue, =
Feb 10, 2015 at 1:13 PM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>One of the issues that was not discussed on the call is the structure =
that is going to be used for the repository.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>TLS has a project which is the working group and then a different =
repository for each different document <a =
href=3D"https://github.com/tlswg" =
target=3D"_blank">https://github.com/tlswg</a></span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have also seen a single repository with a different subdirectory =
for each different </span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>One could also I suppose have a single repository with different =
files in that repository for each draft.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The choice makes a difference in terms of how issues are going to be =
tracked.&nbsp; The first means that each different draft has its own =
issue tracker.&nbsp; There is no easy way to look at all of the issues =
in a single view.&nbsp; It can also be a problem if an issue is attached =
to two different drafts as the issue either needs to cross point to the =
other one or be duplicated.&nbsp; </span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The first is easier if you are using all of the fancy makefiles that =
have been created for doing releases and automatic building of files =
during merges.&nbsp;&nbsp; I don=E2=80=99t know that doing tagging works =
well for doing tags on different directories of different =
strings.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
sacm [mailto:<a href=3D"mailto:sacm-bounces@ietf.org" =
target=3D"_blank">sacm-bounces@ietf.org</a>] <b>On Behalf Of =
</b>Kathleen Moriarty<br><b>Sent:</b> Monday, February 09, 2015 7:51 =
AM<br><b>To:</b> Chris Inacio<br><b>Cc:</b> Dan Romascanu; Sean Turner; =
<a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a>; =
Lorenzin, Lisa<br><b>Subject:</b> Re: [sacm] poll: Trac or GitHub or =
None?</span><o:p></o:p></p></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Is the WG =
interested in editing drafts via GitHub as well or just tracking =
issues?&nbsp; Other WGs find editing drafts via GitHub very =
helpful.&nbsp; I believe both Sean and I have sent links for examples =
and how to do this.<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks.<o:p>=
</o:p></p></div></div><div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Mon, Feb =
9, 2015 at 10:44 AM, Chris Inacio &lt;<a href=3D"mailto:inacio@cert.org" =
target=3D"_blank">inacio@cert.org</a>&gt; wrote:<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>+1 for =
GitHub.<br><br><br>--<br>Chris Inacio<br><a =
href=3D"mailto:inacio@cert.org" =
target=3D"_blank">inacio@cert.org</a><o:p></o:p></p><div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><br><br><br>&gt; =
On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty &lt;<a =
href=3D"mailto:kathleen.moriarty.ietf@gmail.com" =
target=3D"_blank">kathleen.moriarty.ietf@gmail.com</a>&gt; =
wrote:<br>&gt;<br>&gt;<br>&gt;<br>&gt; Sent from my =
iPhone<br>&gt;<br>&gt;&gt;&gt; On Jan 29, 2015, at 2:25 PM, Sean Turner =
&lt;<a href=3D"mailto:turners@ieca.com" =
target=3D"_blank">turners@ieca.com</a>&gt; =
wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; On Jan 23, 2015, at 20:29, =
Lorenzin, Lisa &lt;<a href=3D"mailto:llorenzin@pulsesecure.net" =
target=3D"_blank">llorenzin@pulsesecure.net</a>&gt; =
wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; If it was just me, I'd use Trac =
because it seems simpler to me. But if the rest of the group prefers =
Github, I will endeavor to wrap my head around it. =
:)<br>&gt;&gt;<br>&gt;&gt; I=E2=80=99ve got some links to some pointers =
for GitHub that Martin Thompson provided when I had to get my head =
around GitHub too.<br>&gt;&gt;<br>&gt;&gt; For ID authors =
there=E2=80=99s:<br>&gt;&gt; <a =
href=3D"https://github.com/martinthomson/i-d-template" =
target=3D"_blank">https://github.com/martinthomson/i-d-template</a><br>&g=
t;&gt;<br>&gt;&gt; If the chairs make a WG repo (and make you a =
contributor) then it=E2=80=99ll look slightly more official - and they =
can add note well and the like.<br>&gt;&gt;<br>&gt;&gt; Personally, I =
like github because there=E2=80=99s a whole lotta open source folks =
using it.<br>&gt;<br>&gt; +1. I believe the WG is only talking about =
issue tracking right now, but WGs using this for document editing seem =
to really prefer the ability to see updates/draft management in between =
IETF versions.<br>&gt;<br>&gt; Kathleen<br>&gt; No =
hat<br>&gt;&gt;<br>&gt;&gt; spt<br>&gt;&gt; =
_______________________________________________<br>&gt;&gt; sacm mailing =
list<br>&gt;&gt; <a href=3D"mailto:sacm@ietf.org" =
target=3D"_blank">sacm@ietf.org</a><br>&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/sacm" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>&gt;<=
br>&gt; _______________________________________________<br>&gt; sacm =
mailing list<br>&gt; <a href=3D"mailto:sacm@ietf.org" =
target=3D"_blank">sacm@ietf.org</a><br>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/sacm" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><o:p></o:=
p></p></div></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><br =
clear=3Dall><o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-- =
<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Best =
regards,<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Kathleen<o:p=
></o:p></p></div></div></div></div></div></div></div></div></div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>______________________________________=
_________<br>sacm mailing list<br><a =
href=3D"mailto:sacm@ietf.org">sacm@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sacm" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><o:p></o:=
p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_057B_01D0453E.F156F080--


From nobody Tue Feb 10 17:54:04 2015
Return-Path: <a.mohaisen@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 702CC1A1B70 for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 17:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 T8l2ggASPVwH for <sacm@ietfa.amsl.com>; Tue, 10 Feb 2015 17:54:00 -0800 (PST)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 297E21A1B74 for <sacm@ietf.org>; Tue, 10 Feb 2015 17:54:00 -0800 (PST)
Received: by mail-ig0-f182.google.com with SMTP id h15so1592827igd.3 for <sacm@ietf.org>; Tue, 10 Feb 2015 17:53:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GbLdSaEHRcmqudQOVhVOf+CYM9Q1Hc680LKow1W71P0=; b=yor2YRHYV1YQpO7TXN6ufLhZ9dl1sBikiKAUMO/W1H3ez0n2Iyi8dTLPShuRru1ZMc sKi0O7/K8YosQZZa8tqdsXb+AmSKkAWjtpGbfuFX42FM77z/VccolcnvWjOH17kpwYsj EqTs7XknheRwR0v2CoiqVeL5QKedZac0PAapgL/2PhDQGAjzlgcXx2v7RZQBTheJHX8o JuNGrdYjuh5OM/BCZYZYt9noHdYEQ/BKMBafhlLzN+zL6hxvRWUUhSBbDcnQX2VdtFyd UEv7SRHQVKch1gD+2dl8PEZFCnyLcEt97mcdkxczunA8NqBiaN5yPmaDmnqs0XF3NZ/V SKkw==
MIME-Version: 1.0
X-Received: by 10.42.223.194 with SMTP id il2mr669973icb.94.1423619639408; Tue, 10 Feb 2015 17:53:59 -0800 (PST)
Received: by 10.50.43.68 with HTTP; Tue, 10 Feb 2015 17:53:59 -0800 (PST)
Received: by 10.50.43.68 with HTTP; Tue, 10 Feb 2015 17:53:59 -0800 (PST)
In-Reply-To: <057a01d04581$ff75c3b0$fe614b10$@augustcellars.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C95DBE6@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA5C972BEA@AZ-FFEXMB04.global.avaya.com> <BN1PR06MB4371D85CDE35C14995C64AFA8370@BN1PR06MB437.namprd06.prod.outlook.com> <D125BD81-4F6A-477D-9E2F-B1B6DFDC9A27@ieca.com> <794082DB-C61D-4AE9-8AB9-92839EA7073A@gmail.com> <82184C37-E235-42EF-AC2E-BFD45C361D81@cert.org> <CAHbuEH7_zAvAS7gQG4gBDN-fjw5fuOeZjeaFEUQ8nxkvDU7sPg@mail.gmail.com> <04ee01d0455d$4a305160$de90f420$@augustcellars.com> <CAMjhxSePkURr8TuS4sW=+oYJoYH-K0APfMXg-kmkysP72aAA6w@mail.gmail.com> <057a01d04581$ff75c3b0$fe614b10$@augustcellars.com>
Date: Tue, 10 Feb 2015 20:53:59 -0500
Message-ID: <CAMjhxSe+4321PUxR1f9PAgFWkzT4CsQFoENy2Z1iyQAQJL4ryw@mail.gmail.com>
From: Aziz Mohaisen <a.mohaisen@gmail.com>
To: Jim Schaad <ietf@augustcellars.com>, sacm@ietf.org
Content-Type: multipart/alternative; boundary=001a1132fb6ee6fec8050ec64679
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/QxtSWYDlpuozzz-CbQ9uVUlSi0A>
Subject: Re: [sacm] poll: Trac or GitHub or None?
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 01:54:03 -0000

--001a1132fb6ee6fec8050ec64679
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That is correct. Collaborators (and owners of an organizations in the terms
of github) are only main authors on documents.

My earlier comment is concerning manageability of large repositories.

Aziz
On Feb 10, 2015 5:37 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:

> Note =E2=80=93 You don=E2=80=99t need to be a collaborator on a document =
in order to
>
> 1)      Open issues
>
> 2)      Clone and make pull requests
>
>
>
> The collaborators should be the main document editors.
>
>
>
> Jim
>
>
>
>
>
> *From:* Aziz Mohaisen [mailto:a.mohaisen@gmail.com]
> *Sent:* Tuesday, February 10, 2015 10:42 AM
> *To:* Jim Schaad
> *Cc:* sacm@ietf.org
> *Subject:* Re: [sacm] poll: Trac or GitHub or None?
>
>
>
> That is perhaps something that the working group or chairs have to decide=
.
> I am not sure if the TLS WG is using GitHub for issue tracking, editing
> documents, or both, so cannot speak for their choice.
>
> If we are going to use GitHub for issue tracking only, I think it would b=
e
> reasonable to have all document in a single repository for cross-referenc=
e
> of issues -- just the way Jim explained it.
>
> However, if we are to use GitHub for tracking and authoring --
> contributing to documents, it becomes infeasible to have a single
> repository with a directory structure for documents.
>
> As of now, I have created a single repository for each document that's
> posted on the WG page:
>
> https://github.com/sacm
>
> I need everyone who wants to be a collaborator on any document to send me
> their user id on github.
>
> Thanks,
> Aziz
>
>
>
> ---------
>
> Aziz Mohaisen
>
> www.mohaisen.net
>
>
>
> On Tue, Feb 10, 2015 at 1:13 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:
>
> One of the issues that was not discussed on the call is the structure tha=
t
> is going to be used for the repository.
>
>
>
> TLS has a project which is the working group and then a different
> repository for each different document https://github.com/tlswg
>
>
>
> I have also seen a single repository with a different subdirectory for
> each different
>
>
>
> One could also I suppose have a single repository with different files in
> that repository for each draft.
>
>
>
> The choice makes a difference in terms of how issues are going to be
> tracked.  The first means that each different draft has its own issue
> tracker.  There is no easy way to look at all of the issues in a single
> view.  It can also be a problem if an issue is attached to two different
> drafts as the issue either needs to cross point to the other one or be
> duplicated.
>
>
>
> The first is easier if you are using all of the fancy makefiles that have
> been created for doing releases and automatic building of files during
> merges.   I don=E2=80=99t know that doing tagging works well for doing ta=
gs on
> different directories of different strings.
>
>
>
> Jim
>
>
>
>
>
> *From:* sacm [mailto:sacm-bounces@ietf.org] *On Behalf Of *Kathleen
> Moriarty
> *Sent:* Monday, February 09, 2015 7:51 AM
> *To:* Chris Inacio
> *Cc:* Dan Romascanu; Sean Turner; sacm@ietf.org; Lorenzin, Lisa
> *Subject:* Re: [sacm] poll: Trac or GitHub or None?
>
>
>
> Is the WG interested in editing drafts via GitHub as well or just trackin=
g
> issues?  Other WGs find editing drafts via GitHub very helpful.  I believ=
e
> both Sean and I have sent links for examples and how to do this.
>
>
>
> Thanks.
>
>
>
> On Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio <inacio@cert.org> wrote:
>
> +1 for GitHub.
>
>
> --
> Chris Inacio
> inacio@cert.org
>
>
>
>
> > On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty <
> kathleen.moriarty.ietf@gmail.com> wrote:
> >
> >
> >
> > Sent from my iPhone
> >
> >>> On Jan 29, 2015, at 2:25 PM, Sean Turner <turners@ieca.com> wrote:
> >>>
> >>> On Jan 23, 2015, at 20:29, Lorenzin, Lisa <llorenzin@pulsesecure.net>
> wrote:
> >>>
> >>> If it was just me, I'd use Trac because it seems simpler to me. But i=
f
> the rest of the group prefers Github, I will endeavor to wrap my head
> around it. :)
> >>
> >> I=E2=80=99ve got some links to some pointers for GitHub that Martin Th=
ompson
> provided when I had to get my head around GitHub too.
> >>
> >> For ID authors there=E2=80=99s:
> >> https://github.com/martinthomson/i-d-template
> >>
> >> If the chairs make a WG repo (and make you a contributor) then it=E2=
=80=99ll
> look slightly more official - and they can add note well and the like.
> >>
> >> Personally, I like github because there=E2=80=99s a whole lotta open s=
ource
> folks using it.
> >
> > +1. I believe the WG is only talking about issue tracking right now, bu=
t
> WGs using this for document editing seem to really prefer the ability to
> see updates/draft management in between IETF versions.
> >
> > Kathleen
> > No hat
> >>
> >> spt
> >> _______________________________________________
> >> sacm mailing list
> >> sacm@ietf.org
> >> https://www.ietf.org/mailman/listinfo/sacm
> >
> > _______________________________________________
> > sacm mailing list
> > sacm@ietf.org
> > https://www.ietf.org/mailman/listinfo/sacm
>
>
>
>
>
> --
>
>
>
> Best regards,
>
> Kathleen
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>
>
>

--001a1132fb6ee6fec8050ec64679
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">That is correct. Collaborators (and owners of an organizatio=
ns in the terms of github) are only main authors on documents. </p>
<p dir=3D"ltr">My earlier comment is concerning manageability of large repo=
sitories. </p>
<p dir=3D"ltr">Aziz </p>
<div class=3D"gmail_quote">On Feb 10, 2015 5:37 PM, &quot;Jim Schaad&quot; =
&lt;<a href=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a>&gt=
; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=
=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">Note =E2=80=93 You don=E2=80=99t need to be a collabo=
rator on a document in order to <u></u><u></u></span></p><p><u></u><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d"><span>1)<span style=3D"font:7.0pt &quot;Times New Roman&=
quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span></span></span><u></u><span sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;color:#1f497d">Open issues<u></u><u></u></span></p><p><u></u><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d"><span>2)<span style=3D"font:7.0pt &quot;Times New Roman&quo=
t;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span></span></span><u></u><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:#1f497d">Clone and make pull requests<u></u><u></u></span></p><p cla=
ss=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p>=
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The collaborators should =
be the main document editors.<u></u><u></u></span></p><p class=3D"MsoNormal=
"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p class=3D"Mso=
Normal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></span></p><p class=3D"=
MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p><p cla=
ss=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></span></p>=
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Aziz Mohaisen [mailto:<a href=3D"mailto:a.mohaisen@gmail.com" =
target=3D"_blank">a.mohaisen@gmail.com</a>] <br><b>Sent:</b> Tuesday, Febru=
ary 10, 2015 10:42 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> <a href=3D"mai=
lto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br><b>Subject:</b> R=
e: [sacm] poll: Trac or GitHub or None?<u></u><u></u></span></p></div></div=
><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><div><div><div><div><p=
 class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">That is perhaps somethi=
ng that the working group or chairs have to decide. I am not sure if the TL=
S WG is using GitHub for issue tracking, editing documents, or both, so can=
not speak for their choice. <u></u><u></u></p></div><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt">If we are going to use GitHub for issue trac=
king only, I think it would be reasonable to have all document in a single =
repository for cross-reference of issues -- just the way Jim explained it. =
<u></u><u></u></p></div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0p=
t">However, if we are to use GitHub for tracking and authoring -- contribut=
ing to documents, it becomes infeasible to have a single repository with a =
directory structure for documents. <u></u><u></u></p></div><p class=3D"MsoN=
ormal" style=3D"margin-bottom:12.0pt">As of now, I have created a single re=
pository for each document that&#39;s posted on the WG page:<br><br><a href=
=3D"https://github.com/sacm" target=3D"_blank">https://github.com/sacm</a><=
u></u><u></u></p></div><p class=3D"MsoNormal">I need everyone who wants to =
be a collaborator on any document to send me their user id on github.<br><b=
r>Thanks,<br>Aziz<u></u><u></u></p></div><div><p class=3D"MsoNormal"><br cl=
ear=3D"all"><u></u><u></u></p><div><div><div><div><div><div><div><div><div>=
<div><div><div><div><p class=3D"MsoNormal"><br>---------<u></u><u></u></p><=
/div><div><p class=3D"MsoNormal">Aziz Mohaisen<u></u><u></u></p></div></div=
></div></div><p class=3D"MsoNormal"><a href=3D"http://www.mohaisen.net/" ta=
rget=3D"_blank">www.mohaisen.net</a><u></u><u></u></p></div></div></div></d=
iv></div></div></div></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u=
></p><div><p class=3D"MsoNormal">On Tue, Feb 10, 2015 at 1:13 PM, Jim Schaa=
d &lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augu=
stcellars.com</a>&gt; wrote:<u></u><u></u></p><div><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">One of the issues that was not discussed on =
the call is the structure that is going to be used for the repository.</spa=
n><u></u><u></u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=
=A0</span><u></u><u></u></p><p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497=
d">TLS has a project which is the working group and then a different reposi=
tory for each different document <a href=3D"https://github.com/tlswg" targe=
t=3D"_blank">https://github.com/tlswg</a></span><u></u><u></u></p><p class=
=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></u></p><p=
 class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1f497d">I have also seen a single r=
epository with a different subdirectory for each different </span><u></u><u=
></u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u>=
</u><u></u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">One could =
also I suppose have a single repository with different files in that reposi=
tory for each draft.</span><u></u><u></u></p><p class=3D"MsoNormal"><span s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d">=C2=A0</span><u></u><u></u></p><p class=3D"MsoNormal"><=
span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:#1f497d">The choice makes a difference in terms of how iss=
ues are going to be tracked.=C2=A0 The first means that each different draf=
t has its own issue tracker.=C2=A0 There is no easy way to look at all of t=
he issues in a single view.=C2=A0 It can also be a problem if an issue is a=
ttached to two different drafts as the issue either needs to cross point to=
 the other one or be duplicated.=C2=A0 </span><u></u><u></u></p><p class=3D=
"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></u></p><p cl=
ass=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1f497d">The first is easier if you are=
 using all of the fancy makefiles that have been created for doing releases=
 and automatic building of files during merges.=C2=A0=C2=A0 I don=E2=80=99t=
 know that doing tagging works well for doing tags on different directories=
 of different strings.</span><u></u><u></u></p><p class=3D"MsoNormal"><span=
 style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">=C2=A0</span><u></u><u></u></p><p class=3D"MsoNormal"=
><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1f497d">Jim</span><u></u><u></u></p><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></u></p><p class=3D"M=
soNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></u></p><div st=
yle=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">=
<div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt=
 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;"> sacm [mailto:<a href=3D"mailto:sacm-bounces@ietf.org" target=3D"_blan=
k">sacm-bounces@ietf.org</a>] <b>On Behalf Of </b>Kathleen Moriarty<br><b>S=
ent:</b> Monday, February 09, 2015 7:51 AM<br><b>To:</b> Chris Inacio<br><b=
>Cc:</b> Dan Romascanu; Sean Turner; <a href=3D"mailto:sacm@ietf.org" targe=
t=3D"_blank">sacm@ietf.org</a>; Lorenzin, Lisa<br><b>Subject:</b> Re: [sacm=
] poll: Trac or GitHub or None?</span><u></u><u></u></p></div></div><p clas=
s=3D"MsoNormal">=C2=A0<u></u><u></u></p><div><p class=3D"MsoNormal">Is the =
WG interested in editing drafts via GitHub as well or just tracking issues?=
=C2=A0 Other WGs find editing drafts via GitHub very helpful.=C2=A0 I belie=
ve both Sean and I have sent links for examples and how to do this.<u></u><=
u></u></p><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p></div><div><p=
 class=3D"MsoNormal">Thanks.<u></u><u></u></p></div></div><div><div><div><p=
 class=3D"MsoNormal">=C2=A0<u></u><u></u></p><div><p class=3D"MsoNormal">On=
 Mon, Feb 9, 2015 at 10:44 AM, Chris Inacio &lt;<a href=3D"mailto:inacio@ce=
rt.org" target=3D"_blank">inacio@cert.org</a>&gt; wrote:<u></u><u></u></p><=
p class=3D"MsoNormal">+1 for GitHub.<br><br><br>--<br>Chris Inacio<br><a hr=
ef=3D"mailto:inacio@cert.org" target=3D"_blank">inacio@cert.org</a><u></u><=
u></u></p><div><div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><=
br><br><br>&gt; On Feb 8, 2015, at 11:13 AM, Kathleen Moriarty &lt;<a href=
=3D"mailto:kathleen.moriarty.ietf@gmail.com" target=3D"_blank">kathleen.mor=
iarty.ietf@gmail.com</a>&gt; wrote:<br>&gt;<br>&gt;<br>&gt;<br>&gt; Sent fr=
om my iPhone<br>&gt;<br>&gt;&gt;&gt; On Jan 29, 2015, at 2:25 PM, Sean Turn=
er &lt;<a href=3D"mailto:turners@ieca.com" target=3D"_blank">turners@ieca.c=
om</a>&gt; wrote:<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; On Jan 23, 2015, at 20:29=
, Lorenzin, Lisa &lt;<a href=3D"mailto:llorenzin@pulsesecure.net" target=3D=
"_blank">llorenzin@pulsesecure.net</a>&gt; wrote:<br>&gt;&gt;&gt;<br>&gt;&g=
t;&gt; If it was just me, I&#39;d use Trac because it seems simpler to me. =
But if the rest of the group prefers Github, I will endeavor to wrap my hea=
d around it. :)<br>&gt;&gt;<br>&gt;&gt; I=E2=80=99ve got some links to some=
 pointers for GitHub that Martin Thompson provided when I had to get my hea=
d around GitHub too.<br>&gt;&gt;<br>&gt;&gt; For ID authors there=E2=80=99s=
:<br>&gt;&gt; <a href=3D"https://github.com/martinthomson/i-d-template" tar=
get=3D"_blank">https://github.com/martinthomson/i-d-template</a><br>&gt;&gt=
;<br>&gt;&gt; If the chairs make a WG repo (and make you a contributor) the=
n it=E2=80=99ll look slightly more official - and they can add note well an=
d the like.<br>&gt;&gt;<br>&gt;&gt; Personally, I like github because there=
=E2=80=99s a whole lotta open source folks using it.<br>&gt;<br>&gt; +1. I =
believe the WG is only talking about issue tracking right now, but WGs usin=
g this for document editing seem to really prefer the ability to see update=
s/draft management in between IETF versions.<br>&gt;<br>&gt; Kathleen<br>&g=
t; No hat<br>&gt;&gt;<br>&gt;&gt; spt<br>&gt;&gt; _________________________=
______________________<br>&gt;&gt; sacm mailing list<br>&gt;&gt; <a href=3D=
"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br>&gt;&gt; <a h=
ref=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">https:=
//www.ietf.org/mailman/listinfo/sacm</a><br>&gt;<br>&gt; __________________=
_____________________________<br>&gt; sacm mailing list<br>&gt; <a href=3D"=
mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br>&gt; <a href=
=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">https://w=
ww.ietf.org/mailman/listinfo/sacm</a><u></u><u></u></p></div></div></div><p=
 class=3D"MsoNormal"><br><br clear=3D"all"><u></u><u></u></p><div><p class=
=3D"MsoNormal">=C2=A0<u></u><u></u></p></div><p class=3D"MsoNormal">-- <u><=
/u><u></u></p><div><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p><div=
><p class=3D"MsoNormal">Best regards,<u></u><u></u></p></div><div><p class=
=3D"MsoNormal">Kathleen<u></u><u></u></p></div></div></div></div></div></di=
v></div></div></div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><=
br>_______________________________________________<br>sacm mailing list<br>=
<a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">https=
://www.ietf.org/mailman/listinfo/sacm</a><u></u><u></u></p></div><p class=
=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></div></div></div></blockquote=
></div>

--001a1132fb6ee6fec8050ec64679--


From nobody Wed Feb 11 07:56:03 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9502A1A86E4 for <sacm@ietfa.amsl.com>; Wed, 11 Feb 2015 07:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ZbIKrY9p0cKI for <sacm@ietfa.amsl.com>; Wed, 11 Feb 2015 07:55:59 -0800 (PST)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13B211A8876 for <sacm@ietf.org>; Wed, 11 Feb 2015 07:55:45 -0800 (PST)
Received: by mail-oi0-f46.google.com with SMTP id x69so12820204oia.5 for <sacm@ietf.org>; Wed, 11 Feb 2015 07:55:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:message-id:mime-version:subject:date:references :to; bh=xRP5uC4MIOGsWZDJoovZNtNhx66mciiCxZMuW0ukLqA=; b=k5l02RXJE0dtuYUQn7PDPRts3tSPOpR0CvVBa9HkQk8MyXJ2yGOsP1s+OwXpr3pt1G gWfyoEncQLeHsEfjcqTsxaMpvBqG6t+WDu1Sg+RLbGvprMd5yMpMxkMBGZ7Ah9F4hxDv V1bWl7zGN9U16o+JbxlYktNNwXj8ojHAkQfyTASnVdxK90fupQSYjm5jEGUnTl+9qJQ5 DKkXx4OvhQ6KT6rZnaOvmKX+pWIM3lI7nr0idyR33eNHhmruXJmwg9B3NMdz4M+4WHrF oF+5sbine6KlJksXhJgwhQE9+CfjVsjxXcs4JRDAX6Orlf6FiTmoxhPyap3xAXcz6AgW r4jQ==
X-Received: by 10.182.19.167 with SMTP id g7mr19700374obe.75.1423670143724; Wed, 11 Feb 2015 07:55:43 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:5453:87d0:7c1a:4774? ([2602:306:3406:4f00:5453:87d0:7c1a:4774]) by mx.google.com with ESMTPSA id uk9sm544332oeb.0.2015.02.11.07.55.41 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Feb 2015 07:55:42 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_787F4B09-229C-48D2-BC9A-0A70DD1C0B0D"
Message-Id: <819CF3A8-253D-416D-8148-6194245FC9A3@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Priority: 3
Date: Wed, 11 Feb 2015 09:55:17 -0600
References: <3B99D2BA-2B3D-4160-BB19-B560F604FA50@amsl.com>
To: sacm@ietf.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/fAciTZVnWFCVo5Va8-7es8BQQsA>
Subject: [sacm] Fwd: Your WebEx recording is available for viewing: SACM-20150209 1504-1
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 15:56:01 -0000

--Apple-Mail=_787F4B09-229C-48D2-BC9A-0A70DD1C0B0D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

FYI.

> Begin forwarded message:
>=20
> From: Cindy Morgan <cmorgan@amsl.com>
> Subject: Fwd: Your WebEx recording is available for viewing: =
SACM-20150209 1504-1
> Date: February 11, 2015 at 8:28:00 AM CST
> To: Dan Romascanu <dromasca@avaya.com>, "Adam W. Montville" =
<adam.w.montville@gmail.com>
>=20
>=20
>=20
> Begin forwarded message:
>=20
>> From: messenger@webex.com <mailto:messenger@webex.com>
>> Date: February 11, 2015 1:08:41 AM PST
>> To: cmorgan@amsl.com <mailto:cmorgan@amsl.com>
>> Subject: Your WebEx recording is available for viewing: SACM-20150209 =
1504-1
>> Reply-To: messenger@webex.com <mailto:messenger@webex.com>
>>=20
>>=20
>> Hi, Cindy Morgan,=20
>>=20
>> Your recording is now available on your WebEx site.=20
>>=20
>>=20
>> SACM-20150209 1504-1=20
>> Monday, February 9, 2015=20
>> 7:04 am | Pacific Standard Time (San Francisco, GMT-08:00)=20
>>=20
>>=20
>> PLAY RECORDING (42 hr 0 min 38 sec)=20
>> =
https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899aba=
41bdd6d3e96 =
<https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899ab=
a41bdd6d3e96>=20
>>=20
>> You can forward this message to others to allow them to play back the =
recording.=20
>=20


--Apple-Mail=_787F4B09-229C-48D2-BC9A-0A70DD1C0B0D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">FYI.<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">Begin forwarded =
message:</div><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">Cindy Morgan &lt;<a =
href=3D"mailto:cmorgan@amsl.com" class=3D"">cmorgan@amsl.com</a>&gt;<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">Fwd: Your WebEx =
recording is available for viewing: SACM-20150209 1504-1</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">February 11, 2015 at 8:28:00 AM =
CST<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">Dan Romascanu &lt;<a =
href=3D"mailto:dromasca@avaya.com" class=3D"">dromasca@avaya.com</a>&gt;, =
"Adam W. Montville" &lt;<a href=3D"mailto:adam.w.montville@gmail.com" =
class=3D"">adam.w.montville@gmail.com</a>&gt;<br =
class=3D""></span></div><br class=3D""><div class=3D""><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; " class=3D""><br class=3D"">
<div class=3D""><br class=3D""><div class=3D"">Begin forwarded =
message:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite" class=3D""><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">From: </b></span><span style=3D"font-family: Helvetica; =
font-size: inherit;" class=3D""><a href=3D"mailto:messenger@webex.com" =
class=3D"">messenger@webex.com</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: Helvetica; =
font-size: inherit;" class=3D""><b class=3D"">Date: </b></span><span =
style=3D"font-family: Helvetica; font-size: inherit;" class=3D"">February =
11, 2015 1:08:41 AM PST<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: Helvetica; =
font-size: inherit;" class=3D""><b class=3D"">To: </b></span><span =
style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><a =
href=3D"mailto:cmorgan@amsl.com" class=3D"">cmorgan@amsl.com</a><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">Subject: </b></span><span style=3D"font-family: Helvetica; =
font-size: inherit;" class=3D""><b class=3D"">Your WebEx recording is =
available for viewing: SACM-20150209 1504-1</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">Reply-To: </b></span><span style=3D"font-family: Helvetica; =
font-size: inherit;" class=3D""><a href=3D"mailto:messenger@webex.com" =
class=3D"">messenger@webex.com</a><br class=3D""></span></div><br =
class=3D""><font face=3D"Tahoma, Arial, sans-serif, Helvetica, Geneva" =
size=3D"2" class=3D""><br class=3D""> Hi, Cindy Morgan, <br class=3D""> =
<br class=3D""> Your recording is now available on your WebEx site. <br =
class=3D""> <br class=3D""> <br class=3D""> SACM-20150209 1504-1 <br =
class=3D""> Monday, February 9, 2015 <br class=3D""> 7:04 am | Pacific =
Standard Time (San Francisco, GMT-08:00) <br class=3D""> <br class=3D""> =
<br class=3D""> PLAY RECORDING (42 hr 0 min 38 sec) <br class=3D""> <a =
href=3D"https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b82664=
53899aba41bdd6d3e96" target=3D"_blank" =
class=3D"">https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b82=
66453899aba41bdd6d3e96</a> <br class=3D""> <br class=3D""> You can =
forward this message to others to allow them to play back the recording. =
<br class=3D""></font></blockquote></div><br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_787F4B09-229C-48D2-BC9A-0A70DD1C0B0D--


From nobody Wed Feb 11 09:45:19 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F921A1B0E; Wed, 11 Feb 2015 09:45:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 NkBYSEBswpWF; Wed, 11 Feb 2015 09:45:15 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C741A1AE7; Wed, 11 Feb 2015 09:45:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211174514.7785.22432.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 09:45:14 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/btkHyMD4sZDtvkAE7W73UbuY4PY>
Cc: sacm@ietf.org
Subject: [sacm] I-D Action: draft-ietf-sacm-terminology-06.txt
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 17:45:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Security Automation and Continuous Monitoring Working Group of the IETF.

        Title           : Terminology for Security Assessment
        Authors         : David Waltermire
                          Adam W. Montville
                          David Harrington
                          Nancy Cam-Winget
                          Jarrett Lu
                          Brian Ford
                          Merike Kaeo
	Filename        : draft-ietf-sacm-terminology-06.txt
	Pages           : 10
	Date            : 2015-02-11

Abstract:
   This memo documents terminology used in the documents produced by
   SACM (Security Automation and Continuous Monitoring).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sacm-terminology-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sacm-terminology-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 11 09:48:35 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD2E1A8A15 for <sacm@ietfa.amsl.com>; Wed, 11 Feb 2015 09:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 NjYNzJpRtR30 for <sacm@ietfa.amsl.com>; Wed, 11 Feb 2015 09:48:31 -0800 (PST)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA95E1A8A05 for <sacm@ietf.org>; Wed, 11 Feb 2015 09:48:16 -0800 (PST)
Received: by mail-ob0-f181.google.com with SMTP id vb8so4724534obc.12 for <sacm@ietf.org>; Wed, 11 Feb 2015 09:48:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=EPUZyewy08XymjSrP4tHD6Qi3q3M6NoJ8s5N9Leik8o=; b=LdrRDkXZSuO/RzePi/GuEzRTfCH78EbrNIwqJMMN6FeKh/R50hvPumQ6QFAn0K8pXA BNNlxGsX6T+4RrBznHpMXUb/gbegOOhirHkxAPU8FbJsXJjcrwd38EtcmTw+tVqES9Uv wS/WZN2YWVN+qwrea+2Z9yzEv5S53LZs4TcjcKt/bY3Zeb+t1hGyTayvvBT1Ppjwlqj4 37UH/3a+DN7/6/BCk0MS7oR4BjhLMC2/ubEqR9fZObXNTDJHaI4OVUYzQPHDK5s8iPK1 bGFXO3CAI0NfUJ/7wUeeAm2itjmGUC+ZUf7NjOrlre2YRCO0HJZAHARiQSesBYp5Ejc6 8AhA==
X-Received: by 10.202.221.84 with SMTP id u81mr19050181oig.71.1423676896172; Wed, 11 Feb 2015 09:48:16 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:5453:87d0:7c1a:4774? ([2602:306:3406:4f00:5453:87d0:7c1a:4774]) by mx.google.com with ESMTPSA id r83sm699297oif.28.2015.02.11.09.48.14 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Feb 2015 09:48:15 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: "Adam W. Montville" <adam.w.montville@gmail.com>
In-Reply-To: <20150211174514.7785.22432.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 11:47:50 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8B1A2C7-C755-4417-932E-B11A6B6A2FAF@gmail.com>
References: <20150211174514.7785.22432.idtracker@ietfa.amsl.com>
To: sacm@ietf.org
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/quf-tqNuIpag_v80P9wpVF5CwTE>
Subject: Re: [sacm] I-D Action: draft-ietf-sacm-terminology-06.txt
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 17:48:34 -0000

All:

This is a relatively minor revision on the terminology draft.  No terms =
have been altered, added, or removed.  Instead, some structural changes =
were made and the draft submitted to avoid expiration.

Adam

> On Feb 11, 2015, at 11:45 AM, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Security Automation and Continuous =
Monitoring Working Group of the IETF.
>=20
>        Title           : Terminology for Security Assessment
>        Authors         : David Waltermire
>                          Adam W. Montville
>                          David Harrington
>                          Nancy Cam-Winget
>                          Jarrett Lu
>                          Brian Ford
>                          Merike Kaeo
> 	Filename        : draft-ietf-sacm-terminology-06.txt
> 	Pages           : 10
> 	Date            : 2015-02-11
>=20
> Abstract:
>   This memo documents terminology used in the documents produced by
>   SACM (Security Automation and Continuous Monitoring).
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-sacm-terminology-06
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sacm-terminology-06
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm


From nobody Thu Feb 12 06:19:37 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A75A1A8872 for <sacm@ietfa.amsl.com>; Thu, 12 Feb 2015 06:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.609
X-Spam-Level: 
X-Spam-Status: No, score=-6.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Ty4F87vHAZ3U for <sacm@ietfa.amsl.com>; Thu, 12 Feb 2015 06:19:32 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 913281A8844 for <sacm@ietf.org>; Thu, 12 Feb 2015 06:19:32 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArsIAIm13FSHCzIm/2dsb2JhbABbgkMhIiIwXoI3R61SAQEBAQEBBgWSHR0BhXoCHIELQwEBAQEBAXyEDgEBAwwGEQpeAQYPBRAgAgQwFwMMAQQbGogLAaBfjSSEf4pJlxcBCgEBAR6GBIlEgmUMLxEdgRQFjUKBZ4VnhGSDBoI+jCQig26BcSQefwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,565,1418101200";  d="scan'208,217";a="106607784"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 12 Feb 2015 09:19:30 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 12 Feb 2015 09:19:30 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Thu, 12 Feb 2015 09:19:29 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: =?utf-8?B?Y29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFyY2hpdGVjdHVy?= =?utf-8?B?ZeKAkDAy?=
Thread-Index: AdBGzujW5hdC8qSIQH+lv5X9LxOgCA==
Date: Thu, 12 Feb 2015 14:19:29 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C994479AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/mcfq_ihqQahW0iGh9V7FVfy7sSU>
Subject: [sacm] =?utf-8?b?Y29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFy?= =?utf-8?b?Y2hpdGVjdHVyZeKAkDAy?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 14:19:35 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C994479AZFFEXMB04globa_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNClBsZWFzZSBmaW5kIGJlbG93IG15IGNvbW1lbnRzIG9uIGRyYWZ04oCQaWV0ZuKAkHNh
Y23igJBhcmNoaXRlY3R1cmXigJAwMi4gSSBhbHNvICBhZGRyZXNzZWQgaW4gbXkgY29tbWVudHMg
c29tZSBvZiB0aGUgb3BlbiBxdWVzdGlvbnMgcmFpc2VkIGluIHRoZSBJLUQuDQoNCg0KMS4gICAg
ICAgVGhlIGZpcnN0IHNlbnRlbmNlIGNvbnRhaW5zIGEgbG9naWNhbCByZXBldGl0aW9uIOKAkyB0
aGUgU0FDTSByZWZlcmVuY2UgYXJjaGl0ZWN0dXJlIGlzIG9idmlvdXNseSByZWxhdGVkIHRvIFNB
Q00gKGV2ZW4gaWYgb25lIGlzIHdpdGggYWNyb255bXMgZXhwYW5kZWQgYW5kIHRoZSBvdGhlciBp
cyBub3QpLiBQbGVhc2UgZmluZCBzb21lIG1vcmUgaW5zcGlyaW5nIHdvcmRzIGF2b2lkaW5nIHRo
ZSByZXBldGl0aW9uLg0KDQoNCg0KMi4gICAgICAgVGhlIG9wZW4gcXVlc3Rpb24gYXQgdGhlIGVu
ZCBvZiBTZWN0aW9uIDI6DQoNCg0Kw5ggIFdoeSBkb2VzIHRoZSBjaGFydGVyIG5vdCBzdWZmaWNl
Pw0KDQrDmCAgV2hhdCBpcyB0aGUgcHVycG9zZSBvZiBpbnNlcnRpbmcgdGhpcyBzZWN0aW9uIGlu
IHRoaXMgZHJhZnQ/DQoNCg0KVGhlIGFuc3dlciBpcyB0aGF0IHRoZSBjaGFydGVyIGlzIGEgdGVt
cG9yYXJ5IGRvY3VtZW50IHZpc2libGUgYW5kIGFjY2Vzc2libGUgd2hpbGUgdGhlIFdHIGlzIGFj
dGl2ZSAoYW5kIHN1YmplY3QgdG8gY2hhbmdlIGR1cmluZyB0aGlzIHBlcmlvZCkgYnV0IHRlbmRz
IHRvIGRpc2FwcGVhcmVkIHdoZW4gdGhlIFdHIGlzIGNvbmNsdWRlZC4gQSByZWNhcCBvZiB0aGUg
cHJvYmxlbSBzdGF0ZW1lbnQgaW4gdGhlIGludHJvZHVjdG9yeSBzZWN0aW9ucyBvZiB0aGUgYXJj
aGl0ZWN0dXJlIGRvY3VtZW50IHByb3ZpZGVzIGJhY2tncm91bmQgaW5mb3JtYXRpb24gZm9yIHRo
ZSBhcmNoaXRlY3R1cmUgdGhhdCBmb2xsb3dzIGFuZCBjYW4gYmUgdmVyeSB1c2VmdWwgZm9yIHVu
ZGVyc3RhbmRpbmcgc29tZSBvZiB0aGUgZnVuZGFtZW50YWwgZGVjaXNpb25zLg0KDQoNCjMuICAg
ICAgIEVkaXRvcmlhbCBpc3N1ZXMgaW4gU2VjdGlvbiAzLjEuMzoNCg0Kcy9UaGUgaW50cm9kdWN0
aW9uIG9mIHRoZSBjb250cm9sbGVyIHN1cHBvcnRzIHVzZSBjYXNlcy8gVGhlIGNvbnRyb2xsZXIg
c3VwcG9ydHMgdXNlIGNhc2VzLw0Kcy9Db25zdW1lcuKAmXMvQ29uc3VtZXJzLw0Kcy9Qcm92aWRl
cuKAmXMvUHJvdmlkZXJzLw0Kcy9pbnRlcmZhY2Ug4oCcQ+KAnSBzaG93biBpbiBGaWd1cmUgMSBk
ZW1vbnN0cmF0ZXMvIGludGVyZmFjZSDigJxD4oCdIHNob3duIGluIEZpZ3VyZSAxIGlsbHVzdHJh
dGVzLw0KDQoNCjQuICAgICAgIEluIG9yZGVyIHRvIHVuZGVyc3RhbmQgdGhlIHNlbnRlbmNlIOKA
mGEgY29udHJvbGxlciBtYXkgYWxzbyBwcm92aWRlIHRoZSBwcm94eSBvciBicm9rZXIgKGFuZCBw
b3NzaWJseSByb3V0aW5nKSBmdW5jdGlvbiBpbiB0aGUgZGF0YSBwbGFuZeKAmSBJIHdlbnQgYmFj
ayB0byB0aGUgdGVybWlub2xvZ3kgZG9jdW1lbnQuDQoNCldoYXQgSSBmb3VuZCBpcyB0aGF0IHRo
ZSBmb2xsb3dpbmcgdGVybXMgYXJlIGRlZmluZWQ6DQoNCiAgICAgICAgQnJva2VyIC0gQW4gZW50
aXR5IHByb3ZpZGluZyBhbmQvb3IgY29ubmVjdGluZyBzZXJ2aWNlcyBvbiB0aGUgYmVoYWxmIG9m
DQogICAgICBvdGhlciBhcmNoaXRlY3R1cmFsIGNvbXBvbmVudHMuDQoNCiAgICAgICAgUHJveHkg
LSBBbiBhcmNoaXRlY3R1cmFsIGNvbXBvbmVudCBwcm92aWRpbmcgZnVuY3Rpb25zLCBpbmZvcm1h
dGlvbiwgb3INCg0KICAgICAgc2VydmljZXMgb24gYmVoYWxmIG9mIGFub3RoZXIgY29tcG9uZW50
LCB3aGljaCBpcyBub3QgZGlyZWN0bHkNCg0KICAgICAgcGFydGljaXBhdGluZyBpbiB0aGUgYXJj
aGl0ZWN0dXJlLg0KDQpUaGVzZSBkZWZpbml0aW9ucyBzZWVtIHRvIG5lZWQgbW9yZSB3b3JrLiBU
aGV5IGFyZSBwYXJ0aWFsbHkgcmVkdW5kYW50IOKAkyBpcyB0aGlzIGJ5IGRlc2lnbj8gUHJveHkg
aXMgbm90IOKAmHBhcnRpY2lwYXRpbmcgaW4gdGhlIGFyY2hpdGVjdHVyZeKAmT8gVGhlbiBob3cg
aXMgaXQgYmV0d2VlbiB0aGUgMi0zIGZ1bmRhbWVudGFsIGZ1bmN0aW9ucyBvZiB0aGUgY29udHJv
bGxlcj8gVGhlcmUgbmVlZHMgdG8gYmUgbW9yZSB3b3JrIGluIHRoZSB0ZXJtaW5vbG9neSBkb2N1
bWVudCBJIGd1ZXNzLg0KDQoNCjUuICBUT0RPIOKAkCBhZGQgdGV4dCBhcm91bmQgdGhlIHVzYWdl
IG9mIHZhcmlvdXMgcHJvdG9jb2xzIGZvciBlbmRwb2ludA0KZGF0YSBjb2xsZWN0aW9uIChTTk1Q
LCBORVRDT05GLCBldGMuPykNCg0KICAgICAgICAgICAgICAgIGRvIHdlIHJlYWxseSBuZWVkIHRo
ZXNlIGluIGFuIGFyY2hpdGVjdHVyZSBkb2N1bWVudD8NCg0KVGhhbmtzIGFuZCBSZWdhcmRzLA0K
DQpEYW4NCg0KDQoNCg==

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C994479AZFFEXMB04globa_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5v
c2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5N
c29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1h
cmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28t
c3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7
fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQ
cmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7
DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnAuTXNv
TGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGNtOw0KCW1hcmdpbi1yaWdo
dDowY207DQoJbWFyZ2luLWJvdHRvbTowY207DQoJbWFyZ2luLWxlZnQ6MzYuMHB0Ow0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0K
CWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5
bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6IkNv
dXJpZXIgTmV3Ijt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0
aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4w
cHQgOTAuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyog
TGlzdCBEZWZpbml0aW9ucyAqLw0KQGxpc3QgbDANCgl7bXNvLWxpc3QtaWQ6MTI0MTUxOTgxMDsN
Cgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6LTEzMDE3NTMx
ODQgLTg3OTQ2Mjg5MCA2NzY5ODcxMyA2NzY5ODcxNSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcx
NSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcxNTt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxl
dmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRl
eHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0KQGxp
c3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotMTguMHB0O30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpyb21hbi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpAbGlz
dCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw1
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotMTguMHB0O30NCkBsaXN0IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpy
b21hbi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVy
LXBvc2l0aW9uOnJpZ2h0Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDcN
Cgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZl
bC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0O30N
CkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJp
Z2h0Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpAbGlzdCBsMQ0KCXttc28tbGlzdC1pZDoxNDM3
MDIyODI3Ow0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczot
MTMwMTc1MzE4NCAtODc5NDYyODkwIDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAzIDY3Njk4NzEz
IDY3Njk4NzE1IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1O30NCkBsaXN0IGwxOmxldmVsMQ0K
CXttc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYmlkaS1mb250LWZhbWlseTpDb25zb2xh
czt9DQpAbGlzdCBsMTpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93
ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDE6bGV2ZWwzDQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25l
Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246cmlnaHQ7DQoJdGV4dC1pbmRlbnQ6LTkuMHB0
O30NCkBsaXN0IGwxOmxldmVsNA0KCXttc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlzdCBs
MTpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxl
dmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRl
eHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDE6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246cmlnaHQ7DQoJdGV4dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwx
OmxldmVsNw0KCXttc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlzdCBsMTpsZXZlbDgNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0x
OC4wcHQ7fQ0KQGxpc3QgbDE6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OnJvbWFu
LWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246cmlnaHQ7DQoJdGV4dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwyDQoJe21zby1saXN0
LWlkOjE3NDAxMzE1NzU7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxh
dGUtaWRzOjQ0OTc0NjE5NiAtMTA0MzE5NzIgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2
OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDI6bGV2
ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
g5g7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzOw0K
CW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6
QXJpYWw7fQ0KQGxpc3QgbDI6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDI6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwyOmxldmVsNA0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMjps
ZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3
Ijt9DQpAbGlzdCBsMjpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZh
bWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDI6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4w
cHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwyOmxldmVsOA0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwyOmxldmVs
OQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674Kn
Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpv
bA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQotLT48
L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0i
ZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9
ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8
L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8
ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGksIDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5QbGVhc2UgZmluZCBiZWxvdyBteSBjb21tZW50cyBvbiBkcmFm
dOKAkGlldGbigJBzYWNt4oCQYXJjaGl0ZWN0dXJl4oCQMDIuIEkgYWxzbyAmbmJzcDthZGRyZXNz
ZWQgaW4gbXkgY29tbWVudHMgc29tZSBvZiB0aGUgb3BlbiBxdWVzdGlvbnMgcmFpc2VkIGluIHRo
ZSBJLUQuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0LWluZGVu
dDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8xIj48IVtpZiAhc3VwcG9ydExpc3RzXT48
c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4xLjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZx
dW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBkaXI9IkxUUiI+PC9zcGFuPlRo
ZSBmaXJzdCBzZW50ZW5jZSBjb250YWlucyBhIGxvZ2ljYWwgcmVwZXRpdGlvbiDigJMgdGhlIFNB
Q00gcmVmZXJlbmNlIGFyY2hpdGVjdHVyZSBpcyBvYnZpb3VzbHkgcmVsYXRlZCB0byBTQUNNIChl
dmVuIGlmIG9uZSBpcyB3aXRoIGFjcm9ueW1zIGV4cGFuZGVkIGFuZCB0aGUgb3RoZXIgaXMgbm90
KS4gUGxlYXNlIGZpbmQgc29tZSBtb3JlIGluc3BpcmluZyB3b3Jkcw0KIGF2b2lkaW5nIHRoZSBy
ZXBldGl0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0
ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8xIj48IVtpZiAhc3VwcG9y
dExpc3RzXT48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4yLjxzcGFuIHN0eWxlPSJmb250
OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBkaXI9IkxUUiI+
PC9zcGFuPlRoZSBvcGVuIHF1ZXN0aW9uIGF0IHRoZSBlbmQgb2YgU2VjdGlvbiAyOg0KPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28t
bGlzdDpsMiBsZXZlbDEgbGZvMjt0ZXh0LWF1dG9zcGFjZTpub25lIj4NCjwhW2lmICFzdXBwb3J0
TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OldpbmdkaW5n
cyI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+w5g8c3BhbiBzdHlsZT0iZm9udDo3LjBw
dCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3Nw
YW4+PCFbZW5kaWZdPjxzcGFuIGRpcj0iTFRSIj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6Q29uc29sYXMiPldoeSBkb2VzIHRoZSBjaGFydGVyIG5vdCBz
dWZmaWNlPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMiBsZXZlbDEgbGZvMiI+PCFb
aWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OldpbmdkaW5ncyI+PHNw
YW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+w5g8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVv
dDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFb
ZW5kaWZdPjxzcGFuIGRpcj0iTFRSIj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6Q29uc29sYXMiPldoYXQgaXMgdGhlIHB1cnBvc2Ugb2YgaW5zZXJ0aW5n
IHRoaXMgc2VjdGlvbiBpbiB0aGlzIGRyYWZ0Pzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29MaXN0UGFyYWdyYXBoIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxOC4wcHQiPlRoZSBhbnN3ZXIgaXMgdGhhdCB0
aGUgY2hhcnRlciBpcyBhIHRlbXBvcmFyeSBkb2N1bWVudCB2aXNpYmxlIGFuZCBhY2Nlc3NpYmxl
IHdoaWxlIHRoZSBXRyBpcyBhY3RpdmUgKGFuZCBzdWJqZWN0IHRvIGNoYW5nZSBkdXJpbmcgdGhp
cyBwZXJpb2QpIGJ1dCB0ZW5kcyB0byBkaXNhcHBlYXJlZCB3aGVuIHRoZSBXRyBpcyBjb25jbHVk
ZWQuIEEgcmVjYXAgb2YgdGhlDQogcHJvYmxlbSBzdGF0ZW1lbnQgaW4gdGhlIGludHJvZHVjdG9y
eSBzZWN0aW9ucyBvZiB0aGUgYXJjaGl0ZWN0dXJlIGRvY3VtZW50IHByb3ZpZGVzIGJhY2tncm91
bmQgaW5mb3JtYXRpb24gZm9yIHRoZSBhcmNoaXRlY3R1cmUgdGhhdCBmb2xsb3dzIGFuZCBjYW4g
YmUgdmVyeSB1c2VmdWwgZm9yIHVuZGVyc3RhbmRpbmcgc29tZSBvZiB0aGUgZnVuZGFtZW50YWwg
ZGVjaXNpb25zLg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bWFyZ2luLWxlZnQ6MTguMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29M
aXN0UGFyYWdyYXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZl
bDEgbGZvMSI+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9y
ZSI+My48c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsi
PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48IVtl
bmRpZl0+PHNwYW4gZGlyPSJMVFIiPjwvc3Bhbj5FZGl0b3JpYWwgaXNzdWVzIGluIFNlY3Rpb24g
My4xLjM6DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE4LjBw
dCI+cy9UaGUgaW50cm9kdWN0aW9uIG9mIHRoZSBjb250cm9sbGVyIHN1cHBvcnRzIHVzZSBjYXNl
cy8gVGhlIGNvbnRyb2xsZXIgc3VwcG9ydHMgdXNlIGNhc2VzLzxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE4LjBwdCI+cy9Db25zdW1lcuKA
mXMvQ29uc3VtZXJzLzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0OjE4LjBwdCI+cy9Qcm92aWRlcuKAmXMvUHJvdmlkZXJzLzxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE4LjBwdCI+cy9p
bnRlcmZhY2Ug4oCcQ+KAnSBzaG93biBpbiBGaWd1cmUgMSBkZW1vbnN0cmF0ZXMvIGludGVyZmFj
ZSDigJxD4oCdIHNob3duIGluIEZpZ3VyZSAxIGlsbHVzdHJhdGVzLzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE4LjBwdCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9InRleHQtaW5k
ZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPjwhW2lmICFzdXBwb3J0TGlzdHNd
PjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPjQuPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQg
JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIGRpcj0iTFRSIj48L3NwYW4+
SW4gb3JkZXIgdG8gdW5kZXJzdGFuZCB0aGUgc2VudGVuY2Ug4oCYYSBjb250cm9sbGVyIG1heSBh
bHNvIHByb3ZpZGUgdGhlIHByb3h5IG9yIGJyb2tlciAoYW5kIHBvc3NpYmx5IHJvdXRpbmcpIGZ1
bmN0aW9uIGluIHRoZSBkYXRhIHBsYW5l4oCZIEkgd2VudCBiYWNrIHRvIHRoZSB0ZXJtaW5vbG9n
eSBkb2N1bWVudC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE4
LjBwdCI+V2hhdCBJIGZvdW5kIGlzIHRoYXQgdGhlIGZvbGxvd2luZyB0ZXJtcyBhcmUgZGVmaW5l
ZDoNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0OjE4LjBwdCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IEJyb2tlciAtIEFuIGVudGl0eSBwcm92aWRpbmcgYW5kL29yIGNvbm5lY3Rpbmcgc2Vy
dmljZXMgb24gdGhlIGJlaGFsZiBvZjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgb3RoZXIgYXJjaGl0ZWN0dXJhbCBjb21wb25lbnRzLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgUHJveHkgLSBBbiBhcmNoaXRlY3R1cmFsIGNvbXBvbmVudCBw
cm92aWRpbmcgZnVuY3Rpb25zLCBpbmZvcm1hdGlvbiwgb3I8bzpwPjwvbzpwPjwvc3Bhbj48L3By
ZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgc2VydmljZXMgb24gYmVoYWxmIG9mIGFub3RoZXIgY29tcG9uZW50LCB3aGljaCBp
cyBub3QgZGlyZWN0bHk8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgcGFydGljaXBhdGlu
ZyBpbiB0aGUgYXJjaGl0ZWN0dXJlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxOC4wcHQiPlRo
ZXNlIGRlZmluaXRpb25zIHNlZW0gdG8gbmVlZCBtb3JlIHdvcmsuIFRoZXkgYXJlIHBhcnRpYWxs
eSByZWR1bmRhbnQg4oCTIGlzIHRoaXMgYnkgZGVzaWduPyBQcm94eSBpcyBub3Qg4oCYcGFydGlj
aXBhdGluZyBpbiB0aGUgYXJjaGl0ZWN0dXJl4oCZPyBUaGVuIGhvdyBpcyBpdCBiZXR3ZWVuIHRo
ZSAyLTMgZnVuZGFtZW50YWwgZnVuY3Rpb25zIG9mIHRoZSBjb250cm9sbGVyPw0KIFRoZXJlIG5l
ZWRzIHRvIGJlIG1vcmUgd29yayBpbiB0aGUgdGVybWlub2xvZ3kgZG9jdW1lbnQgSSBndWVzcy4g
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MTguMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBo
IiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMTt0ZXh0
LWF1dG9zcGFjZTpub25lIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6
SWdub3JlIj41LjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZx
dW90OyI+Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gZGlyPSJM
VFIiPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25z
b2xhcyI+VE9ETyDigJAgYWRkIHRleHQgYXJvdW5kIHRoZSB1c2FnZSBvZiB2YXJpb3VzIHByb3Rv
Y29scyBmb3IgZW5kcG9pbnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MTguMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTpDb25zb2xhcyI+ZGF0YSBjb2xsZWN0aW9uIChTTk1QLCBORVRDT05G
LCBldGMuPyk8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBkbyB3ZSByZWFsbHkgbmVlZCB0aGVzZSBpbiBhbiBhcmNoaXRlY3R1
cmUgZG9jdW1lbnQ/DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmtzIGFuZCBSZWdhcmRz
LDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5EYW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C994479AZFFEXMB04globa_--


From nobody Fri Feb 13 09:23:40 2015
Return-Path: <bjoernboesch@gmx.net>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABDD1A8761; Fri, 13 Feb 2015 09:23:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.622
X-Spam-Level: **
X-Spam-Status: No, score=2.622 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-0.01, URI_HEX=1.122] autolearn=no
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 5qaoksSko2VU; Fri, 13 Feb 2015 09:23:19 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DA201A0162; Fri, 13 Feb 2015 09:23:18 -0800 (PST)
Received: from [192.168.2.100] ([79.246.51.108]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M3d9B-1XW0O20QQD-00rHSb; Fri, 13 Feb 2015 18:23:15 +0100
Message-ID: <54DE32FF.5030504@gmx.net>
Date: Fri, 13 Feb 2015 18:23:11 +0100
From: "B.-C. Boesch" <bjoernboesch@gmx.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Jerome Athias <athiasjerome@gmail.com>, sacm@ietf.org, saag@ietf.org,  ietf@ietf.org, OPSAWG@ietf.org
References: <54BB6D67.6010509@gmx.net>	<23D534A9-90E7-45C0-AE78-419617965D15@comcast.net>	<54CFCC5F.6080709@gmx.net>	<CAA=AuEfYPXPV0EBRm4UxTk8NpVb5B9sOgNW+-_DVbc4e_sNrOQ@mail.gmail.com>	<54D12183.2090105@gmx.net> <CAA=AuEfB0HZkKGg0keKoNunS_N-MpQnOdG+A91kweNwHQfPhww@mail.gmail.com>
In-Reply-To: <CAA=AuEfB0HZkKGg0keKoNunS_N-MpQnOdG+A91kweNwHQfPhww@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040006060109020703050002"
X-Provags-ID: V03:K0:axO4E17ajvDU1oagUwCaFzpMyMr+mQrEWbN7PSE28lnqRF2iWPs MOeHXgchTlbKCLhK4yGQ55flks72ZZd8m6ylbmqrEPFf6U9/N3UL8r/bbogVarLoJ81Yr5t RfpaGQ4DQUovy85f3X6D62Bxs9gCvI2Z62aj+bDDqX6SQ83dTWqhw8QsxaXcpJnn4GPk9Tu o5XhXsctsgwHiDB2jMYpA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/23AToNTnTODAkcrJxWkxfgZVXKE>
Subject: Re: [sacm] [OPSAWG] Internet Draft: Standardized Parameterization of Intrusion Detection Entities
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 17:23:22 -0000

This is a multi-part message in MIME format.
--------------040006060109020703050002
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Jerome,

thanks for your feedback and support to align "contact" with "3.10. Contact Class" of RfC 5070 (IODEFv2). I had lots of thoughts about**your recommendation and currently I am not sure if this is the best choice. The IODEFv2 is focussed on exchange and handle of incident information by CSIRT humans (maybe with systems support and so it should be parsable). So more than one contact could be helpful to handle the incident. Also it must be flexible to use it for any kind of contact.

IDMEF (RfC 4765) is focused on signalling of events / incidents within an IDS or its user interface. The IDPEF as Internet Draft is intended to parametrize the Analyzer of an IDS (communication between Manager and Manager or Analyzer). The information handler use the information which is presented to him by the format.

Focused on the contact class for the field service and the technical contact there will be a single point of contact. The contact node of IDPEF provides multiple contact channels for the field service or a second level service / technical administration where other information like postal address or contact name is located in upper nodes. So This could be the input for IDMEF / IODEF and should predefine to information for this two support contacts of an entity. And there is always one group exclusive responsible for this job.

IMHO this kind of detailed structured information supports that all information are present. With a machine-machine interaction this could be checked automatically. On the other hand an Analyzer is able to combine or chain these values for IDMEF / IODEF with less efforts, but maybe in any cases not the complete information is needed.

I am aware that IDPEF and its structure (especially the contact section) could be change in the next years be new communication methods and channels but I believe that at this point it will be time to update IDPEF to a new version. Did you (or the community) have any example, what information for field services or technical administration could be necessary which is currently not addressed by IDPEF with could be valuable for incident handling?

Thanks for the feedback and the start of discussion.

Kind regards.

B.-C. Boesch


Am 03.02.2015 um 22:21 schrieb Jerome Athias:
> after partial second review, I would suggest reviewing "contact" to
> align it on "3.10. Contact Class" that you can find here
> https://tools.ietf.org/html/draft-ietf-mile-rfc5070-bis-10
>
>
>
> 2015-02-03 20:29 GMT+01:00 B.-C. Boesch <bjoernboesch@gmx.net>:
>> Hi Jerome,
>>
>> thanks for your feedback and the post to the STIX community. This is very
>> useful to me.
>>
>> Currently I am not familiar with the STIX specifications but I hope that I
>> will be become acquainted with it in the next time. At the first view it
>> seems that STIX is focused on signalizing and correlation of events like
>> IDMEF. My approach is more a parametrization of IDS entities (Analyzers). I
>> keep to make some Data model mappings with STIX. I hope that I will be able
>> to spend some time on it next weekend to get familiar with STIX.
>>
>> I am looking forward to a valuable feedback from the STIX community.
>>
>> kind regards
>>
>> Bjoern.-C. Boesch
>>
>> Am 02.02.2015 um 22:40 schrieb Jerome Athias:
>>
>>> Hi,
>>>
>>> very interesting idea and document.
>>> Congratulations, and thanks!
>>>
>>> After a first review, I think I would have quite a lot of comments.
>>> Unfortunately I would not have time for proper review before this
>>> week-end.
>>> Meantime, I would think that there is an opportunity to suggest your
>>> work as an extension for STIX, and CybOX
>>> http://stix.mitre.org/
>>> Are you familiar with these specifications?
>>> I would mainly recommend trying some mappings, etc. I'll be able to help
>>>
>>> I understand the importance for you to obtain feedbacks, so I should
>>> introduce your draft into the STIX community
>>>
>>> http://making-security-measurable.1364806.n2.nabble.com/STIX-Discussion-List-f7579090.html
>>> I hope it's ok for you, and I'm pretty sure you could obtain valuable
>>> feedback from there (even if this community is not working with the
>>> same requirements as IETF)
>>>
>>> Best regards
>>>
>>> 2015-02-02 20:13 GMT+01:00 B.-C. Boesch <bjoernboesch@gmx.net>:
>>>> Dear David,
>>>>
>>>> thanks for your hint to the SACM WG. I have also posted it within the
>>>> SACM
>>>> community for any comments, feedback, suggestions, notations, hints,
>>>> recommendations, etc. but haven´t  received any response or feedback to
>>>> the
>>>> Internet Draft so far. I hope this will change and a lively discussion is
>>>> going to come up.
>>>>
>>>> Kind regards
>>>>
>>>> B.-C. Boesch
>>>>
>>>>
>>>> Am 02.02.2015 um 18:32 schrieb David Harrington:
>>>>> I think similar work is being addressed in the sacm wg.
>>>>>
>>>>> David Harrington
>>>>> ietfdbh@comcast.net
>>>>>
>>>>>
>>>>>
>>>>> On Jan 18, 2015, at 3:23 AM, B.-C. Boesch <bjoernboesch@gmx.net> wrote:
>>>>>
>>>>>> Dear Community,
>>>>>>
>>>>>> Efficiency of Intrusion Detection Systems (IDS) depends on their
>>>>>> configuration and coverage of services. The coverage depends on used
>>>>>> IDS
>>>>>> with currently vendor-specific configurations. In case of usage of
>>>>>> multiple
>>>>>> systems the operations could become complex. Individual Communication
>>>>>> between management interface and the IDS entities results that current
>>>>>> multi-vendor IDS architectures do not interact with each other. They
>>>>>> are
>>>>>> independent coexistent.
>>>>>>
>>>>>> The Internet Draft defines data formats and exchange procedures to
>>>>>> standardize parametrization information exchange into intrusion
>>>>>> detection
>>>>>> and response systems from a Manager to an Analyzer.
>>>>>>
>>>>>> The created Intrusion Detection Parametrization Exchange Format (IDPEF)
>>>>>> is intended to be a standard data format to parametrize IDS. The
>>>>>> development
>>>>>> of this open standardized format and the Intrusion Detection Message
>>>>>> Exchange Format (IDMEF) will be enable in combination interoperability
>>>>>> among
>>>>>> commercial, open source, and research systems, allowing users to
>>>>>> mix-and-match the deployment of these systems according to their strong
>>>>>> and
>>>>>> weak points to obtain an optimal IDS implementation.
>>>>>>
>>>>>> The most obvious place to implement IDPEF is in the data channel
>>>>>> between
>>>>>> a Manager and an Analyzer of an IDS within this data channel where the
>>>>>> Manager sends the configuration parameters to the Analyzers. But there
>>>>>> are
>>>>>> other places where the IDPEF can be useful:
>>>>>>
>>>>>> - Combination of specialized IDS like application-IDS with server-IDS,
>>>>>> WLAN-IDS and network-IDS to one functional interacting meta-IDS.
>>>>>>
>>>>>> - Management of different IDS vendors with one central management
>>>>>> interface.
>>>>>>
>>>>>> - Interaction of different IDS by using IDPEF and IDMEF.
>>>>>>
>>>>>> - Parametrization backups and restore of parametrized IDS entities.
>>>>>>
>>>>>> - For a communication between a Manager and a Manager in a multi-stage
>>>>>> management architecture.
>>>>>>
>>>>>> I am happy to invite you to give me feedback, suggestions, notations,
>>>>>> hints, recommendations, etc. to improve the Internet Draft. The initial
>>>>>> version of the Internet Draft could be found at:
>>>>>>
>>>>>> http://www.ietf.org/id/draft-boesch-idxp-idpef-00.txt
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> B.-C. Boesch
>>>>>>
>>>>>> _______________________________________________
>>>>>> OPSAWG mailing list
>>>>>> OPSAWG@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/opsawg
>>>>
>>>> _______________________________________________
>>>> sacm mailing list
>>>> sacm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sacm
>>


--------------040006060109020703050002
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <pre wrap="">Hi Jerome,

thanks for your feedback and support to align "contact" with "3.10. Contact Class" of RfC 5070 (IODEFv2). I had lots of thoughts about <b class="b3"></b>your recommendation and currently I am not sure if this is the best choice. The IODEFv2 is focussed on exchange and handle of incident information by CSIRT humans (maybe with systems support and so it should be parsable). So more than one contact could be helpful to handle the incident. Also it must be flexible to use it for any kind of contact. 

IDMEF (RfC 4765) is focused on signalling of events / incidents within an IDS or its user interface. The IDPEF as Internet Draft is intended to parametrize the Analyzer of an IDS (communication between Manager and Manager or Analyzer). The information handler use the information which is presented to him by the format. 

Focused on the contact class for the field service and the technical contact there will be a single point of contact. The contact node of IDPEF provides multiple contact channels for the field service or a second level service / technical administration where other information like postal address or contact name is located in upper nodes. So This could be the input for IDMEF / IODEF and should predefine to information for this two support contacts of an entity. And there is always one group exclusive responsible for this job. 

IMHO this kind of detailed structured information supports that all information are present. With a machine-machine interaction this could be checked automatically. On the other hand an Analyzer is able to combine or chain these values for IDMEF / IODEF with less efforts, but maybe in any cases not the complete information is needed. 

I am aware that IDPEF and its structure (especially the contact section) could be change in the next years be new communication methods and channels but I believe that at this point it will be time to update IDPEF to a new version. Did you (or the community) have any example, what information for field services or technical administration could be necessary which is currently not addressed by IDPEF with could be valuable for incident handling? 

Thanks for the feedback and the start of discussion. 

Kind regards. 

B.-C. Boesch


</pre>
    <div class="moz-cite-prefix">Am 03.02.2015 um 22:21 schrieb Jerome
      Athias:<br>
    </div>
    <blockquote
cite="mid:CAA=AuEfB0HZkKGg0keKoNunS_N-MpQnOdG+A91kweNwHQfPhww@mail.gmail.com"
      type="cite">
      <pre wrap="">after partial second review, I would suggest reviewing "contact" to
align it on "3.10. Contact Class" that you can find here
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-mile-rfc5070-bis-10">https://tools.ietf.org/html/draft-ietf-mile-rfc5070-bis-10</a>



2015-02-03 20:29 GMT+01:00 B.-C. Boesch <a class="moz-txt-link-rfc2396E" href="mailto:bjoernboesch@gmx.net">&lt;bjoernboesch@gmx.net&gt;</a>:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi Jerome,

thanks for your feedback and the post to the STIX community. This is very
useful to me.

Currently I am not familiar with the STIX specifications but I hope that I
will be become acquainted with it in the next time. At the first view it
seems that STIX is focused on signalizing and correlation of events like
IDMEF. My approach is more a parametrization of IDS entities (Analyzers). I
keep to make some Data model mappings with STIX. I hope that I will be able
to spend some time on it next weekend to get familiar with STIX.

I am looking forward to a valuable feedback from the STIX community.

kind regards

Bjoern.-C. Boesch

Am 02.02.2015 um 22:40 schrieb Jerome Athias:

</pre>
        <blockquote type="cite">
          <pre wrap="">Hi,

very interesting idea and document.
Congratulations, and thanks!

After a first review, I think I would have quite a lot of comments.
Unfortunately I would not have time for proper review before this
week-end.
Meantime, I would think that there is an opportunity to suggest your
work as an extension for STIX, and CybOX
<a class="moz-txt-link-freetext" href="http://stix.mitre.org/">http://stix.mitre.org/</a>
Are you familiar with these specifications?
I would mainly recommend trying some mappings, etc. I'll be able to help

I understand the importance for you to obtain feedbacks, so I should
introduce your draft into the STIX community

<a class="moz-txt-link-freetext" href="http://making-security-measurable.1364806.n2.nabble.com/STIX-Discussion-List-f7579090.html">http://making-security-measurable.1364806.n2.nabble.com/STIX-Discussion-List-f7579090.html</a>
I hope it's ok for you, and I'm pretty sure you could obtain valuable
feedback from there (even if this community is not working with the
same requirements as IETF)

Best regards

2015-02-02 20:13 GMT+01:00 B.-C. Boesch <a class="moz-txt-link-rfc2396E" href="mailto:bjoernboesch@gmx.net">&lt;bjoernboesch@gmx.net&gt;</a>:
</pre>
          <blockquote type="cite">
            <pre wrap="">
Dear David,

thanks for your hint to the SACM WG. I have also posted it within the
SACM
community for any comments, feedback, suggestions, notations, hints,
recommendations, etc. but haven´t  received any response or feedback to
the
Internet Draft so far. I hope this will change and a lively discussion is
going to come up.

Kind regards

B.-C. Boesch


Am 02.02.2015 um 18:32 schrieb David Harrington:
</pre>
            <blockquote type="cite">
              <pre wrap="">
I think similar work is being addressed in the sacm wg.

David Harrington
<a class="moz-txt-link-abbreviated" href="mailto:ietfdbh@comcast.net">ietfdbh@comcast.net</a>



On Jan 18, 2015, at 3:23 AM, B.-C. Boesch <a class="moz-txt-link-rfc2396E" href="mailto:bjoernboesch@gmx.net">&lt;bjoernboesch@gmx.net&gt;</a> wrote:

</pre>
              <blockquote type="cite">
                <pre wrap="">Dear Community,

Efficiency of Intrusion Detection Systems (IDS) depends on their
configuration and coverage of services. The coverage depends on used
IDS
with currently vendor-specific configurations. In case of usage of
multiple
systems the operations could become complex. Individual Communication
between management interface and the IDS entities results that current
multi-vendor IDS architectures do not interact with each other. They
are
independent coexistent.

The Internet Draft defines data formats and exchange procedures to
standardize parametrization information exchange into intrusion
detection
and response systems from a Manager to an Analyzer.

The created Intrusion Detection Parametrization Exchange Format (IDPEF)
is intended to be a standard data format to parametrize IDS. The
development
of this open standardized format and the Intrusion Detection Message
Exchange Format (IDMEF) will be enable in combination interoperability
among
commercial, open source, and research systems, allowing users to
mix-and-match the deployment of these systems according to their strong
and
weak points to obtain an optimal IDS implementation.

The most obvious place to implement IDPEF is in the data channel
between
a Manager and an Analyzer of an IDS within this data channel where the
Manager sends the configuration parameters to the Analyzers. But there
are
other places where the IDPEF can be useful:

- Combination of specialized IDS like application-IDS with server-IDS,
WLAN-IDS and network-IDS to one functional interacting meta-IDS.

- Management of different IDS vendors with one central management
interface.

- Interaction of different IDS by using IDPEF and IDMEF.

- Parametrization backups and restore of parametrized IDS entities.

- For a communication between a Manager and a Manager in a multi-stage
management architecture.

I am happy to invite you to give me feedback, suggestions, notations,
hints, recommendations, etc. to improve the Internet Draft. The initial
version of the Internet Draft could be found at:

<a class="moz-txt-link-freetext" href="http://www.ietf.org/id/draft-boesch-idxp-idpef-00.txt">http://www.ietf.org/id/draft-boesch-idxp-idpef-00.txt</a>

Kind regards,

B.-C. Boesch

_______________________________________________
OPSAWG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPSAWG@ietf.org">OPSAWG@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/opsawg">https://www.ietf.org/mailman/listinfo/opsawg</a>
</pre>
              </blockquote>
            </blockquote>
            <pre wrap="">

_______________________________________________
sacm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sacm@ietf.org">sacm@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/sacm">https://www.ietf.org/mailman/listinfo/sacm</a>
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">

</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------040006060109020703050002--


From nobody Fri Feb 13 09:31:35 2015
Return-Path: <bcheikes@mitre.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3698C1A00E7 for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 09:31:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.225
X-Spam-Level: *
X-Spam-Status: No, score=1.225 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_GREY=0.424] autolearn=no
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 0pI0xiqs1yoq for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 09:31:28 -0800 (PST)
Received: from smtpvbsrv1.mitre.org (smtpvbsrv1.mitre.org [198.49.146.234]) by ietfa.amsl.com (Postfix) with ESMTP id E3EBA1A00E6 for <sacm@ietf.org>; Fri, 13 Feb 2015 09:31:27 -0800 (PST)
Received: from smtpvbsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 79AC172E160 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:31:27 -0500 (EST)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpvbsrv1.mitre.org (Postfix) with ESMTP id 4543072E164 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:31:27 -0500 (EST)
Received: from IMCMBX04.MITRE.ORG ([169.254.4.251]) by IMCCAS03.MITRE.ORG ([129.83.29.80]) with mapi id 14.03.0224.002; Fri, 13 Feb 2015 12:31:27 -0500
From: "Cheikes, Brant A." <bcheikes@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: The Open Group - Security Automation Vendor Workshop - Call for participation
Thread-Index: AdBHsdjtvMzGvPi3SSWeLq77+9skRg==
Date: Fri, 13 Feb 2015 17:31:26 +0000
Message-ID: <808A833A2D415D41996B1CF760901A0A341394FE@IMCMBX04.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.140.19.249]
Content-Type: multipart/related; boundary="_004_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/8l_Y-n9a8s86Bi5OSPZKAZ09QOs>
Subject: [sacm] The Open Group - Security Automation Vendor Workshop - Call for participation
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 17:31:32 -0000

--_004_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_
Content-Type: multipart/alternative;
	boundary="_000_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_"

--_000_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The Open Group (TOG) has formed a "Security Automation" working group to ev=
aluate what TOG might do in the area of security automation standards. A ve=
ndor workshop has been announced for 31 March, to be hosted by HP in Palo A=
lto; details are below. It would seem like a good idea to have some members=
 of the SACM community attend this workshop, to help shape the Open Group's=
 efforts and deconflict it from IETF efforts. Also note they've posted a Su=
rveyMonkey survey (link below) to collect additional inputs in advance of t=
he workshop.

/Brant

Brant A. Cheikes
The MITRE Corporation
202 Burlington Road, M/S M300
Bedford, MA 01730-1420
Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352


[cid:image002.png@01D0477D.D1E982D0]

Vendor Workshop: Security Automation

The attack/response dynamic facing IT security organizations is a significa=
nt challenge. With attacks from various threat actors escalating, there is =
pressure to respond to attacks faster, with greater effectiveness, and with=
 more automation.

The Open Group conducted a series of workshops (held in London, Mexico City=
, and Minneapolis, and virtually via WebEx) on the topic of security automa=
tion in October, November, and December, 2014. We used a business scenario =
approach to determine end user pain points, business objectives, and soluti=
on requirements. The output of these events is a Security Automation Busine=
ss Scenario, capturing input from large IT security organizations in North =
America and Europe.

To engage the security vendor community on this topic, we are bringing a wo=
rkshop to Silicon Valley (location below).  In preparation for the vendor w=
orkshop, we are asking IT security vendors to complete a short survey regar=
ding your plans for development of automated security capabilities. All ind=
ividual results will be kept confidential to Open Group staff, and anonymiz=
ed before discussion. The survey may be accessed here:

https://www.surveymonkey.com/r/LH7QMFH

Security Automation vendor workshop:

If you are an IT security vendor product manager, product architect, or dev=
elopment manager, please consider attending. There is no cost for this work=
shop, and we need your input. Participants will have an opportunity to hear=
 customer pain points, objectives, and product requirements regarding secur=
ity automation solutions. You will also have the opportunity to weigh in on=
 needed standards activity, and help shape work that The Open Group Securit=
y Forum is or should be doing to help move the industry forward.

If you have questions about the workshop, or to reserve a spot, please cont=
act Jim Hietala, VP, Security, at: j.hietala@opengroup.org<mailto:j.hietala=
@opengroup.org>, or Steve Borchert at: s.borchert@opengroup.org<mailto:s.bo=
rchert@opengroup.org>.

Agenda

Vendor Security Automation Workshop

8:00-8:30              Check in and breakfast

8:30-9:00              Introductions, agenda review, and topic overview

9:00-9:45              Overview of Security Automation End User Workshops &=
 Results


9:45-10:30           Standards landscape in security automation (survey of =
what standards exist                                       and are being wo=
rked on in other standards organizations, how they relate,                 =
                               and their current status)

10:30-10:45         Break

10:45-11:30         Vendor security automation status (based upon survey)

11:30-12:15         Discussion of work needed going forward

-          Developing the ROI/business case for vendors security automation=
 development

-          Developing the ROI/business case for customer use of automated s=
ecurity

-          Creating an overarching framework that leverages disparate lower=
 level standards

-          Other?

12:15                     Adjourn

Location

Address:
Hewlett-Packard Co.
3000 Hanover St.
Building 20
Palo Alto CA 94304

Take Interstate 101 to the Embarcadero-Oregon Expressway exit.
Be careful to stay on Oregon Expressway, which becomes Page Mill Road after=
 about two miles.
Drive three traffic lights past El Camino and turn left onto Hanover Street=
.
Turn right into the first driveway.
Follow the signs for Visitor Parking / Lobby
Executive Briefing Center
On-site Contact
Mary Ann Mezzapelle
Mobile +1-925-683-3679


Steve Borchert
Director - The Open Group
Office:       +1 512-243-7675
Mobile:      +1 512-945-3606
Skype:       steve_borchert

Join the conversation on Twitter<http://twitter.com/#!/theopengroup>, Linke=
dIn<http://www.linkedin.com/groups?mostPopular=3D&gid=3D1125667>, Facebook<=
http://www.facebook.com/theopengroup> and The Open Group Blog<http://blog.o=
pengroup.org/>





--_000_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1607418136;
	mso-list-type:hybrid;
	mso-list-template-ids:-1933417992 567542676 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Cambria",serif;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:5.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D">The Open Group (TOG) has formed a &#8220;Security Automation&#8221; w=
orking group to evaluate what TOG might do in the area of security automati=
on standards. A vendor workshop has been announced
 for 31 March, to be hosted by HP in Palo Alto; details are below. It would=
 seem like a good idea to have some members of the SACM community attend th=
is workshop, to help shape the Open Group&#8217;s efforts and deconflict it=
 from IETF efforts. Also note they&#8217;ve
 posted a SurveyMonkey survey (link below) to collect additional inputs in =
advance of the workshop.<o:p></o:p></span></a></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">/Brant<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;color:#002060">Brant=
 A. Cheikes<br>
The MITRE Corporation<br>
202 Burlington Road, M/S M300<br>
Bedford, MA 01730-1420<br>
Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352</span><span style=
=3D"color:#002060"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><img width=3D"138" height=3D"34" id=3D"Picture_x0020=
_1" src=3D"cid:image002.png@01D0477D.D1E982D0"><b><o:p></o:p></b></p>
<p class=3D"MsoNormal"><b><o:p>&nbsp;</o:p></b></p>
<p class=3D"MsoNormal"><b>Vendor Workshop:</b> <b>Security Automation<o:p><=
/o:p></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The attack/response dynamic facing IT security organ=
izations is a significant challenge. With attacks from various threat actor=
s escalating, there is pressure to respond to attacks faster, with greater =
effectiveness, and with more automation.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The Open Group conducted a series of workshops (held=
 in London, Mexico City, and Minneapolis, and virtually via WebEx) on the t=
opic of security automation in October, November, and December, 2014. We us=
ed a business scenario approach to
 determine end user pain points, business objectives, and solution requirem=
ents. The output of these events is a Security Automation Business Scenario=
, capturing input from large IT security organizations in North America and=
 Europe.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">To engage the security vendor community on this topi=
c, we are bringing a workshop to Silicon Valley (location below).&nbsp; In =
preparation for the vendor workshop, we are asking IT security vendors to c=
omplete a short survey regarding your plans
 for development of automated security capabilities. All individual results=
 will be kept confidential to Open Group staff, and anonymized before discu=
ssion. The survey may be accessed here:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://www.surveymonkey.com/r/LH7QMFH">h=
ttps://www.surveymonkey.com/r/LH7QMFH</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Security Automation vendor workshop:<o:p></o:p></p>
<p class=3D"MsoNormal"><i><o:p>&nbsp;</o:p></i></p>
<p class=3D"MsoNormal"><i>If you are an IT security vendor product manager,=
 product architect, or development manager, please consider attending. Ther=
e is no cost for this workshop, and we need your input. Participants will h=
ave an opportunity to hear customer
 pain points, objectives, and product requirements regarding security autom=
ation solutions. You will also have the opportunity to weigh in on needed s=
tandards activity, and help shape work that The Open Group Security Forum i=
s or should be doing to help move
 the industry forward.<o:p></o:p></i></p>
<p class=3D"MsoNormal"><i><o:p>&nbsp;</o:p></i></p>
<p class=3D"MsoNormal">If you have questions about the workshop, or to rese=
rve a spot, please contact Jim Hietala, VP, Security, at:
<a href=3D"mailto:j.hietala@opengroup.org">j.hietala@opengroup.org</a>, or =
Steve Borchert at:
<a href=3D"mailto:s.borchert@opengroup.org">s.borchert@opengroup.org</a>.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Agenda<o:p></o:p></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Vendor Security Automation Workshop<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">8:00-8:30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in and breakfast<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">8:30-9:00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Introductions, agenda review, and topic=
 overview<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">9:00-9:45&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Overview of Security Automation End Use=
r Workshops &amp; Results<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">9:45-10:30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; Standards landscape in security automation (survey of wh=
at standards exist &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; and are being worked on in other standards organizations, =
how they relate, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 and their current status)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">10:30-10:45&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Break<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">10:45-11:30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Vendor security automation status (based upon survey)<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">11:30-12:15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Discussion of work needed going forward<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpFirst" style=3D"margin-left:1.25in;mso-add-=
space:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Developing the ROI/business case for vendors=
 security automation development<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpMiddle" style=3D"margin-left:1.25in;mso-add=
-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Developing the ROI/business case for custome=
r use of automated security<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpMiddle" style=3D"margin-left:1.25in;mso-add=
-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Creating an overarching framework that lever=
ages disparate lower level standards<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpLast" style=3D"margin-left:1.25in;mso-add-s=
pace:auto;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Other?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">12:15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A=
djourn<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Location<o:p></o:p></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Address: </b><o:p></o:p></p>
<p class=3D"MsoNormal"><b>Hewlett-Packard Co. </b><o:p></o:p></p>
<p class=3D"MsoNormal">3000 Hanover St. <o:p></o:p></p>
<p class=3D"MsoNormal">Building 20 <o:p></o:p></p>
<p class=3D"MsoNormal">Palo Alto CA 94304<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Take Interstate 101 to the Embarcadero-Oregon Expres=
sway exit.<o:p></o:p></p>
<p class=3D"MsoNormal">Be careful to stay on Oregon Expressway, which becom=
es Page Mill Road after about two miles.<o:p></o:p></p>
<p class=3D"MsoNormal">Drive three traffic lights past El Camino and turn l=
eft onto Hanover Street.<o:p></o:p></p>
<p class=3D"MsoNormal">Turn right into the first driveway.<o:p></o:p></p>
<p class=3D"MsoNormal">Follow the signs for Visitor Parking / Lobby <o:p></=
o:p></p>
<p class=3D"MsoNormal">Executive Briefing Center<o:p></o:p></p>
<p class=3D"MsoNormal"><b>On-site Contact<o:p></o:p></b></p>
<p class=3D"MsoNormal">Mary Ann Mezzapelle<br>
Mobile &#43;1-925-683-3679 <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Steve Borchert<br>
Director - The Open Group<br>
Office: &nbsp; &nbsp; &nbsp; &#43;1 512-243-7675 &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp;<br>
Mobile: &nbsp;&nbsp;&nbsp;&nbsp; &#43;1 512-945-3606 &nbsp; &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<br>
Skype: &nbsp; &nbsp;&nbsp;&nbsp; steve_borchert &nbsp; &nbsp; &nbsp;<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;color:gray"><o:p>=
&nbsp;</o:p></span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;color:gray">Join =
the conversation on&nbsp;<a href=3D"http://twitter.com/#!/theopengroup"><sp=
an style=3D"color:blue">Twitter</span></a>,&nbsp;<a href=3D"http://www.link=
edin.com/groups?mostPopular=3D&amp;gid=3D1125667"><span style=3D"color:blue=
">LinkedIn</span></a>,&nbsp;<a href=3D"http://www.facebook.com/theopengroup=
"><span style=3D"color:blue">Facebook</span></a>&nbsp;and&nbsp;<a href=3D"h=
ttp://blog.opengroup.org/"><span style=3D"color:blue">The
 Open Group Blog</span></a></span></b><b><span style=3D"font-size:10.0pt;co=
lor:#144FAE"><o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;color:#144FAE"><o=
:p>&nbsp;</o:p></span></b></p>
<p class=3D"MsoNormal"><b><span style=3D"color:#144FAE"><o:p>&nbsp;</o:p></=
span></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_--

--_004_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_
Content-Type: image/png; name="image002.png"
Content-Description: image002.png
Content-Disposition: inline; filename="image002.png"; size=2003;
	creation-date="Fri, 13 Feb 2015 17:11:36 GMT";
	modification-date="Fri, 13 Feb 2015 17:11:36 GMT"
Content-ID: <image002.png@01D0477D.D1E982D0>
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAIoAAAAiCAYAAACAyEHnAAAAAXNSR0ICQMB9xQAAAAlwSFlzAAAO
xAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAdTSURBVHja
7ZstbFRZGIYrNmEFooKECkQFSRGIChIqEBWEIBAgCBiSqgZFSFYsrnfu3JaB9I8uXcj+dXcNEolE
IpFIJBKJZO/TzNu88/Xc6Uynne1Mr/gyM/f8n+897/dzz0w0Go2JkywLeTaPzD9rZAjfF4ts9qTP
e9zkRE7qwUp28/J6880PL5e/TWwvf0cubBYfrq7lG4Dl4mbxbmat+fbOSr5QK/EUAgWATG4VnwWO
My+Xv95ayR+2Wq0fq9jm2mr+9Ocsm6yVeQqAgqJn14odAUQM8lOWTffSthuYahkToAAGZxEEsxPr
AQQY526R37/eyp9Q58pq8epRll1Sea3QMQVKCiT4Hymlp9jl3kp2++wvxRfMT63MMQVKaTKmIkjO
vyg+9ssM+Cm0xdGtFTqGQJneLN47SIhwZEb6FSIg+sBXqZU6RkBBoQ4SBL/jsP0RJtMHZqj2VcYE
KPganh85rMlJmR+kzq2MCVDwJSKbEM0M0qcDBTNUK/YYgPIge35zIVuZj8LzxayY02++q1H5fVbP
yWPAErH9o6y4lHJgU2wy6CKIftQf5qdbXZjrTra6cC1/8XQ6/+39lXz7Fb/7SdqxjrtLz+/fWFp9
zF5UjUMd9iKW0Wa+sZHdy1q3RwYos/n2jpQ70fz3OxvIdz4FIp6z6A7z0fznG3W0KefyPz/N5K/f
Up+6KCAOdqOVP45sgpIHXUTsN6V0njHfM82/v7IelKx18uxsc+cL6z0IZCgYgKFsDo/66mC4sl/2
gzL69jlczF+/Uxly0JgnBiicjr0f5cQ5XdoUsQXP48mYLP76rLq7UUy5eWxit7wH7HHUbJIyZ4tF
NuflKIP5MWfWgqLiCQf4SBVDsBf0gcif4hn9cUD2HOtyT9gHxvSxYFhA6XuKjAqrdP4woLjC+wUK
i3cA7m1qYBOY4DhCbQfK9Wz9ydV8awNFSTmRAZDL+a9vKOPEp0CCwmEdZyvWS5tbS+sPBUgYmu+A
QgzN2MxB7WBcsc2oRGk9A4VTw8YgmJVYF6CwmWwMIIqM4n6EmYipQRfARke/R2NrvrusUyqKOcMa
KdMkpbupkACeaCakbAGDMcU2CKBSGwcJcqHx+wfK4vNTxyjQd1RGNA+k6o9iAR7xOFDkTApM8k1S
vpMDCenwf0r2ieYFxgRwzkxtFp30NgCMds4a7I0BdupUAiWeEI+UlD096nwH73m8X64m7EvwlaZB
IKjyQZh/wvmcQqE8x3ygcNYIc6aiGYESNqEd5ixGfwDnIDZh39hbwKfIEvGosgpkjEc72vtavb0/
1zP07NEs4gDv9CHaNjVOOjpdTNLr0iHAOd/846MGYSOcqqMf0csVgl6EcNj7ZZx9TnQ5L+bLZ5Vy
xTiYhahUPtl4yuSPVIbq5T5V+UIHsQlKZgzGYg/pS6DcvYpRmjnasq+wVTTx6IPnSm+wXmdQ2rNO
B6/q0T+6ppx6rBPA4+PtAYVKmlw7fzLrXrxCXlGrkM4nE1W+wHMwmCFHpEc8vAw8LrPDDbgYqkpx
kS2jeXHH1BWOQnjei+MpUKLgWL8bmwAcFBPB5fpg/swldVgpo72PqTpaEzpRexf5WbIUciHoG2AO
NTN7bqv4JGVySeko+oyXnRDAk1JO3MSUcttRzZRHQd3adWOTmB8RYKvYhJMrE1fVvwNFLoHAzxqY
c2wjpj8MUJjT0IGC81p16g8jvWR53ceo8gmk3HYOZc+nUjt3YmPirQpwqTYq0zyU+XZlAcpuawYU
SnQqwnT/MroNAryU3Q9Q3AwOFSge9QzyprgqikrlZZTLQFI+keg++hOeEEvlXNhYz1RHwO1LDVgZ
Y3oo7VGXFKo58Iw1CJQyL5q3g5/f9JkCihiFtcTwXw56CiiVUc9xil8tGDTiSbFJvGLguYwqVlB+
JHUS1dadV9oAkm5skmIu5U1wLPE36COmDxQ0eDQlwKZ8FIXoKhPQopmEeTwRGiM/xvM1uun5X4DC
f3Gk1EFvo6XYJF5aUkJMQHHFiFbZRKd/FyUVqYeZ4DRWRT3um8ST6BlhKaHK56FvAKc+1Fb+DuXO
CACONSh8Zn4e5VDf8zg6PLAM9QV8nw/lqYMz1KSNQuRB3vE44PzGftUJRzlsuJhAdI5yuzmplOHM
QedsNt+r3jArykuZKfpBMW02mTtofcyVvhiP/viEWRBlmn0cxnbwUsb6YJ9oHsXG9KlMuzvWek+F
xDzRUIHiafzD/hcnvlhMXaFUvqLKx6hlwMzsMIS/WVT9JaPfLGyVvwN7jGKavAZKB7VmM0rn9+Or
ECn1AhIPiT3sq2XEgIKPgdlB8ZgRTAfAATQwRkyYxYjpoMhJiatu73VqGQGg7CZ+njUyzzVU/U0D
dvBEncLgeDHJ6k8qrPV3NrWMKFAU4iIpH0J/PudNsIOElH3KCSZSwGlVpKPUO9FAtzettYwAUBQF
iTEARXzDrBeImKluyvawLiU1UEYcKJLdW/wli5CCxyzxR3R+H9VVhFoGl/8AKyM7Ci2KbKoAAAAA
SUVORK5CYII=

--_004_808A833A2D415D41996B1CF760901A0A341394FEIMCMBX04MITREOR_--


From nobody Fri Feb 13 12:36:19 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 688C11A19F4 for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 12:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 HncIIl4CNi2K for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 12:36:13 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2F1E1A19E9 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:36:11 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wp4so24310705obc.0 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:36:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=qoD8XEfj0es77W5e5fPg03GlNy3lDIZV8fTLbSCz6F8=; b=OZxI8+GZRA0oP7VsRdAl6avj3kLBIWVBTzSIBfLrRJ5HAFOA9oFlCu213+rTj9PY7q lf8wWozfc4245uHu3E7dfvxLmBspPmDcYljlPhKHVlPGh7/Zqn7hF1r/cgszY1x3CULI BWyPzm6XnToG0EtRXAji/V/6/uSZuG8LuVS54fUGZjiV/b3OaGG3K94mwTVbQNLiBj73 6k+49z84ETKJY2dkeGR0a9lzTgNyMw3PFXN6qr9BCUfom/O71xzRS39bYx3n7TY01tur KUNbLJ3b0DDxpfIvhwMJedLqaAy11aaZPezYRZBZmrgLUTvQ2qhgzvXg85MPKnzapMN1 ssqw==
X-Received: by 10.202.210.13 with SMTP id j13mr7278433oig.131.1423859771031; Fri, 13 Feb 2015 12:36:11 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:5c5c:ade3:24a7:95e8? ([2602:306:3406:4f00:5c5c:ade3:24a7:95e8]) by mx.google.com with ESMTPSA id nq10sm4528158obb.28.2015.02.13.12.36.09 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Feb 2015 12:36:10 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF271F1B-07E0-4D56-BD23-30045CDE19AD@gmail.com>
Date: Fri, 13 Feb 2015 14:35:42 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/RPyvjCpnJ3npeFeDP-uSdiJtBUI>
Subject: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 20:36:17 -0000

SACM Endpoint ID Design Team Notes
2015-02-13
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

Agenda:

	* Reminder:
		- WebEx Chat and SACM Jabber Room
		- Recording will be (is) enabled
	* Endpoint ID Example Continued
		- Update on updating Information Model draft
		- POSTPONED Continued Provenance Discussion
			- Virtual Interim Considerations
			- W3C investigation considerations
	* Next Steps
		- Could we use a "by week"?

Attendees:
	Clifford Kahn
	Danny Haynes
	David Waltermire
	Jim Bieda
	Ron Colvin
	Lisa Lorenzin
	Adam Montville
	Jessica Fitzgerald-McKay

Overview
=3D=3D=3D=3D=3D=3D=3D=3D
We had some technical difficulties at the outset of the meeting, but =
eventually decided to start talking about how we start updating the =
Information Model and postponing the provenance discussion until next =
week.  We ended the formal part of the meeting at about half past the =
hour and allowed the balance of the 2-hour block for Dave and Cliff to =
further discuss the structural changes of the IM draft.

To update the Information Model, we might consider:
	- Identify the information element gaps between current IM draft =
and Endpoint ID
	- We should more robustly define the entities in the =
relationship diagram
	- We have a notional model of an Endpoint Identity Assertion, =
and the IM draft should be updated with this infomration as well =
(perhaps that an endpoint attribute assertion can be an identity =
assertion)
	-=20

Additional Comments
	- It's noted that we haven't yet indicated the normative =
information in the IM that would help determine whether specific data =
models would be compliant with the IM.
	- Concise is good.  We have made conclusions that could be =
distilled.
	-=20

Way Forward
	- We're not 100% clear on how we want to organize the notion of =
Endpoint Assertion and/or Endpoint Identity Assertion (for next week)
	- Focus our efforts this go around on what a good organizational =
structure might be to convert the balance of the notes into the =
information model (this week)
	- Work on the ERD (this week)
	- Dave and Cliff will get together to determine how to split =
things out.
	- PROV will be pushed out



Amended, Ongoing Notes Pertaining to Endpoint Identification
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Scenarios:

	- Scenario A: Software on an endpoint is asserting posture =
relating to the endpoint's software inventory and configuration.

Endpoint Identity Assertion
---------------------------

	* All endpoint attributes can be used to establish identity
	* We are defining a core set of (primary) attributes that can be =
used to assert identity in a consistent fashon
		- High level of assurance, attributes can be =
authenticated
	* Other (secondary) attributes can be used to check an identity =
assertion or to further define the endpoint's identity (e.g. =
configuration, software inventory, capability)


Attribute/value pairs
---------------------

	Identity attributes (used to determine what the endpoint is; to =
be provided regardless of other posture attributes):

		* Certificates (e.g., device, user, drive, other =
hardware)
			- Device mandatory if available on device; =
favored by consumers of the assertion
			- Others if available as associated with the =
session
			- Use whole cert or some aspect (e.g., public =
key)
	=09
		* Hostname(s) - configured on the device; may be =
multiple and possibly of different kinds
			- Consider how to specify type: multiple =
attributes for each type or type qualifier
	=09
		* FQDN(s) (if available); some hosts may have multiple; =
also list DNS aliases
			- Sourced from the DNS infrastructure
			- Think abou the security considerations of =
insecure DNS deployments
	=09
		* Interface(s) (comprehensive, if possible)
			- MAC address(es)
			- IP address(es)
				- Including additional IPs assigned to =
the interface
			- Interfaces may be nested (e.g., overlay =
networks - VLANs) - NOTE: Need to verify that standardized methods are =
available to do this.
	=09
		* Other cryptographic information (e.g., IPSec Key-hash, =
HIP-HIT (RFC4423, 5201), 802.1AR)
			- NOTE: Investigate options to determine if they =
should be included as primary attributes; post a summary of how to use =
these specs
				- Cliff: HIP-HIT
					- Experimental implementation at =
the moment; not a lot of adoption
					- ID is a public key; an =
endpoint can have more than one
					- A public key might be a good =
identifier type in general for SACM; public keys tend to exist, even =
when a certificate doesn't (e.g. SSH)
				- Lisa: IPSec Security Associations (SA)
					- The SA contains the IPSEC keys =
and what algorithms are in use
					- Unable to differentiate by =
source IP address
					- Keys can rotate, and may be =
less useful as a result				=09
					- Likely not a primary identity =
attribute, but likely useful to include as an aspect of posture.
				- Henk: 802.1AR
					- Appendix B in specification =
discusses use of TPM
					- The standard's intent is to =
support unattended operation
					- A strong, globally unique =
identifier (re: iDevID - preinstalled; lDevID - enterprise defined).
					- lDevID can be generated =
specifically for SACM uses
					- Any xDevID has to ahve a =
certificate.  Could a public key from the certificate be used as the =
identifier?
					- How would a SACM component =
know of the ID?  It could be collected from both the endpoint as well as =
the device making a network access control decision.
					- The secret (e.g. certificate) =
does not need to be hardware rooted
					- How widely is this =
implemented?  About 6 years old.  Many infrastructure vendors have =
implementations, but not much use has been seen.
				- Other notes:
					- To include public keys, we =
need to discuss: what algorithm was used and the intended use of the key =
as data points?  Need to consider authentication using private keys.
	=09
		* Tool-specific identitier - provided by the software =
making the assertion
			- SHOULD be provided
			- May be session scoped if the tool is not able =
to distinguish an endpoint across sessions
			- May be omitted if the tool is unable to =
distinguish the endpoint across multiple assertions

		* Identification information from bios/firmware (e.g., =
serial numbers, asset tags, VM id) that can be queried on the device =
using softare. NOTE: Need to discuss more.
			- Assets are compositional.  Some components may =
have specific identifiers.  It would be useful to indicate which =
component has a specific identifying attribute.
			- Information should be made available by all =
manufacturers
			- If available should be provided as an =
attribute


Temporal Data
-------------

A timestamp indicating when the observation is made for a given AVP:

	* If periodic, a timestamp at present time
	* If event-based, an interval last-change to present time
	* A timestamp is included on an attribute-by-attribute basis

For information that changes frequently having the ability to poll and =
represent the poll interval is beneficial. =20

Time to Live (TTL) values provide an indication of when a given aspect =
of state will change.  Provide when naturally occurring (e.g., a tool =
will know when the DHCP lease expires). MAY be provided if applicable.

	- Do not include in current model unless we have a good use =
case.



Provenance Data
---------------

	What constitutes provenance:
		* Assessing confidence
			* Identity of the reporter itself (possibly =
endpoint identity but may be software component identity)
			* Have some idea of what that thing is
			* Have some sort of timestamp
			* Is entity aware that it=E2=80=99s =E2=80=9Cself =
reporting=E2=80=9D or =E2=80=9Cother reporting=E2=80=9D

	3 Aspects of Provenance from W3C:
	1. Chain of Custody:
		* Who said the information
		* Who handles the information
		* Endpoint is in chain
		* SACM component is in chain
		* Should include how information was transported

	2. Method (=E2=80=9CProcess=E2=80=9D in W3C terminology)
		* How did you go about harvesting

	3. Basis

	We should provide enough information for the consumer to =
determine degree of confidence.  May require guidance about what may or =
may not constitute some degree of confidence (perhaps an informational =
draft?). TODO: Need to recruit people to write this informational draft =
(certain areas in this set of notes could be used as a basis for such a =
draft).

	Reporter=E2=80=99s identity and the timestamp should be a MUST =
in all instances.  Others may lean toward SHOULD, because they may not =
always be possible. =20


	Example: IP address of an endpoint
		Goal is to associate IP address with Unique endpoint ID.
			Endpoint self-report
			Third-party assigns IP address reporting (e.g. =
IP address mgt sys)
			Third-party observer (e.g. profiler, =
infrastructure witnessing traffic)

		We want provenance for that IP address attribute to tell =
us from where the information came.  If it=E2=80=99s observed, is it =
authoritative, or is it simply passive?  We want to know the observation =
timestamp.

		CoC is who is doing the reporting.
		Process is how observation was made/communicated.
		Object-oriented Provenance is the source of the =
observation

	Note that endpoints can=E2=80=99t really =E2=80=9Clie=E2=80=9D =
about third-party observations; caution if the observer is not in a =
position to see the accurate observation (e.g. NAT=E2=80=99d =
environments).

	Other observations from discussion:
		It=E2=80=99s valuable to capture time auth/observation =
occurred
		Every AVP should have its own timestamp. =20
			Wouldn=E2=80=99t that be the timestamp of the =
attribute itself?

	TODO: Gap analysis for tying in W3C work to SACM - how do we =
hook into that work in a way that doesn=E2=80=99t bring in the whole =
elephant when we need only the trunk and the leg?  Cliff will iterate =
one more time, people will review and comment as appropriate before next =
meeting (2/13). Need to investigate the W3C concepts a bit further to =
determine how they might apply to SACM - find an example of how =
provenance would be generated/used.

	FUTURE WORK: Consider the =E2=80=9Ccomment=E2=80=9D mechanism as =
in IF-MAP - possibly something that can come later (subsequent SACM =
=E2=80=9Cphase=E2=80=9D).

	DISCUSS: Transport security considerations may apply to Chain of =
Custody and Method, is there a =E2=80=9Cplace=E2=80=9D better than =
others to include this type of information in the model?

	DISCUSS: Is there any way to generalize the notion of chain of =
custody, method, basis, to then generalize =E2=80=9Cconfidence=E2=80=9D? =
=20

	DISUCSS: Chain of custody considerations

	Notes previous to 2/6 conversation:

		* A timestamp indicating when the assertion was received =
- consumer (e.g., collector, borker, repo)

		* Think about compositional model of assertions - =
Asserting additional details related to another assertion

		The SACM component that made the assertion - the =
identity of the software providing the information
			- An assertion of the identity of the software =
used (e.g., vendor, product, version, etc.)
			- The instance of the software (e.g., the device =
the software was run on, the installation of the software) - could be an =
endpoint identity assertion as well - may be the same as the endpoint or =
different if external to the endpoint
				- Reuse the identity information from =
the authentication to establish the identity of the reporter.
			- Cryptographic ifnormation that can be used to =
authenticate the provenance assertion
			- (FOR CONTINUED DISCUSSION) Some questions on =
the call about if providing provenance information is required in all =
cases; self-reported - may/should; other-reported - must
	=09
		The endpoint attribute assertions (if any) on which the =
assertion is based
	=09
		Information about the method used to derive the =
assertion


Other Data
----------

	Endpoint uniquely identified?  True or false; very subjective; =
ask larger WG


Other Considerations
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Write security considerations speaking to=20
		- uniqueness of any identifying attribute - address =
malicious or accidental cases where uniqueness may be compromised
		- Issues relating to compromise of endpoint attributes =
(lying endpoints) - Perhaps slandering other endpoints as a result

	* When authenticating as part ofa SACM posture exchange, the =
authentication information should be incorporated into an endpoint =
identity assertion.  Should be a MUST for any endpoint that has the =
capability to authenticate.

Future Discussion Points
------------------------

	* Discuss identification information from bios/firmware (e.g. =
serial numbers, asset tags, VM id) that can be queried on the device =
using software



NEXT STEPS (Agenda Items to track)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Coordinate Information Model updates on list
	* Start preparing for IETF 92





From nobody Fri Feb 13 12:45:21 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3004D1A1A1C for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 12:45:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 lDTGM1MBWPbW for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 12:45:06 -0800 (PST)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 898EB1A1A14 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:45:06 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id nt9so23811896obb.13 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:45:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=+detN8YUfsYkiPqa82btTC/Q3Aw9reuKxcwJdAX1dsY=; b=SfvgmmpifmSansPKyssB+iSA3GBac4/FJCfa2OwVxAj1lPDj4C68i8Mz1KsjOtjfPc aJIYSXGbe3zUZWJL8vEUIZFvVWb0sW1EkdfPb3bBXXImiQlIlyKtI4Bdj8n/Un3RZEKv gum6YbyOGKQHMxqTUgEBAjdBE0RcfboJq0UyeSqH7UyRQIgZvGvGQ4I3PgER0h0D1uCc hfpK9rtcFU8CnaTXh7gPbWMeS1kxsvkv9dCIrFE+9Ai5YScfvogyeov1DJkXDm6yNh8u BiAHx3l7DBu8z92E5R2wJ3qBtbT6zzm7JDC+FzrxY1bgyJ86gseOUE6Ts9ZLoqVzFhDe y1wA==
X-Received: by 10.202.60.66 with SMTP id j63mr7158928oia.83.1423860305910; Fri, 13 Feb 2015 12:45:05 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:5c5c:ade3:24a7:95e8? ([2602:306:3406:4f00:5c5c:ade3:24a7:95e8]) by mx.google.com with ESMTPSA id h2sm3094179oep.16.2015.02.13.12.45.04 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Feb 2015 12:45:05 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_82B9763D-33DA-44C4-A251-657C5A87CA44"
Message-Id: <D7106CB8-66FF-4125-8FEA-1AF71A8EDF9D@gmail.com>
Date: Fri, 13 Feb 2015 14:44:37 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/vUhsNsggUhRhyBeTPTpcDOQunzc>
Subject: [sacm] Endpoint ID Design Team Meeting Recording Available: 2015-02-13
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 20:45:10 -0000

--Apple-Mail=_82B9763D-33DA-44C4-A251-657C5A87CA44
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The recording from today=E2=80=99s Endpoint ID design meeting is =
available here: =
https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0 =
<https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0>=20

Adam=

--Apple-Mail=_82B9763D-33DA-44C4-A251-657C5A87CA44
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">The recording from today=E2=80=99s Endpoint ID design meeting =
is available here:&nbsp;<a =
href=3D"https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu=
_a?dl=3D0" =
class=3D"">https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3=
bRu_a?dl=3D0</a>&nbsp;<div class=3D""><br class=3D""></div><div =
class=3D"">Adam</div></body></html>=

--Apple-Mail=_82B9763D-33DA-44C4-A251-657C5A87CA44--


From nobody Fri Feb 13 12:51:32 2015
Return-Path: <gunnar.engelbach@threatguard.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD45A1A1A36 for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 12:51:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 dboOkUWe6szB for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 12:51:26 -0800 (PST)
Received: from mail-qc0-f174.google.com (mail-qc0-f174.google.com [209.85.216.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E07961A19F4 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:51:25 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id c9so4325852qcz.5 for <sacm@ietf.org>; Fri, 13 Feb 2015 12:51:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wAY2ngIT3TsuzhHddmvZiqDk47DMLPinhgZ0+083UqI=; b=G2kQY8tE9GA3mNJfEYmxJfXGXxdhNA6zVKc8adDUzdohMv7XLNURCGVtJRWQpfAQh8 wuy1+idRht8aKyTFiu3LtvA0oK7XTNyzHJSTptcVUvscUerGBaFrgR8GQoQ7/nAfoeLw sIEpLrZUeFIDQl2JlRjOqIgDYCk/7AfVwbHHjBubpu+FrCMA+sNyopvXMwyWMuNu0rJE MrqNlTiEWVf3BjIIgrnx3F+aI9a/5gV99rm8a+6jpfhtw8Pomwe3pnVKJ/JI5SV4Z/Z5 XYgLkzhgS6pY2OFWLIYzDzkWz+YvblMcPIahtURe8qv0fHzHHGgo8asErqFzTcNSD0qr N6rg==
X-Gm-Message-State: ALoCoQnHt3ObuEDsauSX3GZyRNd5Of5Yd0y+CthWx7/m+ccE2NTSRtF0YVPdbrwpgVPcII/eqLy8
X-Received: by 10.140.202.141 with SMTP id x135mr5413606qha.96.1423860685152;  Fri, 13 Feb 2015 12:51:25 -0800 (PST)
Received: from [172.16.1.22] (h69-128-196-138.cntcnh.broadband.dynamic.tds.net. [69.128.196.138]) by mx.google.com with ESMTPSA id k197sm720370qhc.28.2015.02.13.12.51.24 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Feb 2015 12:51:24 -0800 (PST)
From: Gunnar Engelbach <gunnar.engelbach@threatguard.com>
X-Google-Original-From: Gunnar Engelbach <Gunnar.Engelbach@ThreatGuard.com>
Message-ID: <54DE63DE.8010904@ThreatGuard.com>
Date: Fri, 13 Feb 2015 15:51:42 -0500
Organization: ThreatGuard, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Adam W. Montville" <adam.w.montville@gmail.com>, sacm@ietf.org
References: <CF271F1B-07E0-4D56-BD23-30045CDE19AD@gmail.com>
In-Reply-To: <CF271F1B-07E0-4D56-BD23-30045CDE19AD@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/C-YYzVqBcenYYsItpGuAjI-RQII>
Subject: Re: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 20:51:29 -0000

A question regarding this effort:

So there will be a list of primary and secondary attributes.

These attributes will be represented in some notation, such as 
name/value pairs.  Some, if not all, of these attributes will also be 
used for security evaluations.

Because this is being defined prior to the adoption of a data format for 
representing the assessment guidance, isn't there a risk that the 
representation of endpoint ID attributes will not be compatible with the 
guidance, necessitating duplication of collection?


--gun

On 2/13/2015 3:35 PM, Adam W. Montville wrote:
> SACM Endpoint ID Design Team Notes
> 2015-02-13
> ==================================
>
> Agenda:
>
> 	* Reminder:
> 		- WebEx Chat and SACM Jabber Room
> 		- Recording will be (is) enabled
> 	* Endpoint ID Example Continued
> 		- Update on updating Information Model draft
> 		- POSTPONED Continued Provenance Discussion
> 			- Virtual Interim Considerations
> 			- W3C investigation considerations
> 	* Next Steps
> 		- Could we use a "by week"?
>
> Attendees:
> 	Clifford Kahn
> 	Danny Haynes
> 	David Waltermire
> 	Jim Bieda
> 	Ron Colvin
> 	Lisa Lorenzin
> 	Adam Montville
> 	Jessica Fitzgerald-McKay
>
> Overview
> ========
> We had some technical difficulties at the outset of the meeting, but eventually decided to start talking about how we start updating the Information Model and postponing the provenance discussion until next week.  We ended the formal part of the meeting at about half past the hour and allowed the balance of the 2-hour block for Dave and Cliff to further discuss the structural changes of the IM draft.
>
> To update the Information Model, we might consider:
> 	- Identify the information element gaps between current IM draft and Endpoint ID
> 	- We should more robustly define the entities in the relationship diagram
> 	- We have a notional model of an Endpoint Identity Assertion, and the IM draft should be updated with this infomration as well (perhaps that an endpoint attribute assertion can be an identity assertion)
> 	-
>
> Additional Comments
> 	- It's noted that we haven't yet indicated the normative information in the IM that would help determine whether specific data models would be compliant with the IM.
> 	- Concise is good.  We have made conclusions that could be distilled.
> 	-
>
> Way Forward
> 	- We're not 100% clear on how we want to organize the notion of Endpoint Assertion and/or Endpoint Identity Assertion (for next week)
> 	- Focus our efforts this go around on what a good organizational structure might be to convert the balance of the notes into the information model (this week)
> 	- Work on the ERD (this week)
> 	- Dave and Cliff will get together to determine how to split things out.
> 	- PROV will be pushed out
>
>
>
> Amended, Ongoing Notes Pertaining to Endpoint Identification
> =============================================================
>
> Scenarios:
>
> 	- Scenario A: Software on an endpoint is asserting posture relating to the endpoint's software inventory and configuration.
>
> Endpoint Identity Assertion
> ---------------------------
>
> 	* All endpoint attributes can be used to establish identity
> 	* We are defining a core set of (primary) attributes that can be used to assert identity in a consistent fashon
> 		- High level of assurance, attributes can be authenticated
> 	* Other (secondary) attributes can be used to check an identity assertion or to further define the endpoint's identity (e.g. configuration, software inventory, capability)
>
>
> Attribute/value pairs
> ---------------------
>
> 	Identity attributes (used to determine what the endpoint is; to be provided regardless of other posture attributes):
>
> 		* Certificates (e.g., device, user, drive, other hardware)
> 			- Device mandatory if available on device; favored by consumers of the assertion
> 			- Others if available as associated with the session
> 			- Use whole cert or some aspect (e.g., public key)
> 		
> 		* Hostname(s) - configured on the device; may be multiple and possibly of different kinds
> 			- Consider how to specify type: multiple attributes for each type or type qualifier
> 		
> 		* FQDN(s) (if available); some hosts may have multiple; also list DNS aliases
> 			- Sourced from the DNS infrastructure
> 			- Think abou the security considerations of insecure DNS deployments
> 		
> 		* Interface(s) (comprehensive, if possible)
> 			- MAC address(es)
> 			- IP address(es)
> 				- Including additional IPs assigned to the interface
> 			- Interfaces may be nested (e.g., overlay networks - VLANs) - NOTE: Need to verify that standardized methods are available to do this.
> 		
> 		* Other cryptographic information (e.g., IPSec Key-hash, HIP-HIT (RFC4423, 5201), 802.1AR)
> 			- NOTE: Investigate options to determine if they should be included as primary attributes; post a summary of how to use these specs
> 				- Cliff: HIP-HIT
> 					- Experimental implementation at the moment; not a lot of adoption
> 					- ID is a public key; an endpoint can have more than one
> 					- A public key might be a good identifier type in general for SACM; public keys tend to exist, even when a certificate doesn't (e.g. SSH)
> 				- Lisa: IPSec Security Associations (SA)
> 					- The SA contains the IPSEC keys and what algorithms are in use
> 					- Unable to differentiate by source IP address
> 					- Keys can rotate, and may be less useful as a result					
> 					- Likely not a primary identity attribute, but likely useful to include as an aspect of posture.
> 				- Henk: 802.1AR
> 					- Appendix B in specification discusses use of TPM
> 					- The standard's intent is to support unattended operation
> 					- A strong, globally unique identifier (re: iDevID - preinstalled; lDevID - enterprise defined).
> 					- lDevID can be generated specifically for SACM uses
> 					- Any xDevID has to ahve a certificate.  Could a public key from the certificate be used as the identifier?
> 					- How would a SACM component know of the ID?  It could be collected from both the endpoint as well as the device making a network access control decision.
> 					- The secret (e.g. certificate) does not need to be hardware rooted
> 					- How widely is this implemented?  About 6 years old.  Many infrastructure vendors have implementations, but not much use has been seen.
> 				- Other notes:
> 					- To include public keys, we need to discuss: what algorithm was used and the intended use of the key as data points?  Need to consider authentication using private keys.
> 		
> 		* Tool-specific identitier - provided by the software making the assertion
> 			- SHOULD be provided
> 			- May be session scoped if the tool is not able to distinguish an endpoint across sessions
> 			- May be omitted if the tool is unable to distinguish the endpoint across multiple assertions
>
> 		* Identification information from bios/firmware (e.g., serial numbers, asset tags, VM id) that can be queried on the device using softare. NOTE: Need to discuss more.
> 			- Assets are compositional.  Some components may have specific identifiers.  It would be useful to indicate which component has a specific identifying attribute.
> 			- Information should be made available by all manufacturers
> 			- If available should be provided as an attribute
>
>
> Temporal Data
> -------------
>
> A timestamp indicating when the observation is made for a given AVP:
>
> 	* If periodic, a timestamp at present time
> 	* If event-based, an interval last-change to present time
> 	* A timestamp is included on an attribute-by-attribute basis
>
> For information that changes frequently having the ability to poll and represent the poll interval is beneficial.
>
> Time to Live (TTL) values provide an indication of when a given aspect of state will change.  Provide when naturally occurring (e.g., a tool will know when the DHCP lease expires). MAY be provided if applicable.
>
> 	- Do not include in current model unless we have a good use case.
>
>
>
> Provenance Data
> ---------------
>
> 	What constitutes provenance:
> 		* Assessing confidence
> 			* Identity of the reporter itself (possibly endpoint identity but may be software component identity)
> 			* Have some idea of what that thing is
> 			* Have some sort of timestamp
> 			* Is entity aware that it’s “self reporting” or “other reporting”
>
> 	3 Aspects of Provenance from W3C:
> 	1. Chain of Custody:
> 		* Who said the information
> 		* Who handles the information
> 		* Endpoint is in chain
> 		* SACM component is in chain
> 		* Should include how information was transported
>
> 	2. Method (“Process” in W3C terminology)
> 		* How did you go about harvesting
>
> 	3. Basis
>
> 	We should provide enough information for the consumer to determine degree of confidence.  May require guidance about what may or may not constitute some degree of confidence (perhaps an informational draft?). TODO: Need to recruit people to write this informational draft (certain areas in this set of notes could be used as a basis for such a draft).
>
> 	Reporter’s identity and the timestamp should be a MUST in all instances.  Others may lean toward SHOULD, because they may not always be possible.
>
>
> 	Example: IP address of an endpoint
> 		Goal is to associate IP address with Unique endpoint ID.
> 			Endpoint self-report
> 			Third-party assigns IP address reporting (e.g. IP address mgt sys)
> 			Third-party observer (e.g. profiler, infrastructure witnessing traffic)
>
> 		We want provenance for that IP address attribute to tell us from where the information came.  If it’s observed, is it authoritative, or is it simply passive?  We want to know the observation timestamp.
>
> 		CoC is who is doing the reporting.
> 		Process is how observation was made/communicated.
> 		Object-oriented Provenance is the source of the observation
>
> 	Note that endpoints can’t really “lie” about third-party observations; caution if the observer is not in a position to see the accurate observation (e.g. NAT’d environments).
>
> 	Other observations from discussion:
> 		It’s valuable to capture time auth/observation occurred
> 		Every AVP should have its own timestamp.
> 			Wouldn’t that be the timestamp of the attribute itself?
>
> 	TODO: Gap analysis for tying in W3C work to SACM - how do we hook into that work in a way that doesn’t bring in the whole elephant when we need only the trunk and the leg?  Cliff will iterate one more time, people will review and comment as appropriate before next meeting (2/13). Need to investigate the W3C concepts a bit further to determine how they might apply to SACM - find an example of how provenance would be generated/used.
>
> 	FUTURE WORK: Consider the “comment” mechanism as in IF-MAP - possibly something that can come later (subsequent SACM “phase”).
>
> 	DISCUSS: Transport security considerations may apply to Chain of Custody and Method, is there a “place” better than others to include this type of information in the model?
>
> 	DISCUSS: Is there any way to generalize the notion of chain of custody, method, basis, to then generalize “confidence”?
>
> 	DISUCSS: Chain of custody considerations
>
> 	Notes previous to 2/6 conversation:
>
> 		* A timestamp indicating when the assertion was received - consumer (e.g., collector, borker, repo)
>
> 		* Think about compositional model of assertions - Asserting additional details related to another assertion
>
> 		The SACM component that made the assertion - the identity of the software providing the information
> 			- An assertion of the identity of the software used (e.g., vendor, product, version, etc.)
> 			- The instance of the software (e.g., the device the software was run on, the installation of the software) - could be an endpoint identity assertion as well - may be the same as the endpoint or different if external to the endpoint
> 				- Reuse the identity information from the authentication to establish the identity of the reporter.
> 			- Cryptographic ifnormation that can be used to authenticate the provenance assertion
> 			- (FOR CONTINUED DISCUSSION) Some questions on the call about if providing provenance information is required in all cases; self-reported - may/should; other-reported - must
> 		
> 		The endpoint attribute assertions (if any) on which the assertion is based
> 		
> 		Information about the method used to derive the assertion
>
>
> Other Data
> ----------
>
> 	Endpoint uniquely identified?  True or false; very subjective; ask larger WG
>
>
> Other Considerations
> ====================
>
> 	* Write security considerations speaking to
> 		- uniqueness of any identifying attribute - address malicious or accidental cases where uniqueness may be compromised
> 		- Issues relating to compromise of endpoint attributes (lying endpoints) - Perhaps slandering other endpoints as a result
>
> 	* When authenticating as part ofa SACM posture exchange, the authentication information should be incorporated into an endpoint identity assertion.  Should be a MUST for any endpoint that has the capability to authenticate.
>
> Future Discussion Points
> ------------------------
>
> 	* Discuss identification information from bios/firmware (e.g. serial numbers, asset tags, VM id) that can be queried on the device using software
>
>
>
> NEXT STEPS (Agenda Items to track)
> ==================================
>
> 	* Coordinate Information Model updates on list
> 	* Start preparing for IETF 92
>
>
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>


From nobody Fri Feb 13 14:23:41 2015
Return-Path: <david.waltermire@nist.gov>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954941A1AC6 for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 14:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 BX20sKzSVrMt for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 14:23:33 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0737.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::737]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75A2F1A1AC1 for <sacm@ietf.org>; Fri, 13 Feb 2015 14:23:33 -0800 (PST)
Received: from DM2PR09MB0224.namprd09.prod.outlook.com (25.160.92.146) by DM2PR09MB0222.namprd09.prod.outlook.com (25.160.92.144) with Microsoft SMTP Server (TLS) id 15.1.81.19; Fri, 13 Feb 2015 22:23:12 +0000
Received: from DM2PR09MB0224.namprd09.prod.outlook.com ([25.160.92.146]) by DM2PR09MB0224.namprd09.prod.outlook.com ([25.160.92.146]) with mapi id 15.01.0081.018; Fri, 13 Feb 2015 22:23:12 +0000
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "Adam W. Montville" <adam.w.montville@gmail.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13
Thread-Index: AQHQR8y+yyMxm/QQMU+VIEZAQeyq/pzvDiQAgAAX+EA=
Date: Fri, 13 Feb 2015 22:23:12 +0000
Message-ID: <DM2PR09MB0224E778A930C41E8AA8A7FCF0230@DM2PR09MB0224.namprd09.prod.outlook.com>
References: <CF271F1B-07E0-4D56-BD23-30045CDE19AD@gmail.com> <54DE63DE.8010904@ThreatGuard.com>
In-Reply-To: <54DE63DE.8010904@ThreatGuard.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.227.107]
authentication-results: threatguard.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0222;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0222;
x-forefront-prvs: 0486A0CB86
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(152014003)(13464003)(24454002)(53824002)(51704005)(40224003)(479174004)(377424004)(377454003)(5423002)(54356999)(40100003)(87936001)(106116001)(230783001)(66066001)(19580395003)(2501002)(46102003)(92566002)(2950100001)(15975445007)(50986999)(76176999)(102836002)(2900100001)(74316001)(122556002)(99286002)(76576001)(77156002)(33656002)(62966003)(107886001)(86362001)(2656002)(19580405001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0222; H:DM2PR09MB0224.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Feb 2015 22:23:12.0907 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0222
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/i4h8fLG7t5cxJjGeQ3CDBaANqMA>
Subject: Re: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 22:23:39 -0000

SSBiZWxpZXZlIHRoaXMgaXMgYSByZWFsIHJpc2sgaWYgd2UgZ2V0IHRvbyBwcmVzY3JpcHRpdmUg
aW4gdGhlIGluZm9ybWF0aW9uIG1vZGVsLiBUbyBhdm9pZCB0aGlzIHdlIGNvdWxkIGRpc2N1c3Mg
dGhlIGRhdGEgYW5kIHJlbGF0aW9uc2hpcHMgdGhhdCBuZWVkIHRvIGJlIHByb3ZpZGVkIHdpdGhv
dXQgaW1wbGljaXRseSBvciBleHBsaWNpdGx5IGRlZmluaW5nIHN5bnRheCBvciBzdHJ1Y3R1cmUu
IFRoaXMgd291bGQgYWxsb3cgZm9yIGZsZXhpYmlsaXR5IGluIGhvdyBhIGdpdmVuIGRhdGEgbW9k
ZWwgY291bGQgYmUgc3RydWN0dXJlZCwgYnV0IGluIGRvaW5nIHNvIHdvdWxkIHByb3ZpZGUgYSBs
aXN0IG9mIG11c3QtaGF2ZXMgdG8gYmUgaW5jbHVkZWQgaW4gdGhlIGRhdGEgbW9kZWwuDQoNClRo
b3VnaHRzPw0KDQpIYXZlIGEgZ3JlYXQgd2Vla2VuZCENCkRhdmUNCg0KLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCkZyb206IHNhY20gW21haWx0bzpzYWNtLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBHdW5uYXIgRW5nZWxiYWNoDQpTZW50OiBGcmlkYXksIEZlYnJ1YXJ5IDEzLCAy
MDE1IDM6NTIgUE0NClRvOiBBZGFtIFcuIE1vbnR2aWxsZTsgc2FjbUBpZXRmLm9yZw0KU3ViamVj
dDogUmU6IFtzYWNtXSBFbmRwb2ludCBJRCBEZXNpZ24gVGVhbSBNZWV0aW5nIE5vdGVzOiAyMDE1
LTAyLTEzDQoNCg0KQSBxdWVzdGlvbiByZWdhcmRpbmcgdGhpcyBlZmZvcnQ6DQoNClNvIHRoZXJl
IHdpbGwgYmUgYSBsaXN0IG9mIHByaW1hcnkgYW5kIHNlY29uZGFyeSBhdHRyaWJ1dGVzLg0KDQpU
aGVzZSBhdHRyaWJ1dGVzIHdpbGwgYmUgcmVwcmVzZW50ZWQgaW4gc29tZSBub3RhdGlvbiwgc3Vj
aCBhcyBuYW1lL3ZhbHVlIHBhaXJzLiAgU29tZSwgaWYgbm90IGFsbCwgb2YgdGhlc2UgYXR0cmli
dXRlcyB3aWxsIGFsc28gYmUgdXNlZCBmb3Igc2VjdXJpdHkgZXZhbHVhdGlvbnMuDQoNCkJlY2F1
c2UgdGhpcyBpcyBiZWluZyBkZWZpbmVkIHByaW9yIHRvIHRoZSBhZG9wdGlvbiBvZiBhIGRhdGEg
Zm9ybWF0IGZvciByZXByZXNlbnRpbmcgdGhlIGFzc2Vzc21lbnQgZ3VpZGFuY2UsIGlzbid0IHRo
ZXJlIGEgcmlzayB0aGF0IHRoZSByZXByZXNlbnRhdGlvbiBvZiBlbmRwb2ludCBJRCBhdHRyaWJ1
dGVzIHdpbGwgbm90IGJlIGNvbXBhdGlibGUgd2l0aCB0aGUgZ3VpZGFuY2UsIG5lY2Vzc2l0YXRp
bmcgZHVwbGljYXRpb24gb2YgY29sbGVjdGlvbj8NCg0KDQotLWd1bg0KDQpPbiAyLzEzLzIwMTUg
MzozNSBQTSwgQWRhbSBXLiBNb250dmlsbGUgd3JvdGU6DQo+IFNBQ00gRW5kcG9pbnQgSUQgRGVz
aWduIFRlYW0gTm90ZXMNCj4gMjAxNS0wMi0xMw0KPiA9PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09DQo+DQo+IEFnZW5kYToNCj4NCj4gCSogUmVtaW5kZXI6DQo+IAkJLSBXZWJFeCBD
aGF0IGFuZCBTQUNNIEphYmJlciBSb29tDQo+IAkJLSBSZWNvcmRpbmcgd2lsbCBiZSAoaXMpIGVu
YWJsZWQNCj4gCSogRW5kcG9pbnQgSUQgRXhhbXBsZSBDb250aW51ZWQNCj4gCQktIFVwZGF0ZSBv
biB1cGRhdGluZyBJbmZvcm1hdGlvbiBNb2RlbCBkcmFmdA0KPiAJCS0gUE9TVFBPTkVEIENvbnRp
bnVlZCBQcm92ZW5hbmNlIERpc2N1c3Npb24NCj4gCQkJLSBWaXJ0dWFsIEludGVyaW0gQ29uc2lk
ZXJhdGlvbnMNCj4gCQkJLSBXM0MgaW52ZXN0aWdhdGlvbiBjb25zaWRlcmF0aW9ucw0KPiAJKiBO
ZXh0IFN0ZXBzDQo+IAkJLSBDb3VsZCB3ZSB1c2UgYSAiYnkgd2VlayI/DQo+DQo+IEF0dGVuZGVl
czoNCj4gCUNsaWZmb3JkIEthaG4NCj4gCURhbm55IEhheW5lcw0KPiAJRGF2aWQgV2FsdGVybWly
ZQ0KPiAJSmltIEJpZWRhDQo+IAlSb24gQ29sdmluDQo+IAlMaXNhIExvcmVuemluDQo+IAlBZGFt
IE1vbnR2aWxsZQ0KPiAJSmVzc2ljYSBGaXR6Z2VyYWxkLU1jS2F5DQo+DQo+IE92ZXJ2aWV3DQo+
ID09PT09PT09DQo+IFdlIGhhZCBzb21lIHRlY2huaWNhbCBkaWZmaWN1bHRpZXMgYXQgdGhlIG91
dHNldCBvZiB0aGUgbWVldGluZywgYnV0IGV2ZW50dWFsbHkgZGVjaWRlZCB0byBzdGFydCB0YWxr
aW5nIGFib3V0IGhvdyB3ZSBzdGFydCB1cGRhdGluZyB0aGUgSW5mb3JtYXRpb24gTW9kZWwgYW5k
IHBvc3Rwb25pbmcgdGhlIHByb3ZlbmFuY2UgZGlzY3Vzc2lvbiB1bnRpbCBuZXh0IHdlZWsuICBX
ZSBlbmRlZCB0aGUgZm9ybWFsIHBhcnQgb2YgdGhlIG1lZXRpbmcgYXQgYWJvdXQgaGFsZiBwYXN0
IHRoZSBob3VyIGFuZCBhbGxvd2VkIHRoZSBiYWxhbmNlIG9mIHRoZSAyLWhvdXIgYmxvY2sgZm9y
IERhdmUgYW5kIENsaWZmIHRvIGZ1cnRoZXIgZGlzY3VzcyB0aGUgc3RydWN0dXJhbCBjaGFuZ2Vz
IG9mIHRoZSBJTSBkcmFmdC4NCj4NCj4gVG8gdXBkYXRlIHRoZSBJbmZvcm1hdGlvbiBNb2RlbCwg
d2UgbWlnaHQgY29uc2lkZXI6DQo+IAktIElkZW50aWZ5IHRoZSBpbmZvcm1hdGlvbiBlbGVtZW50
IGdhcHMgYmV0d2VlbiBjdXJyZW50IElNIGRyYWZ0IGFuZCBFbmRwb2ludCBJRA0KPiAJLSBXZSBz
aG91bGQgbW9yZSByb2J1c3RseSBkZWZpbmUgdGhlIGVudGl0aWVzIGluIHRoZSByZWxhdGlvbnNo
aXAgZGlhZ3JhbQ0KPiAJLSBXZSBoYXZlIGEgbm90aW9uYWwgbW9kZWwgb2YgYW4gRW5kcG9pbnQg
SWRlbnRpdHkgQXNzZXJ0aW9uLCBhbmQgdGhlIElNIGRyYWZ0IHNob3VsZCBiZSB1cGRhdGVkIHdp
dGggdGhpcyBpbmZvbXJhdGlvbiBhcyB3ZWxsIChwZXJoYXBzIHRoYXQgYW4gZW5kcG9pbnQgYXR0
cmlidXRlIGFzc2VydGlvbiBjYW4gYmUgYW4gaWRlbnRpdHkgYXNzZXJ0aW9uKQ0KPiAJLQ0KPg0K
PiBBZGRpdGlvbmFsIENvbW1lbnRzDQo+IAktIEl0J3Mgbm90ZWQgdGhhdCB3ZSBoYXZlbid0IHll
dCBpbmRpY2F0ZWQgdGhlIG5vcm1hdGl2ZSBpbmZvcm1hdGlvbiBpbiB0aGUgSU0gdGhhdCB3b3Vs
ZCBoZWxwIGRldGVybWluZSB3aGV0aGVyIHNwZWNpZmljIGRhdGEgbW9kZWxzIHdvdWxkIGJlIGNv
bXBsaWFudCB3aXRoIHRoZSBJTS4NCj4gCS0gQ29uY2lzZSBpcyBnb29kLiAgV2UgaGF2ZSBtYWRl
IGNvbmNsdXNpb25zIHRoYXQgY291bGQgYmUgZGlzdGlsbGVkLg0KPiAJLQ0KPg0KPiBXYXkgRm9y
d2FyZA0KPiAJLSBXZSdyZSBub3QgMTAwJSBjbGVhciBvbiBob3cgd2Ugd2FudCB0byBvcmdhbml6
ZSB0aGUgbm90aW9uIG9mIEVuZHBvaW50IEFzc2VydGlvbiBhbmQvb3IgRW5kcG9pbnQgSWRlbnRp
dHkgQXNzZXJ0aW9uIChmb3IgbmV4dCB3ZWVrKQ0KPiAJLSBGb2N1cyBvdXIgZWZmb3J0cyB0aGlz
IGdvIGFyb3VuZCBvbiB3aGF0IGEgZ29vZCBvcmdhbml6YXRpb25hbCBzdHJ1Y3R1cmUgbWlnaHQg
YmUgdG8gY29udmVydCB0aGUgYmFsYW5jZSBvZiB0aGUgbm90ZXMgaW50byB0aGUgaW5mb3JtYXRp
b24gbW9kZWwgKHRoaXMgd2VlaykNCj4gCS0gV29yayBvbiB0aGUgRVJEICh0aGlzIHdlZWspDQo+
IAktIERhdmUgYW5kIENsaWZmIHdpbGwgZ2V0IHRvZ2V0aGVyIHRvIGRldGVybWluZSBob3cgdG8g
c3BsaXQgdGhpbmdzIG91dC4NCj4gCS0gUFJPViB3aWxsIGJlIHB1c2hlZCBvdXQNCj4NCj4NCj4N
Cj4gQW1lbmRlZCwgT25nb2luZyBOb3RlcyBQZXJ0YWluaW5nIHRvIEVuZHBvaW50IElkZW50aWZp
Y2F0aW9uIA0KPiA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09DQo+DQo+IFNjZW5hcmlvczoNCj4NCj4gCS0gU2NlbmFyaW8gQTogU29m
dHdhcmUgb24gYW4gZW5kcG9pbnQgaXMgYXNzZXJ0aW5nIHBvc3R1cmUgcmVsYXRpbmcgdG8gdGhl
IGVuZHBvaW50J3Mgc29mdHdhcmUgaW52ZW50b3J5IGFuZCBjb25maWd1cmF0aW9uLg0KPg0KPiBF
bmRwb2ludCBJZGVudGl0eSBBc3NlcnRpb24NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQo+DQo+IAkqIEFsbCBlbmRwb2ludCBhdHRyaWJ1dGVzIGNhbiBiZSB1c2VkIHRvIGVzdGFibGlz
aCBpZGVudGl0eQ0KPiAJKiBXZSBhcmUgZGVmaW5pbmcgYSBjb3JlIHNldCBvZiAocHJpbWFyeSkg
YXR0cmlidXRlcyB0aGF0IGNhbiBiZSB1c2VkIHRvIGFzc2VydCBpZGVudGl0eSBpbiBhIGNvbnNp
c3RlbnQgZmFzaG9uDQo+IAkJLSBIaWdoIGxldmVsIG9mIGFzc3VyYW5jZSwgYXR0cmlidXRlcyBj
YW4gYmUgYXV0aGVudGljYXRlZA0KPiAJKiBPdGhlciAoc2Vjb25kYXJ5KSBhdHRyaWJ1dGVzIGNh
biBiZSB1c2VkIHRvIGNoZWNrIGFuIGlkZW50aXR5IA0KPiBhc3NlcnRpb24gb3IgdG8gZnVydGhl
ciBkZWZpbmUgdGhlIGVuZHBvaW50J3MgaWRlbnRpdHkgKGUuZy4gDQo+IGNvbmZpZ3VyYXRpb24s
IHNvZnR3YXJlIGludmVudG9yeSwgY2FwYWJpbGl0eSkNCj4NCj4NCj4gQXR0cmlidXRlL3ZhbHVl
IHBhaXJzDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPiAJSWRlbnRpdHkgYXR0cmlidXRl
cyAodXNlZCB0byBkZXRlcm1pbmUgd2hhdCB0aGUgZW5kcG9pbnQgaXM7IHRvIGJlIHByb3ZpZGVk
IHJlZ2FyZGxlc3Mgb2Ygb3RoZXIgcG9zdHVyZSBhdHRyaWJ1dGVzKToNCj4NCj4gCQkqIENlcnRp
ZmljYXRlcyAoZS5nLiwgZGV2aWNlLCB1c2VyLCBkcml2ZSwgb3RoZXIgaGFyZHdhcmUpDQo+IAkJ
CS0gRGV2aWNlIG1hbmRhdG9yeSBpZiBhdmFpbGFibGUgb24gZGV2aWNlOyBmYXZvcmVkIGJ5IGNv
bnN1bWVycyBvZiB0aGUgYXNzZXJ0aW9uDQo+IAkJCS0gT3RoZXJzIGlmIGF2YWlsYWJsZSBhcyBh
c3NvY2lhdGVkIHdpdGggdGhlIHNlc3Npb24NCj4gCQkJLSBVc2Ugd2hvbGUgY2VydCBvciBzb21l
IGFzcGVjdCAoZS5nLiwgcHVibGljIGtleSkNCj4gCQkNCj4gCQkqIEhvc3RuYW1lKHMpIC0gY29u
ZmlndXJlZCBvbiB0aGUgZGV2aWNlOyBtYXkgYmUgbXVsdGlwbGUgYW5kIHBvc3NpYmx5IG9mIGRp
ZmZlcmVudCBraW5kcw0KPiAJCQktIENvbnNpZGVyIGhvdyB0byBzcGVjaWZ5IHR5cGU6IG11bHRp
cGxlIGF0dHJpYnV0ZXMgZm9yIGVhY2ggdHlwZSANCj4gb3IgdHlwZSBxdWFsaWZpZXINCj4gCQkN
Cj4gCQkqIEZRRE4ocykgKGlmIGF2YWlsYWJsZSk7IHNvbWUgaG9zdHMgbWF5IGhhdmUgbXVsdGlw
bGU7IGFsc28gbGlzdCBETlMgYWxpYXNlcw0KPiAJCQktIFNvdXJjZWQgZnJvbSB0aGUgRE5TIGlu
ZnJhc3RydWN0dXJlDQo+IAkJCS0gVGhpbmsgYWJvdSB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlv
bnMgb2YgaW5zZWN1cmUgRE5TIA0KPiBkZXBsb3ltZW50cw0KPiAJCQ0KPiAJCSogSW50ZXJmYWNl
KHMpIChjb21wcmVoZW5zaXZlLCBpZiBwb3NzaWJsZSkNCj4gCQkJLSBNQUMgYWRkcmVzcyhlcykN
Cj4gCQkJLSBJUCBhZGRyZXNzKGVzKQ0KPiAJCQkJLSBJbmNsdWRpbmcgYWRkaXRpb25hbCBJUHMg
YXNzaWduZWQgdG8gdGhlIGludGVyZmFjZQ0KPiAJCQktIEludGVyZmFjZXMgbWF5IGJlIG5lc3Rl
ZCAoZS5nLiwgb3ZlcmxheSBuZXR3b3JrcyAtIFZMQU5zKSAtIE5PVEU6IE5lZWQgdG8gdmVyaWZ5
IHRoYXQgc3RhbmRhcmRpemVkIG1ldGhvZHMgYXJlIGF2YWlsYWJsZSB0byBkbyB0aGlzLg0KPiAJ
CQ0KPiAJCSogT3RoZXIgY3J5cHRvZ3JhcGhpYyBpbmZvcm1hdGlvbiAoZS5nLiwgSVBTZWMgS2V5
LWhhc2gsIEhJUC1ISVQgKFJGQzQ0MjMsIDUyMDEpLCA4MDIuMUFSKQ0KPiAJCQktIE5PVEU6IElu
dmVzdGlnYXRlIG9wdGlvbnMgdG8gZGV0ZXJtaW5lIGlmIHRoZXkgc2hvdWxkIGJlIGluY2x1ZGVk
IGFzIHByaW1hcnkgYXR0cmlidXRlczsgcG9zdCBhIHN1bW1hcnkgb2YgaG93IHRvIHVzZSB0aGVz
ZSBzcGVjcw0KPiAJCQkJLSBDbGlmZjogSElQLUhJVA0KPiAJCQkJCS0gRXhwZXJpbWVudGFsIGlt
cGxlbWVudGF0aW9uIGF0IHRoZSBtb21lbnQ7IG5vdCBhIGxvdCBvZiBhZG9wdGlvbg0KPiAJCQkJ
CS0gSUQgaXMgYSBwdWJsaWMga2V5OyBhbiBlbmRwb2ludCBjYW4gaGF2ZSBtb3JlIHRoYW4gb25l
DQo+IAkJCQkJLSBBIHB1YmxpYyBrZXkgbWlnaHQgYmUgYSBnb29kIGlkZW50aWZpZXIgdHlwZSBp
biBnZW5lcmFsIGZvciBTQUNNOyBwdWJsaWMga2V5cyB0ZW5kIHRvIGV4aXN0LCBldmVuIHdoZW4g
YSBjZXJ0aWZpY2F0ZSBkb2Vzbid0IChlLmcuIFNTSCkNCj4gCQkJCS0gTGlzYTogSVBTZWMgU2Vj
dXJpdHkgQXNzb2NpYXRpb25zIChTQSkNCj4gCQkJCQktIFRoZSBTQSBjb250YWlucyB0aGUgSVBT
RUMga2V5cyBhbmQgd2hhdCBhbGdvcml0aG1zIGFyZSBpbiB1c2UNCj4gCQkJCQktIFVuYWJsZSB0
byBkaWZmZXJlbnRpYXRlIGJ5IHNvdXJjZSBJUCBhZGRyZXNzDQo+IAkJCQkJLSBLZXlzIGNhbiBy
b3RhdGUsIGFuZCBtYXkgYmUgbGVzcyB1c2VmdWwgYXMgYSByZXN1bHQJCQkJCQ0KPiAJCQkJCS0g
TGlrZWx5IG5vdCBhIHByaW1hcnkgaWRlbnRpdHkgYXR0cmlidXRlLCBidXQgbGlrZWx5IHVzZWZ1
bCB0byBpbmNsdWRlIGFzIGFuIGFzcGVjdCBvZiBwb3N0dXJlLg0KPiAJCQkJLSBIZW5rOiA4MDIu
MUFSDQo+IAkJCQkJLSBBcHBlbmRpeCBCIGluIHNwZWNpZmljYXRpb24gZGlzY3Vzc2VzIHVzZSBv
ZiBUUE0NCj4gCQkJCQktIFRoZSBzdGFuZGFyZCdzIGludGVudCBpcyB0byBzdXBwb3J0IHVuYXR0
ZW5kZWQgb3BlcmF0aW9uDQo+IAkJCQkJLSBBIHN0cm9uZywgZ2xvYmFsbHkgdW5pcXVlIGlkZW50
aWZpZXIgKHJlOiBpRGV2SUQgLSBwcmVpbnN0YWxsZWQ7IGxEZXZJRCAtIGVudGVycHJpc2UgZGVm
aW5lZCkuDQo+IAkJCQkJLSBsRGV2SUQgY2FuIGJlIGdlbmVyYXRlZCBzcGVjaWZpY2FsbHkgZm9y
IFNBQ00gdXNlcw0KPiAJCQkJCS0gQW55IHhEZXZJRCBoYXMgdG8gYWh2ZSBhIGNlcnRpZmljYXRl
LiAgQ291bGQgYSBwdWJsaWMga2V5IGZyb20gdGhlIGNlcnRpZmljYXRlIGJlIHVzZWQgYXMgdGhl
IGlkZW50aWZpZXI/DQo+IAkJCQkJLSBIb3cgd291bGQgYSBTQUNNIGNvbXBvbmVudCBrbm93IG9m
IHRoZSBJRD8gIEl0IGNvdWxkIGJlIGNvbGxlY3RlZCBmcm9tIGJvdGggdGhlIGVuZHBvaW50IGFz
IHdlbGwgYXMgdGhlIGRldmljZSBtYWtpbmcgYSBuZXR3b3JrIGFjY2VzcyBjb250cm9sIGRlY2lz
aW9uLg0KPiAJCQkJCS0gVGhlIHNlY3JldCAoZS5nLiBjZXJ0aWZpY2F0ZSkgZG9lcyBub3QgbmVl
ZCB0byBiZSBoYXJkd2FyZSByb290ZWQNCj4gCQkJCQktIEhvdyB3aWRlbHkgaXMgdGhpcyBpbXBs
ZW1lbnRlZD8gIEFib3V0IDYgeWVhcnMgb2xkLiAgTWFueSBpbmZyYXN0cnVjdHVyZSB2ZW5kb3Jz
IGhhdmUgaW1wbGVtZW50YXRpb25zLCBidXQgbm90IG11Y2ggdXNlIGhhcyBiZWVuIHNlZW4uDQo+
IAkJCQktIE90aGVyIG5vdGVzOg0KPiAJCQkJCS0gVG8gaW5jbHVkZSBwdWJsaWMga2V5cywgd2Ug
bmVlZCB0byBkaXNjdXNzOiB3aGF0IGFsZ29yaXRobSB3YXMgdXNlZCBhbmQgdGhlIGludGVuZGVk
IHVzZSBvZiB0aGUga2V5IGFzIGRhdGEgcG9pbnRzPyAgTmVlZCB0byBjb25zaWRlciBhdXRoZW50
aWNhdGlvbiB1c2luZyBwcml2YXRlIGtleXMuDQo+IAkJDQo+IAkJKiBUb29sLXNwZWNpZmljIGlk
ZW50aXRpZXIgLSBwcm92aWRlZCBieSB0aGUgc29mdHdhcmUgbWFraW5nIHRoZSBhc3NlcnRpb24N
Cj4gCQkJLSBTSE9VTEQgYmUgcHJvdmlkZWQNCj4gCQkJLSBNYXkgYmUgc2Vzc2lvbiBzY29wZWQg
aWYgdGhlIHRvb2wgaXMgbm90IGFibGUgdG8gZGlzdGluZ3Vpc2ggYW4gZW5kcG9pbnQgYWNyb3Nz
IHNlc3Npb25zDQo+IAkJCS0gTWF5IGJlIG9taXR0ZWQgaWYgdGhlIHRvb2wgaXMgdW5hYmxlIHRv
IGRpc3Rpbmd1aXNoIHRoZSBlbmRwb2ludCANCj4gYWNyb3NzIG11bHRpcGxlIGFzc2VydGlvbnMN
Cj4NCj4gCQkqIElkZW50aWZpY2F0aW9uIGluZm9ybWF0aW9uIGZyb20gYmlvcy9maXJtd2FyZSAo
ZS5nLiwgc2VyaWFsIG51bWJlcnMsIGFzc2V0IHRhZ3MsIFZNIGlkKSB0aGF0IGNhbiBiZSBxdWVy
aWVkIG9uIHRoZSBkZXZpY2UgdXNpbmcgc29mdGFyZS4gTk9URTogTmVlZCB0byBkaXNjdXNzIG1v
cmUuDQo+IAkJCS0gQXNzZXRzIGFyZSBjb21wb3NpdGlvbmFsLiAgU29tZSBjb21wb25lbnRzIG1h
eSBoYXZlIHNwZWNpZmljIGlkZW50aWZpZXJzLiAgSXQgd291bGQgYmUgdXNlZnVsIHRvIGluZGlj
YXRlIHdoaWNoIGNvbXBvbmVudCBoYXMgYSBzcGVjaWZpYyBpZGVudGlmeWluZyBhdHRyaWJ1dGUu
DQo+IAkJCS0gSW5mb3JtYXRpb24gc2hvdWxkIGJlIG1hZGUgYXZhaWxhYmxlIGJ5IGFsbCBtYW51
ZmFjdHVyZXJzDQo+IAkJCS0gSWYgYXZhaWxhYmxlIHNob3VsZCBiZSBwcm92aWRlZCBhcyBhbiBh
dHRyaWJ1dGUNCj4NCj4NCj4gVGVtcG9yYWwgRGF0YQ0KPiAtLS0tLS0tLS0tLS0tDQo+DQo+IEEg
dGltZXN0YW1wIGluZGljYXRpbmcgd2hlbiB0aGUgb2JzZXJ2YXRpb24gaXMgbWFkZSBmb3IgYSBn
aXZlbiBBVlA6DQo+DQo+IAkqIElmIHBlcmlvZGljLCBhIHRpbWVzdGFtcCBhdCBwcmVzZW50IHRp
bWUNCj4gCSogSWYgZXZlbnQtYmFzZWQsIGFuIGludGVydmFsIGxhc3QtY2hhbmdlIHRvIHByZXNl
bnQgdGltZQ0KPiAJKiBBIHRpbWVzdGFtcCBpcyBpbmNsdWRlZCBvbiBhbiBhdHRyaWJ1dGUtYnkt
YXR0cmlidXRlIGJhc2lzDQo+DQo+IEZvciBpbmZvcm1hdGlvbiB0aGF0IGNoYW5nZXMgZnJlcXVl
bnRseSBoYXZpbmcgdGhlIGFiaWxpdHkgdG8gcG9sbCBhbmQgcmVwcmVzZW50IHRoZSBwb2xsIGlu
dGVydmFsIGlzIGJlbmVmaWNpYWwuDQo+DQo+IFRpbWUgdG8gTGl2ZSAoVFRMKSB2YWx1ZXMgcHJv
dmlkZSBhbiBpbmRpY2F0aW9uIG9mIHdoZW4gYSBnaXZlbiBhc3BlY3Qgb2Ygc3RhdGUgd2lsbCBj
aGFuZ2UuICBQcm92aWRlIHdoZW4gbmF0dXJhbGx5IG9jY3VycmluZyAoZS5nLiwgYSB0b29sIHdp
bGwga25vdyB3aGVuIHRoZSBESENQIGxlYXNlIGV4cGlyZXMpLiBNQVkgYmUgcHJvdmlkZWQgaWYg
YXBwbGljYWJsZS4NCj4NCj4gCS0gRG8gbm90IGluY2x1ZGUgaW4gY3VycmVudCBtb2RlbCB1bmxl
c3Mgd2UgaGF2ZSBhIGdvb2QgdXNlIGNhc2UuDQo+DQo+DQo+DQo+IFByb3ZlbmFuY2UgRGF0YQ0K
PiAtLS0tLS0tLS0tLS0tLS0NCj4NCj4gCVdoYXQgY29uc3RpdHV0ZXMgcHJvdmVuYW5jZToNCj4g
CQkqIEFzc2Vzc2luZyBjb25maWRlbmNlDQo+IAkJCSogSWRlbnRpdHkgb2YgdGhlIHJlcG9ydGVy
IGl0c2VsZiAocG9zc2libHkgZW5kcG9pbnQgaWRlbnRpdHkgYnV0IG1heSBiZSBzb2Z0d2FyZSBj
b21wb25lbnQgaWRlbnRpdHkpDQo+IAkJCSogSGF2ZSBzb21lIGlkZWEgb2Ygd2hhdCB0aGF0IHRo
aW5nIGlzDQo+IAkJCSogSGF2ZSBzb21lIHNvcnQgb2YgdGltZXN0YW1wDQo+IAkJCSogSXMgZW50
aXR5IGF3YXJlIHRoYXQgaXTigJlzIOKAnHNlbGYgcmVwb3J0aW5n4oCdIG9yIOKAnG90aGVyIHJl
cG9ydGluZ+KAnQ0KPg0KPiAJMyBBc3BlY3RzIG9mIFByb3ZlbmFuY2UgZnJvbSBXM0M6DQo+IAkx
LiBDaGFpbiBvZiBDdXN0b2R5Og0KPiAJCSogV2hvIHNhaWQgdGhlIGluZm9ybWF0aW9uDQo+IAkJ
KiBXaG8gaGFuZGxlcyB0aGUgaW5mb3JtYXRpb24NCj4gCQkqIEVuZHBvaW50IGlzIGluIGNoYWlu
DQo+IAkJKiBTQUNNIGNvbXBvbmVudCBpcyBpbiBjaGFpbg0KPiAJCSogU2hvdWxkIGluY2x1ZGUg
aG93IGluZm9ybWF0aW9uIHdhcyB0cmFuc3BvcnRlZA0KPg0KPiAJMi4gTWV0aG9kICjigJxQcm9j
ZXNz4oCdIGluIFczQyB0ZXJtaW5vbG9neSkNCj4gCQkqIEhvdyBkaWQgeW91IGdvIGFib3V0IGhh
cnZlc3RpbmcNCj4NCj4gCTMuIEJhc2lzDQo+DQo+IAlXZSBzaG91bGQgcHJvdmlkZSBlbm91Z2gg
aW5mb3JtYXRpb24gZm9yIHRoZSBjb25zdW1lciB0byBkZXRlcm1pbmUgZGVncmVlIG9mIGNvbmZp
ZGVuY2UuICBNYXkgcmVxdWlyZSBndWlkYW5jZSBhYm91dCB3aGF0IG1heSBvciBtYXkgbm90IGNv
bnN0aXR1dGUgc29tZSBkZWdyZWUgb2YgY29uZmlkZW5jZSAocGVyaGFwcyBhbiBpbmZvcm1hdGlv
bmFsIGRyYWZ0PykuIFRPRE86IE5lZWQgdG8gcmVjcnVpdCBwZW9wbGUgdG8gd3JpdGUgdGhpcyBp
bmZvcm1hdGlvbmFsIGRyYWZ0IChjZXJ0YWluIGFyZWFzIGluIHRoaXMgc2V0IG9mIG5vdGVzIGNv
dWxkIGJlIHVzZWQgYXMgYSBiYXNpcyBmb3Igc3VjaCBhIGRyYWZ0KS4NCj4NCj4gCVJlcG9ydGVy
4oCZcyBpZGVudGl0eSBhbmQgdGhlIHRpbWVzdGFtcCBzaG91bGQgYmUgYSBNVVNUIGluIGFsbCBp
bnN0YW5jZXMuICBPdGhlcnMgbWF5IGxlYW4gdG93YXJkIFNIT1VMRCwgYmVjYXVzZSB0aGV5IG1h
eSBub3QgYWx3YXlzIGJlIHBvc3NpYmxlLg0KPg0KPg0KPiAJRXhhbXBsZTogSVAgYWRkcmVzcyBv
ZiBhbiBlbmRwb2ludA0KPiAJCUdvYWwgaXMgdG8gYXNzb2NpYXRlIElQIGFkZHJlc3Mgd2l0aCBV
bmlxdWUgZW5kcG9pbnQgSUQuDQo+IAkJCUVuZHBvaW50IHNlbGYtcmVwb3J0DQo+IAkJCVRoaXJk
LXBhcnR5IGFzc2lnbnMgSVAgYWRkcmVzcyByZXBvcnRpbmcgKGUuZy4gSVAgYWRkcmVzcyBtZ3Qg
c3lzKQ0KPiAJCQlUaGlyZC1wYXJ0eSBvYnNlcnZlciAoZS5nLiBwcm9maWxlciwgaW5mcmFzdHJ1
Y3R1cmUgd2l0bmVzc2luZyANCj4gdHJhZmZpYykNCj4NCj4gCQlXZSB3YW50IHByb3ZlbmFuY2Ug
Zm9yIHRoYXQgSVAgYWRkcmVzcyBhdHRyaWJ1dGUgdG8gdGVsbCB1cyBmcm9tIHdoZXJlIHRoZSBp
bmZvcm1hdGlvbiBjYW1lLiAgSWYgaXTigJlzIG9ic2VydmVkLCBpcyBpdCBhdXRob3JpdGF0aXZl
LCBvciBpcyBpdCBzaW1wbHkgcGFzc2l2ZT8gIFdlIHdhbnQgdG8ga25vdyB0aGUgb2JzZXJ2YXRp
b24gdGltZXN0YW1wLg0KPg0KPiAJCUNvQyBpcyB3aG8gaXMgZG9pbmcgdGhlIHJlcG9ydGluZy4N
Cj4gCQlQcm9jZXNzIGlzIGhvdyBvYnNlcnZhdGlvbiB3YXMgbWFkZS9jb21tdW5pY2F0ZWQuDQo+
IAkJT2JqZWN0LW9yaWVudGVkIFByb3ZlbmFuY2UgaXMgdGhlIHNvdXJjZSBvZiB0aGUgb2JzZXJ2
YXRpb24NCj4NCj4gCU5vdGUgdGhhdCBlbmRwb2ludHMgY2Fu4oCZdCByZWFsbHkg4oCcbGll4oCd
IGFib3V0IHRoaXJkLXBhcnR5IG9ic2VydmF0aW9uczsgY2F1dGlvbiBpZiB0aGUgb2JzZXJ2ZXIg
aXMgbm90IGluIGEgcG9zaXRpb24gdG8gc2VlIHRoZSBhY2N1cmF0ZSBvYnNlcnZhdGlvbiAoZS5n
LiBOQVTigJlkIGVudmlyb25tZW50cykuDQo+DQo+IAlPdGhlciBvYnNlcnZhdGlvbnMgZnJvbSBk
aXNjdXNzaW9uOg0KPiAJCUl04oCZcyB2YWx1YWJsZSB0byBjYXB0dXJlIHRpbWUgYXV0aC9vYnNl
cnZhdGlvbiBvY2N1cnJlZA0KPiAJCUV2ZXJ5IEFWUCBzaG91bGQgaGF2ZSBpdHMgb3duIHRpbWVz
dGFtcC4NCj4gCQkJV291bGRu4oCZdCB0aGF0IGJlIHRoZSB0aW1lc3RhbXAgb2YgdGhlIGF0dHJp
YnV0ZSBpdHNlbGY/DQo+DQo+IAlUT0RPOiBHYXAgYW5hbHlzaXMgZm9yIHR5aW5nIGluIFczQyB3
b3JrIHRvIFNBQ00gLSBob3cgZG8gd2UgaG9vayBpbnRvIHRoYXQgd29yayBpbiBhIHdheSB0aGF0
IGRvZXNu4oCZdCBicmluZyBpbiB0aGUgd2hvbGUgZWxlcGhhbnQgd2hlbiB3ZSBuZWVkIG9ubHkg
dGhlIHRydW5rIGFuZCB0aGUgbGVnPyAgQ2xpZmYgd2lsbCBpdGVyYXRlIG9uZSBtb3JlIHRpbWUs
IHBlb3BsZSB3aWxsIHJldmlldyBhbmQgY29tbWVudCBhcyBhcHByb3ByaWF0ZSBiZWZvcmUgbmV4
dCBtZWV0aW5nICgyLzEzKS4gTmVlZCB0byBpbnZlc3RpZ2F0ZSB0aGUgVzNDIGNvbmNlcHRzIGEg
Yml0IGZ1cnRoZXIgdG8gZGV0ZXJtaW5lIGhvdyB0aGV5IG1pZ2h0IGFwcGx5IHRvIFNBQ00gLSBm
aW5kIGFuIGV4YW1wbGUgb2YgaG93IHByb3ZlbmFuY2Ugd291bGQgYmUgZ2VuZXJhdGVkL3VzZWQu
DQo+DQo+IAlGVVRVUkUgV09SSzogQ29uc2lkZXIgdGhlIOKAnGNvbW1lbnTigJ0gbWVjaGFuaXNt
IGFzIGluIElGLU1BUCAtIHBvc3NpYmx5IHNvbWV0aGluZyB0aGF0IGNhbiBjb21lIGxhdGVyIChz
dWJzZXF1ZW50IFNBQ00g4oCccGhhc2XigJ0pLg0KPg0KPiAJRElTQ1VTUzogVHJhbnNwb3J0IHNl
Y3VyaXR5IGNvbnNpZGVyYXRpb25zIG1heSBhcHBseSB0byBDaGFpbiBvZiBDdXN0b2R5IGFuZCBN
ZXRob2QsIGlzIHRoZXJlIGEg4oCccGxhY2XigJ0gYmV0dGVyIHRoYW4gb3RoZXJzIHRvIGluY2x1
ZGUgdGhpcyB0eXBlIG9mIGluZm9ybWF0aW9uIGluIHRoZSBtb2RlbD8NCj4NCj4gCURJU0NVU1M6
IElzIHRoZXJlIGFueSB3YXkgdG8gZ2VuZXJhbGl6ZSB0aGUgbm90aW9uIG9mIGNoYWluIG9mIGN1
c3RvZHksIG1ldGhvZCwgYmFzaXMsIHRvIHRoZW4gZ2VuZXJhbGl6ZSDigJxjb25maWRlbmNl4oCd
Pw0KPg0KPiAJRElTVUNTUzogQ2hhaW4gb2YgY3VzdG9keSBjb25zaWRlcmF0aW9ucw0KPg0KPiAJ
Tm90ZXMgcHJldmlvdXMgdG8gMi82IGNvbnZlcnNhdGlvbjoNCj4NCj4gCQkqIEEgdGltZXN0YW1w
IGluZGljYXRpbmcgd2hlbiB0aGUgYXNzZXJ0aW9uIHdhcyByZWNlaXZlZCAtIGNvbnN1bWVyIA0K
PiAoZS5nLiwgY29sbGVjdG9yLCBib3JrZXIsIHJlcG8pDQo+DQo+IAkJKiBUaGluayBhYm91dCBj
b21wb3NpdGlvbmFsIG1vZGVsIG9mIGFzc2VydGlvbnMgLSBBc3NlcnRpbmcgDQo+IGFkZGl0aW9u
YWwgZGV0YWlscyByZWxhdGVkIHRvIGFub3RoZXIgYXNzZXJ0aW9uDQo+DQo+IAkJVGhlIFNBQ00g
Y29tcG9uZW50IHRoYXQgbWFkZSB0aGUgYXNzZXJ0aW9uIC0gdGhlIGlkZW50aXR5IG9mIHRoZSBz
b2Z0d2FyZSBwcm92aWRpbmcgdGhlIGluZm9ybWF0aW9uDQo+IAkJCS0gQW4gYXNzZXJ0aW9uIG9m
IHRoZSBpZGVudGl0eSBvZiB0aGUgc29mdHdhcmUgdXNlZCAoZS5nLiwgdmVuZG9yLCBwcm9kdWN0
LCB2ZXJzaW9uLCBldGMuKQ0KPiAJCQktIFRoZSBpbnN0YW5jZSBvZiB0aGUgc29mdHdhcmUgKGUu
Zy4sIHRoZSBkZXZpY2UgdGhlIHNvZnR3YXJlIHdhcyBydW4gb24sIHRoZSBpbnN0YWxsYXRpb24g
b2YgdGhlIHNvZnR3YXJlKSAtIGNvdWxkIGJlIGFuIGVuZHBvaW50IGlkZW50aXR5IGFzc2VydGlv
biBhcyB3ZWxsIC0gbWF5IGJlIHRoZSBzYW1lIGFzIHRoZSBlbmRwb2ludCBvciBkaWZmZXJlbnQg
aWYgZXh0ZXJuYWwgdG8gdGhlIGVuZHBvaW50DQo+IAkJCQktIFJldXNlIHRoZSBpZGVudGl0eSBp
bmZvcm1hdGlvbiBmcm9tIHRoZSBhdXRoZW50aWNhdGlvbiB0byBlc3RhYmxpc2ggdGhlIGlkZW50
aXR5IG9mIHRoZSByZXBvcnRlci4NCj4gCQkJLSBDcnlwdG9ncmFwaGljIGlmbm9ybWF0aW9uIHRo
YXQgY2FuIGJlIHVzZWQgdG8gYXV0aGVudGljYXRlIHRoZSBwcm92ZW5hbmNlIGFzc2VydGlvbg0K
PiAJCQktIChGT1IgQ09OVElOVUVEIERJU0NVU1NJT04pIFNvbWUgcXVlc3Rpb25zIG9uIHRoZSBj
YWxsIGFib3V0IGlmIA0KPiBwcm92aWRpbmcgcHJvdmVuYW5jZSBpbmZvcm1hdGlvbiBpcyByZXF1
aXJlZCBpbiBhbGwgY2FzZXM7IA0KPiBzZWxmLXJlcG9ydGVkIC0gbWF5L3Nob3VsZDsgb3RoZXIt
cmVwb3J0ZWQgLSBtdXN0DQo+IAkJDQo+IAkJVGhlIGVuZHBvaW50IGF0dHJpYnV0ZSBhc3NlcnRp
b25zIChpZiBhbnkpIG9uIHdoaWNoIHRoZSBhc3NlcnRpb24gaXMgDQo+IGJhc2VkDQo+IAkJDQo+
IAkJSW5mb3JtYXRpb24gYWJvdXQgdGhlIG1ldGhvZCB1c2VkIHRvIGRlcml2ZSB0aGUgYXNzZXJ0
aW9uDQo+DQo+DQo+IE90aGVyIERhdGENCj4gLS0tLS0tLS0tLQ0KPg0KPiAJRW5kcG9pbnQgdW5p
cXVlbHkgaWRlbnRpZmllZD8gIFRydWUgb3IgZmFsc2U7IHZlcnkgc3ViamVjdGl2ZTsgYXNrIA0K
PiBsYXJnZXIgV0cNCj4NCj4NCj4gT3RoZXIgQ29uc2lkZXJhdGlvbnMNCj4gPT09PT09PT09PT09
PT09PT09PT0NCj4NCj4gCSogV3JpdGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc3BlYWtpbmcg
dG8NCj4gCQktIHVuaXF1ZW5lc3Mgb2YgYW55IGlkZW50aWZ5aW5nIGF0dHJpYnV0ZSAtIGFkZHJl
c3MgbWFsaWNpb3VzIG9yIGFjY2lkZW50YWwgY2FzZXMgd2hlcmUgdW5pcXVlbmVzcyBtYXkgYmUg
Y29tcHJvbWlzZWQNCj4gCQktIElzc3VlcyByZWxhdGluZyB0byBjb21wcm9taXNlIG9mIGVuZHBv
aW50IGF0dHJpYnV0ZXMgKGx5aW5nIA0KPiBlbmRwb2ludHMpIC0gUGVyaGFwcyBzbGFuZGVyaW5n
IG90aGVyIGVuZHBvaW50cyBhcyBhIHJlc3VsdA0KPg0KPiAJKiBXaGVuIGF1dGhlbnRpY2F0aW5n
IGFzIHBhcnQgb2ZhIFNBQ00gcG9zdHVyZSBleGNoYW5nZSwgdGhlIGF1dGhlbnRpY2F0aW9uIGlu
Zm9ybWF0aW9uIHNob3VsZCBiZSBpbmNvcnBvcmF0ZWQgaW50byBhbiBlbmRwb2ludCBpZGVudGl0
eSBhc3NlcnRpb24uICBTaG91bGQgYmUgYSBNVVNUIGZvciBhbnkgZW5kcG9pbnQgdGhhdCBoYXMg
dGhlIGNhcGFiaWxpdHkgdG8gYXV0aGVudGljYXRlLg0KPg0KPiBGdXR1cmUgRGlzY3Vzc2lvbiBQ
b2ludHMNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+DQo+IAkqIERpc2N1c3MgaWRlbnRp
ZmljYXRpb24gaW5mb3JtYXRpb24gZnJvbSBiaW9zL2Zpcm13YXJlIChlLmcuIHNlcmlhbCANCj4g
bnVtYmVycywgYXNzZXQgdGFncywgVk0gaWQpIHRoYXQgY2FuIGJlIHF1ZXJpZWQgb24gdGhlIGRl
dmljZSB1c2luZyANCj4gc29mdHdhcmUNCj4NCj4NCj4NCj4gTkVYVCBTVEVQUyAoQWdlbmRhIEl0
ZW1zIHRvIHRyYWNrKQ0KPiA9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQo+DQo+
IAkqIENvb3JkaW5hdGUgSW5mb3JtYXRpb24gTW9kZWwgdXBkYXRlcyBvbiBsaXN0DQo+IAkqIFN0
YXJ0IHByZXBhcmluZyBmb3IgSUVURiA5Mg0KPg0KPg0KPg0KPg0KPiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBzYWNtIG1haWxpbmcgbGlzdA0KPiBz
YWNtQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2Fj
bQ0KPg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
c2FjbSBtYWlsaW5nIGxpc3QNCnNhY21AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vc2FjbQ0K


From nobody Fri Feb 13 23:20:26 2015
Return-Path: <athiasjerome@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0251A0062 for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 23:20:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 BBnQuzJ_LRgQ for <sacm@ietfa.amsl.com>; Fri, 13 Feb 2015 23:20:18 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9431B1A1AA7 for <sacm@ietf.org>; Fri, 13 Feb 2015 23:20:17 -0800 (PST)
Received: by labge10 with SMTP id ge10so20203014lab.12 for <sacm@ietf.org>; Fri, 13 Feb 2015 23:20:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3NJDik8/j7OC4sfjUjIkAbp5iT156h1+/JsOuM6PIbY=; b=xJMgQnWSZ3nY7ujdk9JxG5lhdG6RGxlFDVFGmZyIDcFIUOE9sCcFLyJSqBIbb5Iwix tSBJFpxlh+GqXCw5M+AN8IENCpSL00/y4O6aQsoHAEvFUnMz0y9HH/YNHcKFYMqAJdtX qzjRr6AODEHyqvgn07KQf0G2/IH5+MCVxTZrqDEa9Xm8k8OWJIwNg8v5k5F+ZYvQXdue SxnzU6lZWwRq2JnM9d0aX8sqJ3LdBZyD4N9LDp2kF8YGmWcWrQAAFtBzWuEf5fWboyhu g9iJYdFGoSEkp1RfGd+PiBE2WwA5kxNMVMQJLEFaPQGVNuTKTcFzal4Cj+sbe0w7ou34 4/9w==
MIME-Version: 1.0
X-Received: by 10.112.129.195 with SMTP id ny3mr11878970lbb.10.1423898415951;  Fri, 13 Feb 2015 23:20:15 -0800 (PST)
Received: by 10.25.209.5 with HTTP; Fri, 13 Feb 2015 23:20:15 -0800 (PST)
In-Reply-To: <DM2PR09MB0224E778A930C41E8AA8A7FCF0230@DM2PR09MB0224.namprd09.prod.outlook.com>
References: <CF271F1B-07E0-4D56-BD23-30045CDE19AD@gmail.com> <54DE63DE.8010904@ThreatGuard.com> <DM2PR09MB0224E778A930C41E8AA8A7FCF0230@DM2PR09MB0224.namprd09.prod.outlook.com>
Date: Sat, 14 Feb 2015 08:20:15 +0100
Message-ID: <CAA=AuEfchxX4WLuUKPdYhKqqxyZomqiepmoLYJvMy+-6qtSbtg@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "Waltermire, David A." <david.waltermire@nist.gov>
Content-Type: multipart/alternative; boundary=047d7b3441c64774a9050f072f86
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/2s9N46CjSr-uAKDc3GsTUZfMzgk>
Cc: Gunnar Engelbach <gunnar.engelbach@threatguard.com>, "Adam W. Montville" <adam.w.montville@gmail.com>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Feb 2015 07:20:24 -0000

--047d7b3441c64774a9050f072f86
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I concur
That makes sense for me to work first on data/relationships

On Friday, February 13, 2015, Waltermire, David A. <
david.waltermire@nist.gov> wrote:

> I believe this is a real risk if we get too prescriptive in the
> information model. To avoid this we could discuss the data and
> relationships that need to be provided without implicitly or explicitly
> defining syntax or structure. This would allow for flexibility in how a
> given data model could be structured, but in doing so would provide a lis=
t
> of must-haves to be included in the data model.
>
> Thoughts?
>
> Have a great weekend!
> Dave
>
> -----Original Message-----
> From: sacm [mailto:sacm-bounces@ietf.org <javascript:;>] On Behalf Of
> Gunnar Engelbach
> Sent: Friday, February 13, 2015 3:52 PM
> To: Adam W. Montville; sacm@ietf.org <javascript:;>
> Subject: Re: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13
>
>
> A question regarding this effort:
>
> So there will be a list of primary and secondary attributes.
>
> These attributes will be represented in some notation, such as name/value
> pairs.  Some, if not all, of these attributes will also be used for
> security evaluations.
>
> Because this is being defined prior to the adoption of a data format for
> representing the assessment guidance, isn't there a risk that the
> representation of endpoint ID attributes will not be compatible with the
> guidance, necessitating duplication of collection?
>
>
> --gun
>
> On 2/13/2015 3:35 PM, Adam W. Montville wrote:
> > SACM Endpoint ID Design Team Notes
> > 2015-02-13
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > Agenda:
> >
> >       * Reminder:
> >               - WebEx Chat and SACM Jabber Room
> >               - Recording will be (is) enabled
> >       * Endpoint ID Example Continued
> >               - Update on updating Information Model draft
> >               - POSTPONED Continued Provenance Discussion
> >                       - Virtual Interim Considerations
> >                       - W3C investigation considerations
> >       * Next Steps
> >               - Could we use a "by week"?
> >
> > Attendees:
> >       Clifford Kahn
> >       Danny Haynes
> >       David Waltermire
> >       Jim Bieda
> >       Ron Colvin
> >       Lisa Lorenzin
> >       Adam Montville
> >       Jessica Fitzgerald-McKay
> >
> > Overview
> > =3D=3D=3D=3D=3D=3D=3D=3D
> > We had some technical difficulties at the outset of the meeting, but
> eventually decided to start talking about how we start updating the
> Information Model and postponing the provenance discussion until next
> week.  We ended the formal part of the meeting at about half past the hou=
r
> and allowed the balance of the 2-hour block for Dave and Cliff to further
> discuss the structural changes of the IM draft.
> >
> > To update the Information Model, we might consider:
> >       - Identify the information element gaps between current IM draft
> and Endpoint ID
> >       - We should more robustly define the entities in the relationship
> diagram
> >       - We have a notional model of an Endpoint Identity Assertion, and
> the IM draft should be updated with this infomration as well (perhaps tha=
t
> an endpoint attribute assertion can be an identity assertion)
> >       -
> >
> > Additional Comments
> >       - It's noted that we haven't yet indicated the normative
> information in the IM that would help determine whether specific data
> models would be compliant with the IM.
> >       - Concise is good.  We have made conclusions that could be
> distilled.
> >       -
> >
> > Way Forward
> >       - We're not 100% clear on how we want to organize the notion of
> Endpoint Assertion and/or Endpoint Identity Assertion (for next week)
> >       - Focus our efforts this go around on what a good organizational
> structure might be to convert the balance of the notes into the informati=
on
> model (this week)
> >       - Work on the ERD (this week)
> >       - Dave and Cliff will get together to determine how to split
> things out.
> >       - PROV will be pushed out
> >
> >
> >
> > Amended, Ongoing Notes Pertaining to Endpoint Identification
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > Scenarios:
> >
> >       - Scenario A: Software on an endpoint is asserting posture
> relating to the endpoint's software inventory and configuration.
> >
> > Endpoint Identity Assertion
> > ---------------------------
> >
> >       * All endpoint attributes can be used to establish identity
> >       * We are defining a core set of (primary) attributes that can be
> used to assert identity in a consistent fashon
> >               - High level of assurance, attributes can be authenticate=
d
> >       * Other (secondary) attributes can be used to check an identity
> > assertion or to further define the endpoint's identity (e.g.
> > configuration, software inventory, capability)
> >
> >
> > Attribute/value pairs
> > ---------------------
> >
> >       Identity attributes (used to determine what the endpoint is; to b=
e
> provided regardless of other posture attributes):
> >
> >               * Certificates (e.g., device, user, drive, other hardware=
)
> >                       - Device mandatory if available on device; favore=
d
> by consumers of the assertion
> >                       - Others if available as associated with the
> session
> >                       - Use whole cert or some aspect (e.g., public key=
)
> >
> >               * Hostname(s) - configured on the device; may be multiple
> and possibly of different kinds
> >                       - Consider how to specify type: multiple
> attributes for each type
> > or type qualifier
> >
> >               * FQDN(s) (if available); some hosts may have multiple;
> also list DNS aliases
> >                       - Sourced from the DNS infrastructure
> >                       - Think abou the security considerations of
> insecure DNS
> > deployments
> >
> >               * Interface(s) (comprehensive, if possible)
> >                       - MAC address(es)
> >                       - IP address(es)
> >                               - Including additional IPs assigned to th=
e
> interface
> >                       - Interfaces may be nested (e.g., overlay network=
s
> - VLANs) - NOTE: Need to verify that standardized methods are available t=
o
> do this.
> >
> >               * Other cryptographic information (e.g., IPSec Key-hash,
> HIP-HIT (RFC4423, 5201), 802.1AR)
> >                       - NOTE: Investigate options to determine if they
> should be included as primary attributes; post a summary of how to use
> these specs
> >                               - Cliff: HIP-HIT
> >                                       - Experimental implementation at
> the moment; not a lot of adoption
> >                                       - ID is a public key; an endpoint
> can have more than one
> >                                       - A public key might be a good
> identifier type in general for SACM; public keys tend to exist, even when=
 a
> certificate doesn't (e.g. SSH)
> >                               - Lisa: IPSec Security Associations (SA)
> >                                       - The SA contains the IPSEC keys
> and what algorithms are in use
> >                                       - Unable to differentiate by
> source IP address
> >                                       - Keys can rotate, and may be les=
s
> useful as a result
> >                                       - Likely not a primary identity
> attribute, but likely useful to include as an aspect of posture.
> >                               - Henk: 802.1AR
> >                                       - Appendix B in specification
> discusses use of TPM
> >                                       - The standard's intent is to
> support unattended operation
> >                                       - A strong, globally unique
> identifier (re: iDevID - preinstalled; lDevID - enterprise defined).
> >                                       - lDevID can be generated
> specifically for SACM uses
> >                                       - Any xDevID has to ahve a
> certificate.  Could a public key from the certificate be used as the
> identifier?
> >                                       - How would a SACM component know
> of the ID?  It could be collected from both the endpoint as well as the
> device making a network access control decision.
> >                                       - The secret (e.g. certificate)
> does not need to be hardware rooted
> >                                       - How widely is this implemented?
> About 6 years old.  Many infrastructure vendors have implementations, but
> not much use has been seen.
> >                               - Other notes:
> >                                       - To include public keys, we need
> to discuss: what algorithm was used and the intended use of the key as da=
ta
> points?  Need to consider authentication using private keys.
> >
> >               * Tool-specific identitier - provided by the software
> making the assertion
> >                       - SHOULD be provided
> >                       - May be session scoped if the tool is not able t=
o
> distinguish an endpoint across sessions
> >                       - May be omitted if the tool is unable to
> distinguish the endpoint
> > across multiple assertions
> >
> >               * Identification information from bios/firmware (e.g.,
> serial numbers, asset tags, VM id) that can be queried on the device usin=
g
> softare. NOTE: Need to discuss more.
> >                       - Assets are compositional.  Some components may
> have specific identifiers.  It would be useful to indicate which componen=
t
> has a specific identifying attribute.
> >                       - Information should be made available by all
> manufacturers
> >                       - If available should be provided as an attribute
> >
> >
> > Temporal Data
> > -------------
> >
> > A timestamp indicating when the observation is made for a given AVP:
> >
> >       * If periodic, a timestamp at present time
> >       * If event-based, an interval last-change to present time
> >       * A timestamp is included on an attribute-by-attribute basis
> >
> > For information that changes frequently having the ability to poll and
> represent the poll interval is beneficial.
> >
> > Time to Live (TTL) values provide an indication of when a given aspect
> of state will change.  Provide when naturally occurring (e.g., a tool wil=
l
> know when the DHCP lease expires). MAY be provided if applicable.
> >
> >       - Do not include in current model unless we have a good use case.
> >
> >
> >
> > Provenance Data
> > ---------------
> >
> >       What constitutes provenance:
> >               * Assessing confidence
> >                       * Identity of the reporter itself (possibly
> endpoint identity but may be software component identity)
> >                       * Have some idea of what that thing is
> >                       * Have some sort of timestamp
> >                       * Is entity aware that it=E2=80=99s =E2=80=9Cself=
 reporting=E2=80=9D or
> =E2=80=9Cother reporting=E2=80=9D
> >
> >       3 Aspects of Provenance from W3C:
> >       1. Chain of Custody:
> >               * Who said the information
> >               * Who handles the information
> >               * Endpoint is in chain
> >               * SACM component is in chain
> >               * Should include how information was transported
> >
> >       2. Method (=E2=80=9CProcess=E2=80=9D in W3C terminology)
> >               * How did you go about harvesting
> >
> >       3. Basis
> >
> >       We should provide enough information for the consumer to determin=
e
> degree of confidence.  May require guidance about what may or may not
> constitute some degree of confidence (perhaps an informational draft?).
> TODO: Need to recruit people to write this informational draft (certain
> areas in this set of notes could be used as a basis for such a draft).
> >
> >       Reporter=E2=80=99s identity and the timestamp should be a MUST in=
 all
> instances.  Others may lean toward SHOULD, because they may not always be
> possible.
> >
> >
> >       Example: IP address of an endpoint
> >               Goal is to associate IP address with Unique endpoint ID.
> >                       Endpoint self-report
> >                       Third-party assigns IP address reporting (e.g. IP
> address mgt sys)
> >                       Third-party observer (e.g. profiler,
> infrastructure witnessing
> > traffic)
> >
> >               We want provenance for that IP address attribute to tell
> us from where the information came.  If it=E2=80=99s observed, is it auth=
oritative,
> or is it simply passive?  We want to know the observation timestamp.
> >
> >               CoC is who is doing the reporting.
> >               Process is how observation was made/communicated.
> >               Object-oriented Provenance is the source of the observati=
on
> >
> >       Note that endpoints can=E2=80=99t really =E2=80=9Clie=E2=80=9D ab=
out third-party
> observations; caution if the observer is not in a position to see the
> accurate observation (e.g. NAT=E2=80=99d environments).
> >
> >       Other observations from discussion:
> >               It=E2=80=99s valuable to capture time auth/observation oc=
curred
> >               Every AVP should have its own timestamp.
> >                       Wouldn=E2=80=99t that be the timestamp of the att=
ribute
> itself?
> >
> >       TODO: Gap analysis for tying in W3C work to SACM - how do we hook
> into that work in a way that doesn=E2=80=99t bring in the whole elephant =
when we
> need only the trunk and the leg?  Cliff will iterate one more time, peopl=
e
> will review and comment as appropriate before next meeting (2/13). Need t=
o
> investigate the W3C concepts a bit further to determine how they might
> apply to SACM - find an example of how provenance would be generated/used=
.
> >
> >       FUTURE WORK: Consider the =E2=80=9Ccomment=E2=80=9D mechanism as =
in IF-MAP -
> possibly something that can come later (subsequent SACM =E2=80=9Cphase=E2=
=80=9D).
> >
> >       DISCUSS: Transport security considerations may apply to Chain of
> Custody and Method, is there a =E2=80=9Cplace=E2=80=9D better than others=
 to include this
> type of information in the model?
> >
> >       DISCUSS: Is there any way to generalize the notion of chain of
> custody, method, basis, to then generalize =E2=80=9Cconfidence=E2=80=9D?
> >
> >       DISUCSS: Chain of custody considerations
> >
> >       Notes previous to 2/6 conversation:
> >
> >               * A timestamp indicating when the assertion was received =
-
> consumer
> > (e.g., collector, borker, repo)
> >
> >               * Think about compositional model of assertions - Asserti=
ng
> > additional details related to another assertion
> >
> >               The SACM component that made the assertion - the identity
> of the software providing the information
> >                       - An assertion of the identity of the software
> used (e.g., vendor, product, version, etc.)
> >                       - The instance of the software (e.g., the device
> the software was run on, the installation of the software) - could be an
> endpoint identity assertion as well - may be the same as the endpoint or
> different if external to the endpoint
> >                               - Reuse the identity information from the
> authentication to establish the identity of the reporter.
> >                       - Cryptographic ifnormation that can be used to
> authenticate the provenance assertion
> >                       - (FOR CONTINUED DISCUSSION) Some questions on th=
e
> call about if
> > providing provenance information is required in all cases;
> > self-reported - may/should; other-reported - must
> >
> >               The endpoint attribute assertions (if any) on which the
> assertion is
> > based
> >
> >               Information about the method used to derive the assertion
> >
> >
> > Other Data
> > ----------
> >
> >       Endpoint uniquely identified?  True or false; very subjective; as=
k
> > larger WG
> >
> >
> > Other Considerations
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> >       * Write security considerations speaking to
> >               - uniqueness of any identifying attribute - address
> malicious or accidental cases where uniqueness may be compromised
> >               - Issues relating to compromise of endpoint attributes
> (lying
> > endpoints) - Perhaps slandering other endpoints as a result
> >
> >       * When authenticating as part ofa SACM posture exchange, the
> authentication information should be incorporated into an endpoint identi=
ty
> assertion.  Should be a MUST for any endpoint that has the capability to
> authenticate.
> >
> > Future Discussion Points
> > ------------------------
> >
> >       * Discuss identification information from bios/firmware (e.g.
> serial
> > numbers, asset tags, VM id) that can be queried on the device using
> > software
> >
> >
> >
> > NEXT STEPS (Agenda Items to track)
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> >       * Coordinate Information Model updates on list
> >       * Start preparing for IETF 92
> >
> >
> >
> >
> > _______________________________________________
> > sacm mailing list
> > sacm@ietf.org <javascript:;>
> > https://www.ietf.org/mailman/listinfo/sacm
> >
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/sacm
> _______________________________________________
> sacm mailing list
> sacm@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/sacm
>

--047d7b3441c64774a9050f072f86
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I concur<div>That makes sense for me to work first on data/relationships<br=
><br>On Friday, February 13, 2015, Waltermire, David A. &lt;<a href=3D"mail=
to:david.waltermire@nist.gov">david.waltermire@nist.gov</a>&gt; wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">I believe this is a real risk if we get too p=
rescriptive in the information model. To avoid this we could discuss the da=
ta and relationships that need to be provided without implicitly or explici=
tly defining syntax or structure. This would allow for flexibility in how a=
 given data model could be structured, but in doing so would provide a list=
 of must-haves to be included in the data model.<br>
<br>
Thoughts?<br>
<br>
Have a great weekend!<br>
Dave<br>
<br>
-----Original Message-----<br>
From: sacm [mailto:<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&=
#39;, &#39;sacm-bounces@ietf.org&#39;)">sacm-bounces@ietf.org</a>] On Behal=
f Of Gunnar Engelbach<br>
Sent: Friday, February 13, 2015 3:52 PM<br>
To: Adam W. Montville; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;c=
vml&#39;, &#39;sacm@ietf.org&#39;)">sacm@ietf.org</a><br>
Subject: Re: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-13<br>
<br>
<br>
A question regarding this effort:<br>
<br>
So there will be a list of primary and secondary attributes.<br>
<br>
These attributes will be represented in some notation, such as name/value p=
airs.=C2=A0 Some, if not all, of these attributes will also be used for sec=
urity evaluations.<br>
<br>
Because this is being defined prior to the adoption of a data format for re=
presenting the assessment guidance, isn&#39;t there a risk that the represe=
ntation of endpoint ID attributes will not be compatible with the guidance,=
 necessitating duplication of collection?<br>
<br>
<br>
--gun<br>
<br>
On 2/13/2015 3:35 PM, Adam W. Montville wrote:<br>
&gt; SACM Endpoint ID Design Team Notes<br>
&gt; 2015-02-13<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt; Agenda:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Reminder:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- WebEx Chat and=
 SACM Jabber Room<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Recording will=
 be (is) enabled<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Endpoint ID Example Continued<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Update on upda=
ting Information Model draft<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- POSTPONED Cont=
inued Provenance Discussion<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Virtual Interim Considerations<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- W3C investigation considerations<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Next Steps<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Could we use a=
 &quot;by week&quot;?<br>
&gt;<br>
&gt; Attendees:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Clifford Kahn<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Danny Haynes<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0David Waltermire<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Jim Bieda<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Ron Colvin<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Lisa Lorenzin<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Adam Montville<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Jessica Fitzgerald-McKay<br>
&gt;<br>
&gt; Overview<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt; We had some technical difficulties at the outset of the meeting, but e=
ventually decided to start talking about how we start updating the Informat=
ion Model and postponing the provenance discussion until next week.=C2=A0 W=
e ended the formal part of the meeting at about half past the hour and allo=
wed the balance of the 2-hour block for Dave and Cliff to further discuss t=
he structural changes of the IM draft.<br>
&gt;<br>
&gt; To update the Information Model, we might consider:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Identify the information element gaps betw=
een current IM draft and Endpoint ID<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- We should more robustly define the entitie=
s in the relationship diagram<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- We have a notional model of an Endpoint Id=
entity Assertion, and the IM draft should be updated with this infomration =
as well (perhaps that an endpoint attribute assertion can be an identity as=
sertion)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0-<br>
&gt;<br>
&gt; Additional Comments<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- It&#39;s noted that we haven&#39;t yet ind=
icated the normative information in the IM that would help determine whethe=
r specific data models would be compliant with the IM.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Concise is good.=C2=A0 We have made conclu=
sions that could be distilled.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0-<br>
&gt;<br>
&gt; Way Forward<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- We&#39;re not 100% clear on how we want to=
 organize the notion of Endpoint Assertion and/or Endpoint Identity Asserti=
on (for next week)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Focus our efforts this go around on what a=
 good organizational structure might be to convert the balance of the notes=
 into the information model (this week)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Work on the ERD (this week)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Dave and Cliff will get together to determ=
ine how to split things out.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- PROV will be pushed out<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Amended, Ongoing Notes Pertaining to Endpoint Identification<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt; Scenarios:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Scenario A: Software on an endpoint is ass=
erting posture relating to the endpoint&#39;s software inventory and config=
uration.<br>
&gt;<br>
&gt; Endpoint Identity Assertion<br>
&gt; ---------------------------<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* All endpoint attributes can be used to est=
ablish identity<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* We are defining a core set of (primary) at=
tributes that can be used to assert identity in a consistent fashon<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- High level of =
assurance, attributes can be authenticated<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Other (secondary) attributes can be used t=
o check an identity<br>
&gt; assertion or to further define the endpoint&#39;s identity (e.g.<br>
&gt; configuration, software inventory, capability)<br>
&gt;<br>
&gt;<br>
&gt; Attribute/value pairs<br>
&gt; ---------------------<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Identity attributes (used to determine what =
the endpoint is; to be provided regardless of other posture attributes):<br=
>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Certificates (=
e.g., device, user, drive, other hardware)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Device mandatory if available on device; favored by consumer=
s of the assertion<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Others if available as associated with the session<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Use whole cert or some aspect (e.g., public key)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Hostname(s) - =
configured on the device; may be multiple and possibly of different kinds<b=
r>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Consider how to specify type: multiple attributes for each t=
ype<br>
&gt; or type qualifier<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* FQDN(s) (if av=
ailable); some hosts may have multiple; also list DNS aliases<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Sourced from the DNS infrastructure<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Think abou the security considerations of insecure DNS<br>
&gt; deployments<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Interface(s) (=
comprehensive, if possible)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- MAC address(es)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- IP address(es)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Including additional IPs assigne=
d to the interface<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Interfaces may be nested (e.g., overlay networks - VLANs) - =
NOTE: Need to verify that standardized methods are available to do this.<br=
>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Other cryptogr=
aphic information (e.g., IPSec Key-hash, HIP-HIT (RFC4423, 5201), 802.1AR)<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- NOTE: Investigate options to determine if they should be inc=
luded as primary attributes; post a summary of how to use these specs<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Cliff: HIP-HIT<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Expe=
rimental implementation at the moment; not a lot of adoption<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- ID i=
s a public key; an endpoint can have more than one<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- A pu=
blic key might be a good identifier type in general for SACM; public keys t=
end to exist, even when a certificate doesn&#39;t (e.g. SSH)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Lisa: IPSec Security Association=
s (SA)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- The =
SA contains the IPSEC keys and what algorithms are in use<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Unab=
le to differentiate by source IP address<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Keys=
 can rotate, and may be less useful as a result<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Like=
ly not a primary identity attribute, but likely useful to include as an asp=
ect of posture.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Henk: 802.1AR<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Appe=
ndix B in specification discusses use of TPM<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- The =
standard&#39;s intent is to support unattended operation<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- A st=
rong, globally unique identifier (re: iDevID - preinstalled; lDevID - enter=
prise defined).<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- lDev=
ID can be generated specifically for SACM uses<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Any =
xDevID has to ahve a certificate.=C2=A0 Could a public key from the certifi=
cate be used as the identifier?<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- How =
would a SACM component know of the ID?=C2=A0 It could be collected from bot=
h the endpoint as well as the device making a network access control decisi=
on.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- The =
secret (e.g. certificate) does not need to be hardware rooted<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- How =
widely is this implemented?=C2=A0 About 6 years old.=C2=A0 Many infrastruct=
ure vendors have implementations, but not much use has been seen.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Other notes:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- To i=
nclude public keys, we need to discuss: what algorithm was used and the int=
ended use of the key as data points?=C2=A0 Need to consider authentication =
using private keys.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Tool-specific =
identitier - provided by the software making the assertion<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- SHOULD be provided<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- May be session scoped if the tool is not able to distinguish=
 an endpoint across sessions<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- May be omitted if the tool is unable to distinguish the endp=
oint<br>
&gt; across multiple assertions<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Identification=
 information from bios/firmware (e.g., serial numbers, asset tags, VM id) t=
hat can be queried on the device using softare. NOTE: Need to discuss more.=
<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Assets are compositional.=C2=A0 Some components may have spe=
cific identifiers.=C2=A0 It would be useful to indicate which component has=
 a specific identifying attribute.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Information should be made available by all manufacturers<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- If available should be provided as an attribute<br>
&gt;<br>
&gt;<br>
&gt; Temporal Data<br>
&gt; -------------<br>
&gt;<br>
&gt; A timestamp indicating when the observation is made for a given AVP:<b=
r>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* If periodic, a timestamp at present time<b=
r>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* If event-based, an interval last-change to=
 present time<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* A timestamp is included on an attribute-by=
-attribute basis<br>
&gt;<br>
&gt; For information that changes frequently having the ability to poll and=
 represent the poll interval is beneficial.<br>
&gt;<br>
&gt; Time to Live (TTL) values provide an indication of when a given aspect=
 of state will change.=C2=A0 Provide when naturally occurring (e.g., a tool=
 will know when the DHCP lease expires). MAY be provided if applicable.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- Do not include in current model unless we =
have a good use case.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Provenance Data<br>
&gt; ---------------<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0What constitutes provenance:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Assessing conf=
idence<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0* Identity of the reporter itself (possibly endpoint identity =
but may be software component identity)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0* Have some idea of what that thing is<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0* Have some sort of timestamp<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0* Is entity aware that it=E2=80=99s =E2=80=9Cself reporting=E2=
=80=9D or =E2=80=9Cother reporting=E2=80=9D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A03 Aspects of Provenance from W3C:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A01. Chain of Custody:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Who said the i=
nformation<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Who handles th=
e information<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Endpoint is in=
 chain<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* SACM component=
 is in chain<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Should include=
 how information was transported<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A02. Method (=E2=80=9CProcess=E2=80=9D in W3C =
terminology)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* How did you go=
 about harvesting<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A03. Basis<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0We should provide enough information for the=
 consumer to determine degree of confidence.=C2=A0 May require guidance abo=
ut what may or may not constitute some degree of confidence (perhaps an inf=
ormational draft?). TODO: Need to recruit people to write this informationa=
l draft (certain areas in this set of notes could be used as a basis for su=
ch a draft).<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Reporter=E2=80=99s identity and the timestam=
p should be a MUST in all instances.=C2=A0 Others may lean toward SHOULD, b=
ecause they may not always be possible.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Example: IP address of an endpoint<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Goal is to assoc=
iate IP address with Unique endpoint ID.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Endpoint self-report<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Third-party assigns IP address reporting (e.g. IP address mgt =
sys)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Third-party observer (e.g. profiler, infrastructure witnessing=
<br>
&gt; traffic)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0We want provenan=
ce for that IP address attribute to tell us from where the information came=
.=C2=A0 If it=E2=80=99s observed, is it authoritative, or is it simply pass=
ive?=C2=A0 We want to know the observation timestamp.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CoC is who is do=
ing the reporting.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Process is how o=
bservation was made/communicated.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Object-oriented =
Provenance is the source of the observation<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Note that endpoints can=E2=80=99t really =E2=
=80=9Clie=E2=80=9D about third-party observations; caution if the observer =
is not in a position to see the accurate observation (e.g. NAT=E2=80=99d en=
vironments).<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Other observations from discussion:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0It=E2=80=99s val=
uable to capture time auth/observation occurred<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Every AVP should=
 have its own timestamp.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Wouldn=E2=80=99t that be the timestamp of the attribute itself=
?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0TODO: Gap analysis for tying in W3C work to =
SACM - how do we hook into that work in a way that doesn=E2=80=99t bring in=
 the whole elephant when we need only the trunk and the leg?=C2=A0 Cliff wi=
ll iterate one more time, people will review and comment as appropriate bef=
ore next meeting (2/13). Need to investigate the W3C concepts a bit further=
 to determine how they might apply to SACM - find an example of how provena=
nce would be generated/used.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0FUTURE WORK: Consider the =E2=80=9Ccomment=
=E2=80=9D mechanism as in IF-MAP - possibly something that can come later (=
subsequent SACM =E2=80=9Cphase=E2=80=9D).<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0DISCUSS: Transport security considerations m=
ay apply to Chain of Custody and Method, is there a =E2=80=9Cplace=E2=80=9D=
 better than others to include this type of information in the model?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0DISCUSS: Is there any way to generalize the =
notion of chain of custody, method, basis, to then generalize =E2=80=9Cconf=
idence=E2=80=9D?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0DISUCSS: Chain of custody considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Notes previous to 2/6 conversation:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* A timestamp in=
dicating when the assertion was received - consumer<br>
&gt; (e.g., collector, borker, repo)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Think about co=
mpositional model of assertions - Asserting<br>
&gt; additional details related to another assertion<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The SACM compone=
nt that made the assertion - the identity of the software providing the inf=
ormation<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- An assertion of the identity of the software used (e.g., ven=
dor, product, version, etc.)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- The instance of the software (e.g., the device the software =
was run on, the installation of the software) - could be an endpoint identi=
ty assertion as well - may be the same as the endpoint or different if exte=
rnal to the endpoint<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Reuse the identity information f=
rom the authentication to establish the identity of the reporter.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- Cryptographic ifnormation that can be used to authenticate t=
he provenance assertion<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0- (FOR CONTINUED DISCUSSION) Some questions on the call about =
if<br>
&gt; providing provenance information is required in all cases;<br>
&gt; self-reported - may/should; other-reported - must<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The endpoint att=
ribute assertions (if any) on which the assertion is<br>
&gt; based<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Information abou=
t the method used to derive the assertion<br>
&gt;<br>
&gt;<br>
&gt; Other Data<br>
&gt; ----------<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Endpoint uniquely identified?=C2=A0 True or =
false; very subjective; ask<br>
&gt; larger WG<br>
&gt;<br>
&gt;<br>
&gt; Other Considerations<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Write security considerations speaking to<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- uniqueness of =
any identifying attribute - address malicious or accidental cases where uni=
queness may be compromised<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- Issues relatin=
g to compromise of endpoint attributes (lying<br>
&gt; endpoints) - Perhaps slandering other endpoints as a result<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* When authenticating as part ofa SACM postu=
re exchange, the authentication information should be incorporated into an =
endpoint identity assertion.=C2=A0 Should be a MUST for any endpoint that h=
as the capability to authenticate.<br>
&gt;<br>
&gt; Future Discussion Points<br>
&gt; ------------------------<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Discuss identification information from bi=
os/firmware (e.g. serial<br>
&gt; numbers, asset tags, VM id) that can be queried on the device using<br=
>
&gt; software<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; NEXT STEPS (Agenda Items to track)<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Coordinate Information Model updates on li=
st<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0* Start preparing for IETF 92<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; sacm mailing list<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;sac=
m@ietf.org&#39;)">sacm@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/sacm</a><br>
&gt;<br>
<br>
_______________________________________________<br>
sacm mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;sacm@iet=
f.org&#39;)">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/sacm</a><br>
_______________________________________________<br>
sacm mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;sacm@iet=
f.org&#39;)">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/sacm</a><br>
</blockquote></div>

--047d7b3441c64774a9050f072f86--


From nobody Sun Feb 15 13:49:01 2015
Return-Path: <bcheikes@mitre.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE741A0060 for <sacm@ietfa.amsl.com>; Sun, 15 Feb 2015 13:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.225
X-Spam-Level: *
X-Spam-Status: No, score=1.225 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, T_FILL_THIS_FORM_SHORT=0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_GREY=0.424] autolearn=no
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 RJLL5UZmCTD0 for <sacm@ietfa.amsl.com>; Sun, 15 Feb 2015 13:48:56 -0800 (PST)
Received: from smtpvbsrv1.mitre.org (smtpvbsrv1.mitre.org [198.49.146.234]) by ietfa.amsl.com (Postfix) with ESMTP id 521C61A0104 for <sacm@ietf.org>; Sun, 15 Feb 2015 13:48:56 -0800 (PST)
Received: from smtpvbsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 917D633E006 for <sacm@ietf.org>; Sun, 15 Feb 2015 16:48:55 -0500 (EST)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpvbsrv1.mitre.org (Postfix) with ESMTP id 8153736E008 for <sacm@ietf.org>; Sun, 15 Feb 2015 16:48:55 -0500 (EST)
Received: from IMCMBX04.MITRE.ORG ([169.254.4.251]) by IMCCAS03.MITRE.ORG ([129.83.29.80]) with mapi id 14.03.0224.002; Sun, 15 Feb 2015 16:48:54 -0500
From: "Cheikes, Brant A." <bcheikes@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Corrected Announcement - Open Group Security Automation Vendor Workshop
Thread-Index: AdBJaP1D2K6HUzMDSkOb4B16Hrb1cQ==
Date: Sun, 15 Feb 2015 21:48:54 +0000
Message-ID: <808A833A2D415D41996B1CF760901A0A34139ECA@IMCMBX04.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.140.19.249]
Content-Type: multipart/related; boundary="_004_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/87or6uOnKg14nmBsThYZMf6WEtw>
Subject: [sacm] Corrected Announcement - Open Group Security Automation Vendor Workshop
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Feb 2015 21:48:59 -0000

--_004_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_
Content-Type: multipart/alternative;
	boundary="_000_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_"

--_000_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The announcement below contains some corrections and additions to the annou=
ncement I circulated last week. Note that support will be provided for part=
icipation by phone.

/Brant

Brant A. Cheikes
The MITRE Corporation
202 Burlington Road, M/S K302
Bedford, MA 01730-1420
Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352



[cid:image003.png@01D0493F.47E5E380]

Vendor Workshop: Security Automation
When: March 31st 2015
Where: Hewlett-Packard Co.
   3000 Hanover St.
   Building 20
   Palo Alto CA 94304
Link to workshop info: Here<https://collaboration.opengroup.org/projects/se=
curity/sec-automation/>

The attack/response dynamic facing IT security organizations is a significa=
nt challenge. With attacks from various threat actors escalating, there is =
pressure to respond to attacks faster, with greater effectiveness, and with=
 more automation.

The Open Group conducted a series of workshops (held in London, Mexico City=
, and Minneapolis, and virtually via WebEx) on the topic of security automa=
tion in October, November, and December, 2014. We used a business scenario =
approach to determine end user pain points, business objectives, and soluti=
on requirements. The output of these events is a Security Automation Busine=
ss Scenario, capturing input from large IT security organizations in North =
America and Europe.

To engage the security vendor community on this topic, we are bringing a wo=
rkshop to Silicon Valley (location below).  In preparation for the vendor w=
orkshop, we are asking IT security vendors to complete a short survey regar=
ding your plans for development of automated security capabilities. All ind=
ividual results will be kept confidential to Open Group staff, and anonymiz=
ed before discussion. The survey may be accessed here:

https://www.surveymonkey.com/r/LH7QMFH

Security Automation vendor workshop:

If you are an IT security vendor product manager, product architect, or dev=
elopment manager, please consider attending. There is no cost for this work=
shop, and we need your input. Participants will have an opportunity to hear=
 customer pain points, objectives, and product requirements regarding secur=
ity automation solutions. You will also have the opportunity to weigh in on=
 needed standards activity, and help shape work that The Open Group Securit=
y Forum is or should be doing to help move the industry forward.

If you have questions about the workshop, or to reserve a spot, please cont=
act Jim Hietala, VP, Security, at: j.hietala@opengroup.org<mailto:j.hietala=
@opengroup.org>, or Steve Borchert at: s.borchert@opengroup.org.

Agenda

Vendor Security Automation Workshop March 31st 2015

8:00-8:30              Check in and breakfast

8:30-9:00              Introductions, agenda review, and topic overview

9:00-9:45              Overview of Security Automation End User Workshops &=
 Results


9:45-10:30           Standards landscape in security automation (survey of =
what standards exist                                       and are being wo=
rked on in other standards organizations, how they relate,                 =
                               and their current status)

10:30-10:45         Break

10:45-11:30         Vendor security automation status (based upon survey)

11:30-12:15         Discussion of work needed going forward

-          Developing the ROI/business case for vendors security automation=
 development

-          Developing the ROI/business case for customer use of automated s=
ecurity

-          Creating an overarching framework that leverages disparate lower=
 level standards

-          Other?

12:15                     Adjourn

Location

Address:
Hewlett-Packard Co.
3000 Hanover St.
Building 20
Palo Alto CA 94304

Take Interstate 101 to the Embarcadero-Oregon Expressway exit.
Be careful to stay on Oregon Expressway, which becomes Page Mill Road after=
 about two miles.
Drive three traffic lights past El Camino and turn left onto Hanover Street=
.
Turn right into the first driveway.
Follow the signs for Visitor Parking / Lobby
Executive Briefing Center
On-site Contact
Mary Ann Mezzapelle
Mobile +1-925-683-3679

For remote participants wishing to join via Webex:
JOIN WEBEX MEETING
https://opengroup.webex.com/opengroup/j.php?MTID=3Dm76da733c8a2cc862888a98b=
e97d9eba2
Meeting number: 572 299 838

JOIN BY PHONE
1-408-792-6300 Call-in toll number (US/Canada)
Access code: 572 299 838

Global call-in numbers:
https://opengroup.webex.com/opengroup/globalcallin.php?serviceType=3DMC&ED=
=3D292959542&tollFree=3D0

Can't join the meeting? Contact support here:
https://opengroup.webex.com/opengroup/mc


--_000_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Cambria;
	panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast
	{mso-style-priority:34;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	mso-add-space:auto;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1607418136;
	mso-list-type:hybrid;
	mso-list-template-ids:-1933417992 567542676 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Cambria",serif;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:5.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">The announcement below contains some corrections and=
 additions to the announcement I circulated last week. Note that support wi=
ll be provided for participation by phone.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">/Brant<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Brant A. Cheikes<br=
>
The MITRE Corporation<br>
202 Burlington Road, M/S K302<br>
Bedford, MA 01730-1420<br>
Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352 <o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><img width=3D"138" height=3D"34" id=3D"Picture_x0020=
_1" src=3D"cid:image003.png@01D0493F.47E5E380"><b><o:p></o:p></b></p>
<p class=3D"MsoNormal"><b><o:p>&nbsp;</o:p></b></p>
<p class=3D"MsoNormal"><b>Vendor Workshop:</b> <b>Security Automation<o:p><=
/o:p></b></p>
<p class=3D"MsoNormal"><b>When: March 31<sup>st</sup> 2015<o:p></o:p></b></=
p>
<p class=3D"MsoNormal"><b>Where: Hewlett-Packard Co. <o:p></o:p></b></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><b>&nbsp;&nbsp;&nbsp;3000=
 Hanover St. <o:p></o:p></b></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><b>&nbsp;&nbsp;&nbsp;Buil=
ding 20 <o:p></o:p></b></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in"><b>&nbsp;&nbsp;&nbsp;Palo=
 Alto CA 94304<o:p></o:p></b></p>
<p class=3D"MsoNormal"><b>Link to workshop info:</b> <a href=3D"https://col=
laboration.opengroup.org/projects/security/sec-automation/">
Here</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The attack/response dynamic facing IT security organ=
izations is a significant challenge. With attacks from various threat actor=
s escalating, there is pressure to respond to attacks faster, with greater =
effectiveness, and with more automation.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The Open Group conducted a series of workshops (held=
 in London, Mexico City, and Minneapolis, and virtually via WebEx) on the t=
opic of security automation in October, November, and December, 2014. We us=
ed a business scenario approach to
 determine end user pain points, business objectives, and solution requirem=
ents. The output of these events is a Security Automation Business Scenario=
, capturing input from large IT security organizations in North America and=
 Europe.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">To engage the security vendor community on this topi=
c, we are bringing a workshop to Silicon Valley (location below).&nbsp; In =
preparation for the vendor workshop, we are asking IT security vendors to c=
omplete a short survey regarding your plans
 for development of automated security capabilities. All individual results=
 will be kept confidential to Open Group staff, and anonymized before discu=
ssion. The survey may be accessed here:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://www.surveymonkey.com/r/LH7QMFH">h=
ttps://www.surveymonkey.com/r/LH7QMFH</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Security Automation vendor workshop:<o:p></o:p></p>
<p class=3D"MsoNormal"><i><o:p>&nbsp;</o:p></i></p>
<p class=3D"MsoNormal"><i>If you are an IT security vendor product manager,=
 product architect, or development manager, please consider attending. Ther=
e is no cost for this workshop, and we need your input. Participants will h=
ave an opportunity to hear customer
 pain points, objectives, and product requirements regarding security autom=
ation solutions. You will also have the opportunity to weigh in on needed s=
tandards activity, and help shape work that The Open Group Security Forum i=
s or should be doing to help move
 the industry forward.<o:p></o:p></i></p>
<p class=3D"MsoNormal"><i><o:p>&nbsp;</o:p></i></p>
<p class=3D"MsoNormal">If you have questions about the workshop, or to rese=
rve a spot, please contact Jim Hietala, VP, Security, at:
<a href=3D"mailto:j.hietala@opengroup.org">j.hietala@opengroup.org</a>, or =
Steve Borchert at: s.borchert@opengroup.org.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Agenda<o:p></o:p></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Vendor Security Automation Workshop March 31<sup>st<=
/sup> 2015<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">8:00-8:30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in and breakfast<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">8:30-9:00&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Introductions, agenda review, and topic=
 overview<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">9:00-9:45&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Overview of Security Automation End Use=
r Workshops &amp; Results<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">9:45-10:30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; Standards landscape in security automation (survey of wh=
at standards exist &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; and are being worked on in other standards organizations, =
how they relate, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 and their current status)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">10:30-10:45&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Break<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">10:45-11:30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Vendor security automation status (based upon survey)<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">11:30-12:15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; Discussion of work needed going forward<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpFirst" style=3D"margin-left:1.25in;mso-add-=
space:auto;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Developing the ROI/business case for vendors=
 security automation development<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpMiddle" style=3D"margin-left:1.25in;mso-add=
-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Developing the ROI/business case for custome=
r use of automated security<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpMiddle" style=3D"margin-left:1.25in;mso-add=
-space:auto;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Creating an overarching framework that lever=
ages disparate lower level standards<o:p></o:p></p>
<p class=3D"MsoListParagraphCxSpLast" style=3D"margin-left:1.25in;mso-add-s=
pace:auto;text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"font-family:&quot;Cambria&quot;,serif">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>Other?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">12:15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A=
djourn<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Location<o:p></o:p></b></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><b>Address: </b><o:p></o:p></p>
<p class=3D"MsoNormal"><b>Hewlett-Packard Co. </b><o:p></o:p></p>
<p class=3D"MsoNormal">3000 Hanover St. <o:p></o:p></p>
<p class=3D"MsoNormal">Building 20 <o:p></o:p></p>
<p class=3D"MsoNormal">Palo Alto CA 94304<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Take Interstate 101 to the Embarcadero-Oregon Expres=
sway exit.<o:p></o:p></p>
<p class=3D"MsoNormal">Be careful to stay on Oregon Expressway, which becom=
es Page Mill Road after about two miles.<o:p></o:p></p>
<p class=3D"MsoNormal">Drive three traffic lights past El Camino and turn l=
eft onto Hanover Street.<o:p></o:p></p>
<p class=3D"MsoNormal">Turn right into the first driveway.<o:p></o:p></p>
<p class=3D"MsoNormal">Follow the signs for Visitor Parking / Lobby <o:p></=
o:p></p>
<p class=3D"MsoNormal">Executive Briefing Center<o:p></o:p></p>
<p class=3D"MsoNormal"><b>On-site Contact<o:p></o:p></b></p>
<p class=3D"MsoNormal">Mary Ann Mezzapelle<br>
Mobile &#43;1-925-683-3679 <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For remote participants wishing to join via Webex:<o=
:p></o:p></p>
<p class=3D"MsoNormal">JOIN WEBEX MEETING<br>
https://opengroup.webex.com/opengroup/j.php?MTID=3Dm76da733c8a2cc862888a98b=
e97d9eba2<br>
Meeting number: 572 299 838<br>
<br>
JOIN BY PHONE<br>
1-408-792-6300 Call-in toll number (US/Canada)<br>
Access code: 572 299 838<br>
<br>
Global call-in numbers:<br>
https://opengroup.webex.com/opengroup/globalcallin.php?serviceType=3DMC&amp=
;ED=3D292959542&amp;tollFree=3D0<br>
<br>
Can't join the meeting? Contact support here:<br>
https://opengroup.webex.com/opengroup/mc<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_--

--_004_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_
Content-Type: image/png; name="image003.png"
Content-Description: image003.png
Content-Disposition: inline; filename="image003.png"; size=2004;
	creation-date="Sun, 15 Feb 2015 21:48:54 GMT";
	modification-date="Sun, 15 Feb 2015 21:48:54 GMT"
Content-ID: <image003.png@01D0493F.47E5E380>
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAIoAAAAiCAYAAACAyEHnAAAAAXNSR0ICQMB9xQAAAAlwSFlzAAAO
xAAADsQBlSsOGwAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAAdUSURBVHja
7ZsrbFRpGIYrNmEFooIEBKKCpAhEBQkViApCECtAEDAkVQ2KkKxYXM+cOW1nSW906UL21t01SCQS
iUQikUgkkp1nMm/zztf/zKUzzHamR3yZmfPf/+/93+/yn5mp1WozJ1mW82wJWfq5liF8XymyhZM+
72mTEzmpB+vZrSvb9VffPV/7MrO/9hW5uFu8u7aV7wCWS7vFm/mt+us76/lypcRTCBQAMrtXfBQ4
zjxf+/zDev6w0Wh8X8Y2VzeLFz9l2YVKmacAKE1Fzy5sFQcCiBjkxyyb69UWEN1s5I/LwFTJlAAF
MDiLIJidFCBgnLtFfv9GI39CHdjkUZZdVnml0CkFSgok+B8ppafY5d56dvvsL8Wn65v5RqXMKQUK
fkUEyflnxftBmQE/hbY4upVCpxAoc7vFWwcJEY7MyKBCBEQfOL6VUqcIKCjUQYLgdxy3P8Jk+sAM
Vb7KlAAFX8PzI8c1OSnzg1S5lSkBCr5EZBOimWH6dKBghirFfgOgPMie3lrO1pei8HwlKxb1m+9q
1Py+oOfkQGCJ2P5RVlxOObApNhl2EUQ/6g/z0yvvcifbXL6eP9uYy397ezXff8Fv1jGII3539en9
m6ubj9mLsnGow17EMtos1Xaye1nj9sQAZSHfP5ByZ+r/fmUD+c6nQMRzFt1hPur/fKGONuVc/ueH
+fzla+pTFwXEwUiMRTZBycMuIvabUjrPmO+Z+t+fWQ9K1jp5drZ+8In19gIZCgZgKJvDo746GK7Z
L/tBGX37HC7lL9+oDOk15okBiqe/mTinS5situB5PBmzxV8fVbcVxTQ3j03slveAPUbNJilztlJk
i16OMpgfc2YtKCqecICPlDEEe0EfiPwpntEfB+TQsW7uCfvAmD4W/V7L93Z8T5FJYZXOHwYUV/ig
QGHx8f6ltamBTWCCUSwiAtCBciPbfoKCMIVSTmQA5Er+6yvKOPEpkKBwWMfZivU62wIOGJrvMJUY
WiBRO+qLbSYlSusbKJwaNgbBrMS6AIXNZGMAUWQU9yPMRAx9mZcCoMbWfFus01QUc4Y1UqZJSndT
IWZlbfGwSNkCBmOKbRBAJdMSzfDF2u/vKHPwnEpG4QRFZUTzQKp+FAtIAZA5y5mUsuWbpHwnBxLi
z2GkaF5gTADnzNRm0daaeS52op2zBntjgJ2YW++RAiWeEI+UlD0ddb6Di0Hvl1cTjiT4VrcfCgRl
PohYwxlFTjuC6WrdcjcZ5Hz9j/epaEaghE1oA1Bi9AdwerEJ+8beAj5FlohHlWUgYzza0d7X6u39
uZ6xVo9mEQd4R8gnmxo9+H6jHm0gwka4Rx9T9v28QtCPEA57v4xzxIdpzos1QPllyhXjeB0ULRaC
JSiLB+kIwzWVVOYL9WITlKwx2EP6Yl8FFkBKW/aVuUUTjz54rvQG63YGpT3r9DaqR/8AlHLqcbgA
PIx6CBQqaXLt/MmCe/EKeUWtQjqfDKp8gedgMEOOSHc4uQwcBUhI1EWzwxtwKaBHsHeE121TgbBB
UeFsWC+ARFCi4OiodmMTgMM4Gt8VKX0wB8DhB1t9UUZ7H1N11Cc6UXsX+VmyFHIhAB7AHGtm9txe
8UHK5CWlUfQZX3ZCyNKmlBM3MaXcdlRzwaOgbu26sUnMjwiwZWwiX6jbWA4UuQQCP2tgzrEN9Sk7
DlCY09iBgvNaduqPGe30zPK26jQXmjKpUbntHMqhT6V27sTGxFsZ4FJtVCYGYFwfD2WllBiBIpOv
CNP9y9QaAY+UPQhQ3AyOFSge9QxzU1wWRaXyMsplIKlTLLqP/oQnxFI5FzY2mjEH3JHUgJUxpofS
HnVJoZoDz1iDQCnzonm7CeM3faaAIkZhLanw3/txoJRGPd9S/NWCYSOeFJvEVww8l1HGCnJWUydR
bd1noA0g6cYmKf9DeRMcS/wN+ojpA10HeDQlwKZ8FIXoKhPQoumCeTwRGiM/xvM1uun5X4DCf3Gk
1GHfRkuxSXxpSQkxhFPlihGtsolO/x1hdzupSD38DUU90dmMvkk8iZ4RRgmAsswPoW/GUB9qK3+H
cmcEAMcaFD7TlrWqf+p7HkeHR/sh4Pt8KE8dnLEmbRQiD3PHQ3o+goQ39stOOMphw8UEonOU281x
pAxnDjpns/ledsOsKC9lpugHxbTZZLEftmQs9cd3mAVRptnHYWwHL2WskXapKE/9K9PuJln3VEjM
E40VKJ5FHeRa3zfdo6eyVyiVryjzMSoZMjM7DuFvFmV/yThOOJzyd2CPSUyTV0DpsNnZvNL5g/gq
hNT9gMRDYg/7KpkwoOBjYG8JkfFVMB0AhzsbwJB6E79fkHjiqtu9TiUTAJRWfmMz31CuAb+j7G8a
sIMn6hQGxxeTrP6swtqye51KJggoCnGRlA9BGh4wcRPsIMFHSTnBRDU4rYp0lHonGuh201rJBABF
UZAYA1DEG2ZdIGKmuinbw7qUVECZcKBIWm/xN1mEFDz+CH9E5/eoXkWoZHj5Dz/fO8wT7WwwAAAA
AElFTkSuQmCC

--_004_808A833A2D415D41996B1CF760901A0A34139ECAIMCMBX04MITREOR_--


From nobody Mon Feb 16 07:54:28 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D31E1A1AF8 for <sacm@ietfa.amsl.com>; Mon, 16 Feb 2015 07:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 Es5EpxbgcZEg for <sacm@ietfa.amsl.com>; Mon, 16 Feb 2015 07:54:23 -0800 (PST)
Received: from mail-ee0-x22a.google.com (mail-ee0-x22a.google.com [IPv6:2a00:1450:4013:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E3981A1EF7 for <sacm@ietf.org>; Mon, 16 Feb 2015 07:54:23 -0800 (PST)
Received: by mail-ee0-f42.google.com with SMTP id b15so9395eek.1 for <sacm@ietf.org>; Mon, 16 Feb 2015 07:54:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=pLi/yyTxSLFIR4AaBWADl4tbfzLMoTBXW2qSDggermM=; b=aR02s8j5LAiO34U/61Nd6bXOWvrFdGDeYDApwniKWt3MlPeWSgyWEbPtdm8y4esvNg G9merLW6Ff99Jom9biczaviQ3r0tjPqLpHL9rVoyYwxGn7EvW5Vj2OpakOl8jyxxARx4 EJPCAWuALF0kbfCup7kiGhW9rTp5LUntfShknNasuqOI9b773wHTEz0xkxadkdBnZ3U9 Rc5UJQJSYdxM+Y2ySAFhbLjd/lQaqs9mSrna78rLtj3bvUx8xZQP7yPcfz4K+ajI/vzC +TC2BYF4iYb6bJkDEt2HSiRNCS1ZVqgFX0rnd6zSqOtoeooYoVH3qJ1y6CAIm7LlS7IP bEZA==
MIME-Version: 1.0
X-Received: by 10.112.16.101 with SMTP id f5mr23086063lbd.75.1424102062030; Mon, 16 Feb 2015 07:54:22 -0800 (PST)
Received: by 10.112.167.101 with HTTP; Mon, 16 Feb 2015 07:54:21 -0800 (PST)
Date: Mon, 16 Feb 2015 10:54:21 -0500
Message-ID: <CAHbuEH4CNR21UskzwdET5PNh7RMCrpAEsKjcAoBHm+KTt7i5PQ@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3fdfe88042b050f369995
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/IZxJEPkh_oMjSoNCfh_ke-T8vhk>
Subject: [sacm] AD Review of SACM Use Case Draft
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2015 15:54:27 -0000

--001a11c3fdfe88042b050f369995
Content-Type: text/plain; charset=UTF-8

Hello,

The following is my review of the SACM use case draft.  Since this is a
charted item and milestone for SACM, the work can proceed.  A statement
from the IESG on use case drafts will be coming out soon, thanks to those
that assisted in building arguments.

SACM use case draft:

Introduction:
Second sentence - should this be a bulleted list or be multiple sentences?
   It provides a discussion of
   these use cases and associated building block capabilities that
   support securely aggregating configuration and operational data and
   evaluating that data to determine the security posture of individual
   endpoints, and, in the aggregate, the security posture of an
   enterprise.

2nd paragraph, 1st sentence, "information" is redundant:
   These use cases and usage scenarios cross many IT security
   information domains.

There are lots of really long sentences, last sentence of 3rd paragraph is
 run-on.

Section 2.2.2
Can you break this sentence into a few?
   Using the collected hardware and software inventory data and
   associated asset characterization data that may indicate the
   organizational defined functions of each endpoint, checklist guidance
   is queried, located and downloaded from the appropriate vendor and
   3rd-party security automation data store for the appropriate
   checklists.

Same section, following sentence:
 While specific applications for checklists results are out-of-scope
s/checklists/checklist/

And I don't really follow the logic of the full transitional sentence:
   While specific applications for checklists results are out-of-scope
   for current SACM efforts, how the data is used may illuminate
   specific latency and bandwidth requirements.  For this purpose use of
   checklist assessment results may include, but are not limited to:

Could you introduce latency and bandwidth in a different way?  It seems odd
to follow from descriptions on types of checklists (or 'applications of
checklists').

Now that I read the types of checklists and how varied they are, I think it
may be better to delete the transitional sentence listed above as there are
many other types of checklists included in the list that follows.

Section 2.2.4
Could you make it more clear that the query mechanism described int his
section is to be provided by SACM?  I assume that is the case.  This may
come up in other reviews, why is the section here if it doesn't use SACM.

Section 4, Security Considerations.
I recommend replacing the following sentence:
   While it is about security, it does not affect
   security.
with something that explains where the security considerations will be
addressed.  Something like:
   Security considerations will be provided in solution
   standards as appropriate to the function described
   in each solution document.

5. Acknowledgements

Is "Security Automation" copyrighted or trademarked?  The first paragraph
is odd if it is not.  If it is, then disclosures are needed.  By having
this sentence in the draft, some type of disclosure may be needed so people
understand why it is there as there are many instances of security
automation by vendors and groups like ICASI and TCG.

-- 

Best regards,
Kathleen

--001a11c3fdfe88042b050f369995
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>The following is my review of th=
e SACM use case draft.=C2=A0 Since this is a charted item and milestone for=
 SACM, the work can proceed.=C2=A0 A statement from the IESG on use case dr=
afts will be coming out soon, thanks to those that assisted in building arg=
uments.<br><div><br></div><div><div>SACM use case draft:</div><div><br></di=
v><div>Introduction:</div><div>Second sentence - should this be a bulleted =
list or be multiple sentences?</div><div>=C2=A0 =C2=A0It provides a discuss=
ion of</div><div>=C2=A0 =C2=A0these use cases and associated building block=
 capabilities that</div><div>=C2=A0 =C2=A0support securely aggregating conf=
iguration and operational data and</div><div>=C2=A0 =C2=A0evaluating that d=
ata to determine the security posture of individual</div><div>=C2=A0 =C2=A0=
endpoints, and, in the aggregate, the security posture of an</div><div>=C2=
=A0 =C2=A0enterprise.=C2=A0</div><div><br></div><div>2nd paragraph, 1st sen=
tence, &quot;information&quot; is redundant:</div><div>=C2=A0 =C2=A0These u=
se cases and usage scenarios cross many IT security</div><div>=C2=A0 =C2=A0=
information domains.</div><div><br></div><div>There are lots of really long=
 sentences, last sentence of 3rd paragraph is =C2=A0run-on.</div><div><br><=
/div><div>Section 2.2.2</div><div>Can you break this sentence into a few?</=
div><div>=C2=A0 =C2=A0Using the collected hardware and software inventory d=
ata and</div><div>=C2=A0 =C2=A0associated asset characterization data that =
may indicate the</div><div>=C2=A0 =C2=A0organizational defined functions of=
 each endpoint, checklist guidance</div><div>=C2=A0 =C2=A0is queried, locat=
ed and downloaded from the appropriate vendor and</div><div>=C2=A0 =C2=A03r=
d-party security automation data store for the appropriate</div><div>=C2=A0=
 =C2=A0checklists. =C2=A0</div><div><br></div><div>Same section, following =
sentence:</div><div>=C2=A0While specific applications for checklists result=
s are out-of-scope</div><div>s/checklists/checklist/</div><div><br></div><d=
iv>And I don&#39;t really follow the logic of the full transitional sentenc=
e:</div><div>=C2=A0 =C2=A0While specific applications for checklists result=
s are out-of-scope</div><div>=C2=A0 =C2=A0for current SACM efforts, how the=
 data is used may illuminate</div><div>=C2=A0 =C2=A0specific latency and ba=
ndwidth requirements.=C2=A0 For this purpose use of</div><div>=C2=A0 =C2=A0=
checklist assessment results may include, but are not limited to:</div><div=
><br></div><div>Could you introduce latency and bandwidth in a different wa=
y?=C2=A0 It seems odd to follow from descriptions on types of checklists (o=
r &#39;applications of checklists&#39;).</div><div><br></div><div>Now that =
I read the types of checklists and how varied they are, I think it may be b=
etter to delete the transitional sentence listed above as there are many ot=
her types of checklists included in the list that follows.</div><div><br></=
div><div>Section 2.2.4</div><div>Could you make it more clear that the quer=
y mechanism described int his section is to be provided by SACM?=C2=A0 I as=
sume that is the case.=C2=A0 This may come up in other reviews, why is the =
section here if it doesn&#39;t use SACM.</div><div><br></div><div>Section 4=
, Security Considerations.</div><div>I recommend replacing the following se=
ntence:</div><div>=C2=A0 =C2=A0While it is about security, it does not affe=
ct</div><div>=C2=A0 =C2=A0security.</div><div>with something that explains =
where the security considerations will be addressed.=C2=A0 Something like:<=
/div><div>=C2=A0 =C2=A0Security considerations will be provided in solution=
</div><div>=C2=A0 =C2=A0standards as appropriate to the function described<=
/div><div>=C2=A0 =C2=A0in each solution document.</div><div><br></div><div>=
5. Acknowledgements</div><div><br></div><div>Is &quot;Security Automation&q=
uot; copyrighted or trademarked?=C2=A0 The first paragraph is odd if it is =
not.=C2=A0 If it is, then disclosures are needed.=C2=A0 By having this sent=
ence in the draft, some type of disclosure may be needed so people understa=
nd why it is there as there are many instances of security automation by ve=
ndors and groups like ICASI and TCG.</div><div><br></div>-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div><div>Kath=
leen</div></div></div>
</div></div></div>

--001a11c3fdfe88042b050f369995--


From nobody Wed Feb 18 07:52:36 2015
Return-Path: <david.waltermire@nist.gov>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66D651A87BF for <sacm@ietfa.amsl.com>; Wed, 18 Feb 2015 07:52:32 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 fgrBNYeyhXuj for <sacm@ietfa.amsl.com>; Wed, 18 Feb 2015 07:52:24 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0109.outbound.protection.outlook.com [65.55.169.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 099301A89AA for <sacm@ietf.org>; Wed, 18 Feb 2015 07:52:16 -0800 (PST)
Received: from DM2PR09MB0224.namprd09.prod.outlook.com (25.160.92.146) by DM2PR09MB0221.namprd09.prod.outlook.com (25.160.92.143) with Microsoft SMTP Server (TLS) id 15.1.87.18; Wed, 18 Feb 2015 15:52:14 +0000
Received: from DM2PR09MB0224.namprd09.prod.outlook.com ([25.160.92.146]) by DM2PR09MB0224.namprd09.prod.outlook.com ([25.160.92.146]) with mapi id 15.01.0087.013; Wed, 18 Feb 2015 15:52:14 +0000
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] AD Review of SACM Use Case Draft
Thread-Index: AQHQSgDcndOrKBxlLkquKT7evMf96Jz2kLVA
Date: Wed, 18 Feb 2015 15:52:14 +0000
Message-ID: <DM2PR09MB02244B4EEC73876F534D6676F02C0@DM2PR09MB0224.namprd09.prod.outlook.com>
References: <CAHbuEH4CNR21UskzwdET5PNh7RMCrpAEsKjcAoBHm+KTt7i5PQ@mail.gmail.com>
In-Reply-To: <CAHbuEH4CNR21UskzwdET5PNh7RMCrpAEsKjcAoBHm+KTt7i5PQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.227.107]
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0221;
x-microsoft-antispam-prvs: <DM2PR09MB02211FE84F92266C6E5455D4FB2C0@DM2PR09MB0221.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0221;
x-forefront-prvs: 04916EA04C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(51914003)(164054003)(87936001)(50986999)(19580395003)(19580405001)(106116001)(2656002)(19300405004)(99286002)(86362001)(33656002)(19625215002)(2501002)(16236675004)(77156002)(62966003)(122556002)(46102003)(2950100001)(2900100001)(74316001)(92566002)(66066001)(107886001)(76176999)(54356999)(76576001)(15975445007)(40100003)(102836002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0221; H:DM2PR09MB0224.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_DM2PR09MB02244B4EEC73876F534D6676F02C0DM2PR09MB0224namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Feb 2015 15:52:14.0271 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0221
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/-X9CcscHJyib88finvnXwtn4AHs>
Subject: Re: [sacm] AD Review of SACM Use Case Draft
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 15:52:32 -0000

--_000_DM2PR09MB02244B4EEC73876F534D6676F02C0DM2PR09MB0224namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

S2F0aGxlZW4sDQoNClRoYW5rcyBmb3IgdGhlIGZlZWRiYWNrIGFuZCBmb3IgeW91ciBlZmZvcnRz
IHdpdGggdGhlIElFU0cgb24gbW92aW5nIHRoaXMgZm9yd2FyZC4gSeKAmWxsIHdvcmsgb24gYSBy
ZXZpc2lvbiBBU0FQLg0KDQpUaGFua3MsDQpEYXZlDQoNCkZyb206IHNhY20gW21haWx0bzpzYWNt
LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBLYXRobGVlbiBNb3JpYXJ0eQ0KU2VudDog
TW9uZGF5LCBGZWJydWFyeSAxNiwgMjAxNSAxMDo1NCBBTQ0KVG86IHNhY21AaWV0Zi5vcmcNClN1
YmplY3Q6IFtzYWNtXSBBRCBSZXZpZXcgb2YgU0FDTSBVc2UgQ2FzZSBEcmFmdA0KDQpIZWxsbywN
Cg0KVGhlIGZvbGxvd2luZyBpcyBteSByZXZpZXcgb2YgdGhlIFNBQ00gdXNlIGNhc2UgZHJhZnQu
ICBTaW5jZSB0aGlzIGlzIGEgY2hhcnRlZCBpdGVtIGFuZCBtaWxlc3RvbmUgZm9yIFNBQ00sIHRo
ZSB3b3JrIGNhbiBwcm9jZWVkLiAgQSBzdGF0ZW1lbnQgZnJvbSB0aGUgSUVTRyBvbiB1c2UgY2Fz
ZSBkcmFmdHMgd2lsbCBiZSBjb21pbmcgb3V0IHNvb24sIHRoYW5rcyB0byB0aG9zZSB0aGF0IGFz
c2lzdGVkIGluIGJ1aWxkaW5nIGFyZ3VtZW50cy4NCg0KU0FDTSB1c2UgY2FzZSBkcmFmdDoNCg0K
SW50cm9kdWN0aW9uOg0KU2Vjb25kIHNlbnRlbmNlIC0gc2hvdWxkIHRoaXMgYmUgYSBidWxsZXRl
ZCBsaXN0IG9yIGJlIG11bHRpcGxlIHNlbnRlbmNlcz8NCiAgIEl0IHByb3ZpZGVzIGEgZGlzY3Vz
c2lvbiBvZg0KICAgdGhlc2UgdXNlIGNhc2VzIGFuZCBhc3NvY2lhdGVkIGJ1aWxkaW5nIGJsb2Nr
IGNhcGFiaWxpdGllcyB0aGF0DQogICBzdXBwb3J0IHNlY3VyZWx5IGFnZ3JlZ2F0aW5nIGNvbmZp
Z3VyYXRpb24gYW5kIG9wZXJhdGlvbmFsIGRhdGEgYW5kDQogICBldmFsdWF0aW5nIHRoYXQgZGF0
YSB0byBkZXRlcm1pbmUgdGhlIHNlY3VyaXR5IHBvc3R1cmUgb2YgaW5kaXZpZHVhbA0KICAgZW5k
cG9pbnRzLCBhbmQsIGluIHRoZSBhZ2dyZWdhdGUsIHRoZSBzZWN1cml0eSBwb3N0dXJlIG9mIGFu
DQogICBlbnRlcnByaXNlLg0KDQoybmQgcGFyYWdyYXBoLCAxc3Qgc2VudGVuY2UsICJpbmZvcm1h
dGlvbiIgaXMgcmVkdW5kYW50Og0KICAgVGhlc2UgdXNlIGNhc2VzIGFuZCB1c2FnZSBzY2VuYXJp
b3MgY3Jvc3MgbWFueSBJVCBzZWN1cml0eQ0KICAgaW5mb3JtYXRpb24gZG9tYWlucy4NCg0KVGhl
cmUgYXJlIGxvdHMgb2YgcmVhbGx5IGxvbmcgc2VudGVuY2VzLCBsYXN0IHNlbnRlbmNlIG9mIDNy
ZCBwYXJhZ3JhcGggaXMgIHJ1bi1vbi4NCg0KU2VjdGlvbiAyLjIuMg0KQ2FuIHlvdSBicmVhayB0
aGlzIHNlbnRlbmNlIGludG8gYSBmZXc/DQogICBVc2luZyB0aGUgY29sbGVjdGVkIGhhcmR3YXJl
IGFuZCBzb2Z0d2FyZSBpbnZlbnRvcnkgZGF0YSBhbmQNCiAgIGFzc29jaWF0ZWQgYXNzZXQgY2hh
cmFjdGVyaXphdGlvbiBkYXRhIHRoYXQgbWF5IGluZGljYXRlIHRoZQ0KICAgb3JnYW5pemF0aW9u
YWwgZGVmaW5lZCBmdW5jdGlvbnMgb2YgZWFjaCBlbmRwb2ludCwgY2hlY2tsaXN0IGd1aWRhbmNl
DQogICBpcyBxdWVyaWVkLCBsb2NhdGVkIGFuZCBkb3dubG9hZGVkIGZyb20gdGhlIGFwcHJvcHJp
YXRlIHZlbmRvciBhbmQNCiAgIDNyZC1wYXJ0eSBzZWN1cml0eSBhdXRvbWF0aW9uIGRhdGEgc3Rv
cmUgZm9yIHRoZSBhcHByb3ByaWF0ZQ0KICAgY2hlY2tsaXN0cy4NCg0KU2FtZSBzZWN0aW9uLCBm
b2xsb3dpbmcgc2VudGVuY2U6DQogV2hpbGUgc3BlY2lmaWMgYXBwbGljYXRpb25zIGZvciBjaGVj
a2xpc3RzIHJlc3VsdHMgYXJlIG91dC1vZi1zY29wZQ0Kcy9jaGVja2xpc3RzL2NoZWNrbGlzdC8N
Cg0KQW5kIEkgZG9uJ3QgcmVhbGx5IGZvbGxvdyB0aGUgbG9naWMgb2YgdGhlIGZ1bGwgdHJhbnNp
dGlvbmFsIHNlbnRlbmNlOg0KICAgV2hpbGUgc3BlY2lmaWMgYXBwbGljYXRpb25zIGZvciBjaGVj
a2xpc3RzIHJlc3VsdHMgYXJlIG91dC1vZi1zY29wZQ0KICAgZm9yIGN1cnJlbnQgU0FDTSBlZmZv
cnRzLCBob3cgdGhlIGRhdGEgaXMgdXNlZCBtYXkgaWxsdW1pbmF0ZQ0KICAgc3BlY2lmaWMgbGF0
ZW5jeSBhbmQgYmFuZHdpZHRoIHJlcXVpcmVtZW50cy4gIEZvciB0aGlzIHB1cnBvc2UgdXNlIG9m
DQogICBjaGVja2xpc3QgYXNzZXNzbWVudCByZXN1bHRzIG1heSBpbmNsdWRlLCBidXQgYXJlIG5v
dCBsaW1pdGVkIHRvOg0KDQpDb3VsZCB5b3UgaW50cm9kdWNlIGxhdGVuY3kgYW5kIGJhbmR3aWR0
aCBpbiBhIGRpZmZlcmVudCB3YXk/ICBJdCBzZWVtcyBvZGQgdG8gZm9sbG93IGZyb20gZGVzY3Jp
cHRpb25zIG9uIHR5cGVzIG9mIGNoZWNrbGlzdHMgKG9yICdhcHBsaWNhdGlvbnMgb2YgY2hlY2ts
aXN0cycpLg0KDQpOb3cgdGhhdCBJIHJlYWQgdGhlIHR5cGVzIG9mIGNoZWNrbGlzdHMgYW5kIGhv
dyB2YXJpZWQgdGhleSBhcmUsIEkgdGhpbmsgaXQgbWF5IGJlIGJldHRlciB0byBkZWxldGUgdGhl
IHRyYW5zaXRpb25hbCBzZW50ZW5jZSBsaXN0ZWQgYWJvdmUgYXMgdGhlcmUgYXJlIG1hbnkgb3Ro
ZXIgdHlwZXMgb2YgY2hlY2tsaXN0cyBpbmNsdWRlZCBpbiB0aGUgbGlzdCB0aGF0IGZvbGxvd3Mu
DQoNClNlY3Rpb24gMi4yLjQNCkNvdWxkIHlvdSBtYWtlIGl0IG1vcmUgY2xlYXIgdGhhdCB0aGUg
cXVlcnkgbWVjaGFuaXNtIGRlc2NyaWJlZCBpbnQgaGlzIHNlY3Rpb24gaXMgdG8gYmUgcHJvdmlk
ZWQgYnkgU0FDTT8gIEkgYXNzdW1lIHRoYXQgaXMgdGhlIGNhc2UuICBUaGlzIG1heSBjb21lIHVw
IGluIG90aGVyIHJldmlld3MsIHdoeSBpcyB0aGUgc2VjdGlvbiBoZXJlIGlmIGl0IGRvZXNuJ3Qg
dXNlIFNBQ00uDQoNClNlY3Rpb24gNCwgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMuDQpJIHJlY29t
bWVuZCByZXBsYWNpbmcgdGhlIGZvbGxvd2luZyBzZW50ZW5jZToNCiAgIFdoaWxlIGl0IGlzIGFi
b3V0IHNlY3VyaXR5LCBpdCBkb2VzIG5vdCBhZmZlY3QNCiAgIHNlY3VyaXR5Lg0Kd2l0aCBzb21l
dGhpbmcgdGhhdCBleHBsYWlucyB3aGVyZSB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgd2ls
bCBiZSBhZGRyZXNzZWQuICBTb21ldGhpbmcgbGlrZToNCiAgIFNlY3VyaXR5IGNvbnNpZGVyYXRp
b25zIHdpbGwgYmUgcHJvdmlkZWQgaW4gc29sdXRpb24NCiAgIHN0YW5kYXJkcyBhcyBhcHByb3By
aWF0ZSB0byB0aGUgZnVuY3Rpb24gZGVzY3JpYmVkDQogICBpbiBlYWNoIHNvbHV0aW9uIGRvY3Vt
ZW50Lg0KDQo1LiBBY2tub3dsZWRnZW1lbnRzDQoNCklzICJTZWN1cml0eSBBdXRvbWF0aW9uIiBj
b3B5cmlnaHRlZCBvciB0cmFkZW1hcmtlZD8gIFRoZSBmaXJzdCBwYXJhZ3JhcGggaXMgb2RkIGlm
IGl0IGlzIG5vdC4gIElmIGl0IGlzLCB0aGVuIGRpc2Nsb3N1cmVzIGFyZSBuZWVkZWQuICBCeSBo
YXZpbmcgdGhpcyBzZW50ZW5jZSBpbiB0aGUgZHJhZnQsIHNvbWUgdHlwZSBvZiBkaXNjbG9zdXJl
IG1heSBiZSBuZWVkZWQgc28gcGVvcGxlIHVuZGVyc3RhbmQgd2h5IGl0IGlzIHRoZXJlIGFzIHRo
ZXJlIGFyZSBtYW55IGluc3RhbmNlcyBvZiBzZWN1cml0eSBhdXRvbWF0aW9uIGJ5IHZlbmRvcnMg
YW5kIGdyb3VwcyBsaWtlIElDQVNJIGFuZCBUQ0cuDQoNCi0tDQoNCkJlc3QgcmVnYXJkcywNCkth
dGhsZWVuDQo=

--_000_DM2PR09MB02244B4EEC73876F534D6676F02C0DM2PR09MB0224namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQs
IHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5
bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVm
YXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxv
OmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwh
W2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZs
aW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+S2F0aGxl
ZW4sPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj5UaGFua3MgZm9yIHRoZSBmZWVkYmFjayBhbmQgZm9yIHlvdXIgZWZmb3J0
cyB3aXRoIHRoZSBJRVNHIG9uIG1vdmluZyB0aGlzIGZvcndhcmQuIEnigJlsbCB3b3JrIG9uIGEg
cmV2aXNpb24gQVNBUC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+RGF2ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBz
YWNtIFttYWlsdG86c2FjbS1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5L
YXRobGVlbiBNb3JpYXJ0eTxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIEZlYnJ1YXJ5IDE2LCAy
MDE1IDEwOjU0IEFNPGJyPg0KPGI+VG86PC9iPiBzYWNtQGlldGYub3JnPGJyPg0KPGI+U3ViamVj
dDo8L2I+IFtzYWNtXSBBRCBSZXZpZXcgb2YgU0FDTSBVc2UgQ2FzZSBEcmFmdDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhlbGxvLDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIGZvbGxvd2luZyBpcyBteSByZXZpZXcgb2YgdGhl
IFNBQ00gdXNlIGNhc2UgZHJhZnQuJm5ic3A7IFNpbmNlIHRoaXMgaXMgYSBjaGFydGVkIGl0ZW0g
YW5kIG1pbGVzdG9uZSBmb3IgU0FDTSwgdGhlIHdvcmsgY2FuIHByb2NlZWQuJm5ic3A7IEEgc3Rh
dGVtZW50IGZyb20gdGhlIElFU0cgb24gdXNlIGNhc2UgZHJhZnRzIHdpbGwgYmUgY29taW5nIG91
dCBzb29uLCB0aGFua3MgdG8gdGhvc2UgdGhhdCBhc3Npc3RlZCBpbiBidWlsZGluZw0KIGFyZ3Vt
ZW50cy48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5TQUNNIHVzZSBjYXNlIGRyYWZ0OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5JbnRyb2R1Y3Rpb246PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TZWNvbmQgc2VudGVuY2UgLSBzaG91bGQgdGhp
cyBiZSBhIGJ1bGxldGVkIGxpc3Qgb3IgYmUgbXVsdGlwbGUgc2VudGVuY2VzPzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO0l0
IHByb3ZpZGVzIGEgZGlzY3Vzc2lvbiBvZjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO3RoZXNlIHVzZSBjYXNlcyBhbmQgYXNz
b2NpYXRlZCBidWlsZGluZyBibG9jayBjYXBhYmlsaXRpZXMgdGhhdDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO3N1cHBvcnQg
c2VjdXJlbHkgYWdncmVnYXRpbmcgY29uZmlndXJhdGlvbiBhbmQgb3BlcmF0aW9uYWwgZGF0YSBh
bmQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZu
YnNwOyAmbmJzcDtldmFsdWF0aW5nIHRoYXQgZGF0YSB0byBkZXRlcm1pbmUgdGhlIHNlY3VyaXR5
IHBvc3R1cmUgb2YgaW5kaXZpZHVhbDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO2VuZHBvaW50cywgYW5kLCBpbiB0aGUgYWdn
cmVnYXRlLCB0aGUgc2VjdXJpdHkgcG9zdHVyZSBvZiBhbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO2VudGVycHJpc2UuJm5i
c3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjJuZCBwYXJhZ3JhcGgsIDFzdCBzZW50ZW5jZSwgJnF1b3Q7aW5mb3JtYXRpb24mcXVvdDsgaXMg
cmVkdW5kYW50OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7ICZuYnNwO1RoZXNlIHVzZSBjYXNlcyBhbmQgdXNhZ2Ugc2NlbmFyaW9zIGNy
b3NzIG1hbnkgSVQgc2VjdXJpdHk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtpbmZvcm1hdGlvbiBkb21haW5zLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGVyZSBhcmUg
bG90cyBvZiByZWFsbHkgbG9uZyBzZW50ZW5jZXMsIGxhc3Qgc2VudGVuY2Ugb2YgM3JkIHBhcmFn
cmFwaCBpcyAmbmJzcDtydW4tb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlNlY3Rpb24gMi4yLjI8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNhbiB5b3UgYnJlYWsgdGhpcyBzZW50ZW5jZSBp
bnRvIGEgZmV3PzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7ICZuYnNwO1VzaW5nIHRoZSBjb2xsZWN0ZWQgaGFyZHdhcmUgYW5kIHNvZnR3
YXJlIGludmVudG9yeSBkYXRhIGFuZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO2Fzc29jaWF0ZWQgYXNzZXQgY2hhcmFjdGVy
aXphdGlvbiBkYXRhIHRoYXQgbWF5IGluZGljYXRlIHRoZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO29yZ2FuaXphdGlvbmFs
IGRlZmluZWQgZnVuY3Rpb25zIG9mIGVhY2ggZW5kcG9pbnQsIGNoZWNrbGlzdCBndWlkYW5jZTxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7
ICZuYnNwO2lzIHF1ZXJpZWQsIGxvY2F0ZWQgYW5kIGRvd25sb2FkZWQgZnJvbSB0aGUgYXBwcm9w
cmlhdGUgdmVuZG9yIGFuZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOzNyZC1wYXJ0eSBzZWN1cml0eSBhdXRvbWF0aW9uIGRh
dGEgc3RvcmUgZm9yIHRoZSBhcHByb3ByaWF0ZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO2NoZWNrbGlzdHMuICZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TYW1l
IHNlY3Rpb24sIGZvbGxvd2luZyBzZW50ZW5jZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwO1doaWxlIHNwZWNpZmljIGFwcGxpY2F0aW9u
cyBmb3IgY2hlY2tsaXN0cyByZXN1bHRzIGFyZSBvdXQtb2Ytc2NvcGU8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPnMvY2hlY2tsaXN0cy9jaGVja2xp
c3QvPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkFuZCBJIGRvbid0IHJlYWxseSBmb2xsb3cgdGhlIGxvZ2ljIG9mIHRoZSBmdWxsIHRyYW5zaXRp
b25hbCBzZW50ZW5jZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtXaGlsZSBzcGVjaWZpYyBhcHBsaWNhdGlvbnMgZm9yIGNo
ZWNrbGlzdHMgcmVzdWx0cyBhcmUgb3V0LW9mLXNjb3BlPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7Zm9yIGN1cnJlbnQgU0FD
TSBlZmZvcnRzLCBob3cgdGhlIGRhdGEgaXMgdXNlZCBtYXkgaWxsdW1pbmF0ZTxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO3Nw
ZWNpZmljIGxhdGVuY3kgYW5kIGJhbmR3aWR0aCByZXF1aXJlbWVudHMuJm5ic3A7IEZvciB0aGlz
IHB1cnBvc2UgdXNlIG9mPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7Y2hlY2tsaXN0IGFzc2Vzc21lbnQgcmVzdWx0cyBtYXkg
aW5jbHVkZSwgYnV0IGFyZSBub3QgbGltaXRlZCB0bzo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q291bGQgeW91IGludHJvZHVjZSBsYXRlbmN5
IGFuZCBiYW5kd2lkdGggaW4gYSBkaWZmZXJlbnQgd2F5PyZuYnNwOyBJdCBzZWVtcyBvZGQgdG8g
Zm9sbG93IGZyb20gZGVzY3JpcHRpb25zIG9uIHR5cGVzIG9mIGNoZWNrbGlzdHMgKG9yICdhcHBs
aWNhdGlvbnMgb2YgY2hlY2tsaXN0cycpLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Ob3cgdGhhdCBJIHJlYWQgdGhlIHR5cGVzIG9mIGNoZWNr
bGlzdHMgYW5kIGhvdyB2YXJpZWQgdGhleSBhcmUsIEkgdGhpbmsgaXQgbWF5IGJlIGJldHRlciB0
byBkZWxldGUgdGhlIHRyYW5zaXRpb25hbCBzZW50ZW5jZSBsaXN0ZWQgYWJvdmUgYXMgdGhlcmUg
YXJlIG1hbnkgb3RoZXIgdHlwZXMgb2YgY2hlY2tsaXN0cyBpbmNsdWRlZCBpbiB0aGUgbGlzdCB0
aGF0IGZvbGxvd3MuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlNlY3Rpb24gMi4yLjQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkNvdWxkIHlvdSBtYWtlIGl0IG1vcmUgY2xlYXIgdGhhdCB0aGUg
cXVlcnkgbWVjaGFuaXNtIGRlc2NyaWJlZCBpbnQgaGlzIHNlY3Rpb24gaXMgdG8gYmUgcHJvdmlk
ZWQgYnkgU0FDTT8mbmJzcDsgSSBhc3N1bWUgdGhhdCBpcyB0aGUgY2FzZS4mbmJzcDsgVGhpcyBt
YXkgY29tZSB1cCBpbiBvdGhlciByZXZpZXdzLCB3aHkgaXMgdGhlIHNlY3Rpb24gaGVyZSBpZiBp
dCBkb2Vzbid0IHVzZSBTQUNNLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5TZWN0aW9uIDQsIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zLjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSByZWNvbW1l
bmQgcmVwbGFjaW5nIHRoZSBmb2xsb3dpbmcgc2VudGVuY2U6PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7V2hpbGUgaXQgaXMg
YWJvdXQgc2VjdXJpdHksIGl0IGRvZXMgbm90IGFmZmVjdDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO3NlY3VyaXR5LjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+d2l0aCBzb21l
dGhpbmcgdGhhdCBleHBsYWlucyB3aGVyZSB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgd2ls
bCBiZSBhZGRyZXNzZWQuJm5ic3A7IFNvbWV0aGluZyBsaWtlOjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO1NlY3VyaXR5IGNv
bnNpZGVyYXRpb25zIHdpbGwgYmUgcHJvdmlkZWQgaW4gc29sdXRpb248bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtzdGFuZGFy
ZHMgYXMgYXBwcm9wcmlhdGUgdG8gdGhlIGZ1bmN0aW9uIGRlc2NyaWJlZDxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO2luIGVh
Y2ggc29sdXRpb24gZG9jdW1lbnQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjUuIEFja25vd2xlZGdlbWVudHM8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SXMgJnF1b3Q7U2VjdXJpdHkgQXV0
b21hdGlvbiZxdW90OyBjb3B5cmlnaHRlZCBvciB0cmFkZW1hcmtlZD8mbmJzcDsgVGhlIGZpcnN0
IHBhcmFncmFwaCBpcyBvZGQgaWYgaXQgaXMgbm90LiZuYnNwOyBJZiBpdCBpcywgdGhlbiBkaXNj
bG9zdXJlcyBhcmUgbmVlZGVkLiZuYnNwOyBCeSBoYXZpbmcgdGhpcyBzZW50ZW5jZSBpbiB0aGUg
ZHJhZnQsIHNvbWUgdHlwZSBvZiBkaXNjbG9zdXJlIG1heSBiZSBuZWVkZWQgc28gcGVvcGxlIHVu
ZGVyc3RhbmQgd2h5DQogaXQgaXMgdGhlcmUgYXMgdGhlcmUgYXJlIG1hbnkgaW5zdGFuY2VzIG9m
IHNlY3VyaXR5IGF1dG9tYXRpb24gYnkgdmVuZG9ycyBhbmQgZ3JvdXBzIGxpa2UgSUNBU0kgYW5k
IFRDRy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLSA8
bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVzdCByZWdhcmRz
LDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+S2F0
aGxlZW48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_DM2PR09MB02244B4EEC73876F534D6676F02C0DM2PR09MB0224namp_--


From nobody Fri Feb 20 02:46:34 2015
Return-Path: <Carolin.Latze@swisscom.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBDB11A8841 for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 02:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Hu1mh9xlz_Db for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 02:46:30 -0800 (PST)
Received: from mail.swisscom.com (outmail100.swisscom.com [193.222.81.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E808A1A883D for <sacm@ietf.org>; Fri, 20 Feb 2015 02:46:29 -0800 (PST)
Received: by mail.swisscom.com; Fri, 20 Feb 2015 11:46:26 +0100
From: <Carolin.Latze@swisscom.com>
To: <adam.w.montville@gmail.com>, <sacm@ietf.org>
Thread-Topic: [sacm] Fwd: Your WebEx recording is available for viewing: SACM-20150209 1504-1
Thread-Index: AQHQRhNGx2FgHPQAn0emV+Oo4+6Bupz5aMcA
Date: Fri, 20 Feb 2015 10:46:25 +0000
Message-ID: <D10CCED2.1B57D%carolin.latze@swisscom.com>
References: <3B99D2BA-2B3D-4160-BB19-B560F604FA50@amsl.com> <819CF3A8-253D-416D-8148-6194245FC9A3@gmail.com>
In-Reply-To: <819CF3A8-253D-416D-8148-6194245FC9A3@gmail.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [138.190.134.9]
Content-Type: multipart/alternative; boundary="_000_D10CCED21B57Dcarolinlatzeswisscomcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/ZRytt-WRZF2_Or422GZfuV4Zf3w>
Subject: Re: [sacm] Fwd: Your WebEx recording is available for viewing: SACM-20150209 1504-1
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 10:46:33 -0000

--_000_D10CCED21B57Dcarolinlatzeswisscomcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Adam

Would it be possible to store that recording on the dropbox share as well? =
That would allow me to watch it offline.

Best regards
Carolin
From: "Adam W. Montville" <adam.w.montville@gmail.com<mailto:adam.w.montvil=
le@gmail.com>>
Date: Wednesday 11 February 2015 16:55
To: "sacm@ietf.org<mailto:sacm@ietf.org>" <sacm@ietf.org<mailto:sacm@ietf.o=
rg>>
Subject: [sacm] Fwd: Your WebEx recording is available for viewing: SACM-20=
150209 1504-1

FYI.

Begin forwarded message:

From: Cindy Morgan <cmorgan@amsl.com<mailto:cmorgan@amsl.com>>
Subject: Fwd: Your WebEx recording is available for viewing: SACM-20150209 =
1504-1
Date: February 11, 2015 at 8:28:00 AM CST
To: Dan Romascanu <dromasca@avaya.com<mailto:dromasca@avaya.com>>, "Adam W.=
 Montville" <adam.w.montville@gmail.com<mailto:adam.w.montville@gmail.com>>



Begin forwarded message:

From: messenger@webex.com<mailto:messenger@webex.com>
Date: February 11, 2015 1:08:41 AM PST
To: cmorgan@amsl.com<mailto:cmorgan@amsl.com>
Subject: Your WebEx recording is available for viewing: SACM-20150209 1504-=
1
Reply-To: messenger@webex.com<mailto:messenger@webex.com>


Hi, Cindy Morgan,

Your recording is now available on your WebEx site.


SACM-20150209 1504-1
Monday, February 9, 2015
7:04 am | Pacific Standard Time (San Francisco, GMT-08:00)


PLAY RECORDING (42 hr 0 min 38 sec)
https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899aba4=
1bdd6d3e96

You can forward this message to others to allow them to play back the recor=
ding.



--_000_D10CCED21B57Dcarolinlatzeswisscomcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <19BA9C0889B3214B88E10F598F5F2D0C@swisscom.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>
<div>
<div>Hi Adam</div>
<div><br>
</div>
<div>Would it be possible to store that recording on the dropbox share as w=
ell? That would allow me to watch it offline.</div>
<div><br>
</div>
<div>Best regards</div>
<div>Carolin</div>
</div>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Adam W. Montville&quot;=
 &lt;<a href=3D"mailto:adam.w.montville@gmail.com">adam.w.montville@gmail.c=
om</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday 11 February 2015 16=
:55<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:sacm@ie=
tf.org">sacm@ietf.org</a>&quot; &lt;<a href=3D"mailto:sacm@ietf.org">sacm@i=
etf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[sacm] Fwd: Your WebEx rec=
ording is available for viewing: SACM-20150209 1504-1<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
FYI.<br class=3D"">
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif; color: rgb(0, 0, 0);" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D"">Cindy Morgan &lt;<a href=3D"mailto:cm=
organ@amsl.com" class=3D"">cmorgan@amsl.com</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif; color: rgb(0, 0, 0);" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D""><b class=3D"">Fwd: Your WebEx recordi=
ng is available for viewing: SACM-20150209 1504-1</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif; color: rgb(0, 0, 0);" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D"">February 11, 2015 at 8:28:00 AM CST<b=
r class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif; color: rgb(0, 0, 0);" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D"">Dan Romascanu &lt;<a href=3D"mailto:d=
romasca@avaya.com" class=3D"">dromasca@avaya.com</a>&gt;, &quot;Adam W. Mon=
tville&quot; &lt;<a href=3D"mailto:adam.w.montville@gmail.com" class=3D"">a=
dam.w.montville@gmail.com</a>&gt;<br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; " class=3D"">
<br class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite" class=3D"">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">From:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><a href=3D"mailto:messenger@webex.com" class=3D"">messenger@webex.co=
m</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">Date:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D"">February 11, 2015 1:08:41 AM PST<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">To:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><a href=3D"mailto:cmorgan@amsl.com" class=3D"">cmorgan@amsl.com</a><=
br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">Subject:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><b class=3D"">Your WebEx recording is available for viewing: SACM-20=
150209 1504-1</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">Reply-To:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><a href=3D"mailto:messenger@webex.com" class=3D"">messenger@webex.co=
m</a><br class=3D"">
</span></div>
<br class=3D"">
<font face=3D"Tahoma,Arial,sans-serif,Helvetica,Geneva" size=3D"2" class=3D=
""><br class=3D"">
Hi, Cindy Morgan, <br class=3D"">
<br class=3D"">
Your recording is now available on your WebEx site. <br class=3D"">
<br class=3D"">
<br class=3D"">
SACM-20150209 1504-1 <br class=3D"">
Monday, February 9, 2015 <br class=3D"">
7:04 am | Pacific Standard Time (San Francisco, GMT-08:00) <br class=3D"">
<br class=3D"">
<br class=3D"">
PLAY RECORDING (42 hr 0 min 38 sec) <br class=3D"">
<a href=3D"https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b826=
6453899aba41bdd6d3e96" target=3D"_blank" class=3D"">https://workgreen.webex=
.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899aba41bdd6d3e96</a><br class=
=3D"">
<br class=3D"">
You can forward this message to others to allow them to play back the recor=
ding. <br class=3D"">
</font></blockquote>
</div>
<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</span>
</body>
</html>

--_000_D10CCED21B57Dcarolinlatzeswisscomcom_--


From nobody Fri Feb 20 06:36:46 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28F4C1A87D1; Fri, 20 Feb 2015 06:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 yWw_-4WTWZJN; Fri, 20 Feb 2015 06:36:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 76E301A8035; Fri, 20 Feb 2015 06:36:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150220143643.22973.45080.idtracker@ietfa.amsl.com>
Date: Fri, 20 Feb 2015 06:36:43 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/1Tii5FIAlPkqOlk_BjYJbifm-Bo>
Cc: sacm@ietf.org
Subject: [sacm] I-D Action: draft-ietf-sacm-information-model-01.txt
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 14:36:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Security Automation and Continuous Monitoring Working Group of the IETF.

        Title           : SACM Information Model
        Authors         : David Waltermire
                          Kim Watson
                          Clifford Kahn
                          Lisa Lorenzin
	Filename        : draft-ietf-sacm-information-model-01.txt
	Pages           : 81
	Date            : 2015-02-20

Abstract:
   This document proposes an information model for SACM.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sacm-information-model/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sacm-information-model-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sacm-information-model-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Feb 20 08:46:09 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 818A91A0113 for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 08:46:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 CoDtyiTzmgD0 for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 08:46:05 -0800 (PST)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8D9A1A00FE for <sacm@ietf.org>; Fri, 20 Feb 2015 08:46:04 -0800 (PST)
Received: by pdbnh10 with SMTP id nh10so8687098pdb.11 for <sacm@ietf.org>; Fri, 20 Feb 2015 08:46:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=lXLr/+yQdAx9ax697CD3RofbQTLjrYDIpSuDXQOWh6c=; b=CkPrZqrAQi4wnZh2ndvp0/CR19WDs8XMbx9xaktbVk3gLPQIC4/HO2xlljqn7ijQki a8vGgHe6IthDmgBYJaGiwLsZf5sjp2Jhtt2PVPQvy7PZZKt80fHV2z7P8x74VPWudOnP xA61Yye+iINdFi1ay/a1nC/9qhsFXPyDAagHmtXd+AdMPw1XBr7TS8jUDQMwhQ4xeD6P twPgUIZs8bs8eUUMqi1618arzS5tVKafyVQ6J9dIpKeGkICTLy3iECl/N3xjUdZ4DaQt /iOws3ZZPJbgDG20f8O7ZUlMfe8ypoAXX3Wqo4n6F3RIQOdgwK+i2RLfCZcwjNRiyG06 isxg==
X-Received: by 10.70.96.36 with SMTP id dp4mr18247150pdb.98.1424450764173; Fri, 20 Feb 2015 08:46:04 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:2927:817:22f9:d981? ([2602:306:3406:4f00:2927:817:22f9:d981]) by mx.google.com with ESMTPSA id c9sm26222135pdo.13.2015.02.20.08.46.02 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 08:46:03 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <2854C6B2-5204-4F30-85C2-9BADEAD2567C@gmail.com>
Date: Fri, 20 Feb 2015 10:45:22 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/0CUbmvXkqhyng9Zjqj0DCivHzio>
Subject: [sacm] Endpoint ID Design Team Meeting Notes: 2015-02-20
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 16:46:07 -0000

SACM Endpoint ID Design Team Notes
2015-02-20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

Agenda

	Reminder:
		- WebEx Chat and SACM Jabber Room
		- Recording will be (is) enabled
	Endpoint ID Example Continued
		- Orientation on Information Model draft
		- Continued Provenance Discussion
			- Virtual Interim Considerations
			- W3C investigation considerations
	Next Steps
		- See Below

Attendees
	Clifford Kahn
	Danny Haynes
	David Waltermire
	Jessica Fitzgerald-McKay
	Jim Bieda
	Adam Montville
	Henk Birkholz
	Ron Colvin


Overview
=3D=3D=3D=3D=3D=3D=3D=3D
Cliff and Dave worked throughout the week on updating the Information =
Model draft and Cliff posted an update (-01) just this morning (thank =
you!!).  Most of the changes have been capatured in section 1.1 "Changes =
in Revision 01".  We are orienting on the changes that have been made to =
the Information Model. =20

(Contentious points are noted herein, otherwise you're encouraged to =
review the -01 draft as posted.)

There was a brief discussion recognizing that, at the point of =
collection, an attribute is simply an "endpoint attribute".  However, =
when that information is used or relied upon, it may be classified based =
on context to be "posture attribute", "identity attribute", or (perhaps =
later) some other attribute type.

We are discussing a concern about identities.  We might have an identity =
of a user rather than the endpoint.  If we call that an endpoint =
identity, we'd be incorrect because it's an attribute collected from the =
endpoint but not pertaining to the identity of the endpoint - it =
pertains to the identity of the user interacting with that endpoint.

Cliff and Henk are discussing network interfaces and whether they're =
useful for identifying endpoints.  I'm not sure where this discussion =
ended up, but there's something that needs to be considered here (about =
35 minutes in to the discussion).

Do we want to comment on the "normativeness" of the diagram in the =
Information Model?  We have a lot of verbose text, and a lot of that =
text is expressed in the diagram.  Provided the diagram is clear and not =
subject to misinterpretation, then we might consdier this approach.  The =
diagram appears to be in UML format, but there are "ASCII" adaptations =
that may need to first be explained (e.g. define some ASCII notations in =
UML terms).

Jessica is bringing up a metapoint about the diagram.  She's proposing =
that a diagram may not be the best way to express this stuff.  Some =
other information models don't use diagrams except in the component =
model.  Perhaps words or pseudo-code would be better?  This is ONLY =
something to consider at this point - whether we have a "how to read =
this diagram" section, or use it in an "informative only" capacity =
remains to be determined.

We might consider breaking this ASCII diagram apart or using a more =
robust pictorial method and posting that to the Wiki as an informative =
reference.  We might also no longer be limited to ASCII art, which could =
be very useful (Adam will need to look into this).

Do we want to model "account" as part of endpoint identity?  This is =
useful, perhaps, for targeting scenarios (find all servers where =
"account x" has logged in, or has an account established).  This may be =
more "behavioral" than it is "posture" related, and the discussion needs =
to be had to consider whether this aspect is in scope now or later.

If we try to follow the PROV information model, we're running the risk =
of being sucked into a swamp.  As Cliff put it, if we do it the PROV =
way, we're going to carry some frieght.  The notion here is that W3C =
PROV may not be relied upon at this point.  It's not a matter of using =
pieces of it, but it's a matter of what we can do.





Future Discussion Points
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Discuss identification information from bios/firmware (e.g. =
serial numbers, asset tags, VM id) that can be queried on the device =
using software
	* Provenance information from W3C PROV
	* Is "account" as an identity attribute in scope?
	* Should *the* ASCII diagram survive as-is, or should it be =
replaced (with something more robust) or broken apart?  Is the diagram =
something we want to explicitly state as being normative?



NEXT STEPS (Agenda Items to track)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* "Pruny" discussions: Account (above), "Primary" identity =
attributes (what's sufficient).
		- Desired characteristics of primary attributes
	* Discuss identification information from bios/firmware (e.g. =
serial numbers, asset tags, VM id) that can be queried on the device =
using software
	* W3C PROV Homework/Overview






From nobody Fri Feb 20 08:52:22 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C95931A1B80 for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 08:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 NdwzMt0QMa4x for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 08:52:05 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38B8D1A1BAC for <sacm@ietf.org>; Fri, 20 Feb 2015 08:52:04 -0800 (PST)
Received: by paceu11 with SMTP id eu11so9239094pac.10 for <sacm@ietf.org>; Fri, 20 Feb 2015 08:52:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=GOc3fk7qQEiKnZwOIy7n/si2dfgU9iqdjwUPaETg3Cg=; b=E5O2lpvO1wHKn2z9GxuXWZq9uMTsbvD9pRWnbjAFfxLBD6v7JiI6h6//gCHyX2oO8O HqkyYZ4IqNVDlfHqkdp3MUu4ztZss6t8YwWhM+BDjFOb5l56sKFQn7/JFm3aUYAUdiPa d0VRLAcCmrHETkFI8odkaRapvcBh2uE+GlCE5gQ8zBKtZOf674yEbaAd/OwK0US9MCxi 88w4rtl+APGFZh6vWcVBMksathN37qyDBKEtwqbe5HEBqaUGN7E9gS9jL2kzY6JjfMKA U+qmMg5Xz4y3w58YEyx2rw6AvmG02WU5Gw5EhgBZ5WVfnvEXW5QnkEbcGi5+95kSygCE KCnQ==
X-Received: by 10.68.200.134 with SMTP id js6mr18434915pbc.55.1424451123395; Fri, 20 Feb 2015 08:52:03 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:2927:817:22f9:d981? ([2602:306:3406:4f00:2927:817:22f9:d981]) by mx.google.com with ESMTPSA id zd14sm12776300pab.20.2015.02.20.08.52.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 08:52:02 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_453193B5-4337-446F-A1FC-E609D202C844"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: "Adam W. Montville" <adam.w.montville@gmail.com>
In-Reply-To: <D10CCED2.1B57D%carolin.latze@swisscom.com>
Date: Fri, 20 Feb 2015 10:51:22 -0600
Message-Id: <4109684D-B906-4B91-829C-E1F0FEB1C1B6@gmail.com>
References: <3B99D2BA-2B3D-4160-BB19-B560F604FA50@amsl.com> <819CF3A8-253D-416D-8148-6194245FC9A3@gmail.com> <D10CCED2.1B57D%carolin.latze@swisscom.com>
To: Carolin.Latze@swisscom.com
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/8BfMb78kKZwjmi4vyMFpJ5BBoNE>
Cc: sacm@ietf.org
Subject: Re: [sacm] Your WebEx recording is available for viewing: SACM-20150209 1504-1
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 16:52:12 -0000

--Apple-Mail=_453193B5-4337-446F-A1FC-E609D202C844
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Carolin,

I have uploaded the file to: =
https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0 =
<https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0> (this is the same location used for the Endpoint ID Design =
recordings).

If anyone has suggestions about where to store these files other than my =
Dropbox account (e.g. how to get them on the Wiki), I=E2=80=99m all =
ears.

Kind regards,

Adam

> On Feb 20, 2015, at 4:46 AM, Carolin.Latze@swisscom.com wrote:
>=20
> Hi Adam
>=20
> Would it be possible to store that recording on the dropbox share as =
well? That would allow me to watch it offline.
>=20
> Best regards
> Carolin
> From: "Adam W. Montville" <adam.w.montville@gmail.com =
<mailto:adam.w.montville@gmail.com>>
> Date: Wednesday 11 February 2015 16:55
> To: "sacm@ietf.org <mailto:sacm@ietf.org>" <sacm@ietf.org =
<mailto:sacm@ietf.org>>
> Subject: [sacm] Fwd: Your WebEx recording is available for viewing: =
SACM-20150209 1504-1
>=20
> FYI.
>=20
>> Begin forwarded message:
>>=20
>> From: Cindy Morgan <cmorgan@amsl.com <mailto:cmorgan@amsl.com>>
>> Subject: Fwd: Your WebEx recording is available for viewing: =
SACM-20150209 1504-1
>> Date: February 11, 2015 at 8:28:00 AM CST
>> To: Dan Romascanu <dromasca@avaya.com <mailto:dromasca@avaya.com>>, =
"Adam W. Montville" <adam.w.montville@gmail.com =
<mailto:adam.w.montville@gmail.com>>
>>=20
>>=20
>>=20
>> Begin forwarded message:
>>=20
>>> From: messenger@webex.com <mailto:messenger@webex.com>
>>> Date: February 11, 2015 1:08:41 AM PST
>>> To: cmorgan@amsl.com <mailto:cmorgan@amsl.com>
>>> Subject: Your WebEx recording is available for viewing: =
SACM-20150209 1504-1
>>> Reply-To: messenger@webex.com <mailto:messenger@webex.com>
>>>=20
>>>=20
>>> Hi, Cindy Morgan,=20
>>>=20
>>> Your recording is now available on your WebEx site.=20
>>>=20
>>>=20
>>> SACM-20150209 1504-1=20
>>> Monday, February 9, 2015=20
>>> 7:04 am | Pacific Standard Time (San Francisco, GMT-08:00)=20
>>>=20
>>>=20
>>> PLAY RECORDING (42 hr 0 min 38 sec)=20
>>> =
https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899aba=
41bdd6d3e96 =
<https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899ab=
a41bdd6d3e96>
>>>=20
>>> You can forward this message to others to allow them to play back =
the recording.=20
>>=20
>=20


--Apple-Mail=_453193B5-4337-446F-A1FC-E609D202C844
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Carolin,<div class=3D""><br class=3D""></div><div =
class=3D"">I have uploaded the file to:&nbsp;<a =
href=3D"https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu=
_a?dl=3D0" =
class=3D"">https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3=
bRu_a?dl=3D0</a>&nbsp;(this is the same location used for the Endpoint =
ID Design recordings).</div><div class=3D""><br class=3D""></div><div =
class=3D"">If anyone has suggestions about where to store these files =
other than my Dropbox account (e.g. how to get them on the Wiki), I=E2=80=99=
m all ears.</div><div class=3D""><br class=3D""></div><div class=3D"">Kind=
 regards,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Adam</div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Feb 20, 2015, at 4:46 AM, <a =
href=3D"mailto:Carolin.Latze@swisscom.com" =
class=3D"">Carolin.Latze@swisscom.com</a> wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii" class=3D"">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; font-size: 14px; font-family: =
Calibri, sans-serif;" class=3D"">
<div class=3D"">
<div class=3D"">
<div class=3D"">Hi Adam</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Would it be possible to store that recording on the =
dropbox share as well? That would allow me to watch it offline.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Best regards</div>
<div class=3D"">Carolin</div>
</div>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; =
border-width: 1pt medium medium; border-style: solid none none; padding: =
3pt 0in 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>"Adam W. =
Montville" &lt;<a href=3D"mailto:adam.w.montville@gmail.com" =
class=3D"">adam.w.montville@gmail.com</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Wednesday 11 =
February 2015 16:55<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>"<a =
href=3D"mailto:sacm@ietf.org" class=3D"">sacm@ietf.org</a>" &lt;<a =
href=3D"mailto:sacm@ietf.org" class=3D"">sacm@ietf.org</a>&gt;<br =
class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>[sacm] Fwd: =
Your WebEx recording is available for viewing: SACM-20150209 1504-1<br =
class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
FYI.<br class=3D"">
<div class=3D""><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', =
Helvetica, sans-serif;" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica =
Neue', Helvetica, sans-serif;" class=3D"">Cindy Morgan &lt;<a =
href=3D"mailto:cmorgan@amsl.com" class=3D"">cmorgan@amsl.com</a>&gt;<br =
class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', =
Helvetica, sans-serif;" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica =
Neue', Helvetica, sans-serif;" class=3D""><b class=3D"">Fwd: Your WebEx =
recording is available for viewing: SACM-20150209 1504-1</b><br =
class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', =
Helvetica, sans-serif;" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica =
Neue', Helvetica, sans-serif;" class=3D"">February 11, 2015 at 8:28:00 =
AM CST<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', =
Helvetica, sans-serif;" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica =
Neue', Helvetica, sans-serif;" class=3D"">Dan Romascanu &lt;<a =
href=3D"mailto:dromasca@avaya.com" class=3D"">dromasca@avaya.com</a>&gt;, =
"Adam W. Montville" &lt;<a href=3D"mailto:adam.w.montville@gmail.com" =
class=3D"">adam.w.montville@gmail.com</a>&gt;<br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; " class=3D"">
<br class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite" class=3D"">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">From:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" =
class=3D""><a href=3D"mailto:messenger@webex.com" =
class=3D"">messenger@webex.com</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">Date:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" =
class=3D"">February 11, 2015 1:08:41 AM PST<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">To:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" =
class=3D""><a href=3D"mailto:cmorgan@amsl.com" =
class=3D"">cmorgan@amsl.com</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">Subject:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" =
class=3D""><b class=3D"">Your WebEx recording is available for viewing: =
SACM-20150209 1504-1</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b =
class=3D"">Reply-To:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" =
class=3D""><a href=3D"mailto:messenger@webex.com" =
class=3D"">messenger@webex.com</a><br class=3D"">
</span></div>
<br class=3D"">
<font face=3D"Tahoma,Arial,sans-serif,Helvetica,Geneva" size=3D"2" =
class=3D""><br class=3D"">
Hi, Cindy Morgan, <br class=3D"">
<br class=3D"">
Your recording is now available on your WebEx site. <br class=3D"">
<br class=3D"">
<br class=3D"">
SACM-20150209 1504-1 <br class=3D"">
Monday, February 9, 2015 <br class=3D"">
7:04 am | Pacific Standard Time (San Francisco, GMT-08:00) <br class=3D"">=

<br class=3D"">
<br class=3D"">
PLAY RECORDING (42 hr 0 min 38 sec) <br class=3D"">
<a =
href=3D"https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b82664=
53899aba41bdd6d3e96" target=3D"_blank" =
class=3D"">https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b82=
66453899aba41bdd6d3e96</a><br class=3D"">
<br class=3D"">
You can forward this message to others to allow them to play back the =
recording. <br class=3D"">
</font></blockquote>
</div>
<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</span>
</div>

</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_453193B5-4337-446F-A1FC-E609D202C844--


From nobody Fri Feb 20 08:56:01 2015
Return-Path: <Carolin.Latze@swisscom.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0F11A1BDB for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 08:55:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 3sXPqAMllVt5 for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 08:55:55 -0800 (PST)
Received: from mail.swisscom.com (outmail100.swisscom.com [193.222.81.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B9411A1BA5 for <sacm@ietf.org>; Fri, 20 Feb 2015 08:55:40 -0800 (PST)
Received: by mail.swisscom.com; Fri, 20 Feb 2015 17:55:38 +0100
From: <Carolin.Latze@swisscom.com>
To: <adam.w.montville@gmail.com>
Thread-Topic: [sacm] Your WebEx recording is available for viewing: SACM-20150209 1504-1
Thread-Index: AQHQTS2Su9xeWFTnskON78pj6M5DeZz5wbwA
Date: Fri, 20 Feb 2015 16:55:37 +0000
Message-ID: <D10D257D.1B638%carolin.latze@swisscom.com>
References: <3B99D2BA-2B3D-4160-BB19-B560F604FA50@amsl.com> <819CF3A8-253D-416D-8148-6194245FC9A3@gmail.com> <D10CCED2.1B57D%carolin.latze@swisscom.com> <4109684D-B906-4B91-829C-E1F0FEB1C1B6@gmail.com>
In-Reply-To: <4109684D-B906-4B91-829C-E1F0FEB1C1B6@gmail.com>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [138.190.134.7]
Content-Type: multipart/alternative; boundary="_000_D10D257D1B638carolinlatzeswisscomcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/T1fYN49fdyW83OMtDxCRaujNp4s>
Cc: sacm@ietf.org
Subject: Re: [sacm] Your WebEx recording is available for viewing: SACM-20150209 1504-1
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 16:55:59 -0000

--_000_D10D257D1B638carolinlatzeswisscomcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Adam

Thanks a lot. Very much appreciated. And unfortunately I cannot provide a b=
etter location.

Best regards
Carolin
From: "Adam W. Montville" <adam.w.montville@gmail.com<mailto:adam.w.montvil=
le@gmail.com>>
Date: Friday 20 February 2015 17:51
To: Carolin Latze <carolin.latze@swisscom.com<mailto:carolin.latze@swisscom=
.com>>
Cc: "sacm@ietf.org<mailto:sacm@ietf.org>" <sacm@ietf.org<mailto:sacm@ietf.o=
rg>>
Subject: Re: [sacm] Your WebEx recording is available for viewing: SACM-201=
50209 1504-1

Hi Carolin,

I have uploaded the file to: https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA=
2lzSwCFE_pfYMlpP3bRu_a?dl=3D0 (this is the same location used for the Endpo=
int ID Design recordings).

If anyone has suggestions about where to store these files other than my Dr=
opbox account (e.g. how to get them on the Wiki), I'm all ears.

Kind regards,

Adam

On Feb 20, 2015, at 4:46 AM, Carolin.Latze@swisscom.com<mailto:Carolin.Latz=
e@swisscom.com> wrote:

Hi Adam

Would it be possible to store that recording on the dropbox share as well? =
That would allow me to watch it offline.

Best regards
Carolin
From: "Adam W. Montville" <adam.w.montville@gmail.com<mailto:adam.w.montvil=
le@gmail.com>>
Date: Wednesday 11 February 2015 16:55
To: "sacm@ietf.org<mailto:sacm@ietf.org>" <sacm@ietf.org<mailto:sacm@ietf.o=
rg>>
Subject: [sacm] Fwd: Your WebEx recording is available for viewing: SACM-20=
150209 1504-1

FYI.

Begin forwarded message:

From: Cindy Morgan <cmorgan@amsl.com<mailto:cmorgan@amsl.com>>
Subject: Fwd: Your WebEx recording is available for viewing: SACM-20150209 =
1504-1
Date: February 11, 2015 at 8:28:00 AM CST
To: Dan Romascanu <dromasca@avaya.com<mailto:dromasca@avaya.com>>, "Adam W.=
 Montville" <adam.w.montville@gmail.com<mailto:adam.w.montville@gmail.com>>



Begin forwarded message:

From: messenger@webex.com<mailto:messenger@webex.com>
Date: February 11, 2015 1:08:41 AM PST
To: cmorgan@amsl.com<mailto:cmorgan@amsl.com>
Subject: Your WebEx recording is available for viewing: SACM-20150209 1504-=
1
Reply-To: messenger@webex.com<mailto:messenger@webex.com>


Hi, Cindy Morgan,

Your recording is now available on your WebEx site.


SACM-20150209 1504-1
Monday, February 9, 2015
7:04 am | Pacific Standard Time (San Francisco, GMT-08:00)


PLAY RECORDING (42 hr 0 min 38 sec)
https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899aba4=
1bdd6d3e96

You can forward this message to others to allow them to play back the recor=
ding.




--_000_D10D257D1B638carolinlatzeswisscomcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <2B489D564863CC488FD0F521FA2AC556@swisscom.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>
<div>
<div>Hi Adam</div>
<div><br>
</div>
<div>Thanks a lot. Very much appreciated. And unfortunately I cannot provid=
e a better location.</div>
<div><br>
</div>
<div>Best regards</div>
<div>Carolin</div>
</div>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Adam W. Montville&quot;=
 &lt;<a href=3D"mailto:adam.w.montville@gmail.com">adam.w.montville@gmail.c=
om</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 20 February 2015 17:51=
<br>
<span style=3D"font-weight:bold">To: </span>Carolin Latze &lt;<a href=3D"ma=
ilto:carolin.latze@swisscom.com">carolin.latze@swisscom.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:sacm@ie=
tf.org">sacm@ietf.org</a>&quot; &lt;<a href=3D"mailto:sacm@ietf.org">sacm@i=
etf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [sacm] Your WebEx reco=
rding is available for viewing: SACM-20150209 1504-1<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
Hi Carolin,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I have uploaded the file to:&nbsp;<a href=3D"https://www.dr=
opbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D0" class=3D"">h=
ttps://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D0<=
/a>&nbsp;(this is the same location used for the Endpoint
 ID Design recordings).</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">If anyone has suggestions about where to store these files =
other than my Dropbox account (e.g. how to get them on the Wiki), I&#8217;m=
 all ears.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Kind regards,</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Adam</div>
<div class=3D""><br class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Feb 20, 2015, at 4:46 AM, <a href=3D"mailto:Carolin.Latz=
e@swisscom.com" class=3D"">
Carolin.Latze@swisscom.com</a> wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; font-size: 14px; font-family: Calibri, sans-seri=
f;" class=3D"">
<div class=3D"">
<div class=3D"">
<div class=3D"">Hi Adam</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Would it be possible to store that recording on the dropbox=
 share as well? That would allow me to watch it offline.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Best regards</div>
<div class=3D"">Carolin</div>
</div>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" class=3D"">
<div style=3D"font-family: Calibri; font-size: 11pt; text-align: left; bord=
er-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0i=
n 0in; border-top-color: rgb(181, 196, 223);" class=3D"">
<span style=3D"font-weight:bold" class=3D"">From: </span>&quot;Adam W. Mont=
ville&quot; &lt;<a href=3D"mailto:adam.w.montville@gmail.com" class=3D"">ad=
am.w.montville@gmail.com</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Date: </span>Wednesday 11 Febru=
ary 2015 16:55<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">To: </span>&quot;<a href=3D"mai=
lto:sacm@ietf.org" class=3D"">sacm@ietf.org</a>&quot; &lt;<a href=3D"mailto=
:sacm@ietf.org" class=3D"">sacm@ietf.org</a>&gt;<br class=3D"">
<span style=3D"font-weight:bold" class=3D"">Subject: </span>[sacm] Fwd: You=
r WebEx recording is available for viewing: SACM-20150209 1504-1<br class=
=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;" class=3D"">
FYI.<br class=3D"">
<div class=3D""><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">From:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D"">Cindy Morgan &lt;<a href=3D"mailto:cm=
organ@amsl.com" class=3D"">cmorgan@amsl.com</a>&gt;<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">Subject:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D""><b class=3D"">Fwd: Your WebEx recordi=
ng is available for viewing: SACM-20150209 1504-1</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">Date:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D"">February 11, 2015 at 8:28:00 AM CST<b=
r class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: -webkit-system-font, 'Helvetica Neue', Helvetic=
a, sans-serif;" class=3D""><b class=3D"">To:
</b></span><span style=3D"font-family: -webkit-system-font, 'Helvetica Neue=
', Helvetica, sans-serif;" class=3D"">Dan Romascanu &lt;<a href=3D"mailto:d=
romasca@avaya.com" class=3D"">dromasca@avaya.com</a>&gt;, &quot;Adam W. Mon=
tville&quot; &lt;<a href=3D"mailto:adam.w.montville@gmail.com" class=3D"">a=
dam.w.montville@gmail.com</a>&gt;<br class=3D"">
</span></div>
<br class=3D"">
<div class=3D"">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; " class=3D"">
<br class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"">Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite" class=3D"">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">From:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><a href=3D"mailto:messenger@webex.com" class=3D"">messenger@webex.co=
m</a><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">Date:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D"">February 11, 2015 1:08:41 AM PST<br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">To:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><a href=3D"mailto:cmorgan@amsl.com" class=3D"">cmorgan@amsl.com</a><=
br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">Subject:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><b class=3D"">Your WebEx recording is available for viewing: SACM-20=
150209 1504-1</b><br class=3D"">
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;" class=3D"">
<span style=3D"font-family: Helvetica; font-size: inherit;" class=3D""><b c=
lass=3D"">Reply-To:
</b></span><span style=3D"font-family: Helvetica; font-size: inherit;" clas=
s=3D""><a href=3D"mailto:messenger@webex.com" class=3D"">messenger@webex.co=
m</a><br class=3D"">
</span></div>
<br class=3D"">
<font face=3D"Tahoma,Arial,sans-serif,Helvetica,Geneva" size=3D"2" class=3D=
""><br class=3D"">
Hi, Cindy Morgan, <br class=3D"">
<br class=3D"">
Your recording is now available on your WebEx site. <br class=3D"">
<br class=3D"">
<br class=3D"">
SACM-20150209 1504-1 <br class=3D"">
Monday, February 9, 2015 <br class=3D"">
7:04 am | Pacific Standard Time (San Francisco, GMT-08:00) <br class=3D"">
<br class=3D"">
<br class=3D"">
PLAY RECORDING (42 hr 0 min 38 sec) <br class=3D"">
<a href=3D"https://workgreen.webex.com/workgreen/lsr.php?RCID=3D06bdb21b826=
6453899aba41bdd6d3e96" target=3D"_blank" class=3D"">https://workgreen.webex=
.com/workgreen/lsr.php?RCID=3D06bdb21b8266453899aba41bdd6d3e96</a><br class=
=3D"">
<br class=3D"">
You can forward this message to others to allow them to play back the recor=
ding. <br class=3D"">
</font></blockquote>
</div>
<br class=3D"">
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</span></div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D10D257D1B638carolinlatzeswisscomcom_--


From nobody Fri Feb 20 15:39:35 2015
Return-Path: <ietf@augustcellars.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E291A0367 for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 15:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 cI0_FKvlgunD for <sacm@ietfa.amsl.com>; Fri, 20 Feb 2015 15:39:31 -0800 (PST)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFC7C1A017D for <sacm@ietf.org>; Fri, 20 Feb 2015 15:39:31 -0800 (PST)
Received: from Philemon (winery.augustcellars.com [206.212.239.129]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 4755F2C9F8; Fri, 20 Feb 2015 15:39:31 -0800 (PST)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <sacm@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com>
Date: Fri, 20 Feb 2015 15:38:40 -0800
Message-ID: <032f01d04d66$5b6b8380$12428a80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0330_01D04D23.4D4CB050"
X-Mailer: Microsoft Outlook 14.0
thread-index: AQGyIPN1R4PGvGs+u7kTeruCaEcoLJ02iqcQ
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/qSVhJVisk0uuhBx-Oy7biOTbcH8>
Subject: Re: [sacm] comments on draft-ietf-sacm-architecture-02
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 23:39:34 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0330_01D04D23.4D4CB050
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I am confused.   When are we sending these to the mailing list and when =
are we raising issues on github?  I don=E2=80=99t see any of these on =
github at the moment.

=20

Jim

=20

=20

From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Romascanu, Dan =
(Dan)
Sent: Thursday, February 12, 2015 6:19 AM
To: sacm@ietf.org
Subject: [sacm] comments on draft-ietf-sacm-architecture-02

=20

Hi,=20

=20

Please find below my comments on =
draft=E2=80=90ietf=E2=80=90sacm=E2=80=90architecture=E2=80=9002. I also  =
addressed in my comments some of the open questions raised in the I-D.=20

=20

1.       The first sentence contains a logical repetition =E2=80=93 the =
SACM reference architecture is obviously related to SACM (even if one is =
with acronyms expanded and the other is not). Please find some more =
inspiring words avoiding the repetition.

=20

2.       The open question at the end of Section 2:=20

=20

=C3=98  Why does the charter not suffice?

=C3=98  What is the purpose of inserting this section in this draft?

=20

The answer is that the charter is a temporary document visible and =
accessible while the WG is active (and subject to change during this =
period) but tends to disappeared when the WG is concluded. A recap of =
the problem statement in the introductory sections of the architecture =
document provides background information for the architecture that =
follows and can be very useful for understanding some of the fundamental =
decisions.=20

=20

3.       Editorial issues in Section 3.1.3:=20

=20

s/The introduction of the controller supports use cases/ The controller =
supports use cases/

s/Consumer=E2=80=99s/Consumers/

s/Provider=E2=80=99s/Providers/

s/interface =E2=80=9CC=E2=80=9D shown in Figure 1 demonstrates/ =
interface =E2=80=9CC=E2=80=9D shown in Figure 1 illustrates/

=20

4.       In order to understand the sentence =E2=80=98a controller may =
also provide the proxy or broker (and possibly routing) function in the =
data plane=E2=80=99 I went back to the terminology document.

=20

What I found is that the following terms are defined:=20

=20

        Broker - An entity providing and/or connecting services on the =
behalf of

      other architectural components.

        Proxy - An architectural component providing functions, =
information, or
      services on behalf of another component, which is not directly
      participating in the architecture.

=20

These definitions seem to need more work. They are partially redundant =
=E2=80=93 is this by design? Proxy is not =E2=80=98participating in the =
architecture=E2=80=99? Then how is it between the 2-3 fundamental =
functions of the controller? There needs to be more work in the =
terminology document I guess.=20

=20

5.  TODO =E2=80=90 add text around the usage of various protocols for =
endpoint

data collection (SNMP, NETCONF, etc.?)

=20

                do we really need these in an architecture document?=20

=20

Thanks and Regards,

=20

Dan

=20

=20

=20


------=_NextPart_000_0330_01D04D23.4D4CB050
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1241519810;
	mso-list-type:hybrid;
	mso-list-template-ids:-1301753184 -879462890 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Consolas;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1740131575;
	mso-list-type:hybrid;
	mso-list-template-ids:449746196 -10431972 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:=EF=83=98;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I am confused.=C2=A0=C2=A0 When are we sending =
these to the mailing list and when are we raising issues on =
github?=C2=A0 I don=E2=80=99t see any of these on github at the =
moment.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
sacm [mailto:sacm-bounces@ietf.org] <b>On Behalf Of </b>Romascanu, Dan =
(Dan)<br><b>Sent:</b> Thursday, February 12, 2015 6:19 AM<br><b>To:</b> =
sacm@ietf.org<br><b>Subject:</b> [sacm] comments on =
draft-ietf-sacm-architecture-02<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi, =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please find below my comments on =
draft=E2=80=90ietf=E2=80=90sacm=E2=80=90architecture=E2=80=9002. I also =
&nbsp;addressed in my comments some of the open questions raised in the =
I-D. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
first sentence contains a logical repetition =E2=80=93 the SACM =
reference architecture is obviously related to SACM (even if one is with =
acronyms expanded and the other is not). Please find some more inspiring =
words avoiding the repetition.<o:p></o:p></p><p =
class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
open question at the end of Section 2: <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo4;text-autospace:none'><![if !supportLists]><span =
style=3D'font-size:10.5pt;font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=C3=98<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Why does the charter not =
suffice?<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo4'><![if =
!supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=C3=98<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.5pt;font-family:Consolas'>What is the purpose of =
inserting this section in this draft?</span><o:p></o:p></p><p =
class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.25in'>The answer is that the charter is a =
temporary document visible and accessible while the WG is active (and =
subject to change during this period) but tends to disappeared when the =
WG is concluded. A recap of the problem statement in the introductory =
sections of the architecture document provides background information =
for the architecture that follows and can be very useful for =
understanding some of the fundamental decisions. <o:p></o:p></p><p =
class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Editorial issues in Section 3.1.3: =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal style=3D'margin-left:.25in'>s/The introduction of the =
controller supports use cases/ The controller supports use =
cases/<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.25in'>s/Consumer=E2=80=99s/Consumers/<o:p></o:p></p=
><p class=3DMsoNormal =
style=3D'margin-left:.25in'>s/Provider=E2=80=99s/Providers/<o:p></o:p></p=
><p class=3DMsoNormal style=3D'margin-left:.25in'>s/interface =
=E2=80=9CC=E2=80=9D shown in Figure 1 demonstrates/ interface =
=E2=80=9CC=E2=80=9D shown in Figure 1 illustrates/<o:p></o:p></p><p =
class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>4.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>In =
order to understand the sentence =E2=80=98a controller may also provide =
the proxy or broker (and possibly routing) function in the data =
plane=E2=80=99 I went back to the terminology document.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.25in'>What I found is that the following terms are =
defined: <o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Broker - An =
entity providing and/or connecting services on the behalf =
of<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; other architectural =
components.<o:p></o:p></span></p><pre><span =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Proxy - =
An architectural component providing functions, information, =
or<o:p></o:p></span></pre><pre><span =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; services on behalf =
of another component, which is not =
directly<o:p></o:p></span></pre><pre><span =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; participating in =
the architecture.<o:p></o:p></span></pre><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.25in'>These definitions seem to need more work. =
They are partially redundant =E2=80=93 is this by design? Proxy is not =
=E2=80=98participating in the architecture=E2=80=99? Then how is it =
between the 2-3 fundamental functions of the controller? There needs to =
be more work in the terminology document I guess. <o:p></o:p></p><p =
class=3DMsoNormal style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2;text-autospace:none'><![if !supportLists]><span =
style=3D'font-size:10.5pt;font-family:Consolas'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.5pt;font-family:Consolas'>TODO =E2=80=90 add text =
around the usage of various protocols for =
endpoint<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.25in'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>data collection (SNMP, =
NETCONF, etc.?)</span><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; do we really need these in an =
architecture document? <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thanks and =
Regards,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Dan<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0330_01D04D23.4D4CB050--


From nobody Sun Feb 22 00:57:28 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94ECB1A86F1 for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 00:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.009
X-Spam-Level: 
X-Spam-Status: No, score=-5.009 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 yIxjKGSlOItV for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 00:57:21 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62CDD1A86F2 for <sacm@ietf.org>; Sun, 22 Feb 2015 00:57:21 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As8IAL+Y6VSHCzIm/2dsb2JhbABagkMhIlJaBII9R60oAwIGmEUCHHtDAQEBAQEBfIQPAQEBAQMMBhEKQRsCAQYCDQEDAQMBAQsWBwMCAgIwFAMGCAIEARIIGogNAZ1BkiOKSZdOAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4YHhQyEPTcBgmgvgRQFjWGBcYV0hGqDFYJEjD8ig25vgQIkHn8BAQE
X-IronPort-AV: E=Sophos;i="5.09,624,1418101200";  d="scan'208,217";a="105057471"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Feb 2015 03:57:19 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 22 Feb 2015 03:57:19 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0174.001; Sun, 22 Feb 2015 09:57:18 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jim Schaad <ietf@augustcellars.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] comments on draft-ietf-sacm-architecture-02
Thread-Index: AQGyIPN1R4PGvGs+u7kTeruCaEcoLJ02iqcQgAIryPA=
Date: Sun, 22 Feb 2015 08:57:18 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C99F703@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com> <032f01d04d66$5b6b8380$12428a80$@augustcellars.com>
In-Reply-To: <032f01d04d66$5b6b8380$12428a80$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C99F703AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/5JOlz6iYEhPGsJanHB8w9qrWkJs>
Subject: Re: [sacm] comments on draft-ietf-sacm-architecture-02
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 08:57:24 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C99F703AZFFEXMB04globa_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSmltLA0KDQpUaGVzZSBjb21tZW50cyB3ZXJlIHdyaXR0ZW4gYmVmb3JlIEdpdGh1YiB3YXMg
aW4gcGxhY2UuIEJ1dCB5ZXMsIEkgc2hvdWxkIHNldCBhbiBleGFtcGxlIOKYuiBzbyBJIGNyZWF0
ZWQgZ2l0aHViIGlzc3VlcyBmb3IgZWFjaC4gVGhlIChzdHJvbmcpIHJlY29tbWVuZGF0aW9uIGlz
IHRvIHVzZSBHaXRodWIhDQoNClJlZ2FyZHMsDQoNCkRhbg0KDQoNCkZyb206IEppbSBTY2hhYWQg
W21haWx0bzppZXRmQGF1Z3VzdGNlbGxhcnMuY29tXQ0KU2VudDogU2F0dXJkYXksIEZlYnJ1YXJ5
IDIxLCAyMDE1IDE6MzkgQU0NClRvOiBSb21hc2NhbnUsIERhbiAoRGFuKTsgc2FjbUBpZXRmLm9y
Zw0KU3ViamVjdDogUkU6IFtzYWNtXSBjb21tZW50cyBvbiBkcmFmdC1pZXRmLXNhY20tYXJjaGl0
ZWN0dXJlLTAyDQoNCkkgYW0gY29uZnVzZWQuICAgV2hlbiBhcmUgd2Ugc2VuZGluZyB0aGVzZSB0
byB0aGUgbWFpbGluZyBsaXN0IGFuZCB3aGVuIGFyZSB3ZSByYWlzaW5nIGlzc3VlcyBvbiBnaXRo
dWI/ICBJIGRvbuKAmXQgc2VlIGFueSBvZiB0aGVzZSBvbiBnaXRodWIgYXQgdGhlIG1vbWVudC4N
Cg0KSmltDQoNCg0KRnJvbTogc2FjbSBbbWFpbHRvOnNhY20tYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIFJvbWFzY2FudSwgRGFuIChEYW4pDQpTZW50OiBUaHVyc2RheSwgRmVicnVhcnkg
MTIsIDIwMTUgNjoxOSBBTQ0KVG86IHNhY21AaWV0Zi5vcmc8bWFpbHRvOnNhY21AaWV0Zi5vcmc+
DQpTdWJqZWN0OiBbc2FjbV0gY29tbWVudHMgb24gZHJhZnQtaWV0Zi1zYWNtLWFyY2hpdGVjdHVy
ZS0wMg0KDQpIaSwNCg0KUGxlYXNlIGZpbmQgYmVsb3cgbXkgY29tbWVudHMgb24gZHJhZnTigJBp
ZXRm4oCQc2FjbeKAkGFyY2hpdGVjdHVyZeKAkDAyLiBJIGFsc28gIGFkZHJlc3NlZCBpbiBteSBj
b21tZW50cyBzb21lIG9mIHRoZSBvcGVuIHF1ZXN0aW9ucyByYWlzZWQgaW4gdGhlIEktRC4NCg0K
DQoxLiAgICAgICBUaGUgZmlyc3Qgc2VudGVuY2UgY29udGFpbnMgYSBsb2dpY2FsIHJlcGV0aXRp
b24g4oCTIHRoZSBTQUNNIHJlZmVyZW5jZSBhcmNoaXRlY3R1cmUgaXMgb2J2aW91c2x5IHJlbGF0
ZWQgdG8gU0FDTSAoZXZlbiBpZiBvbmUgaXMgd2l0aCBhY3JvbnltcyBleHBhbmRlZCBhbmQgdGhl
IG90aGVyIGlzIG5vdCkuIFBsZWFzZSBmaW5kIHNvbWUgbW9yZSBpbnNwaXJpbmcgd29yZHMgYXZv
aWRpbmcgdGhlIHJlcGV0aXRpb24uDQoNCg0KDQoyLiAgICAgICBUaGUgb3BlbiBxdWVzdGlvbiBh
dCB0aGUgZW5kIG9mIFNlY3Rpb24gMjoNCg0KDQrDmCAgV2h5IGRvZXMgdGhlIGNoYXJ0ZXIgbm90
IHN1ZmZpY2U/DQoNCsOYICBXaGF0IGlzIHRoZSBwdXJwb3NlIG9mIGluc2VydGluZyB0aGlzIHNl
Y3Rpb24gaW4gdGhpcyBkcmFmdD8NCg0KDQpUaGUgYW5zd2VyIGlzIHRoYXQgdGhlIGNoYXJ0ZXIg
aXMgYSB0ZW1wb3JhcnkgZG9jdW1lbnQgdmlzaWJsZSBhbmQgYWNjZXNzaWJsZSB3aGlsZSB0aGUg
V0cgaXMgYWN0aXZlIChhbmQgc3ViamVjdCB0byBjaGFuZ2UgZHVyaW5nIHRoaXMgcGVyaW9kKSBi
dXQgdGVuZHMgdG8gZGlzYXBwZWFyZWQgd2hlbiB0aGUgV0cgaXMgY29uY2x1ZGVkLiBBIHJlY2Fw
IG9mIHRoZSBwcm9ibGVtIHN0YXRlbWVudCBpbiB0aGUgaW50cm9kdWN0b3J5IHNlY3Rpb25zIG9m
IHRoZSBhcmNoaXRlY3R1cmUgZG9jdW1lbnQgcHJvdmlkZXMgYmFja2dyb3VuZCBpbmZvcm1hdGlv
biBmb3IgdGhlIGFyY2hpdGVjdHVyZSB0aGF0IGZvbGxvd3MgYW5kIGNhbiBiZSB2ZXJ5IHVzZWZ1
bCBmb3IgdW5kZXJzdGFuZGluZyBzb21lIG9mIHRoZSBmdW5kYW1lbnRhbCBkZWNpc2lvbnMuDQoN
Cg0KMy4gICAgICAgRWRpdG9yaWFsIGlzc3VlcyBpbiBTZWN0aW9uIDMuMS4zOg0KDQpzL1RoZSBp
bnRyb2R1Y3Rpb24gb2YgdGhlIGNvbnRyb2xsZXIgc3VwcG9ydHMgdXNlIGNhc2VzLyBUaGUgY29u
dHJvbGxlciBzdXBwb3J0cyB1c2UgY2FzZXMvDQpzL0NvbnN1bWVy4oCZcy9Db25zdW1lcnMvDQpz
L1Byb3ZpZGVy4oCZcy9Qcm92aWRlcnMvDQpzL2ludGVyZmFjZSDigJxD4oCdIHNob3duIGluIEZp
Z3VyZSAxIGRlbW9uc3RyYXRlcy8gaW50ZXJmYWNlIOKAnEPigJ0gc2hvd24gaW4gRmlndXJlIDEg
aWxsdXN0cmF0ZXMvDQoNCg0KNC4gICAgICAgSW4gb3JkZXIgdG8gdW5kZXJzdGFuZCB0aGUgc2Vu
dGVuY2Ug4oCYYSBjb250cm9sbGVyIG1heSBhbHNvIHByb3ZpZGUgdGhlIHByb3h5IG9yIGJyb2tl
ciAoYW5kIHBvc3NpYmx5IHJvdXRpbmcpIGZ1bmN0aW9uIGluIHRoZSBkYXRhIHBsYW5l4oCZIEkg
d2VudCBiYWNrIHRvIHRoZSB0ZXJtaW5vbG9neSBkb2N1bWVudC4NCg0KV2hhdCBJIGZvdW5kIGlz
IHRoYXQgdGhlIGZvbGxvd2luZyB0ZXJtcyBhcmUgZGVmaW5lZDoNCg0KICAgICAgICBCcm9rZXIg
LSBBbiBlbnRpdHkgcHJvdmlkaW5nIGFuZC9vciBjb25uZWN0aW5nIHNlcnZpY2VzIG9uIHRoZSBi
ZWhhbGYgb2YNCiAgICAgIG90aGVyIGFyY2hpdGVjdHVyYWwgY29tcG9uZW50cy4NCg0KICAgICAg
ICBQcm94eSAtIEFuIGFyY2hpdGVjdHVyYWwgY29tcG9uZW50IHByb3ZpZGluZyBmdW5jdGlvbnMs
IGluZm9ybWF0aW9uLCBvcg0KDQogICAgICBzZXJ2aWNlcyBvbiBiZWhhbGYgb2YgYW5vdGhlciBj
b21wb25lbnQsIHdoaWNoIGlzIG5vdCBkaXJlY3RseQ0KDQogICAgICBwYXJ0aWNpcGF0aW5nIGlu
IHRoZSBhcmNoaXRlY3R1cmUuDQoNClRoZXNlIGRlZmluaXRpb25zIHNlZW0gdG8gbmVlZCBtb3Jl
IHdvcmsuIFRoZXkgYXJlIHBhcnRpYWxseSByZWR1bmRhbnQg4oCTIGlzIHRoaXMgYnkgZGVzaWdu
PyBQcm94eSBpcyBub3Qg4oCYcGFydGljaXBhdGluZyBpbiB0aGUgYXJjaGl0ZWN0dXJl4oCZPyBU
aGVuIGhvdyBpcyBpdCBiZXR3ZWVuIHRoZSAyLTMgZnVuZGFtZW50YWwgZnVuY3Rpb25zIG9mIHRo
ZSBjb250cm9sbGVyPyBUaGVyZSBuZWVkcyB0byBiZSBtb3JlIHdvcmsgaW4gdGhlIHRlcm1pbm9s
b2d5IGRvY3VtZW50IEkgZ3Vlc3MuDQoNCg0KNS4gIFRPRE8g4oCQIGFkZCB0ZXh0IGFyb3VuZCB0
aGUgdXNhZ2Ugb2YgdmFyaW91cyBwcm90b2NvbHMgZm9yIGVuZHBvaW50DQpkYXRhIGNvbGxlY3Rp
b24gKFNOTVAsIE5FVENPTkYsIGV0Yy4/KQ0KDQogICAgICAgICAgICAgICAgZG8gd2UgcmVhbGx5
IG5lZWQgdGhlc2UgaW4gYW4gYXJjaGl0ZWN0dXJlIGRvY3VtZW50Pw0KDQpUaGFua3MgYW5kIFJl
Z2FyZHMsDQoNCkRhbg0KDQoNCg0K

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C99F703AZFFEXMB04globa_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3Nl
LTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25z
b2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0
aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJn
aW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVy
bGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBO
ZXciO30NCnAuTXNvQWNldGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQgQ2hhciI7
DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjguMHB0
Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpwLk1zb0xpc3RQYXJhZ3Jh
cGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21zby1zdHls
ZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1h
cmdpbi1ib3R0b206MGNtOw0KCW1hcmdpbi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9tOi4w
MDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiO30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhU
TUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5
bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4u
RW1haWxTdHlsZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkJhbGxvb25UZXh0
Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWls
eToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjQNCgl7bXNvLXN0eWxl
LXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
IjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4
cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3Np
emU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7
fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmlu
aXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoxMjQxNTE5ODEwOw0KCW1zby1saXN0
LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczotMTMwMTc1MzE4NCAtODc5NDYy
ODkwIDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAz
IDY3Njk4NzEzIDY3Njk4NzE1O30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtdGFiLXN0
b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6
LTE4LjBwdDsNCgltc28tYmlkaS1mb250LWZhbWlseTpDb25zb2xhczt9DQpAbGlzdCBsMDpsZXZl
bDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246cmlnaHQ7DQoJdGV4dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwwOmxldmVs
NA0KCXttc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7
fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OnJvbWFuLWxvd2Vy
Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
cmlnaHQ7DQoJdGV4dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6
bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246cmlnaHQ7DQoJdGV4
dC1pbmRlbnQ6LTkuMHB0O30NCkBsaXN0IGwxDQoJe21zby1saXN0LWlkOjE3NDAxMzE1NzU7DQoJ
bXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjQ0OTc0NjE5NiAt
MTA0MzE5NzIgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2
OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDE6bGV2ZWwxDQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvg5g7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzOw0KCW1zby1mYXJlYXN0LWZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6QXJpYWw7fQ0KQGxpc3QgbDE6
bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5l
dyI7fQ0KQGxpc3QgbDE6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1m
YW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTgu
MHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDUNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMTpsZXZl
bDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+C
pzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
QGxpc3QgbDE6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6
U3ltYm9sO30NCkBsaXN0IGwxOmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxs
ZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250
LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwxOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9t
OjBjbTt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3Rl
IG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAy
NiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hh
cGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+
DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5n
PSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2Vj
dGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PkhpIEppbSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlRoZXNlIGNvbW1l
bnRzIHdlcmUgd3JpdHRlbiBiZWZvcmUgR2l0aHViIHdhcyBpbiBwbGFjZS4gQnV0IHllcywgSSBz
aG91bGQgc2V0IGFuIGV4YW1wbGUNCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6V2lu
Z2RpbmdzO2NvbG9yOiMxRjQ5N0QiPko8L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
PiBzbyBJIGNyZWF0ZWQgZ2l0aHViIGlzc3VlcyBmb3IgZWFjaC4gVGhlIChzdHJvbmcpIHJlY29t
bWVuZGF0aW9uIGlzIHRvIHVzZSBHaXRodWIhPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjoj
MUY0OTdEIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+RGFu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBj
bSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBKaW0g
U2NoYWFkIFttYWlsdG86aWV0ZkBhdWd1c3RjZWxsYXJzLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9i
PiBTYXR1cmRheSwgRmVicnVhcnkgMjEsIDIwMTUgMTozOSBBTTxicj4NCjxiPlRvOjwvYj4gUm9t
YXNjYW51LCBEYW4gKERhbik7IHNhY21AaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6
IFtzYWNtXSBjb21tZW50cyBvbiBkcmFmdC1pZXRmLXNhY20tYXJjaGl0ZWN0dXJlLTAyPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNv
bG9yOiMxRjQ5N0QiPkkgYW0gY29uZnVzZWQuJm5ic3A7Jm5ic3A7IFdoZW4gYXJlIHdlIHNlbmRp
bmcgdGhlc2UgdG8gdGhlIG1haWxpbmcgbGlzdCBhbmQgd2hlbiBhcmUgd2UgcmFpc2luZyBpc3N1
ZXMgb24gZ2l0aHViPyZuYnNwOyBJIGRvbuKAmXQgc2VlIGFueSBvZiB0aGVzZSBvbiBnaXRodWIg
YXQgdGhlIG1vbWVudC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkppbTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAx
LjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20g
MGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gc2FjbSBb
PGEgaHJlZj0ibWFpbHRvOnNhY20tYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOnNhY20tYm91bmNl
c0BpZXRmLm9yZzwvYT5dDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlJvbWFzY2FudSwgRGFuIChEYW4p
PGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBGZWJydWFyeSAxMiwgMjAxNSA2OjE5IEFNPGJy
Pg0KPGI+VG86PC9iPiA8YSBocmVmPSJtYWlsdG86c2FjbUBpZXRmLm9yZyI+c2FjbUBpZXRmLm9y
ZzwvYT48YnI+DQo8Yj5TdWJqZWN0OjwvYj4gW3NhY21dIGNvbW1lbnRzIG9uIGRyYWZ0LWlldGYt
c2FjbS1hcmNoaXRlY3R1cmUtMDI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5IaSwgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBsZWFzZSBmaW5kIGJlbG93
IG15IGNvbW1lbnRzIG9uIGRyYWZ04oCQaWV0ZuKAkHNhY23igJBhcmNoaXRlY3R1cmXigJAwMi4g
SSBhbHNvICZuYnNwO2FkZHJlc3NlZCBpbiBteSBjb21tZW50cyBzb21lIG9mIHRoZSBvcGVuIHF1
ZXN0aW9ucyByYWlzZWQgaW4gdGhlIEktRC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFw
aCIgc3R5bGU9InRleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzIiPjwh
W2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPjEuPHNwYW4g
c3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFu
IGRpcj0iTFRSIj48L3NwYW4+VGhlIGZpcnN0IHNlbnRlbmNlIGNvbnRhaW5zIGEgbG9naWNhbCBy
ZXBldGl0aW9uIOKAkyB0aGUgU0FDTSByZWZlcmVuY2UgYXJjaGl0ZWN0dXJlIGlzIG9idmlvdXNs
eSByZWxhdGVkIHRvIFNBQ00gKGV2ZW4gaWYgb25lIGlzIHdpdGggYWNyb255bXMgZXhwYW5kZWQg
YW5kIHRoZSBvdGhlciBpcyBub3QpLiBQbGVhc2UgZmluZCBzb21lIG1vcmUgaW5zcGlyaW5nIHdv
cmRzDQogYXZvaWRpbmcgdGhlIHJlcGV0aXRpb24uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTGlzdFBhcmFncmFwaCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTGlz
dFBhcmFncmFwaCIgc3R5bGU9InRleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwx
IGxmbzIiPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUi
PjIuPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PCFbZW5k
aWZdPjxzcGFuIGRpcj0iTFRSIj48L3NwYW4+VGhlIG9wZW4gcXVlc3Rpb24gYXQgdGhlIGVuZCBv
ZiBTZWN0aW9uIDI6DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0
LWluZGVudDotMTguMHB0O21zby1saXN0OmwxIGxldmVsMSBsZm80O3RleHQtYXV0b3NwYWNlOm5v
bmUiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6V2luZ2RpbmdzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7DmDxz
cGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7
DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gZGlyPSJMVFIiPjwvc3Bhbj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcyI+V2h5IGRv
ZXMgdGhlIGNoYXJ0ZXIgbm90IHN1ZmZpY2U/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0
OmwxIGxldmVsMSBsZm80Ij48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6V2luZ2RpbmdzIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj7DmDxzcGFuIHN0
eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7DQo8L3Nw
YW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gZGlyPSJMVFIiPjwvc3Bhbj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTpDb25zb2xhcyI+V2hhdCBpcyB0aGUg
cHVycG9zZSBvZiBpbnNlcnRpbmcgdGhpcyBzZWN0aW9uIGluIHRoaXMgZHJhZnQ/PC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjE4LjBwdCI+
VGhlIGFuc3dlciBpcyB0aGF0IHRoZSBjaGFydGVyIGlzIGEgdGVtcG9yYXJ5IGRvY3VtZW50IHZp
c2libGUgYW5kIGFjY2Vzc2libGUgd2hpbGUgdGhlIFdHIGlzIGFjdGl2ZSAoYW5kIHN1YmplY3Qg
dG8gY2hhbmdlIGR1cmluZyB0aGlzIHBlcmlvZCkgYnV0IHRlbmRzIHRvIGRpc2FwcGVhcmVkIHdo
ZW4gdGhlIFdHIGlzIGNvbmNsdWRlZC4gQSByZWNhcCBvZiB0aGUNCiBwcm9ibGVtIHN0YXRlbWVu
dCBpbiB0aGUgaW50cm9kdWN0b3J5IHNlY3Rpb25zIG9mIHRoZSBhcmNoaXRlY3R1cmUgZG9jdW1l
bnQgcHJvdmlkZXMgYmFja2dyb3VuZCBpbmZvcm1hdGlvbiBmb3IgdGhlIGFyY2hpdGVjdHVyZSB0
aGF0IGZvbGxvd3MgYW5kIGNhbiBiZSB2ZXJ5IHVzZWZ1bCBmb3IgdW5kZXJzdGFuZGluZyBzb21l
IG9mIHRoZSBmdW5kYW1lbnRhbCBkZWNpc2lvbnMuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxOC4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0LWluZGVudDotMTgu
MHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8yIj48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBz
dHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4zLjxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1Rp
bWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
DQo8L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBkaXI9IkxUUiI+PC9zcGFuPkVkaXRvcmlh
bCBpc3N1ZXMgaW4gU2VjdGlvbiAzLjEuMzoNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MTguMHB0Ij5zL1RoZSBpbnRyb2R1Y3Rpb24gb2YgdGhlIGNvbnRyb2xs
ZXIgc3VwcG9ydHMgdXNlIGNhc2VzLyBUaGUgY29udHJvbGxlciBzdXBwb3J0cyB1c2UgY2FzZXMv
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MTguMHB0Ij5zL0NvbnN1bWVy4oCZcy9Db25zdW1lcnMvPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MTguMHB0Ij5zL1Byb3ZpZGVy4oCZcy9Q
cm92aWRlcnMvPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWxlZnQ6MTguMHB0Ij5zL2ludGVyZmFjZSDigJxD4oCdIHNob3duIGluIEZpZ3VyZSAxIGRl
bW9uc3RyYXRlcy8gaW50ZXJmYWNlIOKAnEPigJ0gc2hvd24gaW4gRmlndXJlIDEgaWxsdXN0cmF0
ZXMvPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6MTguMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdy
YXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMiI+
PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+NC48c3Bh
biBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNw
YW4gZGlyPSJMVFIiPjwvc3Bhbj5JbiBvcmRlciB0byB1bmRlcnN0YW5kIHRoZSBzZW50ZW5jZSDi
gJhhIGNvbnRyb2xsZXIgbWF5IGFsc28gcHJvdmlkZSB0aGUgcHJveHkgb3IgYnJva2VyIChhbmQg
cG9zc2libHkgcm91dGluZykgZnVuY3Rpb24gaW4gdGhlIGRhdGEgcGxhbmXigJkgSSB3ZW50IGJh
Y2sgdG8gdGhlIHRlcm1pbm9sb2d5IGRvY3VtZW50LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6MTguMHB0Ij5XaGF0IEkgZm91bmQgaXMgdGhhdCB0aGUgZm9sbG93
aW5nIHRlcm1zIGFyZSBkZWZpbmVkOg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MTguMHB0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgQnJva2VyIC0gQW4gZW50aXR5IHByb3ZpZGluZyBh
bmQvb3IgY29ubmVjdGluZyBzZXJ2aWNlcyBvbiB0aGUgYmVoYWxmIG9mPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBvdGhlciBhcmNoaXRlY3R1cmFsIGNvbXBvbmVudHMu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBQcm94eSAtIEFuIGFyY2hp
dGVjdHVyYWwgY29tcG9uZW50IHByb3ZpZGluZyBmdW5jdGlvbnMsIGluZm9ybWF0aW9uLCBvcjxv
OnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBzZXJ2aWNlcyBvbiBiZWhhbGYgb2YgYW5vdGhl
ciBjb21wb25lbnQsIHdoaWNoIGlzIG5vdCBkaXJlY3RseTxvOnA+PC9vOnA+PC9zcGFuPjwvcHJl
Pg0KPHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyBwYXJ0aWNpcGF0aW5nIGluIHRoZSBhcmNoaXRlY3R1cmUuPG86cD48L286cD48L3Nw
YW4+PC9wcmU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1sZWZ0OjE4LjBwdCI+VGhlc2UgZGVmaW5pdGlvbnMgc2VlbSB0byBuZWVkIG1vcmUgd29y
ay4gVGhleSBhcmUgcGFydGlhbGx5IHJlZHVuZGFudCDigJMgaXMgdGhpcyBieSBkZXNpZ24/IFBy
b3h5IGlzIG5vdCDigJhwYXJ0aWNpcGF0aW5nIGluIHRoZSBhcmNoaXRlY3R1cmXigJk/IFRoZW4g
aG93IGlzIGl0IGJldHdlZW4gdGhlIDItMyBmdW5kYW1lbnRhbCBmdW5jdGlvbnMgb2YgdGhlIGNv
bnRyb2xsZXI/DQogVGhlcmUgbmVlZHMgdG8gYmUgbW9yZSB3b3JrIGluIHRoZSB0ZXJtaW5vbG9n
eSBkb2N1bWVudCBJIGd1ZXNzLiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tbGVmdDoxOC4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0
OmwwIGxldmVsMSBsZm8yO3RleHQtYXV0b3NwYWNlOm5vbmUiPg0KPCFbaWYgIXN1cHBvcnRMaXN0
c10+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6Q29uc29sYXMiPjxz
cGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPjUuPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1
b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwh
W2VuZGlmXT48c3BhbiBkaXI9IkxUUiI+PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzIj5UT0RPIOKAkCBhZGQgdGV4dCBhcm91bmQgdGhlIHVz
YWdlIG9mIHZhcmlvdXMgcHJvdG9jb2xzIGZvciBlbmRwb2ludDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDoxOC4wcHQiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzIj5kYXRhIGNvbGxl
Y3Rpb24gKFNOTVAsIE5FVENPTkYsIGV0Yy4/KTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRvIHdlIHJlYWxseSBuZWVkIHRo
ZXNlIGluIGFuIGFyY2hpdGVjdHVyZSBkb2N1bWVudD8NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5UaGFua3MgYW5kIFJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRhbjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5
Pg0KPC9odG1sPg0K

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C99F703AZFFEXMB04globa_--


From nobody Sun Feb 22 01:16:01 2015
Return-Path: <athiasjerome@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E71261A0AF8 for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 01:15:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.2
X-Spam-Level: 
X-Spam-Status: No, score=0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 jb7bcQ15rr8f for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 01:15:58 -0800 (PST)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFEC11A1B0B for <sacm@ietf.org>; Sun, 22 Feb 2015 01:15:57 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id hi2so10953914wib.4 for <sacm@ietf.org>; Sun, 22 Feb 2015 01:15:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qGxULTtEjP6DFJb+0laTvcxmA4bkn4DgFR9O+0OEfjA=; b=pG5qTuMyrSLxu8vv6qsMrb54HTum2OJ+Cq6AWG4jBRaclvokYgevZbxaX1ZXEdoa0+ pFuLClBhRCIA4NQ0XgA7qwCZCmfX9iIIxk9AY3Bgs+sD8Ytayb/kxGMHlbY6bNf9Nqw9 1/X1n+TN9sDfSxrZZ+HU0Fezq2uFgM/8MLXyX4E/wtF+82jdHTQ7s7Eb8wVN62Q8PCcZ Dg/7LcPZz1z4jq3LoUQuz7EepSGu1CDLi/5tMCWw2DotTQrlx8t2LSZqqx8zE+MIDTkK kllLmMB2Ac3LZkPpaSo45zs/7CMj5UMZjwdFvmC+FbKILLenDiGRfHXW/iyNMvcuPPLV gakw==
MIME-Version: 1.0
X-Received: by 10.180.96.168 with SMTP id dt8mr10524214wib.82.1424596556421; Sun, 22 Feb 2015 01:15:56 -0800 (PST)
Received: by 10.28.158.3 with HTTP; Sun, 22 Feb 2015 01:15:56 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com>
Date: Sun, 22 Feb 2015 10:15:56 +0100
Message-ID: <CAA=AuEcGcNC1XKC29KXmVBYf5amZsk4RX9w3kKLSxU1wqk3azw@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/QwuUlr_Vpu5KWIoDzZu80hjarns>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] =?utf-8?b?Y29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFy?= =?utf-8?b?Y2hpdGVjdHVyZeKAkDAy?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 09:16:00 -0000

I'm afraid I would have too many comments to list them all after
review of new ETSI Deliverables related to M2M (few thousands pages),
including Functional Architecture, Requirements, Terminology,
Security, Management, Bindings, etc.

I don't know how to proceed...

Would some of you have some time to quickly review some documents?
Guidance regarding the order of suggested readings could be provided if nee=
ded.

This one, for example, is 'only' 100 pages
http://www.etsi.org/deliver/etsi_ts/118100_118199/118103/01.00.00_60/ts_118=
103v010000p.pdf

You can find few more here (search ETSI TS 118):
http://webapp.etsi.org/action/pu/20150222/20150222.htm

Best regards



2015-02-12 15:19 GMT+01:00 Romascanu, Dan (Dan) <dromasca@avaya.com>:
> Hi,
>
>
>
> Please find below my comments on draft=E2=80=90ietf=E2=80=90sacm=E2=80=90=
architecture=E2=80=9002. I also
> addressed in my comments some of the open questions raised in the I-D.
>
>
>
> 1.       The first sentence contains a logical repetition =E2=80=93 the S=
ACM
> reference architecture is obviously related to SACM (even if one is with
> acronyms expanded and the other is not). Please find some more inspiring
> words avoiding the repetition.
>
>
>
> 2.       The open question at the end of Section 2:
>
>
>
> =C3=98  Why does the charter not suffice?
>
> =C3=98  What is the purpose of inserting this section in this draft?
>
>
>
> The answer is that the charter is a temporary document visible and
> accessible while the WG is active (and subject to change during this peri=
od)
> but tends to disappeared when the WG is concluded. A recap of the problem
> statement in the introductory sections of the architecture document provi=
des
> background information for the architecture that follows and can be very
> useful for understanding some of the fundamental decisions.
>
>
>
> 3.       Editorial issues in Section 3.1.3:
>
>
>
> s/The introduction of the controller supports use cases/ The controller
> supports use cases/
>
> s/Consumer=E2=80=99s/Consumers/
>
> s/Provider=E2=80=99s/Providers/
>
> s/interface =E2=80=9CC=E2=80=9D shown in Figure 1 demonstrates/ interface=
 =E2=80=9CC=E2=80=9D shown in
> Figure 1 illustrates/
>
>
>
> 4.       In order to understand the sentence =E2=80=98a controller may al=
so provide
> the proxy or broker (and possibly routing) function in the data plane=E2=
=80=99 I
> went back to the terminology document.
>
>
>
> What I found is that the following terms are defined:
>
>
>
>         Broker - An entity providing and/or connecting services on the
> behalf of
>
>       other architectural components.
>
>         Proxy - An architectural component providing functions, informati=
on,
> or
>
>       services on behalf of another component, which is not directly
>
>       participating in the architecture.
>
>
>
> These definitions seem to need more work. They are partially redundant =
=E2=80=93 is
> this by design? Proxy is not =E2=80=98participating in the architecture=
=E2=80=99? Then how
> is it between the 2-3 fundamental functions of the controller? There need=
s
> to be more work in the terminology document I guess.
>
>
>
> 5.  TODO =E2=80=90 add text around the usage of various protocols for end=
point
>
> data collection (SNMP, NETCONF, etc.?)
>
>
>
>                 do we really need these in an architecture document?
>
>
>
> Thanks and Regards,
>
>
>
> Dan
>
>
>
>
>
>
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>


From nobody Sun Feb 22 01:38:28 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E491A1F20 for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 01:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.71
X-Spam-Level: 
X-Spam-Status: No, score=-4.71 tagged_above=-999 required=5 tests=[MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 dAewxQiJYZrU for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 01:38:24 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8723B1A1BA2 for <sacm@ietf.org>; Sun, 22 Feb 2015 01:38:24 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtAIAOKi6VTGmAcV/2dsb2JhbABagmQiUloEgj1HrSgDAgaSVIVxAhx7QwEBAQEBAXyEDwEBAQEDDAYREToLDAQCAQYCDQQBAwEBAwIGHQMCAgIfERQBAgMDCAIEDgUIGod5AxEBDJ08kiOKSZIWDYUsAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSBIYRmhQyCRIF5FhsHBoJiL4EUBY9Sg16CFoIIAYJhgxWCRIY4hgcig25vgQIkHn8BAQE
X-IronPort-AV: E=Sophos;i="5.09,624,1418101200"; d="scan'208";a="107986075"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 22 Feb 2015 04:38:22 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 22 Feb 2015 04:38:21 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Sun, 22 Feb 2015 04:38:21 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jerome Athias <athiasjerome@gmail.com>
Thread-Topic: =?utf-8?B?W3NhY21dIGNvbW1lbnRzIG9uIGRyYWZ04oCQaWV0ZuKAkHNhY23igJBhcmNo?= =?utf-8?B?aXRlY3R1cmXigJAwMg==?=
Thread-Index: AQHQToA9s8UOQpUJeEmgFHI1P0nhIpz8aI+A
Date: Sun, 22 Feb 2015 09:38:20 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C99F7D7@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com> <CAA=AuEcGcNC1XKC29KXmVBYf5amZsk4RX9w3kKLSxU1wqk3azw@mail.gmail.com>
In-Reply-To: <CAA=AuEcGcNC1XKC29KXmVBYf5amZsk4RX9w3kKLSxU1wqk3azw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/DUr30VGIqqG7pV99cJOZOkbsWek>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] =?utf-8?b?Y29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFy?= =?utf-8?b?Y2hpdGVjdHVyZeKAkDAy?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 09:38:26 -0000

SGkgSmVyb21lLCANCg0KSSBhbSBhZnJhaWQgdGhhdCB5b3Ugd2lsbCBuZWVkIHRvIG1ha2UgdGhl
IGVmZm9ydCBvZiBzb3J0aW5nIG91dCB0aGUgY29tbWVudHMgdGhhdCB5b3UgYmVsaWV2ZSBhcmUg
aW1wb3J0YW50IGFuZCByZWxldmFudCB0byB0aGUgU0FDTSBjaGFydGVyIGFuZCB3b3JrLWluLXBy
b2dyZXNzIGFuZCBlbnRlciB0aGVtIGluIEdpdGh1YiwgYXMgaXNzdWVzIHRvIGJlIHRyYWNrZWQg
Zm9yIHRoZSBTQUNNIGRvY3VtZW50cy4gUmVmZXJyaW5nIHRvIHB1YmxpY2x5IGF2YWlsYWJsZSBk
b2N1bWVudHMgZnJvbSBFVFNJIGlzIGZpbmUsIGJ1dCBub3QgYWxsIGFyZSByZWxldmFudCBhbmQg
YXNraW5nIHRoZSBTQUNNIFdHIHBhcnRpY2lwYW50cyB0byByZXZpZXcgYWxsIHRoZXNlIGlzIEkg
YW0gYWZyYWlkIGEgYnVyZGVuIHRoYXQgbWFueSBvZiB1cyB3aG8gYXJlIG5vdCBhbHJlYWR5IGlu
dm9sdmVkIGluIHRoZSBFVFNJIHdvcmsgY2Fubm90IGFmZm9yZC4gIA0KDQpUaGFua3MgYW5kIFJl
Z2FyZHMsDQoNCkRhbg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
SmVyb21lIEF0aGlhcyBbbWFpbHRvOmF0aGlhc2plcm9tZUBnbWFpbC5jb21dDQo+IFNlbnQ6IFN1
bmRheSwgRmVicnVhcnkgMjIsIDIwMTUgMTE6MTYgQU0NCj4gVG86IFJvbWFzY2FudSwgRGFuIChE
YW4pDQo+IENjOiBzYWNtQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbc2FjbV0gY29tbWVudHMg
b24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFyY2hpdGVjdHVyZeKAkDAyDQo+IA0KPiBJJ20gYWZy
YWlkIEkgd291bGQgaGF2ZSB0b28gbWFueSBjb21tZW50cyB0byBsaXN0IHRoZW0gYWxsIGFmdGVy
IHJldmlldyBvZg0KPiBuZXcgRVRTSSBEZWxpdmVyYWJsZXMgcmVsYXRlZCB0byBNMk0gKGZldyB0
aG91c2FuZHMgcGFnZXMpLCBpbmNsdWRpbmcNCj4gRnVuY3Rpb25hbCBBcmNoaXRlY3R1cmUsIFJl
cXVpcmVtZW50cywgVGVybWlub2xvZ3ksIFNlY3VyaXR5LCBNYW5hZ2VtZW50LA0KPiBCaW5kaW5n
cywgZXRjLg0KPiANCj4gSSBkb24ndCBrbm93IGhvdyB0byBwcm9jZWVkLi4uDQo+IA0KPiBXb3Vs
ZCBzb21lIG9mIHlvdSBoYXZlIHNvbWUgdGltZSB0byBxdWlja2x5IHJldmlldyBzb21lIGRvY3Vt
ZW50cz8NCj4gR3VpZGFuY2UgcmVnYXJkaW5nIHRoZSBvcmRlciBvZiBzdWdnZXN0ZWQgcmVhZGlu
Z3MgY291bGQgYmUgcHJvdmlkZWQgaWYNCj4gbmVlZGVkLg0KPiANCj4gVGhpcyBvbmUsIGZvciBl
eGFtcGxlLCBpcyAnb25seScgMTAwIHBhZ2VzDQo+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBv
aW50LmNvbS92Mi91cmw/dT1odHRwLQ0KPiAzQV9fd3d3LmV0c2kub3JnX2RlbGl2ZXJfZXRzaS01
RnRzXzExODEwMC01RjExODE5OV8xMTgxMDNfMDEuMDAuMDAtDQo+IDVGNjBfdHMtDQo+IDVGMTE4
MTAzdjAxMDAwMHAucGRmJmQ9QXdJRmFRJmM9QkZwV1F3OGJzdUtwbDFTZ2laSDY0USZyPUk0ZHpH
eA0KPiBSMzFPY05YQ0pmUXp2bHNpTFFmdWNCWFJ1Y1B2ZHJwaHBCc0ZBJm09RF9FVUo5N1F1U0Fm
WlF0RWNQU3NPeUZJDQo+IHFKdzFFOVU0cldnQmhLSFUyOGMmcz1lWWg5WHBFQThXWWhqT0hPZ3pq
ZUFpYUZhaWFrYkxFSS0NCj4geU5hX21XU1NpVSZlPQ0KPiANCj4gWW91IGNhbiBmaW5kIGZldyBt
b3JlIGhlcmUgKHNlYXJjaCBFVFNJIFRTIDExOCk6DQo+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9v
ZnBvaW50LmNvbS92Mi91cmw/dT1odHRwLQ0KPiAzQV9fd2ViYXBwLmV0c2kub3JnX2FjdGlvbl9w
dV8yMDE1MDIyMl8yMDE1MDIyMi5odG0mZD1Bd0lGYVEmYz1CDQo+IEZwV1F3OGJzdUtwbDFTZ2la
SDY0USZyPUk0ZHpHeFIzMU9jTlhDSmZRenZsc2lMUWZ1Y0JYUnVjUHZkcnBocEINCj4gc0ZBJm09
RF9FVUo5N1F1U0FmWlF0RWNQU3NPeUZJcUp3MUU5VTRyV2dCaEtIVTI4YyZzPU5sZTN4Ni0NCj4g
Z29neXVOVTJHcnktSHRWR0dRdmp1c2hsNWpYQnFnOG9ZQmprJmU9DQo+IA0KPiBCZXN0IHJlZ2Fy
ZHMNCj4gDQo+IA0KPiANCj4gMjAxNS0wMi0xMiAxNToxOSBHTVQrMDE6MDAgUm9tYXNjYW51LCBE
YW4gKERhbikNCj4gPGRyb21hc2NhQGF2YXlhLmNvbT46DQo+ID4gSGksDQo+ID4NCj4gPg0KPiA+
DQo+ID4gUGxlYXNlIGZpbmQgYmVsb3cgbXkgY29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2Fj
beKAkGFyY2hpdGVjdHVyZeKAkDAyLiBJDQo+ID4gYWxzbyBhZGRyZXNzZWQgaW4gbXkgY29tbWVu
dHMgc29tZSBvZiB0aGUgb3BlbiBxdWVzdGlvbnMgcmFpc2VkIGluIHRoZQ0KPiBJLUQuDQo+ID4N
Cj4gPg0KPiA+DQo+ID4gMS4gICAgICAgVGhlIGZpcnN0IHNlbnRlbmNlIGNvbnRhaW5zIGEgbG9n
aWNhbCByZXBldGl0aW9uIOKAkyB0aGUgU0FDTQ0KPiA+IHJlZmVyZW5jZSBhcmNoaXRlY3R1cmUg
aXMgb2J2aW91c2x5IHJlbGF0ZWQgdG8gU0FDTSAoZXZlbiBpZiBvbmUgaXMNCj4gPiB3aXRoIGFj
cm9ueW1zIGV4cGFuZGVkIGFuZCB0aGUgb3RoZXIgaXMgbm90KS4gUGxlYXNlIGZpbmQgc29tZSBt
b3JlDQo+ID4gaW5zcGlyaW5nIHdvcmRzIGF2b2lkaW5nIHRoZSByZXBldGl0aW9uLg0KPiA+DQo+
ID4NCj4gPg0KPiA+IDIuICAgICAgIFRoZSBvcGVuIHF1ZXN0aW9uIGF0IHRoZSBlbmQgb2YgU2Vj
dGlvbiAyOg0KPiA+DQo+ID4NCj4gPg0KPiA+IMOYICBXaHkgZG9lcyB0aGUgY2hhcnRlciBub3Qg
c3VmZmljZT8NCj4gPg0KPiA+IMOYICBXaGF0IGlzIHRoZSBwdXJwb3NlIG9mIGluc2VydGluZyB0
aGlzIHNlY3Rpb24gaW4gdGhpcyBkcmFmdD8NCj4gPg0KPiA+DQo+ID4NCj4gPiBUaGUgYW5zd2Vy
IGlzIHRoYXQgdGhlIGNoYXJ0ZXIgaXMgYSB0ZW1wb3JhcnkgZG9jdW1lbnQgdmlzaWJsZSBhbmQN
Cj4gPiBhY2Nlc3NpYmxlIHdoaWxlIHRoZSBXRyBpcyBhY3RpdmUgKGFuZCBzdWJqZWN0IHRvIGNo
YW5nZSBkdXJpbmcgdGhpcw0KPiA+IHBlcmlvZCkgYnV0IHRlbmRzIHRvIGRpc2FwcGVhcmVkIHdo
ZW4gdGhlIFdHIGlzIGNvbmNsdWRlZC4gQSByZWNhcCBvZg0KPiA+IHRoZSBwcm9ibGVtIHN0YXRl
bWVudCBpbiB0aGUgaW50cm9kdWN0b3J5IHNlY3Rpb25zIG9mIHRoZSBhcmNoaXRlY3R1cmUNCj4g
PiBkb2N1bWVudCBwcm92aWRlcyBiYWNrZ3JvdW5kIGluZm9ybWF0aW9uIGZvciB0aGUgYXJjaGl0
ZWN0dXJlIHRoYXQNCj4gPiBmb2xsb3dzIGFuZCBjYW4gYmUgdmVyeSB1c2VmdWwgZm9yIHVuZGVy
c3RhbmRpbmcgc29tZSBvZiB0aGUgZnVuZGFtZW50YWwNCj4gZGVjaXNpb25zLg0KPiA+DQo+ID4N
Cj4gPg0KPiA+IDMuICAgICAgIEVkaXRvcmlhbCBpc3N1ZXMgaW4gU2VjdGlvbiAzLjEuMzoNCj4g
Pg0KPiA+DQo+ID4NCj4gPiBzL1RoZSBpbnRyb2R1Y3Rpb24gb2YgdGhlIGNvbnRyb2xsZXIgc3Vw
cG9ydHMgdXNlIGNhc2VzLyBUaGUNCj4gPiBjb250cm9sbGVyIHN1cHBvcnRzIHVzZSBjYXNlcy8N
Cj4gPg0KPiA+IHMvQ29uc3VtZXLigJlzL0NvbnN1bWVycy8NCj4gPg0KPiA+IHMvUHJvdmlkZXLi
gJlzL1Byb3ZpZGVycy8NCj4gPg0KPiA+IHMvaW50ZXJmYWNlIOKAnEPigJ0gc2hvd24gaW4gRmln
dXJlIDEgZGVtb25zdHJhdGVzLyBpbnRlcmZhY2Ug4oCcQ+KAnSBzaG93biBpbg0KPiA+IEZpZ3Vy
ZSAxIGlsbHVzdHJhdGVzLw0KPiA+DQo+ID4NCj4gPg0KPiA+IDQuICAgICAgIEluIG9yZGVyIHRv
IHVuZGVyc3RhbmQgdGhlIHNlbnRlbmNlIOKAmGEgY29udHJvbGxlciBtYXkgYWxzbyBwcm92aWRl
DQo+ID4gdGhlIHByb3h5IG9yIGJyb2tlciAoYW5kIHBvc3NpYmx5IHJvdXRpbmcpIGZ1bmN0aW9u
IGluIHRoZSBkYXRhIHBsYW5l4oCZDQo+ID4gSSB3ZW50IGJhY2sgdG8gdGhlIHRlcm1pbm9sb2d5
IGRvY3VtZW50Lg0KPiA+DQo+ID4NCj4gPg0KPiA+IFdoYXQgSSBmb3VuZCBpcyB0aGF0IHRoZSBm
b2xsb3dpbmcgdGVybXMgYXJlIGRlZmluZWQ6DQo+ID4NCj4gPg0KPiA+DQo+ID4gICAgICAgICBC
cm9rZXIgLSBBbiBlbnRpdHkgcHJvdmlkaW5nIGFuZC9vciBjb25uZWN0aW5nIHNlcnZpY2VzIG9u
IHRoZQ0KPiA+IGJlaGFsZiBvZg0KPiA+DQo+ID4gICAgICAgb3RoZXIgYXJjaGl0ZWN0dXJhbCBj
b21wb25lbnRzLg0KPiA+DQo+ID4gICAgICAgICBQcm94eSAtIEFuIGFyY2hpdGVjdHVyYWwgY29t
cG9uZW50IHByb3ZpZGluZyBmdW5jdGlvbnMsDQo+ID4gaW5mb3JtYXRpb24sIG9yDQo+ID4NCj4g
PiAgICAgICBzZXJ2aWNlcyBvbiBiZWhhbGYgb2YgYW5vdGhlciBjb21wb25lbnQsIHdoaWNoIGlz
IG5vdCBkaXJlY3RseQ0KPiA+DQo+ID4gICAgICAgcGFydGljaXBhdGluZyBpbiB0aGUgYXJjaGl0
ZWN0dXJlLg0KPiA+DQo+ID4NCj4gPg0KPiA+IFRoZXNlIGRlZmluaXRpb25zIHNlZW0gdG8gbmVl
ZCBtb3JlIHdvcmsuIFRoZXkgYXJlIHBhcnRpYWxseSByZWR1bmRhbnQNCj4gPiDigJMgaXMgdGhp
cyBieSBkZXNpZ24/IFByb3h5IGlzIG5vdCDigJhwYXJ0aWNpcGF0aW5nIGluIHRoZSBhcmNoaXRl
Y3R1cmXigJk/DQo+ID4gVGhlbiBob3cgaXMgaXQgYmV0d2VlbiB0aGUgMi0zIGZ1bmRhbWVudGFs
IGZ1bmN0aW9ucyBvZiB0aGUNCj4gPiBjb250cm9sbGVyPyBUaGVyZSBuZWVkcyB0byBiZSBtb3Jl
IHdvcmsgaW4gdGhlIHRlcm1pbm9sb2d5IGRvY3VtZW50IEkNCj4gZ3Vlc3MuDQo+ID4NCj4gPg0K
PiA+DQo+ID4gNS4gIFRPRE8g4oCQIGFkZCB0ZXh0IGFyb3VuZCB0aGUgdXNhZ2Ugb2YgdmFyaW91
cyBwcm90b2NvbHMgZm9yIGVuZHBvaW50DQo+ID4NCj4gPiBkYXRhIGNvbGxlY3Rpb24gKFNOTVAs
IE5FVENPTkYsIGV0Yy4/KQ0KPiA+DQo+ID4NCj4gPg0KPiA+ICAgICAgICAgICAgICAgICBkbyB3
ZSByZWFsbHkgbmVlZCB0aGVzZSBpbiBhbiBhcmNoaXRlY3R1cmUgZG9jdW1lbnQ/DQo+ID4NCj4g
Pg0KPiA+DQo+ID4gVGhhbmtzIGFuZCBSZWdhcmRzLA0KPiA+DQo+ID4NCj4gPg0KPiA+IERhbg0K
PiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IHNhY20gbWFpbGluZyBsaXN0
DQo+ID4gc2FjbUBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNv
bS92Mi91cmw/dT1odHRwcy0NCj4gM0FfX3d3dy5pZXRmLm9yZ19tYWlsDQo+ID4NCj4gbWFuX2xp
c3RpbmZvX3NhY20mZD1Bd0lGYVEmYz1CRnBXUXc4YnN1S3BsMVNnaVpINjRRJnI9STRkekd4UjMx
DQo+IE9jTlhDSmYNCj4gPg0KPiBRenZsc2lMUWZ1Y0JYUnVjUHZkcnBocEJzRkEmbT1EX0VVSjk3
UXVTQWZaUXRFY1BTc095RklxSncxRTlVNHINCj4gV2dCaEtIVQ0KPiA+IDI4YyZzPW9fdzE3MFd2
TVpyR1JtYkFpaWp5QTlGQ0paNFFjUlhXWWM4S29felNmUmcmZT0NCj4gPg0K


From nobody Sun Feb 22 01:48:30 2015
Return-Path: <athiasjerome@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64C9C1A1A12 for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 01:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.2
X-Spam-Level: 
X-Spam-Status: No, score=0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 s4O4UXSCHDdB for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 01:48:28 -0800 (PST)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBB131A0171 for <sacm@ietf.org>; Sun, 22 Feb 2015 01:48:27 -0800 (PST)
Received: by mail-wg0-f41.google.com with SMTP id b13so20532616wgh.0 for <sacm@ietf.org>; Sun, 22 Feb 2015 01:48:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=9cgBEbd/J3kOlgPMCv15LpFcldJUPg+TCNj3bwsvaFg=; b=FGQmeQS7D0QonbZkfrA/2el2buiLdxae5y+417Yxt8wSgB+OaTu90b7wBwK/zahxyc HFE/52fLtOxICWgDjSR1zPuVck8pFX7pLqE2tiCWLxNoqsMO1iuObGiDxej9ezcDbV08 eayd72/fsWe6phVLUJMLX1hgxH5kfacKe8bndaSuUUTzWFTjo8p1uRM7aOpd/oqjTsbw UIiGuKTkuxLvkhyckSg7sjxxfIEbbTYoiZTA+I10h+JrTnErseS2GL5lssywh31NsrgV FmCXM6yEyQTIKi8CJd39zZuheX13KtMCdJuQ2NwKEqvef357hMxRODo/kjZrqHsERkTv psUA==
MIME-Version: 1.0
X-Received: by 10.180.86.227 with SMTP id s3mr10605524wiz.58.1424598506345; Sun, 22 Feb 2015 01:48:26 -0800 (PST)
Received: by 10.28.158.3 with HTTP; Sun, 22 Feb 2015 01:48:26 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C99F7D7@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com> <CAA=AuEcGcNC1XKC29KXmVBYf5amZsk4RX9w3kKLSxU1wqk3azw@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5C99F7D7@AZ-FFEXMB04.global.avaya.com>
Date: Sun, 22 Feb 2015 10:48:26 +0100
Message-ID: <CAA=AuEfDrEy0nKNREw-YtPxR+Pt2DjY6cwa9nzcjL8o3BHdcUA@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/IXvDV5_SExf7PjaTGcXU7HrrKzg>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] =?utf-8?b?Y29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFy?= =?utf-8?b?Y2hpdGVjdHVyZeKAkDAy?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 09:48:29 -0000

Hi,

thanks for the quick feedback.
I get your point.
Your answer is fair enough.

I could be wrong, but I think you could save moths, or years, of work
by spending few hours looking at it.

Have a nice week-end
Best regards


2015-02-22 10:38 GMT+01:00 Romascanu, Dan (Dan) <dromasca@avaya.com>:
> Hi Jerome,
>
> I am afraid that you will need to make the effort of sorting out the comm=
ents that you believe are important and relevant to the SACM charter and wo=
rk-in-progress and enter them in Github, as issues to be tracked for the SA=
CM documents. Referring to publicly available documents from ETSI is fine, =
but not all are relevant and asking the SACM WG participants to review all =
these is I am afraid a burden that many of us who are not already involved =
in the ETSI work cannot afford.
>
> Thanks and Regards,
>
> Dan
>
>
>> -----Original Message-----
>> From: Jerome Athias [mailto:athiasjerome@gmail.com]
>> Sent: Sunday, February 22, 2015 11:16 AM
>> To: Romascanu, Dan (Dan)
>> Cc: sacm@ietf.org
>> Subject: Re: [sacm] comments on draft=E2=80=90ietf=E2=80=90sacm=E2=80=90=
architecture=E2=80=9002
>>
>> I'm afraid I would have too many comments to list them all after review =
of
>> new ETSI Deliverables related to M2M (few thousands pages), including
>> Functional Architecture, Requirements, Terminology, Security, Management=
,
>> Bindings, etc.
>>
>> I don't know how to proceed...
>>
>> Would some of you have some time to quickly review some documents?
>> Guidance regarding the order of suggested readings could be provided if
>> needed.
>>
>> This one, for example, is 'only' 100 pages
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttp-
>> 3A__www.etsi.org_deliver_etsi-5Fts_118100-5F118199_118103_01.00.00-
>> 5F60_ts-
>> 5F118103v010000p.pdf&d=3DAwIFaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGx
>> R31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DD_EUJ97QuSAfZQtEcPSsOyFI
>> qJw1E9U4rWgBhKHU28c&s=3DeYh9XpEA8WYhjOHOgzjeAiaFaiakbLEI-
>> yNa_mWSSiU&e=3D
>>
>> You can find few more here (search ETSI TS 118):
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttp-
>> 3A__webapp.etsi.org_action_pu_20150222_20150222.htm&d=3DAwIFaQ&c=3DB
>> FpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpB
>> sFA&m=3DD_EUJ97QuSAfZQtEcPSsOyFIqJw1E9U4rWgBhKHU28c&s=3DNle3x6-
>> gogyuNU2Gry-HtVGGQvjushl5jXBqg8oYBjk&e=3D
>>
>> Best regards
>>
>>
>>
>> 2015-02-12 15:19 GMT+01:00 Romascanu, Dan (Dan)
>> <dromasca@avaya.com>:
>> > Hi,
>> >
>> >
>> >
>> > Please find below my comments on draft=E2=80=90ietf=E2=80=90sacm=E2=80=
=90architecture=E2=80=9002. I
>> > also addressed in my comments some of the open questions raised in the
>> I-D.
>> >
>> >
>> >
>> > 1.       The first sentence contains a logical repetition =E2=80=93 th=
e SACM
>> > reference architecture is obviously related to SACM (even if one is
>> > with acronyms expanded and the other is not). Please find some more
>> > inspiring words avoiding the repetition.
>> >
>> >
>> >
>> > 2.       The open question at the end of Section 2:
>> >
>> >
>> >
>> > =C3=98  Why does the charter not suffice?
>> >
>> > =C3=98  What is the purpose of inserting this section in this draft?
>> >
>> >
>> >
>> > The answer is that the charter is a temporary document visible and
>> > accessible while the WG is active (and subject to change during this
>> > period) but tends to disappeared when the WG is concluded. A recap of
>> > the problem statement in the introductory sections of the architecture
>> > document provides background information for the architecture that
>> > follows and can be very useful for understanding some of the fundament=
al
>> decisions.
>> >
>> >
>> >
>> > 3.       Editorial issues in Section 3.1.3:
>> >
>> >
>> >
>> > s/The introduction of the controller supports use cases/ The
>> > controller supports use cases/
>> >
>> > s/Consumer=E2=80=99s/Consumers/
>> >
>> > s/Provider=E2=80=99s/Providers/
>> >
>> > s/interface =E2=80=9CC=E2=80=9D shown in Figure 1 demonstrates/ interf=
ace =E2=80=9CC=E2=80=9D shown in
>> > Figure 1 illustrates/
>> >
>> >
>> >
>> > 4.       In order to understand the sentence =E2=80=98a controller may=
 also provide
>> > the proxy or broker (and possibly routing) function in the data plane=
=E2=80=99
>> > I went back to the terminology document.
>> >
>> >
>> >
>> > What I found is that the following terms are defined:
>> >
>> >
>> >
>> >         Broker - An entity providing and/or connecting services on the
>> > behalf of
>> >
>> >       other architectural components.
>> >
>> >         Proxy - An architectural component providing functions,
>> > information, or
>> >
>> >       services on behalf of another component, which is not directly
>> >
>> >       participating in the architecture.
>> >
>> >
>> >
>> > These definitions seem to need more work. They are partially redundant
>> > =E2=80=93 is this by design? Proxy is not =E2=80=98participating in th=
e architecture=E2=80=99?
>> > Then how is it between the 2-3 fundamental functions of the
>> > controller? There needs to be more work in the terminology document I
>> guess.
>> >
>> >
>> >
>> > 5.  TODO =E2=80=90 add text around the usage of various protocols for =
endpoint
>> >
>> > data collection (SNMP, NETCONF, etc.?)
>> >
>> >
>> >
>> >                 do we really need these in an architecture document?
>> >
>> >
>> >
>> > Thanks and Regards,
>> >
>> >
>> >
>> > Dan
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > sacm mailing list
>> > sacm@ietf.org
>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-
>> 3A__www.ietf.org_mail
>> >
>> man_listinfo_sacm&d=3DAwIFaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31
>> OcNXCJf
>> >
>> QzvlsiLQfucBXRucPvdrphpBsFA&m=3DD_EUJ97QuSAfZQtEcPSsOyFIqJw1E9U4r
>> WgBhKHU
>> > 28c&s=3Do_w170WvMZrGRmbAiijyA9FCJZ4QcRXWYc8Ko_zSfRg&e=3D
>> >


From nobody Sun Feb 22 02:11:58 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF9A1A1A87 for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 02:11:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.71
X-Spam-Level: 
X-Spam-Status: No, score=-4.71 tagged_above=-999 required=5 tests=[MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 iXIEha0q8nht for <sacm@ietfa.amsl.com>; Sun, 22 Feb 2015 02:11:55 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF0C1A1A86 for <sacm@ietf.org>; Sun, 22 Feb 2015 02:11:55 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtAIAAar6VSHCzIm/2dsb2JhbABagmQiUloEgj1HrSgDAgaSVIVxAhx7QwEBAQEBAXyEDwEBAQECAQwGERE6BAcMBAIBBgINBAEDAQEDAgYdAwICAh8RFAECAwMIAgQOBQgah3kDCQgBDJ0vkiOKSZIVDYUsAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSBIYRmhQyCRIF5FhsHBoJiL4EUBY9Sg16CFoIIAYJhgxWCRIY4gkmDPiKCAhyBUG+BAiQefwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,624,1418101200"; d="scan'208";a="107987646"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 22 Feb 2015 05:11:53 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 22 Feb 2015 05:11:53 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Sun, 22 Feb 2015 11:11:51 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jerome Athias <athiasjerome@gmail.com>
Thread-Topic: =?utf-8?B?W3NhY21dIGNvbW1lbnRzIG9uIGRyYWZ04oCQaWV0ZuKAkHNhY23igJBhcmNo?= =?utf-8?B?aXRlY3R1cmXigJAwMg==?=
Thread-Index: AQHQToA9s8UOQpUJeEmgFHI1P0nhIpz8aI+A///zFQCAABS/wA==
Date: Sun, 22 Feb 2015 10:11:51 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C99F7F4@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C994479@AZ-FFEXMB04.global.avaya.com> <CAA=AuEcGcNC1XKC29KXmVBYf5amZsk4RX9w3kKLSxU1wqk3azw@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5C99F7D7@AZ-FFEXMB04.global.avaya.com> <CAA=AuEfDrEy0nKNREw-YtPxR+Pt2DjY6cwa9nzcjL8o3BHdcUA@mail.gmail.com>
In-Reply-To: <CAA=AuEfDrEy0nKNREw-YtPxR+Pt2DjY6cwa9nzcjL8o3BHdcUA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.48]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/SaqxfkNSrgII-bUn1SxYUV4G430>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] =?utf-8?b?Y29tbWVudHMgb24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFy?= =?utf-8?b?Y2hpdGVjdHVyZeKAkDAy?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 10:11:57 -0000

SGkgSmVyb21lLCANCg0KQXMgSSBzYWlkLCB3ZSBjYW4gdXNlIHlvdXIgaGVscCBoZXJlLiBZb3Ug
c2VlbSB0byBiZSBmYW1pbGlhciB3aXRoIHRoZSBFVFNJIE0yTSB3b3JrLCBtYW55IG9mIHVzIGFy
ZSBub3QuIEd1aWRhbmNlIHdvdWxkIGJlIGFwcHJlY2lhdGVkIHdpdGggYSBzaG9ydCBleHBsYW5h
dGlvbiBhYm91dCB0aGUgcmVsYXRpb24gYmV0d2VlbiB0aGUgRVRTSSBNMk0gd29yayBhbmQgU0FD
TSBXRyBzY29wZSBhbmQgd29yay1pbi1wcm9ncmVzcywgYW5kIHdoYXQgeW91IGJlbGlldmUgY2Fu
IGJlIHVzZWQgb3IgcmVmZXJyZWQuIFdlIGNhbiBhbHNvIG1ha2Ugcm9vbSBmb3IgYSBzaG9ydCBp
bnRyb2R1Y3Rpb24gYXQgSUVURiA5MiBpZiBhZ2VuZGEgYWxsb3dzLiANCg0KVGhhbmtzIGFuZCBS
ZWdhcmRzLA0KDQpEYW4NCiANCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9t
OiBKZXJvbWUgQXRoaWFzIFttYWlsdG86YXRoaWFzamVyb21lQGdtYWlsLmNvbV0NCj4gU2VudDog
U3VuZGF5LCBGZWJydWFyeSAyMiwgMjAxNSAxMTo0OCBBTQ0KPiBUbzogUm9tYXNjYW51LCBEYW4g
KERhbikNCj4gQ2M6IHNhY21AaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtzYWNtXSBjb21tZW50
cyBvbiBkcmFmdOKAkGlldGbigJBzYWNt4oCQYXJjaGl0ZWN0dXJl4oCQMDINCj4gDQo+IEhpLA0K
PiANCj4gdGhhbmtzIGZvciB0aGUgcXVpY2sgZmVlZGJhY2suDQo+IEkgZ2V0IHlvdXIgcG9pbnQu
DQo+IFlvdXIgYW5zd2VyIGlzIGZhaXIgZW5vdWdoLg0KPiANCj4gSSBjb3VsZCBiZSB3cm9uZywg
YnV0IEkgdGhpbmsgeW91IGNvdWxkIHNhdmUgbW90aHMsIG9yIHllYXJzLCBvZiB3b3JrIGJ5DQo+
IHNwZW5kaW5nIGZldyBob3VycyBsb29raW5nIGF0IGl0Lg0KPiANCj4gSGF2ZSBhIG5pY2Ugd2Vl
ay1lbmQNCj4gQmVzdCByZWdhcmRzDQo+IA0KPiANCj4gMjAxNS0wMi0yMiAxMDozOCBHTVQrMDE6
MDAgUm9tYXNjYW51LCBEYW4gKERhbikNCj4gPGRyb21hc2NhQGF2YXlhLmNvbT46DQo+ID4gSGkg
SmVyb21lLA0KPiA+DQo+ID4gSSBhbSBhZnJhaWQgdGhhdCB5b3Ugd2lsbCBuZWVkIHRvIG1ha2Ug
dGhlIGVmZm9ydCBvZiBzb3J0aW5nIG91dCB0aGUNCj4gY29tbWVudHMgdGhhdCB5b3UgYmVsaWV2
ZSBhcmUgaW1wb3J0YW50IGFuZCByZWxldmFudCB0byB0aGUgU0FDTSBjaGFydGVyDQo+IGFuZCB3
b3JrLWluLXByb2dyZXNzIGFuZCBlbnRlciB0aGVtIGluIEdpdGh1YiwgYXMgaXNzdWVzIHRvIGJl
IHRyYWNrZWQgZm9yDQo+IHRoZSBTQUNNIGRvY3VtZW50cy4gUmVmZXJyaW5nIHRvIHB1YmxpY2x5
IGF2YWlsYWJsZSBkb2N1bWVudHMgZnJvbSBFVFNJIGlzDQo+IGZpbmUsIGJ1dCBub3QgYWxsIGFy
ZSByZWxldmFudCBhbmQgYXNraW5nIHRoZSBTQUNNIFdHIHBhcnRpY2lwYW50cyB0byByZXZpZXcN
Cj4gYWxsIHRoZXNlIGlzIEkgYW0gYWZyYWlkIGEgYnVyZGVuIHRoYXQgbWFueSBvZiB1cyB3aG8g
YXJlIG5vdCBhbHJlYWR5IGludm9sdmVkDQo+IGluIHRoZSBFVFNJIHdvcmsgY2Fubm90IGFmZm9y
ZC4NCj4gPg0KPiA+IFRoYW5rcyBhbmQgUmVnYXJkcywNCj4gPg0KPiA+IERhbg0KPiA+DQo+ID4N
Cj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogSmVyb21lIEF0aGlh
cyBbbWFpbHRvOmF0aGlhc2plcm9tZUBnbWFpbC5jb21dDQo+ID4+IFNlbnQ6IFN1bmRheSwgRmVi
cnVhcnkgMjIsIDIwMTUgMTE6MTYgQU0NCj4gPj4gVG86IFJvbWFzY2FudSwgRGFuIChEYW4pDQo+
ID4+IENjOiBzYWNtQGlldGYub3JnDQo+ID4+IFN1YmplY3Q6IFJlOiBbc2FjbV0gY29tbWVudHMg
b24gZHJhZnTigJBpZXRm4oCQc2FjbeKAkGFyY2hpdGVjdHVyZeKAkDAyDQo+ID4+DQo+ID4+IEkn
bSBhZnJhaWQgSSB3b3VsZCBoYXZlIHRvbyBtYW55IGNvbW1lbnRzIHRvIGxpc3QgdGhlbSBhbGwg
YWZ0ZXINCj4gPj4gcmV2aWV3IG9mIG5ldyBFVFNJIERlbGl2ZXJhYmxlcyByZWxhdGVkIHRvIE0y
TSAoZmV3IHRob3VzYW5kcyBwYWdlcyksDQo+ID4+IGluY2x1ZGluZyBGdW5jdGlvbmFsIEFyY2hp
dGVjdHVyZSwgUmVxdWlyZW1lbnRzLCBUZXJtaW5vbG9neSwNCj4gPj4gU2VjdXJpdHksIE1hbmFn
ZW1lbnQsIEJpbmRpbmdzLCBldGMuDQo+ID4+DQo+ID4+IEkgZG9uJ3Qga25vdyBob3cgdG8gcHJv
Y2VlZC4uLg0KPiA+Pg0KPiA+PiBXb3VsZCBzb21lIG9mIHlvdSBoYXZlIHNvbWUgdGltZSB0byBx
dWlja2x5IHJldmlldyBzb21lIGRvY3VtZW50cz8NCj4gPj4gR3VpZGFuY2UgcmVnYXJkaW5nIHRo
ZSBvcmRlciBvZiBzdWdnZXN0ZWQgcmVhZGluZ3MgY291bGQgYmUgcHJvdmlkZWQNCj4gPj4gaWYg
bmVlZGVkLg0KPiA+Pg0KPiA+PiBUaGlzIG9uZSwgZm9yIGV4YW1wbGUsIGlzICdvbmx5JyAxMDAg
cGFnZXMNCj4gPj4gaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0
dHAtDQo+ID4+IDNBX193d3cuZXRzaS5vcmdfZGVsaXZlcl9ldHNpLTVGdHNfMTE4MTAwLTVGMTE4
MTk5XzExODEwM18wMS4wMC4wMC0NCj4gPj4gNUY2MF90cy0NCj4gPj4NCj4gNUYxMTgxMDN2MDEw
MDAwcC5wZGYmZD1Bd0lGYVEmYz1CRnBXUXc4YnN1S3BsMVNnaVpINjRRJnI9STRkekd4DQo+ID4+
DQo+IFIzMU9jTlhDSmZRenZsc2lMUWZ1Y0JYUnVjUHZkcnBocEJzRkEmbT1EX0VVSjk3UXVTQWZa
UXRFY1BTc095RkkNCj4gPj4gcUp3MUU5VTRyV2dCaEtIVTI4YyZzPWVZaDlYcEVBOFdZaGpPSE9n
emplQWlhRmFpYWtiTEVJLQ0KPiA+PiB5TmFfbVdTU2lVJmU9DQo+ID4+DQo+ID4+IFlvdSBjYW4g
ZmluZCBmZXcgbW9yZSBoZXJlIChzZWFyY2ggRVRTSSBUUyAxMTgpOg0KPiA+PiBodHRwczovL3Vy
bGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cC0NCj4gPj4NCj4gM0FfX3dlYmFw
cC5ldHNpLm9yZ19hY3Rpb25fcHVfMjAxNTAyMjJfMjAxNTAyMjIuaHRtJmQ9QXdJRmFRJmM9Qg0K
PiA+Pg0KPiBGcFdRdzhic3VLcGwxU2dpWkg2NFEmcj1JNGR6R3hSMzFPY05YQ0pmUXp2bHNpTFFm
dWNCWFJ1Y1B2ZHJwaHBCDQo+ID4+IHNGQSZtPURfRVVKOTdRdVNBZlpRdEVjUFNzT3lGSXFKdzFF
OVU0cldnQmhLSFUyOGMmcz1ObGUzeDYtDQo+ID4+IGdvZ3l1TlUyR3J5LUh0VkdHUXZqdXNobDVq
WEJxZzhvWUJqayZlPQ0KPiA+Pg0KPiA+PiBCZXN0IHJlZ2FyZHMNCj4gPj4NCj4gPj4NCj4gPj4N
Cj4gPj4gMjAxNS0wMi0xMiAxNToxOSBHTVQrMDE6MDAgUm9tYXNjYW51LCBEYW4gKERhbikNCj4g
Pj4gPGRyb21hc2NhQGF2YXlhLmNvbT46DQo+ID4+ID4gSGksDQo+ID4+ID4NCj4gPj4gPg0KPiA+
PiA+DQo+ID4+ID4gUGxlYXNlIGZpbmQgYmVsb3cgbXkgY29tbWVudHMgb24gZHJhZnTigJBpZXRm
4oCQc2FjbeKAkGFyY2hpdGVjdHVyZeKAkDAyLiBJDQo+ID4+ID4gYWxzbyBhZGRyZXNzZWQgaW4g
bXkgY29tbWVudHMgc29tZSBvZiB0aGUgb3BlbiBxdWVzdGlvbnMgcmFpc2VkIGluDQo+ID4+ID4g
dGhlDQo+ID4+IEktRC4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4NCj4gPj4gPiAxLiAgICAgICBU
aGUgZmlyc3Qgc2VudGVuY2UgY29udGFpbnMgYSBsb2dpY2FsIHJlcGV0aXRpb24g4oCTIHRoZSBT
QUNNDQo+ID4+ID4gcmVmZXJlbmNlIGFyY2hpdGVjdHVyZSBpcyBvYnZpb3VzbHkgcmVsYXRlZCB0
byBTQUNNIChldmVuIGlmIG9uZSBpcw0KPiA+PiA+IHdpdGggYWNyb255bXMgZXhwYW5kZWQgYW5k
IHRoZSBvdGhlciBpcyBub3QpLiBQbGVhc2UgZmluZCBzb21lIG1vcmUNCj4gPj4gPiBpbnNwaXJp
bmcgd29yZHMgYXZvaWRpbmcgdGhlIHJlcGV0aXRpb24uDQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+
DQo+ID4+ID4gMi4gICAgICAgVGhlIG9wZW4gcXVlc3Rpb24gYXQgdGhlIGVuZCBvZiBTZWN0aW9u
IDI6DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4gw5ggIFdoeSBkb2VzIHRoZSBjaGFy
dGVyIG5vdCBzdWZmaWNlPw0KPiA+PiA+DQo+ID4+ID4gw5ggIFdoYXQgaXMgdGhlIHB1cnBvc2Ug
b2YgaW5zZXJ0aW5nIHRoaXMgc2VjdGlvbiBpbiB0aGlzIGRyYWZ0Pw0KPiA+PiA+DQo+ID4+ID4N
Cj4gPj4gPg0KPiA+PiA+IFRoZSBhbnN3ZXIgaXMgdGhhdCB0aGUgY2hhcnRlciBpcyBhIHRlbXBv
cmFyeSBkb2N1bWVudCB2aXNpYmxlIGFuZA0KPiA+PiA+IGFjY2Vzc2libGUgd2hpbGUgdGhlIFdH
IGlzIGFjdGl2ZSAoYW5kIHN1YmplY3QgdG8gY2hhbmdlIGR1cmluZw0KPiA+PiA+IHRoaXMNCj4g
Pj4gPiBwZXJpb2QpIGJ1dCB0ZW5kcyB0byBkaXNhcHBlYXJlZCB3aGVuIHRoZSBXRyBpcyBjb25j
bHVkZWQuIEEgcmVjYXANCj4gPj4gPiBvZiB0aGUgcHJvYmxlbSBzdGF0ZW1lbnQgaW4gdGhlIGlu
dHJvZHVjdG9yeSBzZWN0aW9ucyBvZiB0aGUNCj4gPj4gPiBhcmNoaXRlY3R1cmUgZG9jdW1lbnQg
cHJvdmlkZXMgYmFja2dyb3VuZCBpbmZvcm1hdGlvbiBmb3IgdGhlDQo+ID4+ID4gYXJjaGl0ZWN0
dXJlIHRoYXQgZm9sbG93cyBhbmQgY2FuIGJlIHZlcnkgdXNlZnVsIGZvciB1bmRlcnN0YW5kaW5n
DQo+ID4+ID4gc29tZSBvZiB0aGUgZnVuZGFtZW50YWwNCj4gPj4gZGVjaXNpb25zLg0KPiA+PiA+
DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+IDMuICAgICAgIEVkaXRvcmlhbCBpc3N1ZXMgaW4gU2Vj
dGlvbiAzLjEuMzoNCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4NCj4gPj4gPiBzL1RoZSBpbnRyb2R1
Y3Rpb24gb2YgdGhlIGNvbnRyb2xsZXIgc3VwcG9ydHMgdXNlIGNhc2VzLyBUaGUNCj4gPj4gPiBj
b250cm9sbGVyIHN1cHBvcnRzIHVzZSBjYXNlcy8NCj4gPj4gPg0KPiA+PiA+IHMvQ29uc3VtZXLi
gJlzL0NvbnN1bWVycy8NCj4gPj4gPg0KPiA+PiA+IHMvUHJvdmlkZXLigJlzL1Byb3ZpZGVycy8N
Cj4gPj4gPg0KPiA+PiA+IHMvaW50ZXJmYWNlIOKAnEPigJ0gc2hvd24gaW4gRmlndXJlIDEgZGVt
b25zdHJhdGVzLyBpbnRlcmZhY2Ug4oCcQ+KAnSBzaG93bg0KPiA+PiA+IGluIEZpZ3VyZSAxIGls
bHVzdHJhdGVzLw0KPiA+PiA+DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+IDQuICAgICAgIEluIG9y
ZGVyIHRvIHVuZGVyc3RhbmQgdGhlIHNlbnRlbmNlIOKAmGEgY29udHJvbGxlciBtYXkgYWxzbyBw
cm92aWRlDQo+ID4+ID4gdGhlIHByb3h5IG9yIGJyb2tlciAoYW5kIHBvc3NpYmx5IHJvdXRpbmcp
IGZ1bmN0aW9uIGluIHRoZSBkYXRhIHBsYW5l4oCZDQo+ID4+ID4gSSB3ZW50IGJhY2sgdG8gdGhl
IHRlcm1pbm9sb2d5IGRvY3VtZW50Lg0KPiA+PiA+DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+IFdo
YXQgSSBmb3VuZCBpcyB0aGF0IHRoZSBmb2xsb3dpbmcgdGVybXMgYXJlIGRlZmluZWQ6DQo+ID4+
ID4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4gICAgICAgICBCcm9rZXIgLSBBbiBlbnRpdHkgcHJv
dmlkaW5nIGFuZC9vciBjb25uZWN0aW5nIHNlcnZpY2VzIG9uDQo+ID4+ID4gdGhlIGJlaGFsZiBv
Zg0KPiA+PiA+DQo+ID4+ID4gICAgICAgb3RoZXIgYXJjaGl0ZWN0dXJhbCBjb21wb25lbnRzLg0K
PiA+PiA+DQo+ID4+ID4gICAgICAgICBQcm94eSAtIEFuIGFyY2hpdGVjdHVyYWwgY29tcG9uZW50
IHByb3ZpZGluZyBmdW5jdGlvbnMsDQo+ID4+ID4gaW5mb3JtYXRpb24sIG9yDQo+ID4+ID4NCj4g
Pj4gPiAgICAgICBzZXJ2aWNlcyBvbiBiZWhhbGYgb2YgYW5vdGhlciBjb21wb25lbnQsIHdoaWNo
IGlzIG5vdA0KPiA+PiA+IGRpcmVjdGx5DQo+ID4+ID4NCj4gPj4gPiAgICAgICBwYXJ0aWNpcGF0
aW5nIGluIHRoZSBhcmNoaXRlY3R1cmUuDQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4g
VGhlc2UgZGVmaW5pdGlvbnMgc2VlbSB0byBuZWVkIG1vcmUgd29yay4gVGhleSBhcmUgcGFydGlh
bGx5DQo+ID4+ID4gcmVkdW5kYW50IOKAkyBpcyB0aGlzIGJ5IGRlc2lnbj8gUHJveHkgaXMgbm90
IOKAmHBhcnRpY2lwYXRpbmcgaW4gdGhlDQo+IGFyY2hpdGVjdHVyZeKAmT8NCj4gPj4gPiBUaGVu
IGhvdyBpcyBpdCBiZXR3ZWVuIHRoZSAyLTMgZnVuZGFtZW50YWwgZnVuY3Rpb25zIG9mIHRoZQ0K
PiA+PiA+IGNvbnRyb2xsZXI/IFRoZXJlIG5lZWRzIHRvIGJlIG1vcmUgd29yayBpbiB0aGUgdGVy
bWlub2xvZ3kgZG9jdW1lbnQNCj4gPj4gPiBJDQo+ID4+IGd1ZXNzLg0KPiA+PiA+DQo+ID4+ID4N
Cj4gPj4gPg0KPiA+PiA+IDUuICBUT0RPIOKAkCBhZGQgdGV4dCBhcm91bmQgdGhlIHVzYWdlIG9m
IHZhcmlvdXMgcHJvdG9jb2xzIGZvcg0KPiA+PiA+IGVuZHBvaW50DQo+ID4+ID4NCj4gPj4gPiBk
YXRhIGNvbGxlY3Rpb24gKFNOTVAsIE5FVENPTkYsIGV0Yy4/KQ0KPiA+PiA+DQo+ID4+ID4NCj4g
Pj4gPg0KPiA+PiA+ICAgICAgICAgICAgICAgICBkbyB3ZSByZWFsbHkgbmVlZCB0aGVzZSBpbiBh
biBhcmNoaXRlY3R1cmUgZG9jdW1lbnQ/DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4g
VGhhbmtzIGFuZCBSZWdhcmRzLA0KPiA+PiA+DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+IERhbg0K
PiA+PiA+DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+DQo+
ID4+ID4NCj4gPj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPiA+PiA+IHNhY20gbWFpbGluZyBsaXN0DQo+ID4+ID4gc2FjbUBpZXRmLm9yZw0KPiA+
PiA+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4g
Pj4gM0FfX3d3dy5pZXRmLm9yZ19tYWlsDQo+ID4+ID4NCj4gPj4NCj4gbWFuX2xpc3RpbmZvX3Nh
Y20mZD1Bd0lGYVEmYz1CRnBXUXc4YnN1S3BsMVNnaVpINjRRJnI9STRkekd4UjMxDQo+ID4+IE9j
TlhDSmYNCj4gPj4gPg0KPiA+Pg0KPiBRenZsc2lMUWZ1Y0JYUnVjUHZkcnBocEJzRkEmbT1EX0VV
Sjk3UXVTQWZaUXRFY1BTc095RklxSncxRTlVNHINCj4gPj4gV2dCaEtIVQ0KPiA+PiA+IDI4YyZz
PW9fdzE3MFd2TVpyR1JtYkFpaWp5QTlGQ0paNFFjUlhXWWM4S29felNmUmcmZT0NCj4gPj4gPg0K


From nobody Mon Feb 23 03:22:38 2015
Return-Path: <dromasca@avaya.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 249471A1A1B for <sacm@ietfa.amsl.com>; Mon, 23 Feb 2015 03:22:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 jKmBMqQHpYvp for <sacm@ietfa.amsl.com>; Mon, 23 Feb 2015 03:22:35 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A478B1A1A46 for <sacm@ietf.org>; Mon, 23 Feb 2015 03:22:35 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4FALMM61SHCzIm/2dsb2JhbABbgkMhIiIwWgSwMwEBAQEBAQYFkiMiAQmFcAKBI0MBAQEBAQF8hBEBAQMSCxBeARUVViYBBBsaiA0BDKpshH+iRwEKAQEBGgSGB4lJLYI4DEEdgRQFj1KDXocAgxWCRIkBgz4ig25vAYFDfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,630,1418101200";  d="scan'208,217";a="105143926"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Feb 2015 06:22:34 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 23 Feb 2015 06:22:34 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Mon, 23 Feb 2015 06:22:33 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: IETF 92 - call for agenda items
Thread-Index: AdBPWwPMrMgqe7QARlqkZ/XHhh/ScQ==
Date: Mon, 23 Feb 2015 11:22:32 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C9A0903@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C9A0903AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/gsdAuxFn1GyXQvqZVGuGzNKHlos>
Subject: [sacm] IETF 92 - call for agenda items
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 11:22:37 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C9A0903AZFFEXMB04globa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The preliminary agenda of IETF 92 was posted at https://datatracker.ietf.or=
g/meeting/92/agenda.txt.

Note that this agenda is preliminary and the time of the meetings are subje=
ct to change.

The SACM WG has two scheduled sessions:

MONDAY, March 23, 2015

1300-1500  Afternoon Session I

Oak                    SEC     sacm           Security Automation and Conti=
nuous Monitoring WG


and:


FRIDAY, March 27, 2015

0900-1130  Morning Session I

Parisian               SEC     sacm           Security Automation and Conti=
nuous Monitoring WG

As we start building the agenda, please send your proposals about the struc=
ture of the two meetings, and the requests for presentation and discussion =
slots. Based on the proposals that we shall receive the chairs will build a=
nd post the draft agenda in the next few days.

Thanks and Regards,

Dan




--_000_9904FB1B0159DA42B0B887B7FA8119CA5C9A0903AZFFEXMB04globa_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">The preliminary agenda of IETF 92 was posted at <a h=
ref=3D"https://datatracker.ietf.org/meeting/92/agenda.txt">
https://datatracker.ietf.org/meeting/92/agenda.txt</a>. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Note that this agenda is preliminary and the time of=
 the meetings are subject to change.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The SACM WG has two scheduled sessions: <o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">MONDAY, March 23, 2015<o:p></o:p></span></p>
<pre><span style=3D"color:black">1300-1500&nbsp; Afternoon Session I<o:p></=
o:p></span></pre>
<pre><span style=3D"color:black">Oak&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEC =
&nbsp;&nbsp;&nbsp; sacm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nb=
sp; Security Automation and Continuous Monitoring WG<o:p></o:p></span></pre=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">and: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre><span style=3D"color:black">FRIDAY, March 27, 2015<o:p></o:p></span></=
pre>
<pre><span style=3D"color:black">0900-1130&nbsp; Morning Session I<o:p></o:=
p></span></pre>
<pre><span style=3D"color:black">Parisian&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEC &nbsp;&nbsp;&nbsp; sacm&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; Security Automation a=
nd Continuous Monitoring WG<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we start building the agenda, please send your pr=
oposals about the structure of the two meetings, and the requests for prese=
ntation and discussion slots. Based on the proposals that we shall receive =
the chairs will build and post the
 draft agenda in the next few days. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks and Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dan<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C9A0903AZFFEXMB04globa_--


From nobody Tue Feb 24 06:43:38 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5F81A0203 for <sacm@ietfa.amsl.com>; Tue, 24 Feb 2015 06:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 EbmmkbYv2yxo for <sacm@ietfa.amsl.com>; Tue, 24 Feb 2015 06:43:36 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A59E21A1B8E for <sacm@ietf.org>; Tue, 24 Feb 2015 06:43:35 -0800 (PST)
Received: by pablf10 with SMTP id lf10so36486717pab.6 for <sacm@ietf.org>; Tue, 24 Feb 2015 06:43:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=hQfyCNBtQ6IJkwhJMiqUOE8WkTOaaSk/xK1lPnEYV34=; b=IhMcyY/wpHnPuuMiMO20IX2q1dhB4uU7GnN1aMpNie/US2f7pziKANoKjonCVnU+C5 OgGEBm/cGZ3hEGbpP83ksrOZgPaOLIB1TDzvbghKFTlvojLbGI/4GP/JiKX2BKEjqtdQ v542oe8LTEiMZY86RtxVDjhSFMmRZiZsnqJ7sy7wVyLEyxg3xEQCPSQrCqgHds4KbD2y Cp0wd/7r+aq0HNp8ahsRWpsUGTTjZTubOahspPpxhby2ETnfRdZJWByR/mYKkJ/xoVp0 ovpYFY+seywZU2Ia9AMyMqiDxbv2Ds/bUYoRKrq8lwpjpSysdfKfFiEqTJZ5AcmlRcZ3 +WYA==
X-Received: by 10.68.191.233 with SMTP id hb9mr4174516pbc.111.1424789014884; Tue, 24 Feb 2015 06:43:34 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:190c:6781:576e:91a? ([2602:306:3406:4f00:190c:6781:576e:91a]) by mx.google.com with ESMTPSA id om9sm38395606pbb.34.2015.02.24.06.43.32 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Feb 2015 06:43:33 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D2CE9510-69B4-4B5F-B8E9-522145117F25"
Message-Id: <7256D1C8-E08C-4BE7-9BD1-0B48A68B168B@gmail.com>
Date: Tue, 24 Feb 2015 08:42:46 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/0Xh9PypYMB46UOwGM4HrRVN8SRI>
Subject: [sacm] (Belated) Notes from February Virtual Interim (2015-02-09)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Feb 2015 14:43:37 -0000

--Apple-Mail=_D2CE9510-69B4-4B5F-B8E9-522145117F25
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Sorry for the delay in getting the notes posted.  Thanks to Aziz for his =
contributions.

=
http://www.ietf.org/proceedings/interim/2015/02/09/sacm/minutes/minutes-in=
terim-2015-sacm-2 =
<http://www.ietf.org/proceedings/interim/2015/02/09/sacm/minutes/minutes-i=
nterim-2015-sacm-2>

Adam=

--Apple-Mail=_D2CE9510-69B4-4B5F-B8E9-522145117F25
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Sorry for the delay in getting the notes posted. &nbsp;Thanks to Aziz for his contributions.<div class=""><br class=""></div><div class=""><a href="http://www.ietf.org/proceedings/interim/2015/02/09/sacm/minutes/minutes-interim-2015-sacm-2" class="">http://www.ietf.org/proceedings/interim/2015/02/09/sacm/minutes/minutes-interim-2015-sacm-2</a></div><div class=""><br class=""></div><div class="">Adam</div></body></html>
--Apple-Mail=_D2CE9510-69B4-4B5F-B8E9-522145117F25--


From nobody Thu Feb 26 09:51:20 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F801A1B25 for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 09:51:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 tLD4m25lh86B for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 09:51:16 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B06C41A040B for <sacm@ietf.org>; Thu, 26 Feb 2015 09:51:16 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id va2so12852838obc.6 for <sacm@ietf.org>; Thu, 26 Feb 2015 09:51:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=fSYGaW2t4qW6it23utR5JpVDpTPf6xRO/vqxUmB8FN8=; b=rAlfq1ms8HdP7DPYxncB2X+jMtni5c6WIjwtq3q/NVMCQ5vcHJQSRIOypKMidIjgqa 2YeDM7mbTyncb6YgB2DARwuqGQSQCguR88Xo3VB1whDl+Oqblvdr+z91lapOYM/WJ+sR BqD3nM94+m+riTOiCPugDZiDo2yV77icFeT0Tl2ySVztA+TBab5AwKZ134WCALVoESPF ZksNBtJOOEnwDNWIPcReM8IS+ebvVciuDJ/85pPxyBl5usqoxJWh74JoOrohjJ/LK6mS 8ZwVI6LYbT2YoWANOZdzThL+LHGGRAA4FC2l3OhafYKdp7MCUH7rUmTSs9oNoC/oKW85 B1Nw==
X-Received: by 10.60.47.42 with SMTP id a10mr6898478oen.75.1424973075988; Thu, 26 Feb 2015 09:51:15 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:5de3:f334:ca80:9ae3? ([2602:306:3406:4f00:5de3:f334:ca80:9ae3]) by mx.google.com with ESMTPSA id s20sm692213oet.12.2015.02.26.09.51.14 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Feb 2015 09:51:15 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_795BEE3A-DBCE-413B-B99A-7FAB5BE3AE4D"
Message-Id: <779D6E67-219B-4AF8-86E5-E1F2538D84AA@gmail.com>
Date: Thu, 26 Feb 2015 11:50:24 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/C5wbH7rzhSYxb8sCRGiMP20qPdI>
Subject: [sacm] Endpoint ID Design Team Recording Available: 2015-02-20
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2015 17:51:18 -0000

--Apple-Mail=_795BEE3A-DBCE-413B-B99A-7FAB5BE3AE4D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks to Danny Haynes for reminding me to get the recording from last =
week=E2=80=99s design team meeting.

The recording should be available here: =
https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0 =
<https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0>

If you don=E2=80=99t see it there right away, give it a few minutes - =
it=E2=80=99s uploading now.

Regards,

Adam=

--Apple-Mail=_795BEE3A-DBCE-413B-B99A-7FAB5BE3AE4D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Thanks to Danny Haynes for reminding me to get the recording =
from last week=E2=80=99s design team meeting.<div class=3D""><br =
class=3D""></div><div class=3D"">The recording should be available =
here:&nbsp;<a =
href=3D"https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu=
_a?dl=3D0" =
class=3D"">https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3=
bRu_a?dl=3D0</a></div><div class=3D""><br class=3D""></div><div =
class=3D"">If you don=E2=80=99t see it there right away, give it a few =
minutes - it=E2=80=99s uploading now.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regards,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Adam</div></body></html>=

--Apple-Mail=_795BEE3A-DBCE-413B-B99A-7FAB5BE3AE4D--


From nobody Thu Feb 26 11:52:22 2015
Return-Path: <ncamwing@cisco.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78A951A1BB1 for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 11:52:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.21
X-Spam-Level: 
X-Spam-Status: No, score=-12.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 1iupBiVGTgxI for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 11:52:18 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5396F1A1BBC for <sacm@ietf.org>; Thu, 26 Feb 2015 11:52:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=42579; q=dns/txt; s=iport; t=1424980338; x=1426189938; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=7sXD0WYeTousSn4pKrbhe/Yiw2vqWS0+mGasPP8IqlY=; b=XSnZJiTzOhDeJsTepWBp81OBPEWL4mbKW1TAELWVw6GD8RjmeHG7Ez1W Qr63AMUHoEY7gm2s3GuhFfxJ+fpCdh/S4pR3DLNbNO0J+ELHv9rnIYU1w lcC0UwN53uVqD+oRtWS7uMkVDslZC2stR6TGn7y9Ry/Vt0xTHliwNvvgC c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BYBgD8eO9U/5xdJa1RCoI/Q1JaBL9TiCACgSRNAQEBAQEBfIQPAQIELV4BCBEBAgECIQEGORQDBggCBAESiC/XNwEBAQEBAQEDAQEBAQEBAQEaixOEEjgTGAKEKQWNdoF5iUWBG4Mei1KDPiODbm+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,654,1418083200";  d="scan'208,217";a="399503854"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 26 Feb 2015 19:52:17 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t1QJqHSG008971 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 26 Feb 2015 19:52:17 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.138]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Thu, 26 Feb 2015 13:52:17 -0600
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] comments on draft-ietf-sacm-requirements-03
Thread-Index: AQHQUf25XUIKATbq4kWVRcfXDlefag==
Date: Thu, 26 Feb 2015 19:52:16 +0000
Message-ID: <D11373F1.EA888%ncamwing@cisco.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C96165D@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.155.84.115]
Content-Type: multipart/alternative; boundary="_000_D11373F1EA888ncamwingciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/uuMO2KtrwJ07uX5OJyGFT1X2UAI>
Subject: Re: [sacm] comments on draft-ietf-sacm-requirements-03
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2015 19:52:21 -0000

--_000_D11373F1EA888ncamwingciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Dan,

Thanks for the feedback, I=92m working on resolving all your comments but h=
ave a question or two,
Please see below:

From: <Romascanu>, "Dan (Dan)" <dromasca@avaya.com<mailto:dromasca@avaya.co=
m>>
Date: Thursday, January 8, 2015 at 9:34 AM
To: "sacm@ietf.org<mailto:sacm@ietf.org>" <sacm@ietf.org<mailto:sacm@ietf.o=
rg>>
Subject: [sacm] comments on draft-ietf-sacm-requirements-03

I apologize for the delay, here are my comments on draft-ietf-sacm-requirem=
ents-03.

I am dividing them into Technical and Editorial.

Technical


T1. In the Introduction:


=D8  Scalable and sustainable collection, expression, and evaluation of

=D8     endpoint information is foundational to SACM's objectives.  To secu=
re

=D8     and defend a network one must reliably determine what devices are o=
n

=D8     the network, how those devices are configured from a hardware

=D8     perspective, what software products are installed on those devices,

=D8     and how those products are configured.  We need to be able to

=D8     determine, share, and use this information in a secure, timely,

=D8     consistent, and automated manner to perform endpoint posture

=D8     assessments.

The location, the interfaces of the devices to the network, and the network=
 topology are also factors that need to be known, understood, modelled and =
factored into the SACM requirements.
[NCW] Sounds reasonable.  I=92ve added some new requirements that speak to =
needing interfaces and network topology into the general requirements.

T2. The usage of the 2119 keywords is inconsistent. One example can be foun=
d in G-001. The requirements in #1, #2, #3 seem to be at the same level =96=
 yet one is capitalized, the other two are not. I suggest a review of all k=
eywords in the document and consistent usage, as per 2119.
[NCW] Have made a run thru all the requirements (old and new) and made an a=
ttempt to clarify them all.  Please review in the upcoming draft and let me=
 know if I missed any.

T3. Requirement G-002 seems to me to be content free, it is equivalent to =
=91we must write good standards=92.
[NCW] I=92m OK removing it, but wanted to make sure the group was OK with t=
hat, so for this upcoming version have left it as an editor=92s note to que=
ry group=85ok?

T4. G-003:  Scalability has one more dimension =96 what about big numbers o=
f endpoints?
[NCW] Right, I=92ve added more points of clarification to the dimension of =
data, topology and target endpoints.


T5. G-004: =91Considerations for lightweight implementations of data

    models and transports is required.=92 =96 this seems to be about downsc=
aling. Does this mean that each SACM standard must have a =91lightweight=92=
 variant, or that it=92s required for any SACM standard to be implemented o=
n lightweight (resource constrained) environments?

 [NCW] I placed the requirement as a =93SHOULD=94 as I=92m not sure it is f=
easible to make it a MUST for all implementations and yet address scalabili=
ty (especially with persistence).


T6. ARCH-002 =96 This requirement (if I understand it correctly) is about d=
eployment in single or federated environments (applications, networks). Why=
 is this called =91Agility=92?

 [NCW] Is a better word Flexibility? In that the architecture needs to be f=
lexibility enough (I chose agility because I was thinking =93nimble=94 or =
=93adaptable=94) to suit different deployments where there are a few partic=
ipating endpoints to very large w/in an enterprise to very large requiring =
federation (or small requiring federation).


T7. Section 2.3 mixes requirements for data models and information models =
=96 I believe that it needs to be broken in two separate sections, one for =
each

[NCW] I=92ve broken out the ones that are part of the operations on the dat=
a model and called that section as such.  But I=92m not sure which ones wou=
ld be information model specific?



T8. At IM-005 =96 IM-005  The data model SHOULD include management of the d=
ata,

    including data lifetime management (longevity or expiration of

    data).

What about persistence? In general I believe it=92s good practice to define=
 persistence in the IM, with specific implementation requirements in the DM

[NCW] Agreed, persistence has been added.



T9. IM-12 to IM-16 seem to me to belong more to the protocol that retrieves=
 information from the data model than to the data model or information mode=
l

[NCW] Right, these have been moved to a section of their own.



T10. IM-19 cannot be a requirement from the data model and is a trivial req=
uirement for the information model. Maybe the requirement tries to say some=
thing different =96 like different transport layers need to be supported =
=96 but then this is a again a requirement for the protocol that accesses t=
he data model, and not for the data model

 [NCW] While I agree, I think the spirit of the requirement is to ensure th=
at the operations on the data model could be consistent (interfaces) across=
 the different transports.  Given that, I=92m OK removing the requirement i=
f the group agrees (I=92ve added an editor=92s note to that effect too).





Editorial


E1. In the Abstract:


=D8  This document defines the scope and set of requirements for the

=D8     Secure Automation and Continuous Monitoring working group.

The requirements are not =91for the =85 working group=92 but for the archit=
ecture, data models, protocols
[NCW] Done in next revision

E2. When talking about sections in the use case document =96 it would be go=
od to provide reference (in brackets)
[NCW] Will try to do, admittedly, am not quite sure how to do the reference=
 in XML, it is okay to just =93[]=94 the section numbers by hand?

E3. Header error =96 need the name of the I-D not =91Abbreviated Title=92
[NCW] Can you help me identify where the header error is?

E4. In T-001 s/network transport/network, transport/
 [NCW] Done in next revision


I hope this helps.

Regards,

Dan



--_000_D11373F1EA888ncamwingciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <3132813587A00B498AB79CFF043C3540@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; font-size: 14px; font-family: Calibri, sans-ser=
if;">
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi Dan,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Thanks for the feedback, I=92m working on resolving all your comments but h=
ave a question or two,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Please see below:</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&lt;Romascanu&gt;, &quot;Dan =
(Dan)&quot; &lt;<a href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</a=
>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Thursday, January 8, 2015 at =
9:34 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:sacm@ie=
tf.org">sacm@ietf.org</a>&quot; &lt;<a href=3D"mailto:sacm@ietf.org">sacm@i=
etf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[sacm] comments on draft-i=
etf-sacm-requirements-03<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:234780247;
	mso-list-type:hybrid;
	mso-list-template-ids:1487203396 362958026 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:449470048;
	mso-list-type:hybrid;
	mso-list-template-ids:922241432 998702054 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I apologize for the delay, here are my comments on d=
raft-ietf-sacm-requirements-03.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am dividing them into Technical and Editorial. <o:=
p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Technical<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">T1. In the Introduction: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">Scalable and sustai=
nable collection, expression, and evaluation of<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;e=
ndpoint information is foundational to SACM's objectives.&nbsp; To secure<o=
:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;a=
nd defend a network one must reliably determine what devices are on<o:p></o=
:p></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;t=
he network, how those devices are configured from a hardware<o:p></o:p></sp=
an></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;p=
erspective, what software products are installed on those devices,<o:p></o:=
p></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;a=
nd how those products are configured.&nbsp; We need to be able to<o:p></o:p=
></span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;d=
etermine, share, and use this information in a secure, timely,<o:p></o:p></=
span></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;c=
onsistent, and automated manner to perform endpoint posture<o:p></o:p></spa=
n></pre>
<pre style=3D"margin-left:36.0pt;text-indent:-18.0pt;mso-list:l1 level1 lfo=
2"><!--[if !supportLists]--><span style=3D"font-family:Wingdings;color:blac=
k"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-style: normal; fo=
nt-variant: normal; font-weight: normal; font-size: 7pt; line-height: norma=
l; font-family: 'Times New Roman';">&nbsp; </span></span></span><!--[endif]=
--><span dir=3D"LTR"></span><span style=3D"color:black">&nbsp;&nbsp;&nbsp;a=
ssessments.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The location, the interfaces of the devices to the n=
etwork, and the network topology are also factors that need to be known, un=
derstood, modelled and factored into the SACM requirements.</p>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d">[NCW] Sounds reasonable. &nbsp;I=92ve added some ne=
w requirements that speak to needing interfaces and network topology into t=
he general requirements.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">T2. The usage of the 2119 keywords is inconsistent. =
One example can be found in G-001. The requirements in #1, #2, #3 seem to b=
e at the same level =96 yet one is capitalized, the other two are not. I su=
ggest a review of all keywords in the
 document and consistent usage, as per 2119.</p>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d"><font face=3D"Calibri,sans-serif">[NCW] Have made a=
 run thru all the requirements (old and new) and made an attempt to clarify=
 them all. &nbsp;Please review in the upcoming draft and let me know if&nbs=
p;I&nbsp;</font></font><font color=3D"#1f497d" face=3D"Calibri,sans-serif">=
missed
 any.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">T3. Requirement G-002 seems to me to be content free=
, it is equivalent to =91we must write good standards=92.</p>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d">[NCW]&nbsp;I=92m OK removing it, but wanted to make=
 sure the group was OK with that, so for this upcoming version have left it=
 as an editor=92s note to query group=85ok?</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">T4. G-003: &nbsp;Scalability has one more dimension =
=96 what about big numbers of endpoints?</p>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d">[NCW] Right,&nbsp;I=92ve added more points of clari=
fication to the dimension of data, topology and target endpoints.</font></d=
iv>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-serif; font-size=
: 14px; color: rgb(0, 0, 0);">
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-serif; font-size=
: 14px; color: rgb(0, 0, 0);">
<o:p>&nbsp;</o:p></p>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f;">T5. G-004: =91<span style=3D"color:black">Considerations for lightweigh=
t implementations of data<o:p></o:p></span></span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">&nbsp;&nbsp;&nbsp; models and transports is required.=92 =
=96 this seems to be about downscaling. Does this mean that each SACM stand=
ard must have a =91lightweight=92 variant, or that it=92s required for any =
SACM standard to be implemented on lightweight (resource constrained) envir=
onments? <o:p></o:p></span></pre>
<pre><o:p><font face=3D"Calibri,sans-serif" size=3D"3">&nbsp;</font><font c=
olor=3D"#1f497d"><font face=3D"Calibri,sans-serif" size=3D"3">[NCW] </font>=
<font face=3D"Calibri,sans-serif"><span style=3D"font-size: 15px;">I</span>=
</font><font face=3D"Calibri,sans-serif" size=3D"3"> placed the requirement=
 as a =93SHOULD=94 as I=92m not sure it is feasible to make it a MUST for a=
ll implementations and yet address scalability (especially with persistence=
).</font></font></o:p></pre>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">T6. ARCH-002 =96 This requirement (if I understand it cor=
rectly) is about deployment in single or federated environments (applicatio=
ns, networks). Why is this called =91Agility=92?<o:p></o:p></span></pre>
<pre><o:p><font face=3D"Calibri,sans-serif" size=3D"3">&nbsp;</font><font c=
olor=3D"#1f497d"><font face=3D"Calibri,sans-serif" size=3D"3">[NCW] Is a be=
tter word Flexibility? In that the architecture needs to be flexibility eno=
ugh (I chose agility because I was thinking =93nimble=94 or =93adaptable=94=
) to suit different deployments where there are a few participating endpoin=
ts to very large w/in an enterprise to very large requiring federation (or =
small requiring federation).</font></font></o:p></pre>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">T7. Section 2.3 mixes requirements for data models and in=
formation models =96 I believe that it needs to be broken in two separate s=
ections, one for each </span></pre>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d"><font face=3D"Calibri,sans-serif">[NCW]&nbsp;I=92ve=
 broken out the ones that are part of the operations on the data model and =
called that section as such. &nbsp;But&nbsp;I=92m not sure which ones would=
 be information model specific?</font></font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p></o:p></span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">T8. At IM-005 =96 </span><span style=3D"color:black">IM-0=
05&nbsp; The data model SHOULD include management of the data,<o:p></o:p></=
span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"color:black">&nbsp;&nbsp;&nbsp; including data l=
ifetime management (longevity or expiration of<o:p></o:p></span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"color:black">&nbsp;&nbsp;&nbsp; data).</span></p=
re>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">What about persistence? In general I believe it=92s good =
practice to define persistence in the IM, with specific implementation requ=
irements in the DM</span></pre>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d">[NCW] Agreed, persistence has been added.</font></d=
iv>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p></o:p></span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">T9. IM-12 to IM-16 seem to me to belong more to the proto=
col that retrieves information from the data model than to the data model o=
r information model</span></pre>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<font color=3D"#1f497d">[NCW] Right, these have been moved to a section of =
their own.</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0);">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<pre style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p></o:p></span></pre>
<pre style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;">T10. IM-19 cannot be a requirement from the data model an=
d is a trivial requirement for the information model. Maybe the requirement=
 tries to say something different =96 like different transport layers need =
to be supported =96 but then this is a again a requirement for the protocol=
 that accesses the data model, and not for the data model<o:p></o:p></span>=
</pre>
<pre><o:p style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; f=
ont-size: 14px;"><font face=3D"Calibri,sans-serif" size=3D"3">&nbsp;</font>=
<font color=3D"#1f497d"><font face=3D"Calibri,sans-serif" size=3D"3">[NCW] =
While </font><font face=3D"Calibri,sans-serif"><span style=3D"font-size: 15=
px;">I</span></font><font face=3D"Calibri,sans-serif" size=3D"3"> agree, I =
think the spirit of the requirement is to ensure that the operations on the=
 data model could be </font></font></o:p><font face=3D"Calibri,sans-serif" =
size=3D"3"><font color=3D"#000000" style=3D"color: rgb(31, 73, 125);">consi=
stent (interfaces) across the different transports.  Given that, </font><fo=
nt color=3D"#1f497d">I</font>=92<font><font color=3D"#1f497d">m OK removing=
 the requirement if the group agrees (I=92ve added an editor=92s note to th=
at effect too).</font></font></font></pre>
<pre style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;"><span style=3D"font-size: 11pt; font-family: Calibri, sans-seri=
f; color: black;"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
Editorial<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
E1. In the Abstract:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"color: rgb(0, 0, 0); font-family: Ca=
libri, sans-serif; font-size: 14px; text-indent: -18pt;">
<!--[if !supportLists]--><span style=3D"font-size:10.0pt;font-family:Wingdi=
ngs;color:black"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-sty=
le: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line=
-height: normal; font-family: 'Times New Roman';">&nbsp;
</span></span></span><!--[endif]--><span dir=3D"LTR"></span><span style=3D"=
font-size: 10pt; font-family: 'Courier New'; color: black;">This document d=
efines the scope and set of requirements for the<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"color: rgb(0, 0, 0); font-family: Ca=
libri, sans-serif; font-size: 14px; text-indent: -18pt;">
<!--[if !supportLists]--><span style=3D"font-size:10.0pt;font-family:Wingdi=
ngs;color:black"><span style=3D"mso-list:Ignore">=D8<span style=3D"font-sty=
le: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line=
-height: normal; font-family: 'Times New Roman';">&nbsp;
</span></span></span><!--[endif]--><span dir=3D"LTR"></span><span style=3D"=
font-size: 10pt; font-family: 'Courier New'; color: black;">&nbsp;&nbsp;&nb=
sp;Secure Automation and Continuous Monitoring working group.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
The requirements are not =91for the =85 working group=92 but for the archit=
ecture, data models, protocols</p>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0);"><font color=3D"#1f497d">[NCW]&nbsp;</fo=
nt><span style=3D"color: rgb(31, 73, 125);">Done in next revision</span></d=
iv>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0);">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
E2. <span style=3D"color:black">When talking about sections in the use case=
 document =96 it would be good to provide reference (in brackets)</span></p=
>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0);"><font color=3D"#1f497d">[NCW] Will try =
to do, admittedly, am not quite sure how to do the reference in XML, it is =
okay to just&nbsp;=93[]=94 the section numbers by hand?</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0);">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
E3. Header error =96 need the name of the I-D not =91Abbreviated Title=92</=
p>
</div>
</div>
</div>
</span>
<div style=3D"color: rgb(0, 0, 0);"><font color=3D"#1f497d">[NCW] Can you h=
elp me identify where the header error is?</font></div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
E4. In T-001 s/network transport/network, transport/<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-serif; font-size=
: 14px;"><o:p>&nbsp;<font color=3D"#1f497d">[NCW] Done in next revision</fo=
nt></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
I hope this helps. <o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
Regards,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
Dan<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); font-family: Calibri, =
sans-serif; font-size: 14px;">
<o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D11373F1EA888ncamwingciscocom_--


From nobody Thu Feb 26 16:07:46 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7178C1A9082; Thu, 26 Feb 2015 16:07:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 l8cEwxXuuj43; Thu, 26 Feb 2015 16:07:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC901A909F; Thu, 26 Feb 2015 16:07:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150227000742.4552.15829.idtracker@ietfa.amsl.com>
Date: Thu, 26 Feb 2015 16:07:42 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/OzOKTPoZZdOmx4XH0G1A9ZKBa9o>
Cc: sacm@ietf.org
Subject: [sacm] I-D Action: draft-ietf-sacm-use-cases-08.txt
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 00:07:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Security Automation and Continuous Monitoring Working Group of the IETF.

        Title           : Endpoint Security Posture Assessment - Enterprise Use Cases
        Authors         : David Waltermire
                          David Harrington
	Filename        : draft-ietf-sacm-use-cases-08.txt
	Pages           : 28
	Date            : 2015-02-26

Abstract:
   This memo documents a sampling of use cases for securely aggregating
   configuration and operational data and evaluating that data to
   determine an organization's security posture.  From these operational
   use cases, we can derive common functional capabilities and
   requirements to guide development of vendor-neutral, interoperable
   standards for aggregating and evaluating data relevant to security
   posture.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sacm-use-cases/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-sacm-use-cases-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-sacm-use-cases-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Feb 26 16:08:23 2015
Return-Path: <david.waltermire@nist.gov>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7773E1A90A6 for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 16:08:22 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Mo0MArSKJ-gy for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 16:08:19 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0102.outbound.protection.outlook.com [207.46.100.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58AB11A9097 for <sacm@ietf.org>; Thu, 26 Feb 2015 16:08:19 -0800 (PST)
Received: from DM2PR09MB0367.namprd09.prod.outlook.com (25.160.247.21) by DM2PR09MB0303.namprd09.prod.outlook.com (25.160.96.148) with Microsoft SMTP Server (TLS) id 15.1.93.16; Fri, 27 Feb 2015 00:08:18 +0000
Received: from DM2PR09MB0365.namprd09.prod.outlook.com (25.160.247.18) by DM2PR09MB0367.namprd09.prod.outlook.com (25.160.247.21) with Microsoft SMTP Server (TLS) id 15.1.93.16; Fri, 27 Feb 2015 00:08:17 +0000
Received: from DM2PR09MB0365.namprd09.prod.outlook.com ([25.160.247.18]) by DM2PR09MB0365.namprd09.prod.outlook.com ([25.160.247.18]) with mapi id 15.01.0093.004; Fri, 27 Feb 2015 00:08:17 +0000
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] AD Review of SACM Use Case Draft
Thread-Index: AQHQSgDcndOrKBxlLkquKT7evMf96J0DplNw
Date: Fri, 27 Feb 2015 00:08:16 +0000
Message-ID: <DM2PR09MB03658ACAAE5927030031A577F0150@DM2PR09MB0365.namprd09.prod.outlook.com>
References: <CAHbuEH4CNR21UskzwdET5PNh7RMCrpAEsKjcAoBHm+KTt7i5PQ@mail.gmail.com>
In-Reply-To: <CAHbuEH4CNR21UskzwdET5PNh7RMCrpAEsKjcAoBHm+KTt7i5PQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.227.107]
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0367;UriScan:;
x-microsoft-antispam-prvs: <DM2PR09MB03677CCFB8B352F92320F4BCFB150@DM2PR09MB0367.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0367;
x-forefront-prvs: 05009853EF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(164054003)(479174004)(15975445007)(2950100001)(66066001)(99286002)(106116001)(19617315012)(19580405001)(19580395003)(102836002)(33656002)(76176999)(107886001)(2900100001)(19300405004)(92566002)(2501003)(50986999)(54356999)(40100003)(122556002)(77156002)(19625215002)(16236675004)(2656002)(87936001)(86362001)(46102003)(74316001)(76576001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0367; H:DM2PR09MB0365.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_DM2PR09MB03658ACAAE5927030031A577F0150DM2PR09MB0365namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2015 00:08:16.1114 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0367
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0303;
X-OriginatorOrg: nist.gov
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/Eb5PzAbo19dAvm0wXN1qCVh6XNQ>
Subject: Re: [sacm] AD Review of SACM Use Case Draft
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 00:08:22 -0000

--_000_DM2PR09MB03658ACAAE5927030031A577F0150DM2PR09MB0365namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

S2F0aGxlZW4sDQoNCkkganVzdCBwb3N0ZWQgYW4gdXBkYXRlZCB1c2UgY2FzZXMgZHJhZnQgYmFz
ZWQgb24geW91ciBjb21tZW50cyBiZWxvdyBhbmQgeW91ciBwcmV2aW91cyBjb21tZW50cyBvbiAx
MS81LzIwMTQgKGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9zYWNtL2N1cnJl
bnQvbXNnMDIxMzkuaHRtbCkuDQoNCkRpc2N1c3Npb24gb2YgdGhlIGNoYW5nZXMgYXJlIGlubGlu
ZSBiZWxvdy4gUGxlYXNlIGxldCBtZSBrbm93IGlmIHlvdeKAmWQgbGlrZSB0byBzZWUgYW55IGFk
ZGl0aW9uYWwgZWRpdHMuDQoNClRoYW5rcywNCkRhdmUNCg0KRnJvbTogc2FjbSBbbWFpbHRvOnNh
Y20tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEthdGhsZWVuIE1vcmlhcnR5DQpTZW50
OiBNb25kYXksIEZlYnJ1YXJ5IDE2LCAyMDE1IDEwOjU0IEFNDQpUbzogc2FjbUBpZXRmLm9yZw0K
U3ViamVjdDogW3NhY21dIEFEIFJldmlldyBvZiBTQUNNIFVzZSBDYXNlIERyYWZ0DQoNCkhlbGxv
LA0KDQpUaGUgZm9sbG93aW5nIGlzIG15IHJldmlldyBvZiB0aGUgU0FDTSB1c2UgY2FzZSBkcmFm
dC4gIFNpbmNlIHRoaXMgaXMgYSBjaGFydGVkIGl0ZW0gYW5kIG1pbGVzdG9uZSBmb3IgU0FDTSwg
dGhlIHdvcmsgY2FuIHByb2NlZWQuICBBIHN0YXRlbWVudCBmcm9tIHRoZSBJRVNHIG9uIHVzZSBj
YXNlIGRyYWZ0cyB3aWxsIGJlIGNvbWluZyBvdXQgc29vbiwgdGhhbmtzIHRvIHRob3NlIHRoYXQg
YXNzaXN0ZWQgaW4gYnVpbGRpbmcgYXJndW1lbnRzLg0KDQpTQUNNIHVzZSBjYXNlIGRyYWZ0Og0K
DQpJbnRyb2R1Y3Rpb246DQpTZWNvbmQgc2VudGVuY2UgLSBzaG91bGQgdGhpcyBiZSBhIGJ1bGxl
dGVkIGxpc3Qgb3IgYmUgbXVsdGlwbGUgc2VudGVuY2VzPw0KICAgSXQgcHJvdmlkZXMgYSBkaXNj
dXNzaW9uIG9mDQogICB0aGVzZSB1c2UgY2FzZXMgYW5kIGFzc29jaWF0ZWQgYnVpbGRpbmcgYmxv
Y2sgY2FwYWJpbGl0aWVzIHRoYXQNCiAgIHN1cHBvcnQgc2VjdXJlbHkgYWdncmVnYXRpbmcgY29u
ZmlndXJhdGlvbiBhbmQgb3BlcmF0aW9uYWwgZGF0YSBhbmQNCiAgIGV2YWx1YXRpbmcgdGhhdCBk
YXRhIHRvIGRldGVybWluZSB0aGUgc2VjdXJpdHkgcG9zdHVyZSBvZiBpbmRpdmlkdWFsDQogICBl
bmRwb2ludHMsIGFuZCwgaW4gdGhlIGFnZ3JlZ2F0ZSwgdGhlIHNlY3VyaXR5IHBvc3R1cmUgb2Yg
YW4NCiAgIGVudGVycHJpc2UuDQoNCltkYXc6IEkgYnJva2UgdGhpcyBvdXQgYXMgYSBidWxsZXRl
ZCBsaXN0Ll0NCg0KMm5kIHBhcmFncmFwaCwgMXN0IHNlbnRlbmNlLCAiaW5mb3JtYXRpb24iIGlz
IHJlZHVuZGFudDoNCiAgIFRoZXNlIHVzZSBjYXNlcyBhbmQgdXNhZ2Ugc2NlbmFyaW9zIGNyb3Nz
IG1hbnkgSVQgc2VjdXJpdHkNCiAgIGluZm9ybWF0aW9uIGRvbWFpbnMuDQoNCltkYXc6IERlbGV0
ZWQg4oCcaW5mb3JtYXRpb27igJ0uXQ0KDQpUaGVyZSBhcmUgbG90cyBvZiByZWFsbHkgbG9uZyBz
ZW50ZW5jZXMsIGxhc3Qgc2VudGVuY2Ugb2YgM3JkIHBhcmFncmFwaCBpcyAgcnVuLW9uLg0KDQpT
ZWN0aW9uIDIuMi4yDQpDYW4geW91IGJyZWFrIHRoaXMgc2VudGVuY2UgaW50byBhIGZldz8NCiAg
IFVzaW5nIHRoZSBjb2xsZWN0ZWQgaGFyZHdhcmUgYW5kIHNvZnR3YXJlIGludmVudG9yeSBkYXRh
IGFuZA0KICAgYXNzb2NpYXRlZCBhc3NldCBjaGFyYWN0ZXJpemF0aW9uIGRhdGEgdGhhdCBtYXkg
aW5kaWNhdGUgdGhlDQogICBvcmdhbml6YXRpb25hbCBkZWZpbmVkIGZ1bmN0aW9ucyBvZiBlYWNo
IGVuZHBvaW50LCBjaGVja2xpc3QgZ3VpZGFuY2UNCiAgIGlzIHF1ZXJpZWQsIGxvY2F0ZWQgYW5k
IGRvd25sb2FkZWQgZnJvbSB0aGUgYXBwcm9wcmlhdGUgdmVuZG9yIGFuZA0KICAgM3JkLXBhcnR5
IHNlY3VyaXR5IGF1dG9tYXRpb24gZGF0YSBzdG9yZSBmb3IgdGhlIGFwcHJvcHJpYXRlDQogICBj
aGVja2xpc3RzLg0KDQpbZGF3OiBNYWRlIHRoaXMgYSBidWxsZXRlZCBsaXN0Ll0NCg0KU2FtZSBz
ZWN0aW9uLCBmb2xsb3dpbmcgc2VudGVuY2U6DQogV2hpbGUgc3BlY2lmaWMgYXBwbGljYXRpb25z
IGZvciBjaGVja2xpc3RzIHJlc3VsdHMgYXJlIG91dC1vZi1zY29wZQ0Kcy9jaGVja2xpc3RzL2No
ZWNrbGlzdC8NCg0KQW5kIEkgZG9uJ3QgcmVhbGx5IGZvbGxvdyB0aGUgbG9naWMgb2YgdGhlIGZ1
bGwgdHJhbnNpdGlvbmFsIHNlbnRlbmNlOg0KICAgV2hpbGUgc3BlY2lmaWMgYXBwbGljYXRpb25z
IGZvciBjaGVja2xpc3RzIHJlc3VsdHMgYXJlIG91dC1vZi1zY29wZQ0KICAgZm9yIGN1cnJlbnQg
U0FDTSBlZmZvcnRzLCBob3cgdGhlIGRhdGEgaXMgdXNlZCBtYXkgaWxsdW1pbmF0ZQ0KICAgc3Bl
Y2lmaWMgbGF0ZW5jeSBhbmQgYmFuZHdpZHRoIHJlcXVpcmVtZW50cy4gIEZvciB0aGlzIHB1cnBv
c2UgdXNlIG9mDQogICBjaGVja2xpc3QgYXNzZXNzbWVudCByZXN1bHRzIG1heSBpbmNsdWRlLCBi
dXQgYXJlIG5vdCBsaW1pdGVkIHRvOg0KDQpbZGF3OiBBIGZldyBwYXJhZ3JhcGhzIGluIHRoaXMg
c2VjdGlvbiBqdW1wZWQgYXJvdW5kIGluIHRoZSBjb25jZXB0cyB0aGV5IHdlcmUgZGlzY3Vzc2lu
Zy4gSSByZW9yZ2FuaXplZCBhbmQgYnJva2UgdXAgc29tZSBvZiB0aGUgY29udGVudCBpbiB0aGlz
IHNlY3Rpb24gdG8gbWFrZSBpdCBlYXNpZXIgdG8gZm9sbG93LiBQbGVhc2UgbGV0IG1lIGtub3cg
aWYgeW91IHdvdWxkIGxpa2UgdG8gc2VlIGFueSBhZGRpdGlvbmFsIGNoYW5nZXMuXQ0KDQpDb3Vs
ZCB5b3UgaW50cm9kdWNlIGxhdGVuY3kgYW5kIGJhbmR3aWR0aCBpbiBhIGRpZmZlcmVudCB3YXk/
ICBJdCBzZWVtcyBvZGQgdG8gZm9sbG93IGZyb20gZGVzY3JpcHRpb25zIG9uIHR5cGVzIG9mIGNo
ZWNrbGlzdHMgKG9yICdhcHBsaWNhdGlvbnMgb2YgY2hlY2tsaXN0cycpLg0KDQpbZGF3OiBJIGNo
YW5nZWQgdGhlIHRleHQgdG8gY2FsbCBvdXQgZGF0YSBhdmFpbGFiaWxpdHksIHRpbWVsaW5lc3Ms
IGFuZCBsaXZlbmVzcyBhcyBzb21ldGhpbmcgdGhhdCBuZWVkcyB0byBiZSBjb25zaWRlcmVkIHJl
bGF0aXZlIHRvIG9wZXJhdGlvbmFsIGNvbnN0cmFpbnRzIGFyb3VuZCBuZXR3b3JrIGxhdGVuY3kg
YW5kIGF2YWlsYWJsZSBiYW5kd2lkdGguIFBsZWFzZSBsZXQgbWUga25vdyBpZiB5b3XigJlkIGxp
a2UgdG8gc2VlIGZ1cnRoZXIgY2hhbmdlcy5dDQoNCk5vdyB0aGF0IEkgcmVhZCB0aGUgdHlwZXMg
b2YgY2hlY2tsaXN0cyBhbmQgaG93IHZhcmllZCB0aGV5IGFyZSwgSSB0aGluayBpdCBtYXkgYmUg
YmV0dGVyIHRvIGRlbGV0ZSB0aGUgdHJhbnNpdGlvbmFsIHNlbnRlbmNlIGxpc3RlZCBhYm92ZSBh
cyB0aGVyZSBhcmUgbWFueSBvdGhlciB0eXBlcyBvZiBjaGVja2xpc3RzIGluY2x1ZGVkIGluIHRo
ZSBsaXN0IHRoYXQgZm9sbG93cy4NCg0KW2RhdzogVGhlcmUgd2VyZSBtdWx0aXBsZSBwYXJhZ3Jh
cGhzIGlkZW50aWZ5aW5nIGRpZmZlcmVudCBjaGVja2xpc3QgdHlwZXMuIEkgY29uc29saWRhdGVk
IHRoZXNlIHdpdGggYSBzaG9ydGVyIHRyYW5zaXRpb25hbCBzZW50ZW5jZS5dDQoNClNlY3Rpb24g
Mi4yLjQNCkNvdWxkIHlvdSBtYWtlIGl0IG1vcmUgY2xlYXIgdGhhdCB0aGUgcXVlcnkgbWVjaGFu
aXNtIGRlc2NyaWJlZCBpbnQgaGlzIHNlY3Rpb24gaXMgdG8gYmUgcHJvdmlkZWQgYnkgU0FDTT8g
IEkgYXNzdW1lIHRoYXQgaXMgdGhlIGNhc2UuICBUaGlzIG1heSBjb21lIHVwIGluIG90aGVyIHJl
dmlld3MsIHdoeSBpcyB0aGUgc2VjdGlvbiBoZXJlIGlmIGl0IGRvZXNuJ3QgdXNlIFNBQ00uDQoN
CltkYXc6IEFkZGVkIHRleHQgc3BlYWtpbmcgdG8gdGhpcy5dDQoNClNlY3Rpb24gNCwgU2VjdXJp
dHkgQ29uc2lkZXJhdGlvbnMuDQpJIHJlY29tbWVuZCByZXBsYWNpbmcgdGhlIGZvbGxvd2luZyBz
ZW50ZW5jZToNCiAgIFdoaWxlIGl0IGlzIGFib3V0IHNlY3VyaXR5LCBpdCBkb2VzIG5vdCBhZmZl
Y3QNCiAgIHNlY3VyaXR5Lg0Kd2l0aCBzb21ldGhpbmcgdGhhdCBleHBsYWlucyB3aGVyZSB0aGUg
c2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgd2lsbCBiZSBhZGRyZXNzZWQuICBTb21ldGhpbmcgbGlr
ZToNCiAgIFNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIHdpbGwgYmUgcHJvdmlkZWQgaW4gc29sdXRp
b24NCiAgIHN0YW5kYXJkcyBhcyBhcHByb3ByaWF0ZSB0byB0aGUgZnVuY3Rpb24gZGVzY3JpYmVk
DQogICBpbiBlYWNoIHNvbHV0aW9uIGRvY3VtZW50Lg0KDQpbZGF3OiBBZGRlZCB0ZXh0IHNwZWFr
aW5nIHRvIHRoaXMgd2l0aCBleGFtcGxlcyBvZiByZWxhdGVkIGRvY3VtZW50cy5dDQoNCjUuIEFj
a25vd2xlZGdlbWVudHMNCg0KSXMgIlNlY3VyaXR5IEF1dG9tYXRpb24iIGNvcHlyaWdodGVkIG9y
IHRyYWRlbWFya2VkPyAgVGhlIGZpcnN0IHBhcmFncmFwaCBpcyBvZGQgaWYgaXQgaXMgbm90LiAg
SWYgaXQgaXMsIHRoZW4gZGlzY2xvc3VyZXMgYXJlIG5lZWRlZC4gIEJ5IGhhdmluZyB0aGlzIHNl
bnRlbmNlIGluIHRoZSBkcmFmdCwgc29tZSB0eXBlIG9mIGRpc2Nsb3N1cmUgbWF5IGJlIG5lZWRl
ZCBzbyBwZW9wbGUgdW5kZXJzdGFuZCB3aHkgaXQgaXMgdGhlcmUgYXMgdGhlcmUgYXJlIG1hbnkg
aW5zdGFuY2VzIG9mIHNlY3VyaXR5IGF1dG9tYXRpb24gYnkgdmVuZG9ycyBhbmQgZ3JvdXBzIGxp
a2UgSUNBU0kgYW5kIFRDRy4NCg0KW2RhdzogVGhlcmUgaXMgbm90IGNvcHlyaWdodCBvciB0cmFk
ZW1hcmsgZm9yIOKAnFNlY3VyaXR5IEF1dG9tYXRpb27igJ0gdGhhdCBJIGFtIGF3YXJlIG9mLiBJ
IGRlbGV0ZWQgdGhlIHNlbnRlbmNlIHNpbmNlIGl0IGlzbuKAmXQgcmVhbGx5IHJlbGV2YW50IHRv
IHRoaXMgZG9jdW1lbnQuXQ0KDQotLQ0KDQpCZXN0IHJlZ2FyZHMsDQpLYXRobGVlbg0K

--_000_DM2PR09MB03658ACAAE5927030031A577F0150DM2PR09MB0365namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQs
IHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5
bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVm
YXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxv
OmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwh
W2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZs
aW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+S2F0aGxl
ZW4sPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj5JIGp1c3QgcG9zdGVkIGFuIHVwZGF0ZWQgdXNlIGNhc2VzIGRyYWZ0IGJh
c2VkIG9uIHlvdXIgY29tbWVudHMgYmVsb3cgYW5kIHlvdXIgcHJldmlvdXMgY29tbWVudHMgb24g
MTEvNS8yMDE0ICg8YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIv
c2FjbS9jdXJyZW50L21zZzAyMTM5Lmh0bWwiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNo
aXZlL3dlYi9zYWNtL2N1cnJlbnQvbXNnMDIxMzkuaHRtbDwvYT48L3NwYW4+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij4pLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5EaXNjdXNzaW9uIG9mIHRoZSBjaGFuZ2VzIGFyZSBpbmxpbmUgYmVsb3cuIFBsZWFzZSBsZXQg
bWUga25vdyBpZiB5b3XigJlkIGxpa2UgdG8gc2VlIGFueSBhZGRpdGlvbmFsIGVkaXRzLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UaGFua3MsPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
Ij5EYXZlPHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gc2FjbSBbbWFpbHRvOnNhY20tYm91bmNlc0Bp
ZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+S2F0aGxlZW4gTW9yaWFydHk8YnI+DQo8Yj5T
ZW50OjwvYj4gTW9uZGF5LCBGZWJydWFyeSAxNiwgMjAxNSAxMDo1NCBBTTxicj4NCjxiPlRvOjwv
Yj4gc2FjbUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBbc2FjbV0gQUQgUmV2aWV3IG9m
IFNBQ00gVXNlIENhc2UgRHJhZnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5IZWxsbyw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRo
ZSBmb2xsb3dpbmcgaXMgbXkgcmV2aWV3IG9mIHRoZSBTQUNNIHVzZSBjYXNlIGRyYWZ0LiZuYnNw
OyBTaW5jZSB0aGlzIGlzIGEgY2hhcnRlZCBpdGVtIGFuZCBtaWxlc3RvbmUgZm9yIFNBQ00sIHRo
ZSB3b3JrIGNhbiBwcm9jZWVkLiZuYnNwOyBBIHN0YXRlbWVudCBmcm9tIHRoZSBJRVNHIG9uIHVz
ZSBjYXNlIGRyYWZ0cyB3aWxsIGJlIGNvbWluZyBvdXQgc29vbiwgdGhhbmtzIHRvIHRob3NlIHRo
YXQgYXNzaXN0ZWQgaW4gYnVpbGRpbmcNCiBhcmd1bWVudHMuPG86cD48L286cD48L3A+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U0FDTSB1c2UgY2FzZSBkcmFmdDo8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SW50cm9k
dWN0aW9uOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+U2Vjb25kIHNlbnRlbmNlIC0gc2hvdWxkIHRoaXMgYmUgYSBidWxsZXRlZCBsaXN0IG9yIGJl
IG11bHRpcGxlIHNlbnRlbmNlcz88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtJdCBwcm92aWRlcyBhIGRpc2N1c3Npb24gb2Y8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNw
OyAmbmJzcDt0aGVzZSB1c2UgY2FzZXMgYW5kIGFzc29jaWF0ZWQgYnVpbGRpbmcgYmxvY2sgY2Fw
YWJpbGl0aWVzIHRoYXQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtzdXBwb3J0IHNlY3VyZWx5IGFnZ3JlZ2F0aW5nIGNvbmZp
Z3VyYXRpb24gYW5kIG9wZXJhdGlvbmFsIGRhdGEgYW5kPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7ZXZhbHVhdGluZyB0aGF0
IGRhdGEgdG8gZGV0ZXJtaW5lIHRoZSBzZWN1cml0eSBwb3N0dXJlIG9mIGluZGl2aWR1YWw8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAm
bmJzcDtlbmRwb2ludHMsIGFuZCwgaW4gdGhlIGFnZ3JlZ2F0ZSwgdGhlIHNlY3VyaXR5IHBvc3R1
cmUgb2YgYW48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPiZuYnNwOyAmbmJzcDtlbnRlcnByaXNlLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPltkYXc6IEkgYnJv
a2UgdGhpcyBvdXQgYXMgYSBidWxsZXRlZCBsaXN0Ll08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjJuZCBwYXJhZ3JhcGgsIDFzdCBzZW50ZW5jZSwgJnF1b3Q7aW5mb3JtYXRpb24mcXVvdDsgaXMg
cmVkdW5kYW50OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7ICZuYnNwO1RoZXNlIHVzZSBjYXNlcyBhbmQgdXNhZ2Ugc2NlbmFyaW9zIGNy
b3NzIG1hbnkgSVQgc2VjdXJpdHk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtpbmZvcm1hdGlvbiBkb21haW5zLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPltkYXc6IERlbGV0ZWQg4oCcaW5mb3JtYXRpb27igJ0uXTxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+VGhlcmUgYXJlIGxvdHMgb2YgcmVhbGx5IGxvbmcgc2VudGVuY2VzLCBsYXN0IHNlbnRl
bmNlIG9mIDNyZCBwYXJhZ3JhcGggaXMgJm5ic3A7cnVuLW9uLjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TZWN0aW9uIDIuMi4yPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DYW4geW91IGJyZWFr
IHRoaXMgc2VudGVuY2UgaW50byBhIGZldz88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtVc2luZyB0aGUgY29sbGVjdGVkIGhh
cmR3YXJlIGFuZCBzb2Z0d2FyZSBpbnZlbnRvcnkgZGF0YSBhbmQ8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDthc3NvY2lhdGVk
IGFzc2V0IGNoYXJhY3Rlcml6YXRpb24gZGF0YSB0aGF0IG1heSBpbmRpY2F0ZSB0aGU8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJz
cDtvcmdhbml6YXRpb25hbCBkZWZpbmVkIGZ1bmN0aW9ucyBvZiBlYWNoIGVuZHBvaW50LCBjaGVj
a2xpc3QgZ3VpZGFuY2U8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtpcyBxdWVyaWVkLCBsb2NhdGVkIGFuZCBkb3dubG9hZGVk
IGZyb20gdGhlIGFwcHJvcHJpYXRlIHZlbmRvciBhbmQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDszcmQtcGFydHkgc2VjdXJp
dHkgYXV0b21hdGlvbiBkYXRhIHN0b3JlIGZvciB0aGUgYXBwcm9wcmlhdGU8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtjaGVj
a2xpc3RzLiAmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5bZGF3OiBNYWRlIHRoaXMgYSBidWxsZXRlZCBsaXN0
Ll08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNhbWUgc2VjdGlvbiwgZm9sbG93aW5nIHNlbnRl
bmNlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Jm5ic3A7V2hpbGUgc3BlY2lmaWMgYXBwbGljYXRpb25zIGZvciBjaGVja2xpc3RzIHJlc3VsdHMg
YXJlIG91dC1vZi1zY29wZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+cy9jaGVja2xpc3RzL2NoZWNrbGlzdC88bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QW5kIEkgZG9uJ3QgcmVhbGx5IGZvbGxv
dyB0aGUgbG9naWMgb2YgdGhlIGZ1bGwgdHJhbnNpdGlvbmFsIHNlbnRlbmNlOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO1do
aWxlIHNwZWNpZmljIGFwcGxpY2F0aW9ucyBmb3IgY2hlY2tsaXN0cyByZXN1bHRzIGFyZSBvdXQt
b2Ytc2NvcGU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPiZuYnNwOyAmbmJzcDtmb3IgY3VycmVudCBTQUNNIGVmZm9ydHMsIGhvdyB0aGUgZGF0YSBp
cyB1c2VkIG1heSBpbGx1bWluYXRlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7c3BlY2lmaWMgbGF0ZW5jeSBhbmQgYmFuZHdp
ZHRoIHJlcXVpcmVtZW50cy4mbmJzcDsgRm9yIHRoaXMgcHVycG9zZSB1c2Ugb2Y8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtj
aGVja2xpc3QgYXNzZXNzbWVudCByZXN1bHRzIG1heSBpbmNsdWRlLCBidXQgYXJlIG5vdCBsaW1p
dGVkIHRvOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDsiPltkYXc6IEEgZmV3IHBhcmFncmFwaHMgaW4gdGhpcyBzZWN0aW9u
IGp1bXBlZCBhcm91bmQgaW4gdGhlIGNvbmNlcHRzIHRoZXkgd2VyZSBkaXNjdXNzaW5nLiBJIHJl
b3JnYW5pemVkIGFuZCBicm9rZSB1cCBzb21lIG9mIHRoZSBjb250ZW50IGluIHRoaXMgc2VjdGlv
biB0byBtYWtlIGl0IGVhc2llcg0KIHRvIGZvbGxvdy4gUGxlYXNlIGxldCBtZSBrbm93IGlmIHlv
dSB3b3VsZCBsaWtlIHRvIHNlZSBhbnkgYWRkaXRpb25hbCBjaGFuZ2VzLl08bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkNvdWxkIHlvdSBpbnRyb2R1Y2UgbGF0ZW5jeSBhbmQgYmFuZHdpZHRoIGlu
IGEgZGlmZmVyZW50IHdheT8mbmJzcDsgSXQgc2VlbXMgb2RkIHRvIGZvbGxvdyBmcm9tIGRlc2Ny
aXB0aW9ucyBvbiB0eXBlcyBvZiBjaGVja2xpc3RzIChvciAnYXBwbGljYXRpb25zIG9mIGNoZWNr
bGlzdHMnKS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5bZGF3OiBJIGNoYW5nZWQgdGhlIHRleHQgdG8gY2FsbCBvdXQg
ZGF0YSBhdmFpbGFiaWxpdHksIHRpbWVsaW5lc3MsIGFuZCBsaXZlbmVzcyBhcyBzb21ldGhpbmcg
dGhhdCBuZWVkcyB0byBiZSBjb25zaWRlcmVkIHJlbGF0aXZlIHRvIG9wZXJhdGlvbmFsIGNvbnN0
cmFpbnRzIGFyb3VuZA0KPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+bmV0d29yayBs
YXRlbmN5IGFuZCBhdmFpbGFibGUgYmFuZHdpZHRoLiBQbGVhc2UgbGV0IG1lIGtub3cgaWYgeW91
4oCZZCBsaWtlIHRvIHNlZSBmdXJ0aGVyIGNoYW5nZXMuXTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Tm93IHRoYXQgSSByZWFkIHRo
ZSB0eXBlcyBvZiBjaGVja2xpc3RzIGFuZCBob3cgdmFyaWVkIHRoZXkgYXJlLCBJIHRoaW5rIGl0
IG1heSBiZSBiZXR0ZXIgdG8gZGVsZXRlIHRoZSB0cmFuc2l0aW9uYWwgc2VudGVuY2UgbGlzdGVk
IGFib3ZlIGFzIHRoZXJlIGFyZSBtYW55IG90aGVyIHR5cGVzIG9mIGNoZWNrbGlzdHMgaW5jbHVk
ZWQgaW4gdGhlIGxpc3QgdGhhdCBmb2xsb3dzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPltkYXc6IFRoZXJlIHdlcmUg
bXVsdGlwbGUgcGFyYWdyYXBocyBpZGVudGlmeWluZyBkaWZmZXJlbnQgY2hlY2tsaXN0IHR5cGVz
LiBJIGNvbnNvbGlkYXRlZCB0aGVzZSB3aXRoIGEgc2hvcnRlciB0cmFuc2l0aW9uYWwgc2VudGVu
Y2UuXTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2VjdGlvbiAyLjIuNDxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q291bGQgeW91IG1ha2UgaXQg
bW9yZSBjbGVhciB0aGF0IHRoZSBxdWVyeSBtZWNoYW5pc20gZGVzY3JpYmVkIGludCBoaXMgc2Vj
dGlvbiBpcyB0byBiZSBwcm92aWRlZCBieSBTQUNNPyZuYnNwOyBJIGFzc3VtZSB0aGF0IGlzIHRo
ZSBjYXNlLiZuYnNwOyBUaGlzIG1heSBjb21lIHVwIGluIG90aGVyIHJldmlld3MsIHdoeSBpcyB0
aGUgc2VjdGlvbiBoZXJlIGlmIGl0IGRvZXNuJ3QgdXNlIFNBQ00uPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+W2Rhdzog
QWRkZWQgdGV4dCBzcGVha2luZyB0byB0aGlzLl08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNl
Y3Rpb24gNCwgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHJlY29tbWVuZCByZXBsYWNpbmcgdGhlIGZv
bGxvd2luZyBzZW50ZW5jZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtXaGlsZSBpdCBpcyBhYm91dCBzZWN1cml0eSwgaXQg
ZG9lcyBub3QgYWZmZWN0PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7c2VjdXJpdHkuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj53aXRoIHNvbWV0aGluZyB0aGF0IGV4cGxhaW5z
IHdoZXJlIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyB3aWxsIGJlIGFkZHJlc3NlZC4mbmJz
cDsgU29tZXRoaW5nIGxpa2U6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7U2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgd2lsbCBi
ZSBwcm92aWRlZCBpbiBzb2x1dGlvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwO3N0YW5kYXJkcyBhcyBhcHByb3ByaWF0ZSB0
byB0aGUgZnVuY3Rpb24gZGVzY3JpYmVkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7aW4gZWFjaCBzb2x1dGlvbiBkb2N1bWVu
dC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij5bZGF3OiBBZGRlZCB0ZXh0IHNwZWFraW5nIHRvIHRoaXMgd2l0aCBleGFt
cGxlcyBvZiByZWxhdGVkIGRvY3VtZW50cy5dPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj41LiBB
Y2tub3dsZWRnZW1lbnRzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPklzICZxdW90O1NlY3VyaXR5IEF1dG9tYXRpb24mcXVvdDsgY29weXJpZ2h0
ZWQgb3IgdHJhZGVtYXJrZWQ/Jm5ic3A7IFRoZSBmaXJzdCBwYXJhZ3JhcGggaXMgb2RkIGlmIGl0
IGlzIG5vdC4mbmJzcDsgSWYgaXQgaXMsIHRoZW4gZGlzY2xvc3VyZXMgYXJlIG5lZWRlZC4mbmJz
cDsgQnkgaGF2aW5nIHRoaXMgc2VudGVuY2UgaW4gdGhlIGRyYWZ0LCBzb21lIHR5cGUgb2YgZGlz
Y2xvc3VyZSBtYXkgYmUgbmVlZGVkIHNvIHBlb3BsZSB1bmRlcnN0YW5kIHdoeQ0KIGl0IGlzIHRo
ZXJlIGFzIHRoZXJlIGFyZSBtYW55IGluc3RhbmNlcyBvZiBzZWN1cml0eSBhdXRvbWF0aW9uIGJ5
IHZlbmRvcnMgYW5kIGdyb3VwcyBsaWtlIElDQVNJIGFuZCBUQ0cuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+W2Rhdzog
VGhlcmUgaXMgbm90IGNvcHlyaWdodCBvciB0cmFkZW1hcmsgZm9yIOKAnFNlY3VyaXR5IEF1dG9t
YXRpb27igJ0gdGhhdCBJIGFtIGF3YXJlIG9mLiBJIGRlbGV0ZWQgdGhlIHNlbnRlbmNlIHNpbmNl
IGl0IGlzbuKAmXQgcmVhbGx5IHJlbGV2YW50IHRvIHRoaXMgZG9jdW1lbnQuXTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLSA8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+S2F0aGxlZW48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_DM2PR09MB03658ACAAE5927030031A577F0150DM2PR09MB0365namp_--


From nobody Thu Feb 26 17:04:55 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5561A005F for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 17:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 h4SlSZoN7KGd for <sacm@ietfa.amsl.com>; Thu, 26 Feb 2015 17:04:50 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7DEE1A0385 for <sacm@ietf.org>; Thu, 26 Feb 2015 17:04:49 -0800 (PST)
Received: by iecar1 with SMTP id ar1so23735340iec.11 for <sacm@ietf.org>; Thu, 26 Feb 2015 17:04:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sapqvlwIdvduxHV0ZQeUYzyFLub+Kudz3nq0d7WSd38=; b=xV8XKMGA5EPZw20LDKf30xU+3hLwOJ/JwkcF/igRjIwfG86jJ7Calog6mI+DJE6dtY wOQRhR6gBSTzLO4zJ8tpVtLHyRWdif96IRYZga8H8ZMqWiy4MJ6hlBxaE+HAQPQDi1TI 0STZSO7nOvCBOO+ZrOKByhRmE+ez2UrUUJKlbJ4UzG8iS9DgGhmvMc7jwwp7fJjVHBy9 3Kw9dvV45OBAZriSEBjnxjZlVtu2bitzqfWCOuaz8TSNne2MxnJLFAessRPm+Iv6Wax3 DUDtdrqpbX+wgP95QYQSLNUpdD7x6+mMsKEPT296mxWq1kjJxexjbPUlFzIzqIU1sckT 7bIQ==
MIME-Version: 1.0
X-Received: by 10.43.54.4 with SMTP id vs4mr12671438icb.72.1424999089148; Thu, 26 Feb 2015 17:04:49 -0800 (PST)
Received: by 10.107.12.34 with HTTP; Thu, 26 Feb 2015 17:04:49 -0800 (PST)
In-Reply-To: <DM2PR09MB03658ACAAE5927030031A577F0150@DM2PR09MB0365.namprd09.prod.outlook.com>
References: <CAHbuEH4CNR21UskzwdET5PNh7RMCrpAEsKjcAoBHm+KTt7i5PQ@mail.gmail.com> <DM2PR09MB03658ACAAE5927030031A577F0150@DM2PR09MB0365.namprd09.prod.outlook.com>
Date: Thu, 26 Feb 2015 20:04:49 -0500
Message-ID: <CAHbuEH6xfarvP4aZN1QFPgGT1MgM0A-EkOMSzaHnmQskUs-FhA@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: "Waltermire, David A." <david.waltermire@nist.gov>
Content-Type: multipart/alternative; boundary=bcaec51b1c198398970510077431
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/zPtpWBiL-gNHLHqA_3ONYasfz7w>
Cc: "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [sacm] AD Review of SACM Use Case Draft
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 01:04:53 -0000

--bcaec51b1c198398970510077431
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dave & Dan,

Thank you for incorporating the updates and the WG for your efforts on this
draft.  I just verified the updates and the draft looks like it is ready to
start IETF last call.  If the shepherd (Dan) agrees, I'll kick that off
right away.

The shepherd report looks good too, thanks Dan!

On Thu, Feb 26, 2015 at 7:08 PM, Waltermire, David A. <
david.waltermire@nist.gov> wrote:

>  Kathleen,
>
>
>
> I just posted an updated use cases draft based on your comments below and
> your previous comments on 11/5/2014 (
> http://www.ietf.org/mail-archive/web/sacm/current/msg02139.html).
>
>
>
> Discussion of the changes are inline below. Please let me know if you=E2=
=80=99d
> like to see any additional edits.
>
>
>
> Thanks,
>
> Dave
>
>
>
> *From:* sacm [mailto:sacm-bounces@ietf.org] *On Behalf Of *Kathleen
> Moriarty
> *Sent:* Monday, February 16, 2015 10:54 AM
> *To:* sacm@ietf.org
> *Subject:* [sacm] AD Review of SACM Use Case Draft
>
>
>
> Hello,
>
>
>
> The following is my review of the SACM use case draft.  Since this is a
> charted item and milestone for SACM, the work can proceed.  A statement
> from the IESG on use case drafts will be coming out soon, thanks to those
> that assisted in building arguments.
>
>
>
> SACM use case draft:
>
>
>
> Introduction:
>
> Second sentence - should this be a bulleted list or be multiple sentences=
?
>
>    It provides a discussion of
>
>    these use cases and associated building block capabilities that
>
>    support securely aggregating configuration and operational data and
>
>    evaluating that data to determine the security posture of individual
>
>    endpoints, and, in the aggregate, the security posture of an
>
>    enterprise.
>
>
>
> [daw: I broke this out as a bulleted list.]
>
>
>
> 2nd paragraph, 1st sentence, "information" is redundant:
>
>    These use cases and usage scenarios cross many IT security
>
>    information domains.
>
>
>
> [daw: Deleted =E2=80=9Cinformation=E2=80=9D.]
>
>
>
> There are lots of really long sentences, last sentence of 3rd paragraph i=
s
>  run-on.
>
>
>
> Section 2.2.2
>
> Can you break this sentence into a few?
>
>    Using the collected hardware and software inventory data and
>
>    associated asset characterization data that may indicate the
>
>    organizational defined functions of each endpoint, checklist guidance
>
>    is queried, located and downloaded from the appropriate vendor and
>
>    3rd-party security automation data store for the appropriate
>
>    checklists.
>
>
>
> [daw: Made this a bulleted list.]
>
>
>
> Same section, following sentence:
>
>  While specific applications for checklists results are out-of-scope
>
> s/checklists/checklist/
>
>
>
> And I don't really follow the logic of the full transitional sentence:
>
>    While specific applications for checklists results are out-of-scope
>
>    for current SACM efforts, how the data is used may illuminate
>
>    specific latency and bandwidth requirements.  For this purpose use of
>
>    checklist assessment results may include, but are not limited to:
>
>
>
> [daw: A few paragraphs in this section jumped around in the concepts they
> were discussing. I reorganized and broke up some of the content in this
> section to make it easier to follow. Please let me know if you would like
> to see any additional changes.]
>
>
>
> Could you introduce latency and bandwidth in a different way?  It seems
> odd to follow from descriptions on types of checklists (or 'applications =
of
> checklists').
>
>
>
> [daw: I changed the text to call out data availability, timeliness, and
> liveness as something that needs to be considered relative to operational
> constraints around network latency and available bandwidth. Please let me
> know if you=E2=80=99d like to see further changes.]
>
>
>
> Now that I read the types of checklists and how varied they are, I think
> it may be better to delete the transitional sentence listed above as ther=
e
> are many other types of checklists included in the list that follows.
>
>
>
> [daw: There were multiple paragraphs identifying different checklist
> types. I consolidated these with a shorter transitional sentence.]
>
>
>
> Section 2.2.4
>
> Could you make it more clear that the query mechanism described int his
> section is to be provided by SACM?  I assume that is the case.  This may
> come up in other reviews, why is the section here if it doesn't use SACM.
>
>
>
> [daw: Added text speaking to this.]
>
>
>
> Section 4, Security Considerations.
>
> I recommend replacing the following sentence:
>
>    While it is about security, it does not affect
>
>    security.
>
> with something that explains where the security considerations will be
> addressed.  Something like:
>
>    Security considerations will be provided in solution
>
>    standards as appropriate to the function described
>
>    in each solution document.
>
>
>
> [daw: Added text speaking to this with examples of related documents.]
>
>
>
> 5. Acknowledgements
>
>
>
> Is "Security Automation" copyrighted or trademarked?  The first paragraph
> is odd if it is not.  If it is, then disclosures are needed.  By having
> this sentence in the draft, some type of disclosure may be needed so peop=
le
> understand why it is there as there are many instances of security
> automation by vendors and groups like ICASI and TCG.
>
>
>
> [daw: There is not copyright or trademark for =E2=80=9CSecurity Automatio=
n=E2=80=9D that I
> am aware of. I deleted the sentence since it isn=E2=80=99t really relevan=
t to this
> document.]
>
>
>
> --
>
>
>
> Best regards,
>
> Kathleen
>



--=20

Best regards,
Kathleen

--bcaec51b1c198398970510077431
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dave &amp; Dan,<div><br></div><div>Thank you for incorpora=
ting the updates and the WG for your efforts on this draft.=C2=A0 I just ve=
rified the updates and the draft looks like it is ready to start IETF last =
call.=C2=A0 If the shepherd (Dan) agrees, I&#39;ll kick that off right away=
.</div><div><br></div><div>The shepherd report looks good too, thanks Dan!<=
/div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu=
, Feb 26, 2015 at 7:08 PM, Waltermire, David A. <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:david.waltermire@nist.gov" target=3D"_blank">david.waltermire@=
nist.gov</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Kathleen,<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I just posted an updated =
use cases draft based on your comments below and your previous comments on =
11/5/2014 (<a href=3D"http://www.ietf.org/mail-archive/web/sacm/current/msg=
02139.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/sacm/cur=
rent/msg02139.html</a></span><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;">).<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Discussion of the changes are inline be=
low. Please let me know if you=E2=80=99d like to see any additional edits.<=
u></u><u></u></span></p><span class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Thanks,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Dave<span style=3D"color:#1f497d"><u></=
u><u></u></span></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> sacm [=
mailto:<a href=3D"mailto:sacm-bounces@ietf.org" target=3D"_blank">sacm-boun=
ces@ietf.org</a>]
<b>On Behalf Of </b>Kathleen Moriarty<br>
<b>Sent:</b> Monday, February 16, 2015 10:54 AM<br>
<b>To:</b> <a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org=
</a><br>
<b>Subject:</b> [sacm] AD Review of SACM Use Case Draft<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</span><div>
<p class=3D"MsoNormal">Hello,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div><span class=3D"">
<p class=3D"MsoNormal">The following is my review of the SACM use case draf=
t.=C2=A0 Since this is a charted item and milestone for SACM, the work can =
proceed.=C2=A0 A statement from the IESG on use case drafts will be coming =
out soon, thanks to those that assisted in building
 arguments.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"">
<div>
<p class=3D"MsoNormal">SACM use case draft:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Introduction:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Second sentence - should this be a bulleted list or =
be multiple sentences?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0It provides a discussion of<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0these use cases and associated building=
 block capabilities that<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0support securely aggregating configurat=
ion and operational data and<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0evaluating that data to determine the s=
ecurity posture of individual<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0endpoints, and, in the aggregate, the s=
ecurity posture of an<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0enterprise.=C2=A0<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: I broke this out as a bulleted li=
st.]<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">2nd paragraph, 1st sentence, &quot;information&quot;=
 is redundant:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0These use cases and usage scenarios cro=
ss many IT security<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0information domains.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: Deleted =E2=80=9Cinformation=E2=
=80=9D.]<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">There are lots of really long sentences, last senten=
ce of 3rd paragraph is =C2=A0run-on.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 2.2.2<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Can you break this sentence into a few?<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0Using the collected hardware and softwa=
re inventory data and<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0associated asset characterization data =
that may indicate the<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0organizational defined functions of eac=
h endpoint, checklist guidance<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0is queried, located and downloaded from=
 the appropriate vendor and<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A03rd-party security automation data stor=
e for the appropriate<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0checklists. =C2=A0<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: Made this a bulleted list.]<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">Same section, following sentence:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0While specific applications for checklists res=
ults are out-of-scope<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">s/checklists/checklist/<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">And I don&#39;t really follow the logic of the full =
transitional sentence:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0While specific applications for checkli=
sts results are out-of-scope<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0for current SACM efforts, how the data =
is used may illuminate<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0specific latency and bandwidth requirem=
ents.=C2=A0 For this purpose use of<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0checklist assessment results may includ=
e, but are not limited to:<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: A few paragraphs in this section =
jumped around in the concepts they were discussing. I reorganized and broke=
 up some of the content in this section to make it easier
 to follow. Please let me know if you would like to see any additional chan=
ges.]<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">Could you introduce latency and bandwidth in a diffe=
rent way?=C2=A0 It seems odd to follow from descriptions on types of checkl=
ists (or &#39;applications of checklists&#39;).<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: I changed the text to call out da=
ta availability, timeliness, and liveness as something that needs to be con=
sidered relative to operational constraints around
</span><span style=3D"color:black">network latency and available bandwidth.=
 Please let me know if you=E2=80=99d like to see further changes.]</span><s=
pan style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">Now that I read the types of checklists and how vari=
ed they are, I think it may be better to delete the transitional sentence l=
isted above as there are many other types of checklists included in the lis=
t that follows.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: There were multiple paragraphs id=
entifying different checklist types. I consolidated these with a shorter tr=
ansitional sentence.]<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">Section 2.2.4<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Could you make it more clear that the query mechanis=
m described int his section is to be provided by SACM?=C2=A0 I assume that =
is the case.=C2=A0 This may come up in other reviews, why is the section he=
re if it doesn&#39;t use SACM.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: Added text speaking to this.]<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">Section 4, Security Considerations.<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal">I recommend replacing the following sentence:<u></u>=
<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0While it is about security, it does not=
 affect<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0security.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">with something that explains where the security cons=
iderations will be addressed.=C2=A0 Something like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0Security considerations will be provide=
d in solution<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0standards as appropriate to the functio=
n described<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0in each solution document.<u></u><u></u=
></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: Added text speaking to this with =
examples of related documents.]<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal">5. Acknowledgements<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Is &quot;Security Automation&quot; copyrighted or tr=
ademarked?=C2=A0 The first paragraph is odd if it is not.=C2=A0 If it is, t=
hen disclosures are needed.=C2=A0 By having this sentence in the draft, som=
e type of disclosure may be needed so people understand why
 it is there as there are many instances of security automation by vendors =
and groups like ICASI and TCG.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">[daw: There is not copyright or tradema=
rk for =E2=80=9CSecurity Automation=E2=80=9D that I am aware of. I deleted =
the sentence since it isn=E2=80=99t really relevant to this document.]<u></=
u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">-- <u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Best regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Kathleen<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div><div>Kath=
leen</div></div></div>
</div>

--bcaec51b1c198398970510077431--


From nobody Fri Feb 27 08:14:03 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 867651ACDAF for <sacm@ietfa.amsl.com>; Fri, 27 Feb 2015 08:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 uLG1TJciVeDU for <sacm@ietfa.amsl.com>; Fri, 27 Feb 2015 08:13:57 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA71A1ACDAE for <sacm@ietf.org>; Fri, 27 Feb 2015 08:13:56 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id vb8so19139679obc.11 for <sacm@ietf.org>; Fri, 27 Feb 2015 08:13:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=UaUT967hmVMVWUFQ+km/Q0VEaSFYSjaoJitfZI15u+w=; b=IbQn6StnoFW/GBOPRsdBEVnCHRG/iRhlD8TyjaNOdhiNcie8IJk2/nsMoUN9SIMKmw Qrtfa819AfZKMZ9W6e224e0k8zJT3J2bwI8+t8R4are6dYcEtPuzZqApMivb2ghEoGRz TnqB4UFOOIG2GH0HWAsK7T1uQ+vJjljLz5ZrSdLLb9gYJTsz+e2C90qAEhdmS/3/NytE yKlMZfc5tLK4D4iYXJWFtwZjsY+XfrYxg/8kYi5/qweSfTATwLLNHdj7En9AfFxrUvE9 Haa5FClUj6+4QsDQW4If8zCml9NnJz3qdNdmJ9wGp0npKUxvg0mq/48SzF/mHx5xkZV0 7mGg==
X-Received: by 10.60.131.238 with SMTP id op14mr10517432oeb.59.1425053636088;  Fri, 27 Feb 2015 08:13:56 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:89ec:77fe:20b6:2b8b? ([2602:306:3406:4f00:89ec:77fe:20b6:2b8b]) by mx.google.com with ESMTPSA id d10sm2543380obf.17.2015.02.27.08.13.54 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Feb 2015 08:13:54 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <739894B8-F646-43D9-9A40-0FA15E8D4323@gmail.com>
Date: Fri, 27 Feb 2015 10:13:03 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/svCaDDdaVBYihjzzF4FPU11hfIk>
Subject: [sacm] Endpoint ID Design Team Notes: 2015-02-27
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 16:14:02 -0000

Participants please review for accuracy.

SACM Endpoint ID Design Team Notes
2015-02-27
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

Agenda

	Reminder:
		- WebEx Chat and SACM Jabber Room
		- Recording will be (is) enabled
	Endpoint ID Example Continued
		- Pruning Discussions
			* "Sufficient" for "primary" identity attributes
			* Is "account" as an identity attribute in =
scope?
		- BIOS/Firmware information for identification
		- Should ASCII diagram survive as-is?
		- Provenance Discussion (W3C considerations)
	Next Steps
		- Review priorities that need to get done
		- Potentially come up with recommendations regarding =
additional concepts

Attendees
	Clifford Kahn
	Danny Haynes
	David Waltermire
	Lisa Lorenzin
	Ron Colvin
	Adam Montville


Overview
=3D=3D=3D=3D=3D=3D=3D=3D
Talking over the agenda. Defer provenance discussion to some other =
point.
Reserve time at the end of the call to review priorities that need to =
get done and decide of the time we need to deal with.  Agenda modified =
accordingly.

Pruning Discussion.
We have a set of things that is open-ended - we can keep adding to the =
set of attributes that "identify" an endpoint.  What we want to do is =
arrive at a succinct list of *primary* attributes, and right now we have =
a lot. =20

We have some cases to consider:

	1. Only one authenticated primary identity attribute
	2. More than one authenticated primary identity attributes
	3. No authenticated primary idenity attributes
		a. Netowork observations + appropriate information for =
correlation
		b. Infrastructure services (e.g. DHCP, Kerberos)
			 i. Sniffing on the wire
			ii. Looking at service information directly

There are some implications from the above.  With (1), we more than =
likely have some cryptographic information.  With (2) we probably have =
something in addition to cryptographic (but not cryptographic) =
information.  With (3) we have "third-party" or "observed" information =
that may not be cryptogrpahic in nature.  It really seems that we've =
defined a continuum of identity strength (1 strong; 3 weaker).

Addresses are probably the best identity we have today - tools already =
do this.  An address augmented with some cryptographic certificate makes =
sense. =20

Dave is suggesting that we should we come up with a list of different =
kinds of device types, and Cliff seems to agree.   What are the useage =
scenarios we want to cover, then determine whether we have the right =
attributes, then identify gaps and what we can do to prune the extra =
attributes.

List the attributes and show how they would come together.  We'll have =
sets of operational security and privacy considerations that would be =
based on such an analysis. =20

There seem to be two parts to this: 1) Idenity assertions and 2) how to =
validate those assertions.

Ensure that the identity attribute maps to a type of device (which =
mappigns apply), then how to validate this.  We want to be descriptive, =
not prescriptive.  We should consider operational concerns, however.  We =
should provide "may" considerations in the form of suggestions about how =
these descriptions would be used. =20

We are goign to have requirements (e.g. MUST) on producers that they =
provide information on the subject of validation.  We are not going to =
require them to adhere to a specific validation method (e.g. MAY).  The =
intent is not to use new validation methods.

We may need to capture the validation method for conveyance to relying =
parties.  For example, if there are multiple consumers, the data from =
which would be later aggregated, and they use disparate validation =
methods, then there should be a way to express that validation method so =
that the aggregation can determine more about whether to rely on that =
information.

We should consider reaching out to folks in the management area to =
figure out whether there is existing work that can help us here (e.g. =
current standards, best current practices).

Who can write some scenarios?  Call for scenarios to be sent to list =
(Dave and Adam will work on this early next week).



Future Discussion Points
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Discuss identification information from bios/firmware (e.g. =
serial numbers, asset tags, VM id) that can be queried on the device =
using software
	* Provenance information from W3C PROV
	* Is "account" as an identity attribute in scope?
	* Should *the* ASCII diagram survive as-is, or should it be =
replaced (with something more robust) or broken apart?  Is the diagram =
something we want to explicitly state as being normative?



NEXT STEPS (Agenda Items to track)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

	* Dedicate next week's time to developing scenarios for pruning
	* Review priorities that need to get done
	* Potentially come up with recommendations regarding additional =
concepts needing work







From nobody Fri Feb 27 08:55:54 2015
Return-Path: <gunnar.engelbach@threatguard.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 546831ACE00 for <sacm@ietfa.amsl.com>; Fri, 27 Feb 2015 08:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 P7y0wb26q0M5 for <sacm@ietfa.amsl.com>; Fri, 27 Feb 2015 08:55:49 -0800 (PST)
Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BB951ACE01 for <sacm@ietf.org>; Fri, 27 Feb 2015 08:55:46 -0800 (PST)
Received: by qcvs11 with SMTP id s11so14843843qcv.11 for <sacm@ietf.org>; Fri, 27 Feb 2015 08:55:45 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xEfpfjxTH2UwQFC0OA0fZZ0f7tvweNpbBuweqEoAvU8=; b=MgLMdVvyMq+GD+rFv3iCGrzrgrg0emt8lLpKq/lBEKfo3XgNiINB3jYfe4RgVn4WNS Myz5ngjJiabNVC/XdfIrFZ9l3/sn+w6ss22xoFglTxv+SPcZTpU9LoMvCEkLI1VvFNJe +fz2EwDjm4bblD+Nt8utJAy3TgHEuOBqw+qbN5FmN9pORGtBkXEN0CaF5xTgxTUb4FCX 0/HmvjLTxVnNIi2cvxTiAxlVCstaxiA9pgsWWI1bCPOEH11DxzFspWkuE2TpVeN3licc GgD7zz629OwDlXKe7L4jRiAXneQAkqLY03Ldw+tGtwAA4s9kOiSM3gQo5XIk7TgbnEAd nb9g==
X-Gm-Message-State: ALoCoQmK3dZukl9DyzqG3tZbfKbrpeNgDLCgLz0F3KCc/4NtEBcEffwIe3jYtDXMMYCCb4wJnE1e
X-Received: by 10.141.28.135 with SMTP id f129mr6420633qhe.73.1425056145329; Fri, 27 Feb 2015 08:55:45 -0800 (PST)
Received: from [172.16.1.22] (h69-128-196-138.cntcnh.broadband.dynamic.tds.net. [69.128.196.138]) by mx.google.com with ESMTPSA id 142sm2952657qhd.14.2015.02.27.08.55.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Feb 2015 08:55:44 -0800 (PST)
From: Gunnar Engelbach <gunnar.engelbach@threatguard.com>
X-Google-Original-From: Gunnar Engelbach <Gunnar.Engelbach@ThreatGuard.com>
Message-ID: <54F0A178.2000205@ThreatGuard.com>
Date: Fri, 27 Feb 2015 11:55:20 -0500
Organization: ThreatGuard, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Adam W. Montville" <adam.w.montville@gmail.com>, sacm@ietf.org
References: <739894B8-F646-43D9-9A40-0FA15E8D4323@gmail.com>
In-Reply-To: <739894B8-F646-43D9-9A40-0FA15E8D4323@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/Xxrt7WjDeZ2PldZ5e7iguJ7okjw>
Subject: Re: [sacm] Endpoint ID Design Team Notes: 2015-02-27
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 16:55:52 -0000

A couple notes as I skimmed this:

- For the non-authenticated cases it's possible to generalize the 
primary attributes, but for the authenticated cases the primary 
attributes and how to use them will be different for each platform.

- In the non-authenticated case for a remote network, the only reliable 
pieces of information are the IP address and time stamp* (MAC address is 
possible for Windows machines and some implementations of samba).

- There is not a straightforward hierarchy of reliability for 
identification attributes:  the algorithm for determining the likelihood 
of a correlation is as important as the attributes themselves and should 
be a part of the standard to have any chance of consistent results.

- Should there be an allowance for proprietary solutions?  Asset 
management systems, as an example, that create their own unique 
identifier for known systems.

- Reliable asset identification isn't a necessity for all uses cases.



* This could be augmented via port scanning and/or OS fingerprinting, 
but both are costly operations that don't offer a great deal of useful 
information.


--gun


On 2/27/2015 11:13 AM, Adam W. Montville wrote:
> Participants please review for accuracy.
>
> SACM Endpoint ID Design Team Notes
> 2015-02-27
> ==================================
>
> Agenda
>
> 	Reminder:
> 		- WebEx Chat and SACM Jabber Room
> 		- Recording will be (is) enabled
> 	Endpoint ID Example Continued
> 		- Pruning Discussions
> 			* "Sufficient" for "primary" identity attributes
> 			* Is "account" as an identity attribute in scope?
> 		- BIOS/Firmware information for identification
> 		- Should ASCII diagram survive as-is?
> 		- Provenance Discussion (W3C considerations)
> 	Next Steps
> 		- Review priorities that need to get done
> 		- Potentially come up with recommendations regarding additional concepts
>
> Attendees
> 	Clifford Kahn
> 	Danny Haynes
> 	David Waltermire
> 	Lisa Lorenzin
> 	Ron Colvin
> 	Adam Montville
>
>
> Overview
> ========
> Talking over the agenda. Defer provenance discussion to some other point.
> Reserve time at the end of the call to review priorities that need to get done and decide of the time we need to deal with.  Agenda modified accordingly.
>
> Pruning Discussion.
> We have a set of things that is open-ended - we can keep adding to the set of attributes that "identify" an endpoint.  What we want to do is arrive at a succinct list of *primary* attributes, and right now we have a lot.
>
> We have some cases to consider:
>
> 	1. Only one authenticated primary identity attribute
> 	2. More than one authenticated primary identity attributes
> 	3. No authenticated primary idenity attributes
> 		a. Netowork observations + appropriate information for correlation
> 		b. Infrastructure services (e.g. DHCP, Kerberos)
> 			 i. Sniffing on the wire
> 			ii. Looking at service information directly
>
> There are some implications from the above.  With (1), we more than likely have some cryptographic information.  With (2) we probably have something in addition to cryptographic (but not cryptographic) information.  With (3) we have "third-party" or "observed" information that may not be cryptogrpahic in nature.  It really seems that we've defined a continuum of identity strength (1 strong; 3 weaker).
>
> Addresses are probably the best identity we have today - tools already do this.  An address augmented with some cryptographic certificate makes sense.
>
> Dave is suggesting that we should we come up with a list of different kinds of device types, and Cliff seems to agree.   What are the useage scenarios we want to cover, then determine whether we have the right attributes, then identify gaps and what we can do to prune the extra attributes.
>
> List the attributes and show how they would come together.  We'll have sets of operational security and privacy considerations that would be based on such an analysis.
>
> There seem to be two parts to this: 1) Idenity assertions and 2) how to validate those assertions.
>
> Ensure that the identity attribute maps to a type of device (which mappigns apply), then how to validate this.  We want to be descriptive, not prescriptive.  We should consider operational concerns, however.  We should provide "may" considerations in the form of suggestions about how these descriptions would be used.
>
> We are goign to have requirements (e.g. MUST) on producers that they provide information on the subject of validation.  We are not going to require them to adhere to a specific validation method (e.g. MAY).  The intent is not to use new validation methods.
>
> We may need to capture the validation method for conveyance to relying parties.  For example, if there are multiple consumers, the data from which would be later aggregated, and they use disparate validation methods, then there should be a way to express that validation method so that the aggregation can determine more about whether to rely on that information.
>
> We should consider reaching out to folks in the management area to figure out whether there is existing work that can help us here (e.g. current standards, best current practices).
>
> Who can write some scenarios?  Call for scenarios to be sent to list (Dave and Adam will work on this early next week).
>
>
>
> Future Discussion Points
> ========================
>
> 	* Discuss identification information from bios/firmware (e.g. serial numbers, asset tags, VM id) that can be queried on the device using software
> 	* Provenance information from W3C PROV
> 	* Is "account" as an identity attribute in scope?
> 	* Should *the* ASCII diagram survive as-is, or should it be replaced (with something more robust) or broken apart?  Is the diagram something we want to explicitly state as being normative?
>
>
>
> NEXT STEPS (Agenda Items to track)
> ==================================
>
> 	* Dedicate next week's time to developing scenarios for pruning
> 	* Review priorities that need to get done
> 	* Potentially come up with recommendations regarding additional concepts needing work
>
>
>
>
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>


From nobody Fri Feb 27 09:12:10 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94CFA1ACE29 for <sacm@ietfa.amsl.com>; Fri, 27 Feb 2015 09:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 RG6BeCu14oh5 for <sacm@ietfa.amsl.com>; Fri, 27 Feb 2015 09:12:07 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EB231ACE11 for <sacm@ietf.org>; Fri, 27 Feb 2015 09:12:07 -0800 (PST)
Received: by mail-oi0-f53.google.com with SMTP id u20so16601798oif.12 for <sacm@ietf.org>; Fri, 27 Feb 2015 09:12:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:message-id:date:to:mime-version; bh=H6HfeSQ7QvqW0GEymKLq63nIM0XMgnTVR7K2a85zgyc=; b=Equ7NYYd3Y+tteBnXz+WNey3dWNAdUawzgqYdOalmpMwzFe0b2pfVkxtfIVBs6J+bp s31+M8TWz/3T5PzH3b7oWt1g1TNdTteaLGhC9BakqYFWw8o3VAH/dNaWw7DfTK293qvV EAUiNeYLN2GY981PKW1z32iJsYUJLtBASAJGjX8FWQM89oB3B13g84gcpqM50N2WnHQb LwDRbgTcn04lx1cKnyf+CHGfdajaqwB0cdk6xcXvjPijPvZhbWWqNSzFx44CDdzHRX/w WWQReuqLpPg9sA87/O2IdyWziXVGQtW2bXdhyfIiDR5rbARRzeiFKWE0LAVL4M9luP3e 9jXg==
X-Received: by 10.60.174.42 with SMTP id bp10mr2998656oec.64.1425057126388; Fri, 27 Feb 2015 09:12:06 -0800 (PST)
Received: from ?IPv6:2602:306:3406:4f00:89ec:77fe:20b6:2b8b? ([2602:306:3406:4f00:89ec:77fe:20b6:2b8b]) by mx.google.com with ESMTPSA id vc7sm2623544obb.28.2015.02.27.09.12.04 for <sacm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Feb 2015 09:12:05 -0800 (PST)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7D843ED5-F8EF-4F6D-A19E-C5BB465581DF"
Message-Id: <B7648591-99E5-4797-A74E-7A59E645A12E@gmail.com>
Date: Fri, 27 Feb 2015 11:11:13 -0600
To: sacm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/_M-rccqSK-d2Y7fSZsAzYYkxTrg>
Subject: [sacm] Endpoint ID Design Team Recording: 2015-02-27
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 17:12:08 -0000

--Apple-Mail=_7D843ED5-F8EF-4F6D-A19E-C5BB465581DF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The recording from today=E2=80=99s Endpoint ID design team meeting is =
available: =
https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0 =
<https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu_a?dl=3D=
0>

Regards,

Adam=

--Apple-Mail=_7D843ED5-F8EF-4F6D-A19E-C5BB465581DF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">The recording from today=E2=80=99s Endpoint ID design team =
meeting is available:&nbsp;<a =
href=3D"https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3bRu=
_a?dl=3D0" =
class=3D"">https://www.dropbox.com/sh/bs0hioy5qh6qzr1/AAA2lzSwCFE_pfYMlpP3=
bRu_a?dl=3D0</a><div class=3D""><br class=3D""></div><div =
class=3D"">Regards,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Adam</div></body></html>=

--Apple-Mail=_7D843ED5-F8EF-4F6D-A19E-C5BB465581DF--

