
From nobody Thu Oct  1 00:32:30 2020
Return-Path: <evyncke@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5DF53A0DCF for <anima@ietfa.amsl.com>; Thu,  1 Oct 2020 00:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level: 
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Q9Wq8Mvo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=TVZysaSO
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 RTeW1SqQ3lHU for <anima@ietfa.amsl.com>; Thu,  1 Oct 2020 00:32:27 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BF393A0DC8 for <anima@ietf.org>; Thu,  1 Oct 2020 00:32:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14640; q=dns/txt; s=iport; t=1601537547; x=1602747147; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=+UcROmuYBXPVKlXoCWJG1IxLnkZbyB3s4jWCvpQLZ2U=; b=Q9Wq8Mvoqi1unOqtSFt5Unt/7l6OhEQ6zNY1Rjci4j3YU6kvQnKmYm6D IfLHHBnTuwieD+nGW7O39ve8yUKTGs9lp5V/pOoJA7tgoEUw3yabAk2Z1 XcrdjYt1RDI8ck7+5thSMU1HbqCLXl1jjPAP6B9vtZJ6h7W9L3fpiZxjK M=;
X-IPAS-Result: =?us-ascii?q?A0CwAAAvhXVf/5JdJa1gHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?T0FAQELAYFRUQdwWS8shD2DRgONWiaBAokNjmiBLhSBEQNVCwEBAQ0BARgLC?= =?us-ascii?q?gIEAQGESwIXghoCJTYHDgIDAQEBAwIDAQEBAQUBAQECAQYEbYUvBicMhXIBA?= =?us-ascii?q?QEEAQEQEREMAQEsDAsEAgEIEQMBAgECAh8HAgICHwYLFQgIAgQBEhsHgwQBg?= =?us-ascii?q?ksDLgEOqgoCgTmIYXaBMoMBAQEFhQ8NC4IQAwaBDioBgnGCXEtCgQOFUBuBQ?= =?us-ascii?q?T+BEScMEIIYNT6CGkIBAYEqNYMXM4ItkzujPVIKgmeVUIUKAx+DDo88jk2TD?= =?us-ascii?q?Y1VjgyELQIEAgQFAg4BAQWBWwsoZ3BwFTsqAYI+UBcCDYdDhlw3gzqFFIVCd?= =?us-ascii?q?AI1AgYBCQEBAwl8jhYBAQ?=
IronPort-PHdr: =?us-ascii?q?9a23=3ABOZWoRfJKaF6iKDpqj510571lGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwaQAdfU7vtFj6zdtKWzEWAD4JPUtncEfdQMUh?= =?us-ascii?q?IekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsutaFjbo3n05jkXSV?= =?us-ascii?q?3zMANvLbHzHYjfx828y+G1/cjVZANFzDqwaL9/NlO4twLU48IXmoBlbK02z0?= =?us-ascii?q?jE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.77,323,1596499200"; d="scan'208";a="543988360"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Oct 2020 07:32:24 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 0917WOtt002003 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Oct 2020 07:32:24 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 1 Oct 2020 02:32:23 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 1 Oct 2020 02:32:23 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 1 Oct 2020 02:32:23 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MaWyintPcpS4zGqjHuLsgrvjRGWYAsv2ttzUYCVFkCoq6EiMaIREV+30WLGc63WW7quBQ+mG/LB1dmeCvLLrJrJ/axAtktVJqTadXiqFM7EVhJccwXaK1rXSSUOaeOt2LhZONMhqodPaGZWfXaEqB6RxCjwHhqI5P5oZ7Vx5zc9oAC8ip2lbWqTszQBVZNyRFniCHN8yJitu0AWlQJIQy9RTF+uIh5wpPc3Jruz5VKUIPU3ob6BGrw/t5M0+bmjHe2a1K56OUDlTeplbZ3wUNu4rS6lqnrc4jbVKsM1nkatFdiiOTEUxbLqnzQ7zWQTmihGiP0Kdp2Uzce0MeI5lcw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+UcROmuYBXPVKlXoCWJG1IxLnkZbyB3s4jWCvpQLZ2U=; b=mrmEgbIJfK1VFss/j55JqEnvEEDzBkIr3aG1zrAi6APsqMSJo9T3Edj8/W6kOopSvEv/6ZCj4l+lZ+hKCf4FKF1qHxoCx3qhWQGqzNCHYL8Ns9gW7r62Bg6ZAuDIftWy0/DlhDXvrCWfT2rWPxo8fFnYUvIFwU2+qeV8I/Kb7xOAt9L39mmgUQ9AkFd1b05FAbS6nInX/3aZIbqSq4Ne+xeAy1/8B/Q9DA9YRUQ5ulHG9VUAF7gH834xnR6/APX54m3ZnVBUqg0dGUFR33eVpUxG4GrefuoVePE0Z1yN0kmyTWXM+mX5ZzbnPz7lUTxgIEZlCZQOhARZutCHco9QBQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+UcROmuYBXPVKlXoCWJG1IxLnkZbyB3s4jWCvpQLZ2U=; b=TVZysaSOW2I5Hk7k3++g0cK1oNAVOFVuK8M5eKiD7viGqpSKUNw3mnkto7OnC1r918FrzdiNy0Y7LhcIZRU+9PNdr9hSkTA4/1fbsqvbiEt2x1LrfevllA73kbvwMq5lp0ermSBGxRm2w4c7882Jv5QOGS3of29xfumMU3oT4WA=
Received: from BN6PR11MB1844.namprd11.prod.outlook.com (2603:10b6:404:103::20) by BN6PR11MB1507.namprd11.prod.outlook.com (2603:10b6:405:9::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.32; Thu, 1 Oct 2020 07:32:22 +0000
Received: from BN6PR11MB1844.namprd11.prod.outlook.com ([fe80::d525:a81a:74e0:12e7]) by BN6PR11MB1844.namprd11.prod.outlook.com ([fe80::d525:a81a:74e0:12e7%12]) with mapi id 15.20.3433.032; Thu, 1 Oct 2020 07:32:22 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
Thread-Index: AQHWcUp6mDHpNv4moUSco3WU8XZCKKl9ToRngAQxfwCAACbuAIAAP4CAgADigIA=
Date: Thu, 1 Oct 2020 07:32:22 +0000
Message-ID: <B27AA07C-C25B-4945-87E9-FE4D34F0CDD0@cisco.com>
References: <159730676576.12387.18205135091671983859@ietfa.amsl.com> <20200911130023.GA64542@faui48f.informatik.uni-erlangen.de> <CAMGpriVX12nhjwPzATRCkntmH5DQNjtQ3M2d490ya2_yJ75CLA@mail.gmail.com> <20200930135504.GA34365@faui48f.informatik.uni-erlangen.de> <A866FDD1-3FF8-430E-BB01-9F05F20C062D@cisco.com> <bf0d0c4c-71b9-f444-e79b-fec9c2dd2848@gmail.com>
In-Reply-To: <bf0d0c4c-71b9-f444-e79b-fec9c2dd2848@gmail.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.41.20091302
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2001:420:c0c1:36:dc81:c3c8:3b32:8b5c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: aa3f8962-4ebc-408e-025c-08d865dc22cb
x-ms-traffictypediagnostic: BN6PR11MB1507:
x-microsoft-antispam-prvs: <BN6PR11MB15077ECA094F388D72D12192A9300@BN6PR11MB1507.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: B267U5i7uG4j+eWtT4SX45EL3oSdmlfNEi9TQnEWuIH3k8KDuO4XHIfcLLCZvGcF63OGecpMr/0V4q7t9ABVglfPbDCp24cy4UYXYGlQfrsv3JYVoITSchRD3NU0v1CfPkV7MPkOrN3V6LNV9afzNCANLeCHK8+EqgrL7Pj6NJqYicAoL1Yze+umlJvk9C5Pnl1YrUueetkT8wcAohjGcXLj9enB37Eia05p4xnEJu70dtKF+j+4f6nUGDQGnb3UB/STlV/Eabua5IC/Lx5IGBfV/ZToPGOeOx+hJnvIUIzWp/gR9k6Owr1jv7U9HCaWiChxLrfn9Ys9JkOIeZer5jgoQYbvF8WMx00aV1dJgfX9Xh1ASh4AAvW2a88BJSkZYmW2DcxgHiHatm947VkBuA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BN6PR11MB1844.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(396003)(376002)(366004)(39860400002)(136003)(316002)(110136005)(76116006)(966005)(86362001)(66476007)(478600001)(91956017)(64756008)(33656002)(66446008)(8676002)(66556008)(71200400001)(36756003)(53546011)(66946007)(5660300002)(6506007)(186003)(2906002)(6512007)(6486002)(8936002)(2616005)(83380400001)(66574015)(83080400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: ZIUfXR1kqffNpFeXP/9Vu+eIOKBKRJtLZSc40dZjZNqFzLv4AXmqkacV1PcNptt7FN9lTbwbwCx2cAyFpFexDQuk0XLTD4o164bm4mIk80SulppiKRu1WpFKDWolLybwwAbxRcRbiEaQ7MnG/+wnf5omeEEKijdc3NnSv0zkuyLij64O1fmrCN51Mh9ytrqMiOi/uAT1ImGGanA68Gx0YSuF5QlhpOP6kENVhUvg6kbqp+YLIeWc3QVOMw+GY2xebPrHHWFLpkarR0larj5/LabNYuWjyVXgwLDzFGP8lyjFrgippvXSf9yuZF3H8gFteYDTazbeG9p+0FlCAd3vcdmfPV8mNF5m946hwSwLLVJLPOUkoayeXysZWyh6aa+62axLSN7KgdtkbZXMoOCZ3eEWFSXAFQMJT9sfQW0x2wf/+gePzewkppGI6/gzbjCAmi1y4Xr2jvJ+wRvvYoLUMM8loSNGyi15+pcGq8uFIglLwnDU7qFLceZ1LWQCDXPGF52Muro6bMZ7fbvCdWwm9DCNLig2JHRU5j6ZhtRrwjS/1vs9oNxY4PBhVlo9DLzOqdVGSbc17bDmeh+xpvF3lWatzdGrjywLCZKc6xV2cO1OmcTQ5rHW0705K7ArV6egS/+dviiOqgmkglxC8F0m6yMisdSK0TPMQPjJakmeLB/9n3IglpoJ2mSbhs2oFkkktz9EEMGT8Xdsk0LG92tj8A==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <6D0EF0AF30F8BA47B42906D67E7D3753@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN6PR11MB1844.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: aa3f8962-4ebc-408e-025c-08d865dc22cb
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2020 07:32:22.2326 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: y/vQeb38J21v6ZxKQ2hS0e1pBBU6i4rxxXmZ/ia4CosweLixO2QcvN0uvPIRi6Do79CG+QvgHWTgCat+EcBOhQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1507
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/LlPmzteJd16kBjLjsSSiDTk15zY>
Subject: Re: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 07:32:30 -0000

SGVsbG8gQnJpYW4sDQoNCkkgYmVsaWV2ZSB0aGF0IHdlIGFncmVlLi4uIG5vdGFibHkgb24gVUxB
IGJlaW5nIHRoZSByaWdodCBjaG9pY2UgZm9yIEFDUCBJTUhPLg0KDQpNeSBwcm9wb3NhbCBpcyB0
byByZW1vdmUgYWxsIHRoZSBqdXN0aWZpY2F0aW9uIHRleHQgYXJvdW5kIHRoZSBjaG9pY2Ugb2Yg
VUxBIGFuZCBvbmx5IGhhdmUgdGhlIDIgbGluZXMgYmVsb3cgaW4gbXkgZW1haWwgKHNvIG5vdGhp
bmcgYWJvdXQgUkZDIDE5MTggYXQgYWxsKS4NCg0KRmluYWxseSwgSSBhbHNvIGFncmVlIHdpdGgg
eW91ciAiRnJhbmtseSBpdCdzIG5vdCBvcHRpbWFsIC4uLiBDYXNlIGNsb3NlZC4pIg0KDQotw6ly
aWMNCg0K77u/LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEFuaW1hIDxhbmltYS1i
b3VuY2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2YgQnJpYW4gRSBDYXJwZW50ZXIgPGJyaWFuLmUu
Y2FycGVudGVyQGdtYWlsLmNvbT4NCkRhdGU6IFdlZG5lc2RheSwgMzAgU2VwdGVtYmVyIDIwMjAg
YXQgMjI6MDINClRvOiAiYW5pbWFAaWV0Zi5vcmciIDxhbmltYUBpZXRmLm9yZz4NClN1YmplY3Q6
IFJlOiBbQW5pbWFdIEVyaWsgS2xpbmUncyBEaXNjdXNzIG9uIGRyYWZ0LWlldGYtYW5pbWEtYXV0
b25vbWljLWNvbnRyb2wtcGxhbmUtMjg6ICh3aXRoIERJU0NVU1MgYW5kIENPTU1FTlQpDQoNCiAg
ICBPbiAwMS1PY3QtMjAgMDM6MTQsIEVyaWMgVnluY2tlIChldnluY2tlKSB3cm90ZToNCiAgICA+
IEFib3V0IFVMQSwgd2h5IG5vdCBzaW1wbHkga2VlcGluZzoNCiAgICA+IA0KICAgID4gIiAgICBV
TEE6IChHbG9iYWwgSUQgcHJlZml4KSAgQSAiVW5pcXVlIExvY2FsIEFkZHJlc3MiIChVTEEpIGlz
IGFuIElQdjYNCiAgICA+ICAgICAgICBhZGRyZXNzIGluIHRoZSBibG9jayBmYzAwOjovNywgZGVm
aW5lZCBpbiBbUkZDNDE5M10uIg0KICAgID4gDQogICAgPiBBbmQgbm90aGluZyBlbHNlIG9mIHRo
ZSBleGlzdGluZyBwYXJhZ3JhcGguIElNSE8sIHRoZXJlIGlzIG5vIG5lZWQgdG8ganVzdGlmeSB0
aGUgY2hvaWNlDQoNCiAgICBMb2dpY2FsbHksIEkgYWdyZWUuIEZyYW5rbHkgaXQncyBub3Qgb3B0
aW1hbCB0byBob2xkIHVwIHRoaXMgZG9jdW1lbnQgZm9yIGEgY29tcGxldGVseSBleHRlcm5hbCBw
b2ludC4gVjZPUFMgY291bGRuJ3QgZXZlciByZWFjaCBjb25zZW5zdXMgb24gZHJhZnQtaWV0Zi12
Nm9wcy11bGEtdXNhZ2UtY29uc2lkZXJhdGlvbnMgc28gSSBkb24ndCB0aGluayB3ZSBzaG91bGQg
dHJ5IHRvIGRvIHRoZSBlcXVpdmFsZW50IGhlcmUgaW4gYSBzaW5nbGUgcGFyYWdyYXBoLg0KDQog
ICAgKElmIHlvdSB3YW50IHRoZSBydW5uaW5nIGNvZGUgYXJndW1lbnQgaXQncyBlYXN5OiBkaXN0
cmlidXRlZCBHUkFTUCBhcHBsaWNhdGlvbnMgc3Vydml2ZSB1bnBsYW5uZWQgcmVudW1iZXJpbmcg
b2YgdGhlIHVwbGluayBiZWNhdXNlIHRoZXkgcHJlZmVyIFVMQXMuIENhc2UgY2xvc2VkLikNCg0K
ICAgICAgIEJyaWFuDQoNCg0KICAgID4gDQogICAgPiAtw6lyaWMNCiAgICA+IA0KICAgID4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCiAgICA+IEZyb206IEFuaW1hIDxhbmltYS1ib3VuY2Vz
QGlldGYub3JnPiBvbiBiZWhhbGYgb2YgVG9lcmxlc3MgRWNrZXJ0IDx0dGVAY3MuZmF1LmRlPg0K
ICAgID4gRGF0ZTogV2VkbmVzZGF5LCAzMCBTZXB0ZW1iZXIgMjAyMCBhdCAxNTo1NQ0KICAgID4g
VG86IEVyaWsgS2xpbmUgPGVrLmlldGZAZ21haWwuY29tPg0KICAgID4gQ2M6ICJhbmltYS1jaGFp
cnNAaWV0Zi5vcmciIDxhbmltYS1jaGFpcnNAaWV0Zi5vcmc+LCAiZHJhZnQtaWV0Zi1hbmltYS1h
dXRvbm9taWMtY29udHJvbC1wbGFuZUBpZXRmLm9yZyIgPGRyYWZ0LWlldGYtYW5pbWEtYXV0b25v
bWljLWNvbnRyb2wtcGxhbmVAaWV0Zi5vcmc+LCBUaGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz4sICJh
bmltYUBpZXRmLm9yZyIgPGFuaW1hQGlldGYub3JnPiwgU2hlbmcgSmlhbmcgPGppYW5nc2hlbmdA
aHVhd2VpLmNvbT4NCiAgICA+IFN1YmplY3Q6IFJlOiBbQW5pbWFdIEVyaWsgS2xpbmUncyBEaXNj
dXNzIG9uIGRyYWZ0LWlldGYtYW5pbWEtYXV0b25vbWljLWNvbnRyb2wtcGxhbmUtMjg6ICh3aXRo
IERJU0NVU1MgYW5kIENPTU1FTlQpDQogICAgPiANCiAgICA+ICAgICBJbmxpbmUNCiAgICA+IA0K
ICAgID4gICAgIE9uIFN1biwgU2VwIDI3LCAyMDIwIGF0IDAyOjUyOjE3UE0gLTA3MDAsIEVyaWsg
S2xpbmUgd3JvdGU6DQogICAgPiAgICAgPiBUb2VybGVzcywNCiAgICA+ICAgICA+IA0KICAgID4g
ICAgID4gVGhhbmtzIGZvciB0YWtpbmcgdGhlIHRpbWUgdG8gZ28gdGhyb3VnaCBhbGwgdGhpcy4g
IEdlbmVyYWxseSBMR1RNLCBidXQgSQ0KICAgID4gICAgID4gd291bGQgbGlrZSB0byBpdGVyYXRl
IG9uIHRoZSBVTEEgdGV4dCAobm90aGluZyBtYWpvcikuDQogICAgPiAgICAgPiANCiAgICA+ICAg
ICA+IA0KICAgID4gICAgID4gPiA+IFsgc2VjdGlvbiAyIF0NCiAgICA+ICAgICA+ID4gPg0KICAg
ID4gICAgID4gPiA+ICogIkl0IGlzIHRoZSBhcHByb3hpbWF0ZSBJUHY2IGNvdW50ZXJwYXJ0IG9m
IHRoZSBJUHY0IHByaXZhdGUgYWRkcmVzcw0KICAgID4gICAgID4gPiA+ICAgKFtSRkMxOTE4XSku
Ig0KICAgID4gICAgID4gPiA+DQogICAgPiAgICAgPiA+ID4gICBJIHVuZGVyc3RhbmQgdGhlIGlu
dGVudCBidXQgSSBkb24ndCB0aGluayB0aGlzIHN0YXRlbWVudCBpcyBjb21wbGV0ZS4gSQ0KICAg
ID4gICAgID4gPiA+ICAgdGhpbmsgd2Ugc2hvdWxkbid0IGxldCB0aGlzIHNlbnRlbmNlIG91dCBp
bnRvIHRoZSB3aWxkIGFzIGlzIHNpbmNlIGl0DQogICAgPiAgICAgPiA+IGNvdWxkDQogICAgPiAg
ICAgPiA+ID4gICBiZSByZWFkIHdpdGhvdXQgYW55IGNvbnRleHQgbm9yIGV2ZW4gYW55IHByZXRl
bnNlIG9mIGludGVyZXN0IGluDQogICAgPiAgICAgPiA+IG51YW5jZS4NCiAgICA+ICAgICA+ID4g
Pg0KICAgID4gICAgID4gPiA+ICAgTWF5IEkgc3VnZ2VzdDoNCiAgICA+ICAgICA+ID4gPg0KICAg
ID4gICAgID4gPiA+ICAgIkl0IGlzIG9mdGVuIHRob3VnaHQgb2YgYXMgdGhlIGFwcHJveGltYXRl
IElQdjYgY291bnRlcnBhcnQgb2YgdGhlIElQdjQNCiAgICA+ICAgICA+ID4gPiAgIHByaXZhdGUg
YWRkcmVzcyBzcGFjZSAoW1JGQzE5MThdKSwgdGhvdWdoIGl0IGlzIGluIGZhY3QgbWVhbmluZ2Z1
bGx5DQogICAgPiAgICAgPiA+ID4gICBkaWZmZXJlbnQgaW4gaW1wb3J0YW50IGFuZCBzdWJ0bGUg
d2F5cyBbYW5kIHVwb24gd2hpY2ggdGhpcyBkb2N1bWVudA0KICAgID4gICAgID4gPiByZWxpZXNd
LiINCiAgICA+ICAgICA+ID4NCiAgICA+ICAgICA+ID4gVGhhbmtzIGZvciBub3QgdHJ5aW5nIHRv
IHRhbGsgbWUgb3V0IG9mIHRoZSBjb21wYXJpc29uLCB3aGljaCBpDQogICAgPiAgICAgPiA+IHN1
Y2Nlc3NmdWxseQ0KICAgID4gICAgID4gPiB1c2VkIHRvIGV4cGxhaW4gVUxBIHRvIG1hbnkgY3Vz
dG9tZXJzLiBZb3VyIHByb3Bvc2FsIGlzIGEgYml0IHRvbyB2ZXJib3NlDQogICAgPiAgICAgPiA+
IGZvcg0KICAgID4gICAgID4gPiB0aGUgdGVybWlub2xveSBzZWN0aW9uLCBzbyBpdCdzIG5vdzoN
CiAgICA+ICAgICA+ID4NCiAgICA+ICAgICA+ID4gSXQgaXMgb2Z0ZW4gdGhvdWdodCBvZiBhcyB0
aGUgYXBwcm94aW1hdGUgSVB2NiBjb3VudGVycGFydCBvZiB0aGUgSVB2NA0KICAgID4gICAgID4g
PiBwcml2YXRlIGFkZHJlc3MgKDx4cmVmIHRhcmdldD0iUkZDMTkxOCIgZm9ybWF0PSJkZWZhdWx0
Ii8+KS4gVGhlcmUgYXJlDQogICAgPiAgICAgPiA+IGltcG9ydGFudCBkaWZmZXJlbmNlcyB0aG91
Z2ggdGhhdCBhcmUgYmVuZWZpY2lhbCBmb3IgYW5kIGV4cGxvaXRlZCBieSB0aGUNCiAgICA+ICAg
ICA+ID4gQUNQLCBzdWNoIGFzIHRoZSBVTEEgR2xvYmFsIElEIHByZWZpeCwgd2hpY2ggYXJlIHRo
ZSBmaXJzdCA0OC1iaXRzIG9mIGEgVUxBDQogICAgPiAgICAgPiA+IGFkZHJlc3MuIEluIHRoaXMg
ZG9jdW1lbnQgaXQgaXMgYWJicmV2aWF0ZWQgYXMgIlVMQSBwcmVmaXgiLg0KICAgID4gICAgID4g
Pg0KICAgID4gICAgID4gDQogICAgPiAgICAgPiBJdCdzIGEgc3RhdGVtZW50IG9mIGZhY3QgdGhh
dCB0aGlzIGlzIGhvdyBwZW9wbGUgdW5mYW1pbGlhciB3aXRoIHRoaXMgc3BhY2UNCiAgICA+ICAg
ICA+IHZpZXcgdGhpcyBzcGFjZS4gIEl0J3MgYXBwYXJlbnRseSBhbHNvIGEgc3RhdGVtZW50IG9m
IGZhY3QgdGhhdCBwZW9wbGUgYXJlDQogICAgPiAgICAgPiBzdGlsbCBhY3RpdmVseSBiZWluZyB0
b2xkIHRoaXMuICA7LSkNCiAgICA+ICAgICA+DQogICAgPiAgICAgPiBCdXQgSSBzdGlsbCB0aGlu
ayBpdCdzIG5vdCBxdWl0ZSByaWdodC4gIEZvciBvbmUsIHRoZSByZWFsIGNvdW50ZXJwYXJ0IHRv
DQogICAgPiAgICAgPiAxOTE4IGluIElQdjYgaXMgdGhlIGRlcHJlY2F0ZWQgc2l0ZS1sb2NhbCBw
cmVmaXguDQogICAgPiAgICAgPg0KICAgID4gICAgID4gQWxzbywgdG8gc2F5IGl0J3MgIm9mdGVu
DQogICAgPiAgICAgPiB0aG91Z2h0IG9mIiBpbiBhbiBJRVRGIGRvY3VtZW50IGltcGxpZXMgbW9y
ZSBJRVRGIGZvbGtzIHRoaW5rIG9mIHRoaXMgd2F5LA0KICAgID4gICAgID4gd2hlbiBpbiByZWFs
aXR5IEknbSBub3Qgc3VyZSB0aGF0J3MgdGhlIGNhc2UuDQogICAgPiANCiAgICA+ICAgICAqY291
Z2gqICpjb3VnaCoNCiAgICA+IA0KICAgID4gICAgIHw+IFsgc2VjdGlvbiAyIF0NCiAgICA+ICAg
ICB8Pg0KICAgID4gICAgIHw+ICogIkl0IGlzIHRoZSBhcHByb3hpbWF0ZSBJUHY2IGNvdW50ZXJw
YXJ0IG9mIHRoZSBJUHY0IHByaXZhdGUgYWRkcmVzcw0KICAgID4gICAgIHw+ICAgKFtSRkMxOTE4
XSkuIg0KICAgID4gICAgIHw+IC4uLg0KICAgID4gICAgIHw+IE1heSBJIHN1Z2dlc3Q6DQogICAg
PiAgICAgfD4gICAiSXQgaXMgb2Z0ZW4gdGhvdWdodCBvZiBhcyB0aGUgYXBwcm94aW1hdGUgSVB2
NiBjb3VudGVycGFydCBvZiB0aGUgSVB2NA0KICAgID4gICAgIHw+ICAgcHJpdmF0ZSBhZGRyZXNz
IHNwYWNlIChbUkZDMTkxOF0pLCB0aG91Z2ggaXQgaXMgaW4gZmFjdCBtZWFuaW5nZnVsbHkNCiAg
ICA+ICAgICB8PiAgIGRpZmZlcmVudCBpbiBpbXBvcnRhbnQgYW5kIHN1YnRsZSB3YXlzIC4uLg0K
ICAgID4gDQogICAgPiAgICAgQWthOiBJdCBpcyBub3cgeW91ciB0ZXh0IHRoYXQgeW91IHdvdWxk
IGxpa2UgdG8gc2VlIHJldmlzaXRlZCAhDQogICAgPiANCiAgICA+ICAgICA+IElmIHlvdSByZWFs
bHkgd2FudCB0byBsZWF2ZSB0aGlzIG5vdGlvbiBpbiAocmVtb3ZpbmcgdGhlIHNlbnRlbmNlDQog
ICAgPiAgICAgPiBhbHRvZ2V0aGVyIGlzIGdvb2QgYnkgbWUpLCBwZXJoYXBzIHdlIGNhbiB3b3Jk
c21pdGggaXQgYSBiaXQgbW9yZS4gIElmIEkNCiAgICA+ICAgICA+IG1heSBwcm9wb3NlOg0KICAg
ID4gDQogICAgPiAgICAgSG93IGFib3V0Og0KICAgID4gDQogICAgPiAgICAgICAgIFVMQTogKEds
b2JhbCBJRCBwcmVmaXgpICBBICJVbmlxdWUgTG9jYWwgQWRkcmVzcyIgKFVMQSkgaXMgYW4gSVB2
Ng0KICAgID4gICAgICAgICAgICBhZGRyZXNzIGluIHRoZSBibG9jayBmYzAwOjovNywgZGVmaW5l
ZCBpbiBbUkZDNDE5M10uICBVTEEgaXMgdGhlDQogICAgPiAgICAgICAgICAgIElQdjYgc3VjY2Vz
c29yIG9mIHRoZSBJUHY0IHByaXZhdGUgYWRkcmVzcyBzcGFjZSAoW1JGQzE5MThdKS4gDQogICAg
PiAgICAgICAgICAgIFVMQSBoYXZlIGltcG9ydGFudCBkaWZmZXJlbmNlcyBvdmVyIElQdjQgcHJp
dmF0ZSBhZGRyZXNzZXMgdGhhdA0KICAgID4gICAgICAgICAgICBhcmUgYmVuZWZpY2lhbCBmb3Ig
YW5kIGV4cGxvaXRlZCBieSB0aGUgQUNQLCBzdWNoIGFzIHRoZSBMb2NhbGx5DQogICAgPiAgICAg
ICAgICAgIEFzc2lnbmVkIEdsb2JhbCBJRCBwcmVmaXgsIHdoaWNoIGFyZSB0aGUgZmlyc3QgNDgt
Yml0cyBvZiBhIFVMQQ0KICAgID4gICAgICAgICAgICBhZGRyZXNzIFtSRkM0MTkzIHNlY3Rpb24g
My4yLjFdLiAgSW4gdGhpcyBkb2N1bWVudCB0aGlzIHByZWZpeCBpcw0KICAgID4gICAgICAgICAg
ICBhYmJyZXZpYXRlZCBhcyAiVUxBIHByZWZpeCIuDQogICAgPiANCiAgICA+ICAgICBTdWNjZXNz
b3IgaXMgaG9wZWZ1bGx5IG1vcmUgY29ycmVjdCB3b3JkLiBTdXJlLCBzaXRlIGxvY2FsIHByZWZp
eGVzDQogICAgPiAgICAgd2hlcmUgYSBzdWNjZXNzb3IgdG9vLCBidXQgaSBob3BlIGkgZG8gbm90
IGhhdmUgdG8gd3JpdGUgDQogICAgPiANCiAgICA+ICAgICAiVUxBIGlzIHRoZSAob25seSBzdXJ2
aXZpbmcpIElQdjYgc3VjY2Vzc29yLi4uIg0KICAgID4gDQogICAgPiAgICAgPiBPTEQ6DQogICAg
PiAgICAgPiANCiAgICA+ICAgICA+ICAgIFVMQTogKEdsb2JhbCBJRCBwcmVmaXgpICBBICJVbmlx
dWUgTG9jYWwgQWRkcmVzcyIgKFVMQSkgaXMgYW4gSVB2Ng0KICAgID4gICAgID4gICAgICAgYWRk
cmVzcyBpbiB0aGUgYmxvY2sgZmMwMDo6LzcsIGRlZmluZWQgaW4gW1JGQzQxOTNdLiAgSXQgaXMg
b2Z0ZW4NCiAgICA+ICAgICA+ICAgICAgIHRob3VnaHQgb2YgYXMgdGhlIGFwcHJveGltYXRlIElQ
djYgY291bnRlcnBhcnQgb2YgdGhlIElQdjQgcHJpdmF0ZQ0KICAgID4gICAgID4gICAgICAgYWRk
cmVzcyAoW1JGQzE5MThdKS4gIFRoZXJlIGFyZSBpbXBvcnRhbnQgZGlmZmVyZW5jZXMgdGhvdWdo
IHRoYXQNCiAgICA+ICAgICA+ICAgICAgIGFyZSBiZW5lZmljaWFsIGZvciBhbmQgZXhwbG9pdGVk
IGJ5IHRoZSBBQ1AsIHN1Y2ggYXMgdGhlIFVMQQ0KICAgID4gICAgID4gICAgICAgR2xvYmFsIElE
IHByZWZpeCwgd2hpY2ggYXJlIHRoZSBmaXJzdCA0OC1iaXRzIG9mIGEgVUxBIGFkZHJlc3MuDQog
ICAgPiAgICAgPiAgICAgICBJbiB0aGlzIGRvY3VtZW50IGl0IGlzIGFiYnJldmlhdGVkIGFzICJV
TEEgcHJlZml4Ii4NCiAgICA+ICAgICA+IA0KICAgID4gICAgID4gTkVXOg0KICAgID4gICAgID4g
DQogICAgPiAgICAgPiAgICBVTEE6IChHbG9iYWwgSUQgcHJlZml4KSAgQSAiVW5pcXVlIExvY2Fs
IEFkZHJlc3MiIChVTEEpIGlzIGFuIElQdjYNCiAgICA+ICAgICA+ICAgICAgIGFkZHJlc3MgaW4g
dGhlIGJsb2NrIGZjMDA6Oi83LCBkZWZpbmVkIGluIFtSRkM0MTkzXS4gIFNvbWV0aW1lcw0KICAg
ID4gICAgID4gICAgICAgdGhvdWdodCBvZiBhcyB0aGUgYXBwcm94aW1hdGUgSVB2NiBjb3VudGVy
cGFydCBvZiB0aGUgSVB2NCBwcml2YXRlDQogICAgPiAgICAgPiAgICAgICBhZGRyZXNzIChbUkZD
MTkxOF0pLCB0aGVyZSBhcmUgaW1wb3J0YW50IGRpZmZlcmVuY2VzIHRoYXQgYXJlDQogICAgPiAg
ICAgPiAgICAgICBiZW5lZmljaWFsIGZvciBhbmQgZXhwbG9pdGVkIGJ5IHRoZSBBQ1AuICBJbiB0
aGlzIGRvY3VtZW50LCB0aGUNCiAgICA+ICAgICA+ICAgICAgICJVTEEgcHJlZml4IiByZWZlcnMg
dG8gTG9jYWxseSBBc3NpZ25lZCBHbG9iYWwgSUQgcHJlZml4ZXMsIHdoaWNoDQogICAgPiAgICAg
PiAgICAgICBhcmUgdGhlIGZpcnN0IDQ4LWJpdHMgb2YgdGhlIFVMQSBhZGRyZXNzIFtSRkM0MTkz
IHNlY3Rpb24gMy4yLjFdLg0KICAgID4gDQogICAgPiAgICAgQmVzaWRlIHRoZSBjb3VudGVycGFy
dCB3b3Jkc21pdGhpbmcsIA0KICAgID4gICAgIGkgZG8gbm90IGxpa2UgdGhlIHJlbW92YWwgb2Yg
cG9pbnRpbmcgb3V0IHRoYXQgdGhlIFVMQSBwcmVmaXggaXMgdGhlDQogICAgPiAgICAgbmV3IGJl
bmVmaXQgb2YgVUxBIHRoYXQgd2UgZXhwbG9pdCB3aXRoIEFDUC4gVGhhdCB3YXMgYXQgdGhlIGNv
cmUgb2YgdGhlDQogICAgPiAgICAgZXhwbGFuYXRpb24uDQogICAgPiANCiAgICA+ICAgICA+IChJ
IGRpZG4ndCB0aGluayBpdCB3YXMgd29ydGggdHJ5aW5nIHRvIGdldCBpbnRvIHRoZSBmYzAwOjov
OCB2cyBmZDAwOjovOA0KICAgID4gICAgID4gZGlzdGluY3Rpb24gaW4gdGhpcyBnbG9zc2FyeSB0
ZXh0LikNCiAgICA+IA0KICAgID4gICAgIEkgYWdyZWUsIGJ1dCBpIGRvIG5vdCBzZWUgbmVpdGhl
ciB0aGUgZ2xvc3Nhcnkgb3IgdGhlIHJlc3Qgb2YgdGhlIHRleHQNCiAgICA+ICAgICBkb2luZyB0
aGF0LiBUaGUgc3BlYyBwYXJ0IGp1c3Qgc3BlY2lmaWVzIHVzZSBvZiBmZDAwOi84IHdpdGhvdXQN
CiAgICA+ICAgICBkaXNjdXNzaW9uIGFuZCB0aGUgZ2xvc3NhcnkganVzdCB1c2VzIHRoZSA6Oi83
IGFzIHRoYXRzIHdoYXQgcmZjNDE5MyBzYXkuLg0KICAgID4gICAgIEFtIGkgbWlzc2luZyBzb21l
dGhpbmcgPw0KICAgID4gDQogICAgPiAgICAgPiA+IFsgc2VjdGlvbiA4LjEuMyBdDQogICAgPiAg
ICAgPiA+ID4NCiAgICA+ICAgICA+ID4gPiAqIFdoeSBpcyBhbiBSSU8gZm9yIDo6LzAgd2l0aCBh
IGxpZmV0aW1lIG9mIDAgcmVxdWlyZWQ/ICBEb2Vzbid0IGl0DQogICAgPiAgICAgPiA+IHN1ZmZp
Y2UNCiAgICA+ICAgICA+ID4gPiAgIGl0IHNldCB0aGUgZGVmYXVsdCByb3V0ZXIgbGlmZXRpbWUg
dG8gMD8gIFNlcGFyYXRlbHksIGFyZSBhbGwgbm9kZXMNCiAgICA+ICAgICA+ID4gcmVxdWlyZWQN
CiAgICA+ICAgICA+ID4gPiAgIHRvIGJlIFR5cGUgQz8NCiAgICA+ICAgICA+ID4NCiAgICA+ICAg
ICA+ID4gQ2hlY2sgdGhlIG5ldyB0ZXh0LCBpIGhvcGUgaXQgZXhwbGFpbnMgZXZlcnl0aGluZy4N
CiAgICA+ICAgICA+ID4NCiAgICA+ICAgICA+ID4gWWVzLCB0eXBlIEEgYW5kIEIgZG8gbm90IHN1
cHBvcnQgcGVyLXByZWZpeCBhdXRvIHNlbGVjdGlvbiBvZiByb3V0ZXIsDQogICAgPiAgICAgPiA+
IFRoZSBsaWZldGltZSBvZiAwIGlzIHVzZWQgc28gb25seSBUeXBlIEMgaG9zdHMgd2lsbCBpbnZh
bGlkYXRlIHRoZQ0KICAgID4gICAgID4gPiBkZWZhdWx0IHJvdXRlIGZvciB0aGUgQUNQIGVkZ2Ug
bm9kZSwgYnV0IG5vdCBUeXBlIEEvQiBob3N0cy4gTWF5YmUgdGhlcmUNCiAgICA+ICAgICA+ID4g
aXMgYW5vdGhlciBwYXJhbWV0ZXIgY29tYmluYXRpb24gdGhhdCBhY2hpZXZlcyB0aGlzIGdvYWws
IGJ1dCB0aGlzIHdhcw0KICAgID4gICAgID4gPiB0aGUgZWFzaWVzdCBmb3IgbWUgdG8gYXNzZXNz
L2Rlc2NyaWJlLg0KICAgID4gICAgID4gPg0KICAgID4gICAgID4gDQogICAgPiAgICAgPiBUaGlz
IGxvb2tzIGJldHRlciwgdGhhbmsgeW91Lg0KICAgID4gICAgID4gDQogICAgPiAgICAgPiBUbyBi
ZSBob25lc3QsIEkgZG9uJ3Qga25vdyB3aGF0IHRoZSBwb2ludCBvZiBUeXBlIEEvQiBob3N0cyBp
cyBhbnltb3JlIChhbmQNCiAgICA+ICAgICA+IGlmIGl0IHdlcmUgcG9zc2libGUgdG8gZGVjbGFy
ZSB0aGVzZSBhbmltYSBkZXBsb3ltZW50cyBncmVlbmZpZWxkIEkgd291bGQNCiAgICA+ICAgICA+
IHJlY29tbWVuZCBzYXlpbmcgdGhlIGRlZmF1bHQgcm91dGVyIGxpZmV0aW1lIE1VU1QgYmUgemVy
byBpbiB0aGUgUkEgaGVhZGVyDQogICAgPiAgICAgPiB0byBmb3JjZSBjbGllbnRzIHRvIHVzZSBh
IHN0YWNrIHRoYXQgd29ya3MgLS0gYnV0IHRoYXQncyBqdXN0IG1lKS4NCiAgICA+IA0KICAgID4g
ICAgIEkgd291bGQgZ3Vlc3MgdGhhdCBBIGFuZCBCIGhhdmUgYmVlbiBzZWVuIGluIHRoZSB3aWxk
IGJlZm9yZSA0MTkxIHdhcw0KICAgID4gICAgIHJlbGVhc2VkIGFuZCBzbyB0aGUgUkZDIHdhcyB3
cml0dGVuIHRvIGJlIGluY2x1c2l2ZS4gTm8gaWRlYS4NCiAgICA+IA0KICAgID4gICAgIEkgaGF2
ZSBubyBpZGVhIGhvdyBwcmV2YWxlbnQgdGhlc2UgdHlwZXMgYXJlLCBhbmQgdGhlIGN1cnJlbnQg
ZGVzY3JpYmVkDQogICAgPiAgICAgbWV0aG9kIG1heSBiZSBhIHRpbnkgYml0IG1vcmUgY29udm9s
dXRlZCBidXQgc2VlbXMgdG8gYmUgbW9yZSBjb21wYXRpYmxlLg0KICAgID4gDQogICAgPiAgICAg
R2l2ZW4gbXkgZGVwbG95bWVudCBleHBlcmllbmNlIG9mIGVudGVycHJpc2VzIHdpdGhob2xkaW5n
IGZyb20gYWRvcHRpbmcNCiAgICA+ICAgICBuZXcgbmV0d29yayB0ZWNobm9sb2d5IHdoZW4gaXQg
d2Fzbid0IGNvbXBhdGlibGUgd2l0aCB0aGVpciBvbGRlc3QNCiAgICA+ICAgICBOTVMgZXF1aXBt
ZW50LCBpIGFtIGEgYml0IGJ1cm5lZCBpbiBwcm9tb3RpbmcgImhhcmQgY3V0IiBzb2x1dGlvbnMs
IGFuZA0KICAgID4gICAgIHRoaXMgYmVuIGFuIE9QUyBhcmVhIGRyYWZ0IGluc3RlYWQgb2YgZS5n
LjogUlRHIGlzIGEgZ29vZCBleGN1c2UgZm9yIHRoYXQNCiAgICA+ICAgICBhcHByb2FjaCA7LSkp
DQogICAgPiANCiAgICA+ICAgICBDaGVlcnMNCiAgICA+ICAgICAgICAgVG9lcmxlc3MNCiAgICA+
IA0KICAgID4gICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQogICAgPiAgICAgQW5pbWEgbWFpbGluZyBsaXN0DQogICAgPiAgICAgQW5pbWFAaWV0Zi5v
cmcNCiAgICA+ICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1h
DQogICAgPiANCiAgICA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQogICAgPiBBbmltYSBtYWlsaW5nIGxpc3QNCiAgICA+IEFuaW1hQGlldGYub3JnDQog
ICAgPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hDQogICAgPiAN
Cg0KICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQog
ICAgQW5pbWEgbWFpbGluZyBsaXN0DQogICAgQW5pbWFAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hDQoNCg==


From nobody Thu Oct  1 02:26:42 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 646DD3A0ECA for <anima@ietfa.amsl.com>; Thu,  1 Oct 2020 02:26:41 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 bnzKOUsdRaYg for <anima@ietfa.amsl.com>; Thu,  1 Oct 2020 02:26:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF4AB3A0E5E for <anima@ietf.org>; Thu,  1 Oct 2020 02:26:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E8E5938A08 for <anima@ietf.org>; Thu,  1 Oct 2020 05:31:27 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6sU4gqcpijB1 for <anima@ietf.org>; Thu,  1 Oct 2020 05:31:25 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 28489389F1 for <anima@ietf.org>; Thu,  1 Oct 2020 05:31:25 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 60D40A5A for <anima@ietf.org>; Thu,  1 Oct 2020 05:26:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: anima@ietf.org
In-Reply-To: <24741.1601393763@localhost>
References: <AM0PR10MB195656D42D37797072F4106CE7320@AM0PR10MB1956.EURPRD10.PROD.OUTLOOK.COM> <24741.1601393763@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 01 Oct 2020 05:26:25 -0400
Message-ID: <9635.1601544385@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/9orMZDsx-kfKr9N_zUkbmo-frCs>
Subject: Re: [Anima] BRSKI extensions design team - meeting
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 09:26:41 -0000

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


Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > Technology (in my order of preference):
    > 1) https://meet.sandelman.ca/        I control it completely. JITSI.
    > 2) https://whereby.com/anima         a service I pay for.
    > 3) ietf.webex.com                    I can set up a meeting.

https://meet.sandelman.ca/BRSKIDesignTeam
password: anima


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl91oMEACgkQgItw+93Q
3WVFBgf5AcdsI/mER9UwLr8VbYKKR7/8X8O8iJ/i0USuMBdYlaVid6CRHBkLQzPR
HQnSlPlFA656M/VLy445YNdaUgq+kL66c97wjX56WsdgS6SpwsgYM7pqO6zxyTZL
CBg8NMHKDI0defemM1I+t3SqBklE1j+41caz5KIH+iWjwQ6pyhrJ7UoKxiaDrEl+
Ym9XGVxkAwuvLqdDyHneAT6F0rSCVuhQ/+pHoCf66BeBAQBjJ8XYKew6YDYgT57q
IhtZeIKYf3ugdTbpHRFpQWP8nYWF+HpDzGvJ5RPQxRZY5N+hTSRkmLC3gGEDCWkF
0xo9NlPrN4ZqrP/WUGODPa3GKHOfmA==
=HsSL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct  1 04:07:04 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 186083A0F35; Thu,  1 Oct 2020 04:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 zRo2lN6_BrG3; Thu,  1 Oct 2020 04:06:58 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9273B3A0C3D; Thu,  1 Oct 2020 04:06:57 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 57061548068; Thu,  1 Oct 2020 13:06:51 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4A38E440059; Thu,  1 Oct 2020 13:06:51 +0200 (CEST)
Date: Thu, 1 Oct 2020 13:06:51 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: Erik Kline <ek.ietf@gmail.com>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "draft-ietf-anima-autonomic-control-plane@ietf.org" <draft-ietf-anima-autonomic-control-plane@ietf.org>,  The IESG <iesg@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
Message-ID: <20201001110651.GB34365@faui48f.informatik.uni-erlangen.de>
References: <159730676576.12387.18205135091671983859@ietfa.amsl.com> <20200911130023.GA64542@faui48f.informatik.uni-erlangen.de> <CAMGpriVX12nhjwPzATRCkntmH5DQNjtQ3M2d490ya2_yJ75CLA@mail.gmail.com> <20200930135504.GA34365@faui48f.informatik.uni-erlangen.de> <A866FDD1-3FF8-430E-BB01-9F05F20C062D@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <A866FDD1-3FF8-430E-BB01-9F05F20C062D@cisco.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/N7g3rk96Jv0il3fLKtSNx1eCN_k>
Subject: Re: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 11:07:02 -0000

On Wed, Sep 30, 2020 at 02:14:25PM +0000, Eric Vyncke (evyncke) wrote:
> About ULA, why not simply keeping:
> 
> "    ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
>        address in the block fc00::/7, defined in [RFC4193]."
> 
> And nothing else of the existing paragraph. IMHO, there is no need to justify the choice

Eric: If we can not agree on a simple sentence comparing what we have in IPv6
with what we had in IPv4, we should stop writing RFCs or using IPv6.

Eliot: Thanks for the "analog" suggestion, but i think "analog" is semantically
close to "counterpoint", aka: suggesting a closer functional equivalence with
 rfc1918 than there actual is, so IMHO it would not resolve Eriks concern.

Cheers
    Toerless
> 
> -éric
> 
> ???-----Original Message-----
> From: Anima <anima-bounces@ietf.org> on behalf of Toerless Eckert <tte@cs.fau.de>
> Date: Wednesday, 30 September 2020 at 15:55
> To: Erik Kline <ek.ietf@gmail.com>
> Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "draft-ietf-anima-autonomic-control-plane@ietf.org" <draft-ietf-anima-autonomic-control-plane@ietf.org>, The IESG <iesg@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
> Subject: Re: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
> 
>     Inline
> 
>     On Sun, Sep 27, 2020 at 02:52:17PM -0700, Erik Kline wrote:
>     > Toerless,
>     > 
>     > Thanks for taking the time to go through all this.  Generally LGTM, but I
>     > would like to iterate on the ULA text (nothing major).
>     > 
>     > 
>     > > > [ section 2 ]
>     > > >
>     > > > * "It is the approximate IPv6 counterpart of the IPv4 private address
>     > > >   ([RFC1918])."
>     > > >
>     > > >   I understand the intent but I don't think this statement is complete. I
>     > > >   think we shouldn't let this sentence out into the wild as is since it
>     > > could
>     > > >   be read without any context nor even any pretense of interest in
>     > > nuance.
>     > > >
>     > > >   May I suggest:
>     > > >
>     > > >   "It is often thought of as the approximate IPv6 counterpart of the IPv4
>     > > >   private address space ([RFC1918]), though it is in fact meaningfully
>     > > >   different in important and subtle ways [and upon which this document
>     > > relies]."
>     > >
>     > > Thanks for not trying to talk me out of the comparison, which i
>     > > successfully
>     > > used to explain ULA to many customers. Your proposal is a bit too verbose
>     > > for
>     > > the terminoloy section, so it's now:
>     > >
>     > > It is often thought of as the approximate IPv6 counterpart of the IPv4
>     > > private address (<xref target="RFC1918" format="default"/>). There are
>     > > important differences though that are beneficial for and exploited by the
>     > > ACP, such as the ULA Global ID prefix, which are the first 48-bits of a ULA
>     > > address. In this document it is abbreviated as "ULA prefix".
>     > >
>     > 
>     > It's a statement of fact that this is how people unfamiliar with this space
>     > view this space.  It's apparently also a statement of fact that people are
>     > still actively being told this.  ;-)
>     >
>     > But I still think it's not quite right.  For one, the real counterpart to
>     > 1918 in IPv6 is the deprecated site-local prefix.
>     >
>     > Also, to say it's "often
>     > thought of" in an IETF document implies more IETF folks think of this way,
>     > when in reality I'm not sure that's the case.
> 
>     *cough* *cough*
> 
>     |> [ section 2 ]
>     |>
>     |> * "It is the approximate IPv6 counterpart of the IPv4 private address
>     |>   ([RFC1918])."
>     |> ...
>     |> May I suggest:
>     |>   "It is often thought of as the approximate IPv6 counterpart of the IPv4
>     |>   private address space ([RFC1918]), though it is in fact meaningfully
>     |>   different in important and subtle ways ...
> 
>     Aka: It is now your text that you would like to see revisited !
> 
>     > If you really want to leave this notion in (removing the sentence
>     > altogether is good by me), perhaps we can wordsmith it a bit more.  If I
>     > may propose:
> 
>     How about:
> 
>         ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
>            address in the block fc00::/7, defined in [RFC4193].  ULA is the
>            IPv6 successor of the IPv4 private address space ([RFC1918]). 
>            ULA have important differences over IPv4 private addresses that
>            are beneficial for and exploited by the ACP, such as the Locally
>            Assigned Global ID prefix, which are the first 48-bits of a ULA
>            address [RFC4193 section 3.2.1].  In this document this prefix is
>            abbreviated as "ULA prefix".
> 
>     Successor is hopefully more correct word. Sure, site local prefixes
>     where a successor too, but i hope i do not have to write 
> 
>     "ULA is the (only surviving) IPv6 successor..."
> 
>     > OLD:
>     > 
>     >    ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
>     >       address in the block fc00::/7, defined in [RFC4193].  It is often
>     >       thought of as the approximate IPv6 counterpart of the IPv4 private
>     >       address ([RFC1918]).  There are important differences though that
>     >       are beneficial for and exploited by the ACP, such as the ULA
>     >       Global ID prefix, which are the first 48-bits of a ULA address.
>     >       In this document it is abbreviated as "ULA prefix".
>     > 
>     > NEW:
>     > 
>     >    ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
>     >       address in the block fc00::/7, defined in [RFC4193].  Sometimes
>     >       thought of as the approximate IPv6 counterpart of the IPv4 private
>     >       address ([RFC1918]), there are important differences that are
>     >       beneficial for and exploited by the ACP.  In this document, the
>     >       "ULA prefix" refers to Locally Assigned Global ID prefixes, which
>     >       are the first 48-bits of the ULA address [RFC4193 section 3.2.1].
> 
>     Beside the counterpart wordsmithing, 
>     i do not like the removal of pointing out that the ULA prefix is the
>     new benefit of ULA that we exploit with ACP. That was at the core of the
>     explanation.
> 
>     > (I didn't think it was worth trying to get into the fc00::/8 vs fd00::/8
>     > distinction in this glossary text.)
> 
>     I agree, but i do not see neither the glossary or the rest of the text
>     doing that. The spec part just specifies use of fd00:/8 without
>     discussion and the glossary just uses the ::/7 as thats what rfc4193 say..
>     Am i missing something ?
> 
>     > > [ section 8.1.3 ]
>     > > >
>     > > > * Why is an RIO for ::/0 with a lifetime of 0 required?  Doesn't it
>     > > suffice
>     > > >   it set the default router lifetime to 0?  Separately, are all nodes
>     > > required
>     > > >   to be Type C?
>     > >
>     > > Check the new text, i hope it explains everything.
>     > >
>     > > Yes, type A and B do not support per-prefix auto selection of router,
>     > > The lifetime of 0 is used so only Type C hosts will invalidate the
>     > > default route for the ACP edge node, but not Type A/B hosts. Maybe there
>     > > is another parameter combination that achieves this goal, but this was
>     > > the easiest for me to assess/describe.
>     > >
>     > 
>     > This looks better, thank you.
>     > 
>     > To be honest, I don't know what the point of Type A/B hosts is anymore (and
>     > if it were possible to declare these anima deployments greenfield I would
>     > recommend saying the default router lifetime MUST be zero in the RA header
>     > to force clients to use a stack that works -- but that's just me).
> 
>     I would guess that A and B have been seen in the wild before 4191 was
>     released and so the RFC was written to be inclusive. No idea.
> 
>     I have no idea how prevalent these types are, and the current described
>     method may be a tiny bit more convoluted but seems to be more compatible.
> 
>     Given my deployment experience of enterprises withholding from adopting
>     new network technology when it wasn't compatible with their oldest
>     NMS equipment, i am a bit burned in promoting "hard cut" solutions, and
>     this ben an OPS area draft instead of e.g.: RTG is a good excuse for that
>     approach ;-))
> 
>     Cheers
>         Toerless
> 
>     _______________________________________________
>     Anima mailing list
>     Anima@ietf.org
>     https://www.ietf.org/mailman/listinfo/anima
> 

-- 
---
tte@cs.fau.de


From nobody Thu Oct  1 04:57:43 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA273A0FA4; Thu,  1 Oct 2020 04:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 0XZgPMB8m1sU; Thu,  1 Oct 2020 04:57:36 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D99AB3A0F9D; Thu,  1 Oct 2020 04:57:35 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DF443548045; Thu,  1 Oct 2020 13:57:30 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D8850440059; Thu,  1 Oct 2020 13:57:30 +0200 (CEST)
Date: Thu, 1 Oct 2020 13:57:30 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: nmrg@irtf.org, anima@ietf.org
Cc: chair@ietf.org, iesg@ietf.org, Scott.Mansfield@Ericsson.com, zhangy88@chinatelecom.cn, tsbsg13@itu.int
Message-ID: <20201001115730.GA38103@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DF_tsYjYdkMhrQTjlNoo4apVlUs>
Subject: [Anima] FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 11:57:39 -0000

FYI: anima, nmrg

  The ITU-T work about scenarios and requirements for intent based networking (SG13-LS181) might be
  of interest to participants to NMRG, ANIMA (if of RG/WG also work on this, pls. let me know and
  forward). I also just stumbled across it due to the following liaison statement posted on datatracker
  and did not have the time to read the work:

  https://datatracker.ietf.org/liaison/1696/

CC Q: (chair, IESG, Scott, Zhang):

  Q1: I am somewhat clueless about the liaison statement. I see some liasons being Cc'ed widely 
  to interested parties in the IETF, whereas this liaison is not copied to any actual
  groups other than leadership. How is distribution and response responsibility being decided on ?

  Q2: IETF/IRTF has done / is doing work on intent and network archtiectures planning to suport
  intent, for example in NMRG and ANIMA (maybe other WGs as well). What is the appropriate way to
  let ITU-T know about this (if such dissemination of information is of interest to IETF at all... ?)

Cheers
    Toerless


From nobody Thu Oct  1 05:09:07 2020
Return-Path: <scott.mansfield@ericsson.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12D3F3A0FBA; Thu,  1 Oct 2020 05:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level: 
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id md_rshovpAD5; Thu,  1 Oct 2020 05:09:00 -0700 (PDT)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2074.outbound.protection.outlook.com [40.107.220.74]) (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 E96EF3A0ED3; Thu,  1 Oct 2020 05:08:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Bgdq/Sbkh0Gkt+bsncXfrCl8XdenWUY5W4btjc3IjQRjMQ5WPHLkDA7M2ct9hmXm5NRrSHgMChETtHtbgr6yl1mR8QaERfTgBMoVpf4KPmfrQettcsPRu6BxPqTw9R7AOqVn3NVLXJPKjBl3oSCZPVzQqZhma6HyBlb9L4bGBS9htfuKhpUWSFgHlclkqUu9zDEtYDJ5SPyPxlytGW+9nYcwCnb/JgyCLr9gvvxylh2ULrGwtCZ/cnUFNlu9mlMtrO6tuCZ49NMgunykls09dnChzEZ2z1l4Vvb3AhiJUmo8OR0TjRFPZYfxRnDuQf3p5cEAcCfE75wCcf++qvImjw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ypWB5tVKuEWWZVvpPRAsCfoaU4+gsSkQUsSAyw6AjKc=; b=Ki+nQst4pBRNujXzw3OiIe6zfUatr+6zFA8Ho7a4WfMRARX/zei6OucuthELneAVeijZpvaW94VIrgCEVrTBdqyr9xZRRu95FEQbDFuct4yH8tUMWU/BI2hcfpKRzkcRe656++ya1YksqNspxtDfT8Qh6DQMv4DggY0fXxIYxeo/7rx9cCwIXrE4LHt9ZqTQmSV5IpCNUudxvJ/xzR81jHILh6hyMdWoCmk5o1zdegNLa+9mPB3L0yc+V6ZvtT3Sf8xfMK9eScII4umAVSlHmCLh08NDlHoQiFWUSD7PSTlMSsVzXopgTpbMAbLtFre2nQuC7Kiv9oK41n72Z3fhdA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ypWB5tVKuEWWZVvpPRAsCfoaU4+gsSkQUsSAyw6AjKc=; b=TbEL2LVNfZHGulUVOUuYt4cZt22Cxku9PMVirC8EcB7U05Fe5Tynk1Qlapaocyay3wzttisRQBIu+/aEgXCzzY3IrJuwrPVRBifxaX60D5BxeFZKGv+WJnE9WqZNcXmWVhPETktUdEKCNibWW9jssHgghETctoYcZ5vSxVlWDP4=
Received: from BL0PR1501MB4130.namprd15.prod.outlook.com (2603:10b6:208:86::17) by BLAPR15MB4017.namprd15.prod.outlook.com (2603:10b6:208:278::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.34; Thu, 1 Oct 2020 12:08:52 +0000
Received: from BL0PR1501MB4130.namprd15.prod.outlook.com ([fe80::3549:1a21:b65e:ecb0]) by BL0PR1501MB4130.namprd15.prod.outlook.com ([fe80::3549:1a21:b65e:ecb0%4]) with mapi id 15.20.3412.029; Thu, 1 Oct 2020 12:08:52 +0000
From: Scott Mansfield <scott.mansfield@ericsson.com>
To: Toerless Eckert <tte@cs.fau.de>, "nmrg@irtf.org" <nmrg@irtf.org>, "anima@ietf.org" <anima@ietf.org>
CC: "chair@ietf.org" <chair@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "zhangy88@chinatelecom.cn" <zhangy88@chinatelecom.cn>, "tsbsg13@itu.int" <tsbsg13@itu.int>
Thread-Topic: FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
Thread-Index: AQHWl+od7dZHh9XaWEqhlwREVFFoIqmCpRRw
Date: Thu, 1 Oct 2020 12:08:52 +0000
Message-ID: <BL0PR1501MB413049DEF336344E748378908B300@BL0PR1501MB4130.namprd15.prod.outlook.com>
References: <20201001115730.GA38103@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20201001115730.GA38103@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: cs.fau.de; dkim=none (message not signed) header.d=none;cs.fau.de; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [24.112.244.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bcabd023-209e-4f24-35ec-08d86602c360
x-ms-traffictypediagnostic: BLAPR15MB4017:
x-microsoft-antispam-prvs: <BLAPR15MB40178AA9B696246901620A038B300@BLAPR15MB4017.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: QeIxX3aGVV05SKp+rQlPHxxA+zf+iZ7pI2ungWy9MqhAIqnmf9Wq6gwPzQuONN1KBB1zGxg938VMFYxt2Ii5oJvRbHWnqNGOhGXb+R/pOsOWSXVdP85n+dCLPpqs9Ag/T4KodAAYDY+NjzwCegLoX4A1s0LlQGJfqv7Etqha6vUfKP8DOXdCVUrLrTKieSPkkwexcEvWUKaO1ua8TOnmaEbbsbGrd/PDOqBMYrnEVWx5intdkijAdzsdmbOYICaTZ6ktTMZqh1XJcOS96r4DTZtXTgD+M6gbSDG75+9tzE1DAF2wS9yzrfghyz0h6X67QjOyJK6yyWqX9Ntdwvj03NYCQmUVFBkSU+1jTkiw/Q8QKvYTlCJeB1xCTLlC9yehc10z5zt/aBxPSzwuhC2gBg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BL0PR1501MB4130.namprd15.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(346002)(136003)(376002)(366004)(396003)(83080400001)(71200400001)(966005)(53546011)(8936002)(55016002)(5660300002)(8676002)(4326008)(99936003)(83380400001)(478600001)(54906003)(110136005)(64756008)(66556008)(76116006)(66446008)(66476007)(316002)(66946007)(186003)(6506007)(52536014)(44832011)(66616009)(33656002)(2906002)(7696005)(9686003)(26005)(86362001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: Trs6huE0q19pkoiXgHmtipJAqRxmO3gQx1Vdz9XBE94ekJdBye5MR2Ngo9wES6TwMsSfSQo0Yu6p6vBEA/9i5BlcB8KC4Lxk+iV/46+jzOk9Kax6CsxLIUVfjFE7zPk7UrhC1FeAXNw5d0UdP1T3WtkCnmiJFzZecL0knNGryTCkxr0mKoTUAW4DH8As0iPz9eg9d1el6xE2tjOuLJWjr5QwCuVwkc/zpQuBFSZ6MmAlkTQ54ZzsoT3rP0DKM8OGmxoSftGRJP99LP9NQ0+MN6ulC4KLQRXpRkRX1QJqbnsZndGHjSxeZzHev8zU3p2oEW5NyV1nffp+QEddwyaPiClnvlmpJLWm7CtYhyz9HwiTWhhkO7zp6SY547lnJxFyrIbKYZTJdx5NikxuqMgYMxKuuG/BDXWdxO8renVA+m+hOUfXiQawtdomepU3HE3fPGJxWAtEwlbMFbbfddV15lS3jqWWPf9F6BBIMfFDSFBMC+X553dhu5Twuh1dDygLFeGA1aYRBttZhuhQuJbvbJoMnzbYYAtRfb5NAvuthb/DQAfOdtfI/PtmS00czo/hyCarYzQ9nu2ds4QjJ50ul7W5qGIBv8axAAXXX3aLaTspdVbINiuBZFV92BK0fOztA9/h4HDfEED5/vA0QTZ3fQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0010_01D697CA.18BC9B50"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BL0PR1501MB4130.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bcabd023-209e-4f24-35ec-08d86602c360
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2020 12:08:52.5036 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Wc/HWUnAp8Ag0CrqcpiPtT11Ucb74WTB0rWK9lsCIWepelM5VEvW5oyyQIslk75umtPSz0XEqPVSgh0Q1NtwTsRsEx0w5fH3gwftLAXyXkQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLAPR15MB4017
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/43YPuNOXTS15B2Y5UWWjBmhMGJg>
Subject: Re: [Anima] FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 12:09:05 -0000

------=_NextPart_000_0010_01D697CA.18BC9B50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

To answer the liaison question.

When liaisons from the ITU-T come in, I request suggestions about the groups
they should be circulated to, if it isn't specific to a group.  If there is
a desire for a response or coordination, the senders can directly contact me
to help pull together/identify interested parties.  Same is true in the
other direction.  If the IETF sends a liaison to the ITU-T, it is very
important that an individual that is interested in the topic be available in
the ITU-T meeting to present and coordinate action.  If the liaison is just
for information, then there may be no need for that level of interaction.

The working methods of the ITU-T and the IETF are significantly different,
but one thing is the same.  Results are driven by people that are motivated
to get something done.  The liaison officers can help connect people, but
there needs to be people that are experts in the subject matter to progress
the work.

Regards,
-scott.

-----Original Message-----
From: Toerless Eckert <tte@cs.fau.de> 
Sent: Thursday, October 1, 2020 7:58 AM
To: nmrg@irtf.org; anima@ietf.org
Cc: chair@ietf.org; iesg@ietf.org; Scott Mansfield
<scott.mansfield@ericsson.com>; zhangy88@chinatelecom.cn; tsbsg13@itu.int
Subject: FYI/Qs: liaison on ITU-T work on intent based networking
(SG13-LS181)

FYI: anima, nmrg

  The ITU-T work about scenarios and requirements for intent based
networking (SG13-LS181) might be
  of interest to participants to NMRG, ANIMA (if of RG/WG also work on this,
pls. let me know and
  forward). I also just stumbled across it due to the following liaison
statement posted on datatracker
  and did not have the time to read the work:

  https://datatracker.ietf.org/liaison/1696/

CC Q: (chair, IESG, Scott, Zhang):

  Q1: I am somewhat clueless about the liaison statement. I see some liasons
being Cc'ed widely 
  to interested parties in the IETF, whereas this liaison is not copied to
any actual
  groups other than leadership. How is distribution and response
responsibility being decided on ?

  Q2: IETF/IRTF has done / is doing work on intent and network archtiectures
planning to suport
  intent, for example in NMRG and ANIMA (maybe other WGs as well). What is
the appropriate way to
  let ITU-T know about this (if such dissemination of information is of
interest to IETF at all... ?)

Cheers
    Toerless

------=_NextPart_000_0010_01D697CA.18BC9B50
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVcTCCAyAw
ggIIoAMCAQICAR0wDQYJKoZIhvcNAQEFBQAwOTELMAkGA1UEBhMCRkkxDzANBgNVBAoTBlNvbmVy
YTEZMBcGA1UEAxMQU29uZXJhIENsYXNzMiBDQTAeFw0wMTA0MDYwNzI5NDBaFw0yMTA0MDYwNzI5
NDBaMDkxCzAJBgNVBAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFz
czIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCQF0o1ncrwDZbHRPoWN/xIvb1/
gC01O+FvqGepvwMcTYxvMkfVQWikEwTBNQyahEP8XB3/ibPoFxjNkV/7iePqv05dfBsm03V57eaE
41flrSnE9Doo56V7hDZps/1edr2jLZnTkE4jKH0YY/FUOyaddluXQrL/rvBO7N05lU6DBn/nSUDI
xQGyVFpmHT38+ek8Cp6BuHDwAYvkI1R8yK74kB4AlnLUVM9hI7zq+50CldG2uXE6aQg/D7ThQseI
9T+YqKe6HOBxce9YV4FQelxrdEYOgwOYw46obvJ2Mm4ng8Jz89wY6LST6nVEawRgIHFXh53zvqCQ
Iz2KJOHaIdvDAgMBAAGjMzAxMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEqgqliE0148MAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQUFAAOCAQEAWs6H+RZyFVdLHdmb56ImMOyTZ9/WLdI0r/c4
pc6rFrmrL3w1y6zQD7RMK/yA72uMkV82dvfbsxsZ6vSyEf1hcUS/KLM6Hb+zQ+ifv9wxCHGwnY3W
NEcykMZlJPegSnwEc485bxeMcrW9S8h6+HuDwyhOnAnqZz+yZwQbwxTa+OdJJJHQHWr6YTnva+ch
dQYH2BK0ISBwQnGB2jyaNr6mWw1qbJofkXv5+e9Cuk5OnswMjZTc2UWcXuxCUGOu9F3EsRLcyjuo
Lp0UWgV1t+zXY+K6NbYECJHo2p2c9ma1GKwKplQmNDPSG8HUfxo6jguqMm7b/E8ln9kyx5ZacKzf
TDCCBX0wggRloAMCAQICEQCH7S4aKCZKxRmqOuu5DaLLMA0GCSqGSIb3DQEBCwUAMDkxCzAJBgNV
BAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFzczIgQ0EwHhcNMTQx
MjA1MDgxOTE1WhcNMjEwNDA1MTAyOTAwWjA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UE
AwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9TgHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65I
tqwA3GV17CpNX8GH9SBlK4GoRz6JI5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75L
jo1kB1c4VWk0Nj0TSO9P4tNmHqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJ
jmhnXb88lxhTuylixcpecsHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c
3TxHoLs1iuKYaIu+5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+J
Wov3F0fUTPHSiXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0h
ADnJoWjiUIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4
pgd7gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpoeDVN
AgMBAAGjggGAMIIBfDBOBggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jYS50cnVz
dC50ZWxpYXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY2VyMA8GA1UdEwEB/wQFMAMBAf8wGQYD
VR0gBBIwEDAOBgwrBgEEAYIPAgMBAQIwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBTwj1k4ALP1
j5qWDNXr+nuqF+gTEjCBuQYDVR0fBIGxMIGuMG+gbaBrhmlsZGFwOi8vY3JsLTEudHJ1c3QudGVs
aWFzb25lcmEuY29tL2NuPVNvbmVyYSUyMENsYXNzMiUyMENBLG89U29uZXJhLGM9Rkk/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnkwO6A5oDeGNWh0dHA6Ly9jcmwtMi50cnVzdC50ZWxp
YXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY3JsMBMGA1UdIwQMMAqACEqgqliE0148MA0GCSqG
SIb3DQEBCwUAA4IBAQAQ1elFTM6fGkQ/aRKdkUZicO3Cb9uzBJOpOtFctw+1El0/17lsjoVvJkZB
D3KnUobnrriFdAa+7FAN55KLmZeB/3Y2bG0bB4toSyaVHjOQnQY9M0dv8U852w0Q7GwchKfebLUI
bh9TMt2hI3Xc6j4knFTBUo7C1WAfO51K4bn1irmX6/Ej2VTgiOFsvOAny28W6enFSEQpSHw60VhN
fSttSqTOxyrRR/7kW7Y8yb/3DZDZ/dH6ZCfx/y+BNIv2NuSd85M9HXUzplXXohti4Ql/qeaMn6by
Ius6XlMWZZfkdVRvTuk2PkeC7UmAJ2+/DUWOPpawaytMXVfF4Hvxk34NMIIGAjCCA+qgAwIBAgIR
ALiW66rAzy4bAGYQ+J3LjhEwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMCU0UxETAPBgNVBAoM
CEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzMB4XDTE3MTEw
NjE1NDEyOVoXDTIwMTEwNjE1NDEyOFowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1Nj
b3R0IE1hbnNmaWVsZDErMCkGCSqGSIb3DQEJARYcc2NvdHQubWFuc2ZpZWxkQGVyaWNzc29uLmNv
bTEQMA4GA1UEBRMHRVNDT01BTjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAI0FubTp
mqEsGKLyzK8ercOcS3oDhD9dqkMkcQHl6VnDNtZ0RLdHcyAG0aCuqm+Q56xA1FkjxcwKX0n1nUCp
GwQthPZ+8VCZ5kZ8Nm0la9685gOfPhmxp3nr1oE36yiKmynpPETStz61j3xJGAR+QmGScTkAQoQC
aHZcVKp5E52E4iLNB/WHbOoQgQA7nF9dBRSNM2AB1CLHUeCK+cDCAybF3tPP68j3XrqiPSci8xC9
quLhWw8wrm4D1IZeAdyst8dtJhMHofJ/QhBL9k6ZzDXV3qmRLzC9sx/iEYTnx0CRaNZxQW5RQ1kd
MxMwhUDvyc268ogTcFcRUjVFqVlCAjkCAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0
dHA6Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jcmwwgYIG
CCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBI
BggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5k
aXZpZHVhbGNhdjMuY2VyMCcGA1UdEQQgMB6BHHNjb3R0Lm1hbnNmaWVsZEBlcmljc3Nvbi5jb20w
VQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0
b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUF
BwMCMB0GA1UdDgQWBBRaoqe7RYT60Apt3h4pCKxcZ3n2/jAfBgNVHSMEGDAWgBQcexmel5x2rCA9
2NzjkWrj2y2mUzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQELBQADggIBAMxVMvMki5LD424D
apnPWAgmI9LaPNRrBhMD5VmiUe3EFoZouN651tAJ5djgWHDHAVwj24atrhVB4rhhxawRvrGlDCDc
DPzfLenpOZMi82l/+Tkbbfbl8rA8X/Jl6JVYYDXb61KI7naJD9aatfTZ1CXk4CNY6K2+ksX4lOiJ
tG4bv+6/SvDikY682e/pptcBxM0w/imluDOmKzKm/7gTFOiJ5OpUcsN3svDkqhgfu+U6Kj6ANLaE
LPVJrWniINVy6RJzKxgJL19cDFNfgETPtOZAeCjlKysi/7kxklmqdGXWyGm9Fya1W3UkRsYfGQVx
pTgxkq0Ss6aexaitFpd7aQG5GcZOnT6hUwhquWuDp5vfMDdTf4/eokkOzUqRYQD1PcuqIWQLG/EU
oKjBeuTm9ji3YC0XegV8eC2Fxo6ZaKfIlZLIcNGO3lFa2LUCyLQOPhGjrifNRXqV1bt3geVIlNLm
HWGJICfjjZLMotimh2hfFH/ONZyPAgDiqqrUG0GnqonQ3LeeZ3RlSaucGt3VT0JXXJqg2f+vqiZF
65rv52k/d3M4SgbjHN9llU/YUW2dfwAXQsrWqWCWmJsHUqCtdQv8aFpTTwtwNuwVYTe7byV+fBow
EQhML/tQfBDSiHBoMmK5GtyPQ9X5I2M71QwkL5R4GKqyUi3i116dk3nHg7sRMIIGwjCCBKqgAwIB
AgIQU7h+g+GcmSiTsJtJHOy46zANBgkqhkiG9w0BAQsFADA3MRQwEgYDVQQKDAtUZWxpYVNvbmVy
YTEfMB0GA1UEAwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTAeFw0xNTEwMjcxMjE2NDZaFw0yNTEw
MjcxMjE2NDZaMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJp
Y3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AOzy3wAAuFDyp7vYVLfGk/fjwao71MNGNLSzzl5DtjQtMtl2ZLPZyX6ViqzTN9JOb7uZ6KxuGSpR
eQvt8XOh7iIhkKH9W5hRpbjTsJmUMJd6zifhOpNK6iSU3q44+FjsQL1lVtcguUuFG6aZN0N3GFVb
gt6jRrASF8t/3wy9bHPAIfMyPybpg6Y2PH5/1NwkTepoDSmK69LGV+lV2IK6U9OWayZXZFIFIDCo
GyFlhFxAEgN+qZ2+Rqg/0TM0oCHvKO2ELSGmAdnJkwizR42ji/Y9SYTSuG75mzSe6OfCGWM8Db/x
vy/20aLEPXNu1PvOgzY63WZ6cmkWnjMlVJ90pWC2haqDm3Yf8TRdjUvAl7Pz1bTuexwShzIGakL7
MkCYrEqHMRaojI/VStloQgW76E76zQ2byw5QxrhOUbisBSKRzlTlOZQgYFFAbG6ViF8DOpJh/ygt
QwuTLUM5r15G7eynQV1AMTNCWcX+HUvgArUw6RfW9L58uA68GjktFTV8s9RlDsUqsNcLqeXaV28S
2WMday0YGaq/bloS8AD7KuumUKH+Ri9IGO9mJvP05tvDHjKpLvv80c3WLJnJU/aznYHYEt2+jjKH
OTqdGTxL/zMdpRSQFSuu+KM8NoYrkU1VJqKga+QLsgqKghMp99gu1P1e6KsqseWHdXORrMbjqkBX
AgMBAAGjggG4MIIBtDCBigYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50
cnVzdC50ZWxpYXNvbmVyYS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0
LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/
AgEAMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6
Ly9jcmwtMy50cnVzdC50ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUHHsZ
npecdqwgPdjc45Fq49stplMwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZI
hvcNAQELBQADggIBAFBYa/HVjDu0LqtXQ8iMp8PLFpqchf41ksQY6R1AsoZbaBUu0NQlAQ9GzlC1
pmI5s0cJnuaZI0xV6TiWS3/R2p9UgW61XD9CTIUbAL31mY3BdJf3P46gzKgQEca/DlFjq9GVmuPS
4q90BLNgvgoxoHubc3C6s0OaY1sbnay5EhnvrAE4Q511FlxmJPLnRmQGpieeXa3cPegFfY1kJDKy
yFRypF1RuRLXcdMIgKEy5NX1bS3M9dQ4mgmUmVT2d33UiKSEYQ6s/B+LFaaz4LywXSv2o3W4kbHo
Qs86IWst821ww0wxsCpEfClIvF7fBw2QkbG/1PwuzAuLVStEhDzkAqOrMGctKyNEaBsyAn7Eq2eC
a8QDXnkmagp9QPsNFs/oqnXj9j1cVtH9a4OPzhtg0pd7gd0NzU/5QxibXqbYvouQgihGXHQDmaL4
ruN7C4arMUqRo82YnREsKL7h3j/jtmzcMLc9Q07F04QQd/iSR1Y5pIi6PdNBiE2/4uyAXS6KOIGZ
rPbNQUNrZtwiQpqQNl8AUzgegfPwrYFlFocpaF3d1m5r+2VKKqiRQVfYPGYeZnWfkcz06JoAhc/9
mjbHXSP9hvWYzeLRuoZqHGUdjOX9DIQb926OneV7C5WMIjSY8ORkamG/HKqngmjypL3gSc6oG/E6
B+1i6Ds5j0Qpj5aQMYIDVjCCA1ICAQEwXDBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nz
b24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEQC4luuqwM8uGwBmEPid
y44RMAkGBSsOAwIaBQCgggHPMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF
MQ8XDTIwMTAwMTEyMDg1MFowIwYJKoZIhvcNAQkEMRYEFI4WGDpouGAafbGbHwom0JEckAH+MGsG
CSsGAQQBgjcQBDFeMFwwRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAhEAuJbrqsDPLhsAZhD4ncuOETBtBgsqhkiG
9w0BCRACCzFeoFwwRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxF
cmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAhEAuJbrqsDPLhsAZhD4ncuOETCBkwYJKoZIhvcN
AQkPMYGFMIGCMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUD
BAECMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCGjALBglghkgBZQMEAgMw
CwYJYIZIAWUDBAICMAsGCWCGSAFlAwQCATANBgkqhkiG9w0BAQEFAASCAQCAE1ZqOyP1c2fkjVLJ
7CTmems8WoMSqd/ds3PMlHXA+C5w2esZir6nOmRmKOYB+84l7mPJbrARxcxNoAI8MGseEYMlJ/LG
ZEs6YURkZI7RPJsVtVZ2Xz7pEKN24NMadBqWMKMqCdUhniHinGWHzW6o7KUYygiAL4xnOY4mp3AT
ckkcLG71DcuN2eydLEJWocfDuaBgRefO9aujWkjVol4NOgiIkNd3a1/17LYZLI5NQb7ax1yFbcDs
5NdqG1iGTS8dTq8wpkUuyGVhZcNZTSBc4ru4y3/iNttdrO4QzPSvujjc79WtEIRLyn0Ta8MnnTBN
9fhXoYepvLGKoKEZlz91AAAAAAAA

------=_NextPart_000_0010_01D697CA.18BC9B50--


From nobody Thu Oct  1 05:57:30 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4763A100F; Thu,  1 Oct 2020 05:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 TEW0nEYwgcCP; Thu,  1 Oct 2020 05:57:27 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C3653A1018; Thu,  1 Oct 2020 05:57:26 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 91EE7548045; Thu,  1 Oct 2020 14:57:21 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 8BAF8440059; Thu,  1 Oct 2020 14:57:21 +0200 (CEST)
Date: Thu, 1 Oct 2020 14:57:21 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "anima@ietf.org" <anima@ietf.org>
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Message-ID: <20201001125721.GC34365@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ekMEI3Q8HmLE533iZXiyigPSY04>
Subject: [Anima] Call for agenda ANIMA @ IETF 109, online
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 12:57:29 -0000

Dear ANIMA WG

Trying to be a little bit less behind the curve this time around, so doing an early call
for agenda items for online IETF 109. Also so we can accordingly allocate a time slot


Please send your request for agenda by anima-chairs@ietf.org.
If you can, pls. cc anima@ietf.org unless you want to discuss something about the agenda just with the chairs.

Name of time slot:

Name of draft(s) (if any, NOT REQUIRED, but usually desired ;-):

Amount of time requested:

Presenter name(s):

Thank you very much
     Toerless (for the chairs)


From nobody Thu Oct  1 10:36:21 2020
Return-Path: <alex@futurewei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94CFA3A118B; Thu,  1 Oct 2020 10:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2Cd7cGErVch; Thu,  1 Oct 2020 10:36:16 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2105.outbound.protection.outlook.com [40.107.236.105]) (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 81CD23A117C; Thu,  1 Oct 2020 10:36:16 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HA7VYTfP9Sg6Z+6rydYdpn0Qpb2V+NdU0EuMY1eKDV+fsuyZ7FCzydxI8R+Qhi6eOiBVPoBvTVvyLm3GIKSZWxEOJE9RajKAQRfYptpMoJrIAHYitfpthUPChEo5r0IFECltL+8P2+q0x6p0NUBc9nqOXH85ntBrdfw6iHwwoX6S0H5KTyH5tYr/pgmG/3pfX0orN95eTzwbZEgJ+Ah6RIwjev7TybfVq16KLYIE4g8HP8MFQkg312tsU03uNIsBm+St/tm/b2+HrvqZZ9bJueKhtXVb+LYViywwQ66jpEC5IYQxnpgTHOKw1UfSvKqH0TPk2KMgK4VRXa33eA2BLQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8hL0wOpbxdvq9LnpYBd0RqhaFrWPivRp2Kp6EOlX5Sg=; b=PRp642seAiN31FvbSvON33hGHFUCk1gaTNbZQtYx5tjtX1RTFthIdv3+iwHOKVAjBozdFzopxDx9yzH2H71tSLz/1wg6T/Rh/Tzs39cUJOVI8+Al6sIPCDT2JxrSbEQq13bAjhAGWNCg7DT6cK35qhM2xlOyLCAXWc5CaRj/bEjrPWA0zKFHR+D0NT6KIPjDNPXqjhs9uRmshY4oZYZMcFzIBcAmlSfIQcHzGGH7TXNwpa9FII7nsr1MkHvr9EQU3vvKJQpmGF5XjD7g19PYrgvZJWkj4If9T0YfrQyf/U3yqKX/Sn1WxU4rvtGx8iq0828MtvNGOs+R7eCxJHmrLw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8hL0wOpbxdvq9LnpYBd0RqhaFrWPivRp2Kp6EOlX5Sg=; b=Vfi0Jhm8BeI0T542GCwW/t9OldlAh9latN0EJD4pdn99RRAG6rrMLYKocymHoBfUZeqEGHO68qZrNBCGFl1KSo3qUuo+BPWrQBKyZTtsciITcvPuGE35xMOfGlmcOLyg2Nzly5HYMSBFJPQmP6h133O6dm0xAnOFqE7/QM3hMfY=
Received: from BY5PR13MB3793.namprd13.prod.outlook.com (2603:10b6:a03:226::15) by BY5PR13MB3378.namprd13.prod.outlook.com (2603:10b6:a03:1a4::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.13; Thu, 1 Oct 2020 17:36:09 +0000
Received: from BY5PR13MB3793.namprd13.prod.outlook.com ([fe80::f0f3:2a3f:eaf2:6f26]) by BY5PR13MB3793.namprd13.prod.outlook.com ([fe80::f0f3:2a3f:eaf2:6f26%5]) with mapi id 15.20.3433.035; Thu, 1 Oct 2020 17:36:08 +0000
From: Alexander Clemm <alex@futurewei.com>
To: Scott Mansfield <scott.mansfield=40ericsson.com@dmarc.ietf.org>, Toerless Eckert <tte@cs.fau.de>, "nmrg@irtf.org" <nmrg@irtf.org>, "anima@ietf.org" <anima@ietf.org>
CC: "chair@ietf.org" <chair@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "zhangy88@chinatelecom.cn" <zhangy88@chinatelecom.cn>, "tsbsg13@itu.int" <tsbsg13@itu.int>
Thread-Topic: FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
Thread-Index: AQHWl+uqvxSU+hTKs0eHPyGDBwebC6mC/0ZQ
Date: Thu, 1 Oct 2020 17:36:08 +0000
Message-ID: <BY5PR13MB3793463E22404F880CA4F741DB300@BY5PR13MB3793.namprd13.prod.outlook.com>
References: <20201001115730.GA38103@faui48f.informatik.uni-erlangen.de> <BL0PR1501MB413049DEF336344E748378908B300@BL0PR1501MB4130.namprd15.prod.outlook.com>
In-Reply-To: <BL0PR1501MB413049DEF336344E748378908B300@BL0PR1501MB4130.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [73.189.160.186]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ee1703bc-c202-4920-7d08-08d866307b80
x-ms-traffictypediagnostic: BY5PR13MB3378:
x-microsoft-antispam-prvs: <BY5PR13MB33784F96825A7C2413AEBF09DB300@BY5PR13MB3378.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FVu0oa/IhchAoZbVttVuutxxc9u8oquFmBw48fDG1yr3rs4qJofrqZG4bxd8Yticn0ngXshqEvsIvv+IgSIxdc8CSxCQ0dxBsEPNRWb98Cl+c+BU4FLfQYCfPaQNO8gzfEIu8owfbFKiUMEmKgD6cQpaed8ejDG+j9dfbNrVxHTqhY8K7C4dODvae7DKFzrT6W/bnH1PBZUFw2a5zAbAg3Y2eZgByaIh4rceswuzEfTFipDXC4ZZJzaocJ5ocUk6Xq3/LlB6kgIlDQiejsKDWq7E+tm47OdbmtueLAmPrGTR619RegOXU9VicwLGAX5DoqBzbbK0FdEvuMLvikiZp9vBW83ZxfEcJyYbF5M8SnAQOwjezuZu+eFxkqxWLYOzBWTt5n9qVcRweQay8Kkkyg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BY5PR13MB3793.namprd13.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(366004)(346002)(39840400004)(136003)(376002)(71200400001)(64756008)(66556008)(66446008)(83080400001)(83380400001)(316002)(66476007)(54906003)(52536014)(66946007)(6506007)(110136005)(76116006)(478600001)(45080400002)(86362001)(5660300002)(55016002)(26005)(4326008)(7696005)(53546011)(186003)(2906002)(9686003)(8936002)(966005)(33656002)(8676002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: QeF9rFf9nQJvCC0xs2wgXmKR+Iuhox9yAi3AXbNH3soAkHzuF9smUh9C81ayG/kT+SNmo6kx7J0wZgZqQp9sIcTp0+flZTyKUAipsRrNkKHYlmnqo8A6Le5WBGj2ivShv0CMp7xqQjHT8bBVTJ+9RbCj4YgSWde/rCqWAx9f4BGWYvXBfp2EWb1fVyQ9FHXR0/vOjLf6c+eLdfIQe8vCbl5xA0Xy3zTNdJxJu9TH//fV9z/Yh09RnZtqT2n+wgSTv6pILbslTgX/Z4PyqI5OmNuZuSvo3tAeYbIjsr2sE1Rr97oBUQepVyPwGSztwCzEwd/A1xWRr+XmlW+hOW/Cn1D+4rr3iy9wVFneEv3MUlxkdczXlEwpJNlHyVLjQLWeKjkknP87oRuOdcrDcPoLRnMko65AdMciob82qx/5Igq3TsVtRqwZuuJvol1nwUAcPsVPlB+CT1afUjWdy4M3jRvzDc6OdsBOx8bHV1PCPuKY2cbAqAImVc5mDFN7seW0My1UC+pgb4uqY/G3BDxFkgvJ6fVfUCdpmC9EhfypLZYvKHeND4VbKftuJMiKDm6C2I3BLlepHIYS/BsBaBVkr3hlWCxnegNGwPRSy99P5kmqQyP958eevi+sGEQIExLJoLGZceAgUCDKQqEEt8fn8A==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR13MB3793.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ee1703bc-c202-4920-7d08-08d866307b80
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2020 17:36:08.7296 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: CwjtmQjYhU/GUIgGXx00CdpbIOcshBZ4CifAdumtrB2XGQLStgNVlhhvHOM4c+5ToZ/jNRkSnlaMYV+aCWfC2g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB3378
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/aXMpZnuikOkTDD-Lc90kJUz6F1U>
Subject: Re: [Anima] FYI/Qs: liaison on ITU-T work on intent based networking (SG13-LS181)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 17:36:20 -0000

The attachment to the liaison statement refers to a draft that I am a coaut=
hor of, and that is relevant to their work.  Clearly it would be great to h=
ave them engage, provide feedback, reach out to us to see if there are comm=
on interests to explore.  They could presumably do already simply using the=
 author contact information that is given in the draft, but given this liai=
son route is taken instead, I am not sure of its purpose and what if any ex=
pectations to respond would be?  As Toerless indicates, the audience for th=
is is in nmrg and anima, so it seems perhaps they should be simply directed=
 to those working groups?
--- Alex

-----Original Message-----
From: nmrg <nmrg-bounces@irtf.org> On Behalf Of Scott Mansfield
Sent: Thursday, October 1, 2020 5:09 AM
To: Toerless Eckert <tte@cs.fau.de>; nmrg@irtf.org; anima@ietf.org
Cc: chair@ietf.org; iesg@ietf.org; zhangy88@chinatelecom.cn; tsbsg13@itu.in=
t
Subject: Re: [nmrg] FYI/Qs: liaison on ITU-T work on intent based networkin=
g (SG13-LS181)

To answer the liaison question.

When liaisons from the ITU-T come in, I request suggestions about the group=
s they should be circulated to, if it isn't specific to a group.  If there =
is a desire for a response or coordination, the senders can directly contac=
t me to help pull together/identify interested parties.  Same is true in th=
e other direction.  If the IETF sends a liaison to the ITU-T, it is very im=
portant that an individual that is interested in the topic be available in =
the ITU-T meeting to present and coordinate action.  If the liaison is just=
 for information, then there may be no need for that level of interaction.

The working methods of the ITU-T and the IETF are significantly different, =
but one thing is the same.  Results are driven by people that are motivated=
 to get something done.  The liaison officers can help connect people, but =
there needs to be people that are experts in the subject matter to progress=
 the work.

Regards,
-scott.

-----Original Message-----
From: Toerless Eckert <tte@cs.fau.de>
Sent: Thursday, October 1, 2020 7:58 AM
To: nmrg@irtf.org; anima@ietf.org
Cc: chair@ietf.org; iesg@ietf.org; Scott Mansfield <scott.mansfield@ericsso=
n.com>; zhangy88@chinatelecom.cn; tsbsg13@itu.int
Subject: FYI/Qs: liaison on ITU-T work on intent based networking
(SG13-LS181)

FYI: anima, nmrg

  The ITU-T work about scenarios and requirements for intent based networki=
ng (SG13-LS181) might be
  of interest to participants to NMRG, ANIMA (if of RG/WG also work on this=
, pls. let me know and
  forward). I also just stumbled across it due to the following liaison sta=
tement posted on datatracker
  and did not have the time to read the work:

  https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdatat=
racker.ietf.org%2Fliaison%2F1696%2F&amp;data=3D02%7C01%7Calex%40futurewei.c=
om%7C3c8cffeebbdb4c89efb708d86602cb45%7C0fee8ff2a3b240189c753a1d5591fedc%7C=
1%7C1%7C637371509493678189&amp;sdata=3DJ03X6EhyIr4nqUnTk97OxwMlLiEdnIYORlmW=
ezf2qhc%3D&amp;reserved=3D0

CC Q: (chair, IESG, Scott, Zhang):

  Q1: I am somewhat clueless about the liaison statement. I see some liason=
s being Cc'ed widely
  to interested parties in the IETF, whereas this liaison is not copied to =
any actual
  groups other than leadership. How is distribution and response responsibi=
lity being decided on ?

  Q2: IETF/IRTF has done / is doing work on intent and network archtiecture=
s planning to suport
  intent, for example in NMRG and ANIMA (maybe other WGs as well). What is =
the appropriate way to
  let ITU-T know about this (if such dissemination of information is of int=
erest to IETF at all... ?)

Cheers
    Toerless


From nobody Thu Oct  1 15:33:19 2020
Return-Path: <kaduk@mit.edu>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469BA3A09BC; Thu,  1 Oct 2020 15:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 dfNWDHqyKboh; Thu,  1 Oct 2020 15:33:09 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 C37693A09BB; Thu,  1 Oct 2020 15:33:08 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 091MWj1W031207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 1 Oct 2020 18:32:47 -0400
Date: Thu, 1 Oct 2020 15:32:44 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Toerless Eckert <tte@cs.fau.de>
Cc: The IESG <iesg@ietf.org>, draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
Message-ID: <20201001223244.GP89563@kduck.mit.edu>
References: <159727599109.5414.1617295798802435987@ietfa.amsl.com> <20200911125956.GA63981@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200911125956.GA63981@faui48f.informatik.uni-erlangen.de>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/EUKwoflukM3JMj7hiUTrYQ8XbzI>
Subject: Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 22:33:15 -0000

Hi Toerless,

Also inline, but I think we're in pretty good shape overall.

On Fri, Sep 11, 2020 at 02:59:56PM +0200, Toerless Eckert wrote:
> Thanks, Ben
> 
> On Wed, Aug 12, 2020 at 04:46:31PM -0700, Benjamin Kaduk via Datatracker wrote:
> > 
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > Hopefully just a couple easy ones...
> > 
> > I made a pass over Ekr's ballot comments (nominally on the -16, though
> > some of the quoted text doesn't seem to match up with that version).
> > We're generally in good shape there, but I wanted to check on the point
> > regarding a "downgrade defense on the meta-negotiation between the
> > protocols", which in theory would allow an attacker to force the use of
> > IPsec or DTLS or whatever other protocol has a weakness.  It seems like
> > there may have been some confusion about DULL vs ACP GRASP in play here,
> > especially with respect to when there might be the possibility of
> > multiple secure channels.  My current understanding is that there is not
> > a major issue here, but let's confirm that: DULL GRASP runs only over a
> > local link (using link-local addresses),
> 
> When DULL GRASP runs "autonomously" it would indeed only run link-local.
> It would also run across a manually crafted tunnels (section 8.2.2)
> to get over a non-autonomic island. That is the least desirable
> workaround option (8.2.1 is preferred).

And you did add special consideration of controlling what secure channel is
used over such tunnels; good idea.

> >  and as currently defined has
> > the option of flooding advertisements that use either DTLS or IKEv2 to
> > establish the ACP secure channel.
> 
> Yes. And of course when other protocols are added (e.g.: MacSec),
> those would be signalled too.
> 
> >  DULL GRASP has no cryptographic
> > protections at all, so if there is somehow (e.g., on a multi-access
> > link) an attacker on the link, they could drop or rewrite some
> > announcements to force either DTLS or IKEv2 to be used for secure
> > channel establishment even if the other would normally have been
> > preferred.
> 
> Yes.
> 
> > On directly-connected wired links, such tampering may be
> > unlikely (but not beyond the capabilities of, e.g., a nation-state or
> > well-funded attacker, especially for, e.g., long fiber runs.) 
> 
> IMHO quote the opposite:
> a) This is not a relevant attack (see below)
> b) This is easy to do, e.g.: not only by nation states.
> 
> If the ACP runs across the universities network in e.g.: a student dorm building
> , i don't need nation state attackers. Every CS student could do it.
> Likewise in a multi-company office building, etc. pp.
> Aka: intercepted wires can and will happen everywhere.
> 
> Aka: I propose "dorm student" as the new meme in addition to nation-states ;-)

Arguably a more motivated attacker, even, in some sense -- I like it :)

> > By itself, this is not useful, since both DTLS and IKEv2+ESP are believed
> > to be secure, but if some future vulnerability is discovered the
> > downgrade might allow for the vulnerability to be exploited in cases it
> > would not otherwise have been usable.  Countermeasures to allow
> > detection of this kind of tampering are possible -- include as part of
> > the DTLS or IKEv2 exchange (or the first operation after it) a
> > preference-ordered list of supported secure channel mechanisms, and bail
> > out if the mechanism being used is not the most-preferred shared
> > mechanism -- but will still fail if the vulnerability in question is
> > sufficiently severe to allow handshake forgery.
> 
> I am surprised this discuss did not come up in before during IESG review.

To be clear, this is something that I think Ekr raised in his original
ballot, but there was a communication mixup about what the actual issue
was (including if it affected DULL vs ACP GRASP), and it didn't get much
follow-up discussion or attention until now.

> Vor many revisions, aCP draft did NOT announce the supported protocol
> options via GRASP exactly because of the concern about downgrade attack,
> but then we changed it because a) it provide benefits, b) the downgrade
> attack vector IMHO does not exist:
> 
> a) Why signaling protocol option is beneficial:
> 
> When we only signal via DULL GRASP the network layer address but
> not the transport address of a supported security protocol, then all
> protols we wanted to support would have to be able to run ONLY on well-known
> transport addresses. This is common for IKEv2, but for example not for DTLS.
> Without announcing transport addresses, we would need to rely on only
> well-known transport adddresses.
> 
> b) Why there is IMHO no downgrade attack (new with GRASP):
> 
> To perform the supposed downgrade attack, the attacker has to be MITM
> to filter the "better" security protocol option. When an attacker can
> do that, then the attacker can also filter the better security
> protocol packets themselves and not only the GRASP announcement.
> E.g.: Filter any UDP port nnn packets if nnn is announced for DTLS by
> GRASP to downgrade for example from an assumed more secure DTLS
> option to a less secure IKEv2 option.
> 
> Let me know if you see a flaw in this argument. If not, then i hope this
> question is closed.

Yes, if you can drop the GRASP announcement it seems like you would also be
able to drop the DTLS messages and make it seem like IKEv2 is the only
thing that works.  But, we still want to be able to detect that that is
happening, if we can.

> Now, i have a counter question: A.6 is an appendix that provides a possible
> future solution for these MITM downgrade attacks - instead of ships in
> the night, use a dual-stage negotiation. Lets say first stage TLS
> to then negotiate the best second stage (IKEv2 or DLTS).
> 
> This section has been on the chopping board from prior reviewers because they
> felt it was too convoluted. But none of those reviewers was a security expert.
> So i kept the text for the case an ctual security reviewer cared about the
> issue and would find thi A.6 useful. So, let me know if you think A.6
> should be kept in the RFC.

I think A.6 is an interesting idea and don't want to drop the idea, but the
current state of the text in A.6 is better suited for a separate doc than
inclusion in this one.  I suppose I could try to do a shorter rewrite that
might be a better fit for this doc if you want; let me know.

> Now, revisiting this DULL GRASP negotiation, the desire to support
> non-well-known secure channel protocols and discovery of their
> transport address does introduce a DoS attack vector whereby a third-party
> attacker on a LAN can create malicious GRASP messages with fake
> transport addresses. I have added text about this attack vector to
> section 6.1.5.1 and added a new requirement for protocols such as IKEv2
> that have well-known ports as a workaround. This new attack vector is not worse than
> the more basic attack vector of simply announcing a million different
> link-local IPv6 addresses of candidate ACP neighbors. Hence it's no
> reason not to leverage the beenfit that the transport address announcements
> of the DULL GRASP messages give. And avoid wasting another well-known
> port before there is a stringent enough reason...

This all sounds/looks good; thanks.

> > ACP GRASP is different, in that it (1) runs over the ACP, so any on-path
> > attack to drop/rewrite GRASP would have as a prerequisite an attacker in
> > the ACP, and (2) unicast GRASP is protected end-to-end by TLS.  However,
> > it seems like broadcast/flooded ACP GRASP objectives will only have the
> > hop-by-hop ACP protection.
> 
> Yes.
> 
> > and so would in theory also be subject to a
> > downgrade attack if there was an in-ACP on-path attacker.
> 
> Except that there is nothing specified right now where such downgrade
> attack could happen, end-to-end GRASP is always only using TSL.
> If there was, then the same consideration as above for DULL GRASP would apply,
> MiTM could filter the actual better connection, not only the GRASP
> announcement thereof.
> 
> This actually would be candidate text for the ASA guideline draft
> wrt. downgrade attacks if they want to support multiple end-to-end
> protocols, but compared to the DULL GRASP case, where the MiTM is
> a dorm student, the MiTM to effectively intrude on an ACP router is
> IMHO really a nation state level actor, because we are talking about
> injection of malicious software on an onpath ACP router whic
> hopefully should have trusted execution paths. For that last point,
> see the amended bullet list in reply to Romans Discuss in the
> security consideration section, which now mentions such trusted
> software to prohibit malicious software injection.
> 
> > It also seems
> > like there's a general expectation that ACP services will run over TLS,
> > and the option of "TLS *or* DTLS (or something else)" is not expected to
> > be common, so the existence of a downgrade to a different protocol is
> > rare as well.
> 
> This is again an ASA guideline draft discussion. Lets say i want to automate
> authentication services and different routers in the network support
> different profiles of radius and/or diameter. I would probably think
> about a dual-stage connection setup, where i first announce
> authentication service flooded via GRASP, then i use the TLS GRASP
> connection to do GRASP negotiation of the best mutually supported
> diameter/radius option. Aka: Like what i wrote for ACP itself into A.6.
> But somehow reviewer might want to kill such elaborate dual stage
> negotiations ? I don't know. I thought GRASP was built to support
> this approach ;-)) (but not an ACP document discussion).
> 
> > While I would like to be able to defend against downgrade attacks by an
> > in-ACP on-path attacker
> 
> A.6 ? ;-))
> 
> > I recognize that it's a defensible position to
> > take that we assume all entities in the ACP to remain secure and just
> > accept the corresponding risks in the case of compromise.
> 
> The end-to-end security view is certainly well taken, and it took me
> to move from TCP for end-to-end GRASP to TLS during Erics review.
> But i want to make sure we don't discount other tools in the box, 
> such as dual-stage negotiation by ASA (in case of alternative protocols)
> as well as secure-software on ACP to minimize/eliminate malicious software injection..

Understood.

> > Similarly,
> > for "big iron" router deployments, physical links are the norm and the
> > DULL GRASP downgrade attack may not be a practical concern; I would
> > again like to have the mechanisms in place to be able to detect
> > downgrade if, for example, deployments broaden to the use of radio
> > technologies, but the absence of such a mechanism does not seem like a
> > critical flaw at this time.
> 
> I have added a section A.10.9 to describe a possible future mechanism and
> mentioned it in the Security Considerations section.
> 
> > So, to be clear, the DISCUSS here is just
> > to be sure that we're all on the same page as to what point Ekr was
> > making and the current state of affairs; given my current understanding,
> > I'm not holding a DISCUSS point for "add the downgrade-detection
> > mechanism" (though I do encourage it).
> 
> Hopefully A.10.9 is a good enough compromise (no specification, but
> placeholder for future work). Anything more would be real painful in this
> document now.

Yes, that works for me, and thank you for it!

> > It looks like Section 6.1.3 is missing a "rule 6: verify that the
> > acp-address/prefix in the certificate matches the address being used to
> > talk to the peer", if I'm reading between the lines properly.
> 
> The address used for the secure channel protocol connection are link-local
> scope addresses, not the actual ACP address, so such a rule would not work.
> 
> End-to-end communication (inside or outside the ACP) will use the
> ACP address, and it could authenticate its IPv6 address (the ACP
> address) by using the ACP certificate during end-to-end authentication,
> but this spec does not mandate that.

I would like (and will put in my forthcoming COMMENT) to at least mention
that there are cases where you could do this sort of check, even though it
is definitely impossible in some cases (such as the secure channel) and
even if it is not mandated.  I think I can live with not requiring it,
though.

> > (If not, and this is just skew introduced by editing, my comments about
> > references to a non-existent rule 6 apply, see COMMENT.)
> 
> XXX
> 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > Thank you for the extensive efforts you put in to respond to the
> > previous rounds of feedback; I'm happy to say that my discuss points on
> > the -19 have all been resolved.  I especially appreciate that you were
> > able to continue discussions with Russ and Barry (and others) even when
> > I myself was not being particularly responsive due to other pressing
> > issues.
> > 
> > I'd also like to express appreciation for the care that went into the
> > various "sweeping changes" (renames/etc.); there was very little fallout
> > that needed further fixup.
> > 
> > I note that I started off reviewing the diff from -19 to -27 and then
> > made a follow-up pass looking at the diff from -27 to -28, so there's
> > some risk I comment on something that I saw in the -27 but is already
> > fixed.
> > 
> > Section 1
> > 
> >    This document describes a modular design for a self-forming, self-
> >    managing and self-protecting ACP, which is a virtual out-of-band
> >    network designed to be as independent as possible of configuration,
> >    addressing and routing and similar self-dependency problems in
> >    current IP networks, but which is still operating in-band on the same
> >    physical network that it is controlling and managing.  The ACP design
> > 
> > nit: the antecedent for "similar self-dependency problems" seems to be
> > intended to be the issues with in-band OAM/control-plane that were
> > discussed a couple paragraphs prior, but grammatically we have to look
> > for a local binding within the same list.  So probably we want something
> > more like "avoiding the self-dependency problems of current IP
> > networks".
> 
> Changed sentence to:
> 
> This document describes a modular design for a self-forming, self-managing and self-protecting ACP,  which is a virtual out-of-band network designed to be as independent as possible of configuration, addressing and routing to avoid the self-dependency problems of current IP  networks while still operating in-band on the same physical network that it is controlling and managing.
> 
> >    In a fully autonomic network node without legacy control or
> >    management functions/protocols, the Data-Plane would be for example
> >    just a forwarding plane for "Data" IPv6 packets, aka: packets that
> >    are not forwarded by the ACP itself such as control or management
> >    plane packets.  In such networks/nodes, there would be no non-
> > 
> > nit: I suggest rewording to "packets other than the control and
> > management plane packets that are forwarded by the ACP itself" to avoid
> > ambiguity about whether the "such as" matches "forwarded by the ACP
> > itself" or "data packets".
> 
> Done.
> 
> > Section 1.1
> > 
> >    The implementation footprint of the ACP consists of Public Key
> >    Infrastructure (PKI) code for the ACP certificate, the GRASP
> >    protocol, UDP, TCP and TLS 1.2 ([RFC5246], for security and
> > 
> > I agree with Barry that it's best to just say "TLS".  Referencing both
> > 8446 and 5246 is okay, but 8446 needs to be there.
> 
> Changed to:
>     protocol, UDP, TCP and TLS ([RFC5246], [RFC8446], for security and
> 
> > Section 5
> > 
> >    4.  For each entry in the candidate adjacency list, the node
> >        negotiates a secure tunnel using the candidate channel types.
> >        See Section 6.5.
> > 
> > Somewhere in this procedure (not necessarily exactly here), we might
> > want to say something about how failed
> > authentication/negotiation/authorization/etc. means that the candidate
> > peer adjacency is not accepted into the ACP, rejected, discarded, or
> > something of that nature.  Having the main focus be on the success case
> > rather than the detailed error handling makes sense for an overview, but
> > if we are listing only "candidate" adjacencies we probably ought to
> > acknowledge that not all candidates succeed.
> 
> Inserted new point 6:
> 
>         <li>Unsuccessful authentication of a candidate peer results in throttled connection retries for as long as the candidate peer is discoverable. See <xref target="neighbor_verification" format="default"/>.</li>
> 
> (the section to which this points explains why there are ongoing retries..)

Excellent!

> > Section 6.1.1
> > 
> >    ACP nodes MUST NOT support certificates with RSA public keys of less
> >    than 2048 bit modulus or curves with group order of less than 256
> >    bit.  They MUST support certificates with RSA public keys with 2048
> >    bit modulus and MAY support longer RSA keys.  They MUST support
> >    certificates with ECC public keys using NIST P-256 curves and SHOULD
> >    support P-384 and P-521 curves.
> > 
> > We probably can nail this down a bit more, particularly on the ECC side
> > as being ECDSA signatures (but RSA as well to be signatures vs.
> > encryption).  Maybe something like:
> > 
> > % ACP nodes MUST NOT support certificates with RSA public keys whose
> > % modulus is less than 2048 bits, or certificates whose ECC public keys
> > % are in groups whose order is less than 256 bits.  RSA signing
> > % certificates with 2048-bit public keys MUST be supported, and such
> > % certificates with longer public keys MAY be supported.  ECDSA
> > % certificates using the NIST P-256 curve MUST be supported, and such
> > % certificates using the P-384 and P-521 curves SHOULD be supported.
> 
> Thanks. That is the new text now.
> 
> > Also, 2048-bit RSA is starting to look shaky; note that
> > draft-cooley-cnsa-dtls-tls-profile insists on 3072-bit or larger at this
> > point, which would be my own personal recommendation as well.
> 
> https://trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-1-Architecture-01.07-2014-03-13.pdf
> 
> Page 51:
> 
>  "If a TPM supports RSA, it should support a key size of 2048 bits or larger. Support for smaller key sizes is
>   allowed but discouraged."
> 
> I am somewhat nervous of not knowing enough about TPMs to be sure that
> we would NOT invalidate likely deployed TPM by forcing 3072, but TPM 2.0 seems
> to be still widely used, and that text does not make me hopeful all TPM in routers
> would support 3072. Note that i had also reduced the requirements for longer keys
> from higher req. levels to MAY i think from discuss with Russ re. avoiding
> to make implementation requirements too difficult (otherwise we could do a SHOULD 3072
> in addition to 2048, and MAY beyond 3072...).
> 
> Aka: no change unless IMHO we know better about adoptability
> (remember this is OPS, more focussed on operationalizing what we have,
>  not SEC or RTG where we drive what should exist...)
> 
> Would also be good if we could start figuring out an exit strategy from
> doing these type of requirements in the ACP document and instead try to
> find a document for these type of requirements for routers/switches,
> where we want to ensure wider compatibility with HW such as TPM and
> HW encryption (ESP). By (i think) not having documents that explicitly
> mention support for scuh hardware components, i am worried as if a lot
> of end-to-end security in IETF is really driven by use-cases and experts
> primarily focussed on the much easier to upgrade software on endpoints and
> cloud servers (but which may not be as HW-secure/performant/cost-effective
> compared to those solutions that does expect to be supported in available
> hardware).
> 
> If there is an idea for a good more narrowly scoped doc wrt. sec. on router
> hardware, i'd be happy to contribute the (limited ;-) knowledge i have.
> 
> >    ACP nodes MUST support SHA-256 and SHOULD support SHA-384, SHA-512
> >    signatures for certificates with RSA key and the same RSA signatures
> >    plus ECDSA signatures for certificates with ECC key.
> > 
> > We should probably reword this to be clearer that we're talking about
> > the signature on the certificate, not the signatures made by the
> > certificate.  Perhaps:
> > 
> > % ACP nodes MUST support RSA certificates that are signed by RSA
> > % signatures over the SHA-256 digest of the contents, and SHOULD
> > % additionally support SHA-384 and SHA-512 digests in such signatures.
> > % The same requirements for certificate signatures apply to ECDSA
> > % certificates, and additionally, ACP nodes MUST support ECDSA
> > % signatures on ECDSA certificates.
> 
> Thanks. That is the new text now.
> 
> >    The ACP certificate SHOULD use an RSA key and an RSA signature when
> >    the ACP certificate is intended to be used not only for ACP
> >    authentication but also for other purposes.  The ACP certificate MAY
> >    use an ECC key and an ECDSA signature if the ACP certificate is only
> >    used for ACP and ANI authentication and authorization.
> > 
> > There may be a mismatch in the normative guidance here: we have MUST
> > baseline guidance earlier for 2048-bit RSA and P-256, but SHOULD
> > (stronger than MAY) for P-384/P-521 and only MAY for >2048-bit-RSA.  But
> > here, it's SHOULD use RSA and only MAY ECC, which is reversed.  I know
> > that the flexibility-of-strength question is not exactly the same as
> > what-to-use-externally, so maybe it's fine, but I wanted to check.
> 
> Yes, this is just very weak guidance how an operator setting up ACP
> would pick RSA vs. ECC. Re-using the ACP certs for any other feature
> on the router is a nice simplification but makes it almost impossible to
> figure out the complete extend of peers with which to authenticate and
> hence only RSA is a safe bet. 
> 
> The guidance for ECC is very weak and it should be SHOULD, but its a 
> lot easier to write in followup work more comprehensive text as to what
> set of functions would constitute a complete set of service components
> of a complete ACP/ANI that needs to be checked for ECC support.
> 
> For example, i am worried about enterprises using widely used NOC components
> that then turn out to be not supporting ECC. Something like a NOC radius/diameter
> server to be used to authenticate further services using TLS with ACP
> cert across the ACP. And that server is not supporting ECC certs, but
> is of course part of the core of the enterprises security system
> (i am just making up the example, but lets say i have seen hese type
>  of NOC sytems holding back enterprises to move to IPv6, hence the
>  paranoia).
> 
> And this type of operational considerations looks like text beyond what
> fits into this base spec (not that a lot of that type of operational
> thought haven't already gone into this doc already ...).
> 
> Aka: strategy is something like: lets make sure ACP software itself 
> has MUST for what we want, but otherwise keep operational/configuration
> advise (such as selection RSA vs ECC) to be as painless as possible to
> adopt ACP. 

Understood, and thanks for the additional explanation.

> >    Any secure channel protocols used for the ACP as specified in this
> >    document or extensions of this document MUST therefore support
> >    authentication (e.g.:signing) starting with these type of
> >    certificates.  See [RFC4492] for more information.
> > 
> > Do they all have to support both RSA and ECDSA certs, or is it okay to
> > only support one?
> 
> Otherwise we can not give operators the freedom to move
> from RSA to ECC but we would create within the ACP nodes themselves
> a hurdle. The way it is written, the only hurdle to move to ECC are
> non-ACP-software dependencies.
> 
> >    The ACP certificate SHOULD be used for any authentication between
> >    nodes with ACP domain certificates (ACP nodes and NOC nodes) where
> >    the required authorization condition is ACP domain membership, such
> > 
> > I suggest s/the required authorization condition/a required
> > authorization condition/, since even if there is more fine-grained
> > authorization needed, you still need an ACP certificate to prove you're
> > part of the domain.
> 
> Thanks, done.
> 
> >    In support of ECDH key establishment, ACP certificates with ECC keys
> >    MUST indicate to be Elliptic Curve Diffie-Hellman capable (ECDH) if
> >    X.509 v3 keyUsage and extendedKeyUsage are included in the
> >    certificate.
> > 
> > nit: "if X.509 v3 keyUsage and extendedKeyUsage are included" sounds
> > like both need to be present, but I don't think that's really what's
> > needed.  AFAICT only the non-extended keyUsage is relevant, so we would
> > just say "if the X.509v3 keyUsage extension is present, the keyAgreement
> > bit MUST be set".
> 
> Thanks. done.
> 
> >    Any other field of the ACP domain certificate is to be populated as
> >    required by [RFC5280] or desired by the operator of the ACP domain
> >    ACP registrars/CA and required by other purposes that the ACP domain
> >    certificate is intended to be used for.
> > 
> > This sentence is a bit hard to parse; it has three clauses and it's not
> > entirely clear how they're intended to relate to each other ("populated
> > as required by RFC5280", "desired by the operator of the ACP domain",
> > "required by other purposes that the ACP domain certificate is intended
> > to be used for").
> 
> Changed to:
> 
>           <t>Any other fields of the ACP certificate are to be populated as required by <xref target="RFC5280" format="default"/>. As long as they are compliant with <xref target="RFC5280" format="default"/>, any other field of an ACP certificate can be set as desired by the operator of the ACP domain through appropriate ACP registrar/ACP CA procedures. For example, other fields may be required for other purposes that the ACP certificate is intended to be used for (such as elements of a SubjectName).<t>
> 
> Admittedly this may be formally redundant given how we have already a
> MUST comply with RFC5280, but as an author who is not a security/certificate
> expert that is writing this primarily for a similar audience,
> i felt this would emphasize the logic by which other
> fields of the ACP certificate are to be determined (aka: ACP does not care,
> but RFC5280 cares and other uses of the ACP certificate may care).
> 
> >    certificate information can be retrieved bei neighboring nodes
> > 
> > s/bei/by/
> 
> already fixed in -28.
> 
> >    For diagnostic and other operational purposes, it is beneficial to
> >    copy the device identifying fields of the node's IDevID certificate
> >    into the ACP domain certificate, such as the "serialNumber" (see
> >    [I-D.ietf-anima-bootstrapping-keyinfra] section 2.3.1).  This can be
> > 
> > I suggest noting that this "serialNumber" is the X520SerialNumber name
> > attribute, not the CertificateSerialNumber (IIUC this is the first usage
> > of "serialNumber" in this document).  IMO the quotes, while helpful to
> > set it apart, are not enough to indicate that this is not the normal
> > certificate serial number (of "issuer and serial number" that is
> > supposed to uniquely identify a certificate).
> 
> I could not find any explanation of X520<name> "explicit tagging" in RFC5280.
> I grep'ed all RFC and could not find any reference to the X520<name> syntax,
> i have also never seen these names used in any router-CLI.
> 
> Aka: i would not want ACP be the first RFC referring to such unused and
> unexplained name. An explanation of what the heck this is about would
> be lovely though.
> 
> For now i have simply added a reference for X.520 such as done in other
> RFCs (e.g.: RFC4519]) when referring to the serialNumber we are talking about:
> 
> such as the <xref target="X.520" format="default"/>, section 6.2.9 "serialNumber" attribute in the subjects field distinguished name encoding (note that this is not the certificate serial number). See also <xref target="I-D.ietf-anima-bootstrapping-keyinfra" format="default"/> section 2.3.1.
> 
> i hope "serialNumber attribute in the subjects field distinguished name encoding"
> is the correct way to refer unambiguously to the right serialNumber. It is
> the way how 802.1AR section 7.2.8 refers to it. I for once still don't talk
> X.500 ASN.1 and so i continue to be confused about the right use of the words
> subject (subjectName ;-), distinguished name, field and attribute *sigh*.

I think that's correct (not that I am particularly fluent in the
distinguished name stuff, myself -- there's a reason we like SANs a lot
more, nowadays).  The RFC Editor can probably help make sure that we are
consistent in the terminology throughout the whole document, too.

> ( Did i say in my prior replies that i welcome text suggestions ? Especially this special language.)
> 
> I also had to raise the issue with BRSKI that their section 2.3.1 is equally confused
> about the references/naming, but its still a desirable reference because it further elaborated about the benefits
> of the serialNumber of the IDevID...

Thank you for thinking to check back with BRSKI as well.

> >    Note that there is no intention to constrain authorization within the
> >    ACP or autonomic networks using the ACP to just the ACP domain
> >    membership check as defined in this document.  It can be extended or
> >    modified with future requirements.  Such future authorizations can
> >    use and require additional elements in certificates or policies or
> >    even additional certificates.  For an example, see Appendix A.10.5.
> > 
> > It might be worth noting that we already have the id-kp-cmcRA check for
> > EST servers, in addition to the "domain membership" check.
> 
> Great point. Changed "For an example ...." to: 
> 
> See the additional check agagainst the id-kp-cmcRA <xref target="RFC6402" format="default"/> extended key usage attribute (<xref target="domcert-maint" format="default"/>) and for possible future extensions, see <xref target="role-assignments" format="default"/>.
> 
> Also added note about this to security considerations:
> 
> When Registrars use their ACP certificate to authenticate towards a CA, the id-kp-cmcRA <xref target="RFC6402" format="default"/> extended key usage attribute allows the CA to determine that the ACP node was permitted during enrollment to act as an ACP registrar
> 
> > Section 6.1.2
> > 
> >      HEXLC = DIGIT / "a" / "b" / "c" / "d" / "e" / "f"
> >              ; DIGIT as of RFC5234 section B.1
> > 
> > Note that (if I remember my ABNF right), this is not restricted to just
> > "lower case" hex digits, since matching is case-insensitive.  (Of
> > course, "LC" could stand for something else...)  In order to get the
> > case sensitivity, the %s"a" construction from RFC 7405 (or bare %x61)
> > would be needed.
> 
> Oops. Right. Case insensitive is actually fine. But then of course
> i do not need to define HEXLC, but pre-defined HEXDIG does it as well.
> So, replaced HEXLC with HEXDIG and added explanation:
> 
> Acp-address is case insensitive because ABNF HEXDIG is. It is recommended to encode acp-address with lower case letters
> 
> >      extension = ; future standard definition.
> >                  ; Must fit RFC5322 simple dot-atom format.
> > 
> > I think there's a different convention than "empty definition" for
> > extensibility points and am hoping that my colleagues will chime in
> > about it.
> 
> replaced by:
> 
>   extensions = *( "+" extension )
>   extension  = 1*etext  ; future standard definition.
>   etext      = ALPHA / DIGIT /  ; Printable US-ASCII
>                "!" / "#" / "$" / "%" / "&" / "'" /
>                "*" / "-" / "/" / "=" / "?" / "^" / 
>                "_" / "`" / "{" / "|" / "}" / "~"
> 
> Aka: extension is like atom, except character "+" is not allowed.
> 
> Could not find a blank extension syntax option, but given how we
> can not have "+" or "@" (for the parser to succeed), this was
> a good thing to fully specify.
> 
> >      acp-node-name      = fd89b714F3db00000200000064000000
> >                           +area51.research@acp.example.com
> > 
> > [has upper-case hex digit, if that ends up mattering]
> 
> Changed to lower case.
> 
> >    Nodes complying with this specification MUST also be able to
> >    authenticate nodes as ACP domain members or ACP secure channel peers
> >    when they have a 0-value acp-address field and as ACP domain members
> >    (but not as ACP secure channel peers) when they have an empty acp-
> >    address field.  See Section 6.1.3.
> > 
> > An "empty acp-address field" would seem to mean "", the empty string,
> > which is not allowed by the ABNF.  It is, however, allowed to omit the
> > acp-address, so I think that it's better to talk about the acp-address
> > field being "absent" rather than "empty" (and there are many subsequent
> > mentions of an "empty acp-address" in the document; I tried to point out
> > most of them as they occur.
> 
> Ok. Tried to change all "empty" with omitted, also where found for rsub,
> and changed setnences accordingly where it didn't sound right just to
> put in omitted. See diff.

I think this all came through properly.

> >    To keep the encoding simple, there is no consideration for
> >    internationalized acp-domain-names.  The acp-node-name is not
> >    intended for end user consumption, and there is no protection against
> >    someone not owning a domain name to simpy choose it.  Instead, it
> > 
> > We should presumably say somewhere (not necessarily here) that if
> > someone does maliciously try to choose a domain name they don't own as
> > the acp-domain-name, they won't be able to pass a domain-membership test
> > unless it's signed by the real domain's CA, and the CA should know
> > enough to not issue such certs to unauthorized entities.
> > In other words, the combination of acp-domain-name and root CA identify
> > the domain, so collisions of acp-domain-name are not fatal (which is
> > good, since they're trivial to produce).
> 
> This is somewhat painfull, because with the demise of the use of
> rfc822Name based AcpNodeName in -28, we lost the ability to use ACME style
> address verification, which would be better than any domain-name verification
> alone.
> 
> There is one additional quirk as well related.
> 
> Here is the new text to address your suggestion and the quirk, its in the "Security Considerations" section.
> 
> <t>The security model of the ACP as defined in this document is tailored for use with private PKI. The TA of a private PKI provide the security against maliciously created ACP certificates to give access to an ACP. Such attacks can create fake ACP certificates with correct looking AcpNodeNames, but those certificates would not pass the certificate path validation of the ACP domain membership check (see <xref target="certcheck"/>, point 2).</t>
> 
> <t>If public CA are to be used, ACP registrars would need to prove ownership of the domain-name of AcpNodeNames to the public CA. However, maintaining the ULA based address allocation when using a public CA might be considered to be a violation of the private allocation expectation of ULA prefixes. To avoid this issue, further changes to registrar address allocation procedures might be needed, for example using global IPv6 address prefixes owned by the public CA instead of ULA.<t>
> 
> The first paragraph is not actionable, but hopefully ok. here to re-describe
> the core security property and as a counterpart to the second paragraph addressing
> what you mention.
> 
> Because of the address allocation happening via AcpNodeNames, public PKI
> would get us into a lot of more points about certificate signing for address
> space with public PKI... Could be interesting, but out of scope in this document.

Yes, let's definitely keep this out of scope for this document.  We want to
actually publish it and not add a few more years of discussion...

> >        1.2  If "acp-address" is empty, and "rsub" is empty too, the
> >             "local-part" will have the format ":++extension(s)".  The
> >             two plus characters are necessary so the node can
> > 
> > nit: there's no ":" in the ABNF.
> 
> Thanks, fixed. Leftover text from rfc822Name.
> 
> >        2.4  Addresses of the form <local><@domain> have become the
> > 
> > nit(?): is the '@' intended to be outside the angle brackets?
> 
> Thanks, fixed. (hard to see when reading the XML...)
> 
> >        3.1  It should be possible to use the ACP certificate as an
> >             LDevID certificate on the system for other uses beside the
> >             ACP.  Therefore, the information element required for the
> >             ACP should be encoded so that it minimizes the possibility
> >             of creating incompatibilities with such other uses.  The
> >             subjectName is for example often used as an entity
> >             identifier in non-ACP uses of a the ACP certificate.
> > 
> > There's not a "subjectName" field in a PKIX certificate, and I'm not
> > sure if this is intended to refer to subjectAltName (so as to say that
> > the ACP name can be used for non-ACP uses) or to some other field
> > (commonName?) (so as to say that we are leaving that field unoccupied
> > for other uses).  In light of the surrounding context, I'd guess the
> > former, but please clarify.
> 
> Fixed sentence to:
> 
> The attributes of the subject field for example are often used in non-ACP uses of a the ACP certificate and should therefore not be occupied by new ACP values.
> 
> Btw: Given how subject is of type Name, it seems to be common to call this subject-name,
> for example in common router CLI output.  Or as i did call it subjectName - as
> the counterpart to subjectAltName ... I guess that would have been too easy ;-)

It's quite understandable to try, yes; too bad we aren't allowed to have
things easy :)

> > Section 6.1.3
> > 
> >    3:   If the node certificate indicates a Certificate Revocation List
> >       (CRL) Distribution Point (CRLDP) ([RFC5280], section 4.2.1.13) or
> >       Online Certificate Status Protocol (OCSP) responder ([RFC5280],
> >       section 4.2.2.1), then the peer's certificate MUST be valid
> >       according to those mechanisms when they are available: An OCSP
> >       check for the peer's certificate across the ACP must succeed or
> >       the peer certificate must not be listed in the CRL retrieved from
> >       the CRLDP.  These mechanisms are not available when the node has
> > 
> > IIUC, the "node certificate" in the first line is the same as the
> > "peer's certificate" thereafter; we should probably use "peer node's
> > certificate" the first time as well, for consistency.
> 
> Fixed to use just "peer's" in both places. "node" sounds redundant,
> whole certcheck text only talks about peer. 
> 
> >       peer if there are multiple.  The ACP secure channel connection
> >       MUST be retried periodically to support the case that the neighbor
> >       acquires a new, valid certificate.
> > 
> > (I forget if we already give guidance somewhere about the order of
> > magnitude for "periodically"; if not, we might want some here.)
> 
> Yes
> 6.6.  Candidate ACP Neighbor verification, exponential backoff with
> recommended timers.
> 
> >    5:   The candidate peer certificate's acp-node-name has a non-empty
> >       acp-address field (either 32HEXLC or 0, according to Figure 2).
> > 
> > nit: per the ABNF, we should probably refer to the acp-address field
> > being absent rather than being empty.
> 
> Ack.
> 
> >       Steps 1...4 do not include verification of any pre-existing form
> >       of non-public-key-only based identity elements of a certificate
> >       such as a web servers domain name prefix often encoded in
> >       certificate common name.  Steps 5 and 6 are the equivalent steps.
> > 
> > I think we only have a step 5 (no 6) now?
> > 
> >       Steps 1...5 authorize to build any secure connection between
> >       members of the same ACP domain except for ACP secure channels.
> > 
> >       Step 6 is the additional verification of the presence of an ACP
> >       address.
> > 
> >       Steps 1...6 authorize to build an ACP secure channel.
> > 
> > (ditto)
> 
> *Sigh*. How did i overlook these. I vividly remember doing a lot of fixup
> when i think Erics review had me merge two points into one. 
> Fixed.
> 
> > Section 6.1.3.1
> > 
> >    node SHOULD obtain the current time in a secured fashion
> > 
> > I note with excitement that draft-ietf-ntp-using-nts-for-ntp is in the
> > RFC Editor's queue!
> 
> Indeed. But the draft is so much better than the RFC will be due to
> the presence of section 8 ;-)
> 
> Of course, this does not solve the fundamental recursion problem of
> verifying the lifetime of a cert used to authenticate time information
> required to verify the cert.
> 
> > Section 6.1.5.3
> > 
> >    A CRLDP can be reachable across the ACP either by running it on a
> >    node with ACP or by connecting its node via an ACP connect interface
> >    (see Section 8.1).  The CRLDP SHOULD use an ACP certificate for its
> >    HTTPs connections.  The connecting ACP node SHOULD verify that the
> >    CRLDP certificate used during the HTTPs connection has the same ACP
> >    address as indicated in the CRLDP URL of the node's ACP certificate
> >    if the CRLDP URL uses an IPv6 address.
> > 
> > CRLDPs typically run over HTTP, not HTTPS, so this SHOULD is surprising.
> > That said, if there is to be a certificate check, why SHOULD vs MUST
> > verify that the IPv6 address matches?
> 
> This text came about in revision 14, but as i also answered to the
> same SHOULD vs. MUST question from Roman: I have no practical experience
> with CRLDP, so i was hoping for feedback from reviewers with more
> experience. YOu are the first to point out HTTP is common (and
> by some implication of mine also usually sufficient).
> 
> Upon trying to figure this out better now, i added the following
> sentence so to explain and define the potential for HTTPS. Note that
> the the section has only a SHOULD HTTP (no S) requirement, so there
> is no requirement against HTTPS for CRLDP.
> 
> <t>When using a private PKI, the CRL may considered to be need-to-know.
> In this case, HTTPS may be chosen to provide confidentiality, especially
> when making the CRL available via the Data-Plane. When the CRLDP URL
> is HTTPS, normal ACP domain membership check is performed. The CRLDP MAY
> omit the CRL verification during this domain membership check to permit retrieval 
> of the CRL by a node with revoked ACP certificate to allow that node to quickly
> discover its ACP certificate revocation.</t>
> 
> I deleted the prior sentences you are referring to:
> 
> <t>When using a private PKI, the CRL may considered to be need-to-know.
> In this case, HTTPS may be chosen to provide confidentiality, especially
> when making the CRL available via the Data-Plane. When the CRLDP URL
> is HTTPS, normal ACP domain membership check is performed.</t>
> 
> I think these where based on a misunderstanding of mine that a CRL
> could be faked by an attacker and so i wanted to be sure it was
> served by an authentic CRLDP, but my current (hopefully improved)
>  understanding is that an attacker can not fake CRL because its signed
> by the CA, but instead it can only disrupt reception of a CRL, and sending an
> old/outdated CRL is just a variation of that. Hence there does not seem
> to be a relevant security benefit of trying to verify the address of
> the CRLDP.

Yes, the CRL is signed by the CA (usually by the CA certificate directly,
IIUC, though it's allowed to designated a different certificate only used
for signing CRLs).  And there's a timestamp, so you're right that the
address verification doesn't help much.

> > Section 6.1.5.5
> > 
> >    Maintaining existing TA information is especially important when
> >    enrollment mechanisms are used that unlike BRSKI do not leverage a
> >    voucher mechanism to authenticate the ACP registrar and where
> >    therefore the injection of certificate failures could otherwise make
> >    the ACP node easily attackable remotely.
> > 
> > We should probably not say that you SHOULD immediatelly fall back to
> > forgetting the remembered TAs on the first TLS failure.  Some kind of
> > retry mechanism would give a bit more resilience against this attack.
> 
> Added two sentences:
> 
> at end of BRSKI paragraph:
> 
> To prohibit 
> attacks that attempt to force the ACP node to forget it prior (expired) certificate
> and TA, the ACP node should alternate between attempting to re-enroll using
> its old keying material and attempting to re-enroll with its IDevID and requesting
> a voucher.</t>
> 
> and at end of non-BRSKI text:
> 
> and where therefore the injection of certificate failures could otherwise make the ACP node easily
> attackable remotely by returning the ACP node to a "duckling" state in which
> it accepts to be enrolled by any network it connects to. The (expired) ACP
> certificate and ACP TA SHOULD therefore be maintained and used for re-enrollment
> until new keying material is enrolled.</t>

(I'll offer some wordsmithing advice in the forthcoming COMMENT.)

> > Section 6.3
> > 
> >    Note that the use of the IPv6 link-local multicast address
> >    (ALL_GRASP_NEIGHBORS) implies the need to use Multicast Listener
> >    Discovery Version 2 (MLDv2, see [RFC3810]) to announce the desire to
> >    receive packets for that address.  Otherwise DULL GRASP could fail to
> >    operate correctly in the presence of MLD snooping, non-ACP enabled L2
> >    switches ([RFC4541]) - because those would stop forwarding DULL GRASP
> >    packets.  Switches not supporting MLD snooping simply need to operate
> > 
> > nit: I suggest putting the 4541 reference right after "MLD snooping"
> > (i.e., before "non-ACP-enabled L2 switches").
> 
> Done.
> 
> > Section 6.7.3.1.1
> > 
> > It's a bit surprising to see ENCR_AES_CCM_8 as a "MAY", since the 8-byte
> > authentication tag may be significantly weaker than the strength of the
> > other primitives being used for ACP secure channels.
> 
> Because of RFC8247: "ENCR_AES_CCM_8 was not considered in RFC 4307.  This document
> considers it as SHOULD be implemented in order to be able to interact
> with IoT devices."
> 
> MAY is already a downgrade from RFC8247 SHOULD and it's only upgraded
> to SHOULD in ACP if it actually turns out to be faster than the
> alternative crypto on those type of ACP nodes.
> 
> > If ENCR_AES_CBC is listed, we probably want to say something about the
> > ESP Authentication Algorithm used with it (the AUTH_HMAC_SHA2_256_128
> > that's a MUST in 8221 would be fine).
> 
> Changed sentence to:
> 
> ENCR_AES_CBC with AUTH_HMAC_SHA2_256_128 (as the ESP authentication algorithm) and ENCR_AES_CCM_8 MAY be supported.
> > 
> >    o  There is no MTI requirement against support of ENCR_AES_CBC
> >       because ENCR_AES_GCM_16 is assumed to be feasible with less cost/
> >       higher performance in modern devices hardware accelerated
> >       implementations compared to ENCR-AES_CBC.
> > 
> > I'm not sure what "against support of ENCR_AES_CBC" is intended to mean.
> > It sounds like it's saying "we don't forbid AES-CBC" but the rest of the
> > sentence doesn't really support that.
> 
> Changed to "There is no MTI requirement for the support of ENCR_AES_CBC"
> (aka: No MUST for ENCR_AES_CBC)
> 
> > Section 6.7.3.1.2
> > 
> >    ACP nodes SHOULD set up IKEv2 to only use the ACP certificate and TA
> >    when acting as an IKEv2 responder on the IPv6 link local address and
> >    port number indicated in the AN_ACP DULL GRASP announcements (see
> >    Section 6.3).
> > 
> > There's a subtlety of English here -- "to only use <X> when <Y>" means
> > that the only time X is used is when Y, whereas "to use only <X> when
> > <Y>" means that X is the only thing that is used when Y, which I think
> > is the intent of this statement.  (But I could be wrong!)
> > 
> >    In IKEv2, ACP nodes are identified by their ACP address.  The
> >    ID_IPv6_ADDR IKEv2 identification payload MUST be used and MUST
> >    convey the ACP address.  If the peer's ACP certificate includes a
> >    32HEXLC ACP address in the acp-node-name (not "0" or empty), the
> > 
> > [another case of "empty" vs "absent" for acp-address]
> 
> fixed.
> 
> > Section 6.7.4
> > 
> > nit: s/negoting/negotiating/
> 
> fixed.
> 
> >    An ACP node announces its ability to support DTLS v1.2 compliant with
> >    the requirements defined in this document as an ACP secure channel
> >    protocol in GRASP through the "DTLS" objective-value in the "AN_ACP"
> >    objective.
> > 
> >    To run ACP via UDP and DTLS v1.2 [RFC6347], a locally assigned UDP
> >    [...]
> > 
> > As previously, we probably want the "DTLS" objective value to be
> > version-agnostic; the 1.2 minimum/MTI can be specified in the following
> > paragraphs.
> 
> I have removed the "v1.2" in that sentence
> 
> >    Unlike for IPsec, no attempts are made to simplify the requirements
> >    of the BCP 195 recommendations because the expectation is that DTLS
> >    would be using software-only implementations where the ability to
> >    reuse of widely adopted implementations is more important than
> >    minizing the complexity of a hardware accelerated implementation
> >    which is known to be important for IPsec.
> > 
> > (side note: hardware TLS support is becoming more common these days,
> > though only for the record encryption and not the handshake protocol, as
> > I understand it.  Analogous to supporting ESP but not IKEv2 in hardware,
> > basically.)
> 
> Most likely SmartNIC in Servers though, not actual routers. I am still
> how much his type of HW can ake over WAN networks. The first whitebox
> switches for DC with SmartNICs seem to appear. Oh well...
> 
> > Section 6.8.2
> > 
> >    TLS for GRASP MUST offer TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and
> >    TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and MUST NOT offer options
> >    with less than 256 bit symmetric key strength or hash strength of
> >    less han SHA384.  [...]
> > 
> > Those are TLS 1.2 ciphers; do you want to also say "when TLS 1.3 is
> > supported, TLS_AES_256_GCM_SHA384 MUST be offered and
> > TLS_CHACHA20_POLY1305_SHA256 MAY be offered"?
> 
> Sure. Added that proposed text at the end of above cited text.
> 
> >    less han SHA384.  TLS for GRASP MUST also include the "Supported
> >    Elliptic Curves" extension, it MUST support support the NIST P-256
> >    (secp256r1) and P-384 (secp384r1(24)) curves [RFC4492].  In addition,
> >    GRASP TLS clients SHOULD send an ec_point_formats extension with a
> >    single element, "uncompressed".  For further interoperability
> >    recommendations, GRASP TLS implementations SHOULD follow [RFC7525].
> > 
> > Note that RFC 8446 retconned "Supported Elliptic Curves" to being
> > "Supported Groups".  (It also obviated the need for "ec_point_formats",
> > but since ACP mandates ability to use TLS 1.2, you still have to send
> > that one.)
> 
> Noted.
> 
> > Section 6.10.2
> > 
> >    o  When creating a new routing-subdomain for an existing autonomic
> >       network, it MUST be ensured, that rsub is selected so the
> >       resulting hash of the routing-subdomain does not collide with the
> >       hash of any pre-existing routing-subdomains of the autonomic
> >       network.  This ensures that ACP addresses created by registrars
> >       for different routing subdomains do not collide with each others.
> > 
> > Ensured by whom?  What if the domain uses a "public CA" as a trust
> > anchor that might also be used by some other autonomic domain -- does
> > the CA also need to be checking?
> 
> ;-) This document only raises the requirements, it does not make operational
> recommendations how to achieve them (how to get certificate creation is 
> out of scope).
> 
> To answer your question: If i wanted to seet up managed CA service
> for ACPs for different customers, i would leave address assignment to
> the customer owned registrars but add a check to the CA ruotines that
> the addresses allocated have the right prefix for the domain of the
> customer. And of course the customer registrar authentication to the
> CA will allow it to only manage certificates from the customer domain.
> And when a new custmer comes along and his desired domain ULA prefix
> would collide with one of my existing customer ULA prefixes i would
> tell him to use a different domain or to add an rsub component.
> Domain ownership would not be verified for every signing, but only
> for every customer (who could use multiple registrars).
> 
> Aka: All not that difficult, but after a 160 page document i would
> rather like to answer those questions via new < 10 page operationalizing
> RFCs ;-))
> 
> And i would call it "managed service CA" because obviously the
> addresses used from one such "managed service CA" will not be aligned
> with another "managed service CA", aka: you can't simply create a large
> pool of TA across all those "managed service CA" without creating
> address overlap. And "managed service CA" also indicates that the
> decision to use a particular ULA prefix is made by the customer
> (by selecting a domain-name), and not by the CA provider. Because
> as i wrote in the security considerations, that CA provider allocation
> of ULA prefixes might violate the IETF intended spirit of ULA prefixes.
> 
> > Section 6.10.3
> > 
> >    o  Node-Number: Number to make the Node-ID unique.  This can be
> >       sequentially assigned by the ACP Registrar owning the Registrar-
> >       ID.
> > 
> > I see "can be sequentially assigned" and immediately think of
> > draft-gont-numeric-identifiers-sec-considerations, which I'm
> > AD-sponsoring for publication.  I don't have an obvious attack handy
> > against sequential assignment, but it may be worth a closer look.
> 
> put on reading list ;-)
> 
> The closer you're to the RPL root, the more you will see the whole
> list of ACP addresses active anyhow, and given how the addresses
> spaces per registrar in our addressing scheme are just something
> like 16 bit or so, brute force search will always work.
> 
> > Section 6.10.7.1
> > 
> >    Any protocols or mechanisms may be used as ACP registrars, as long as
> >    the resulting ACP certificate and TA certificate(s) allow to perform
> > 
> > nit(?): the ACP registrar is a PKI registration authority, i.e., a
> > specific entity that plays a role in certificate issuance.  I don't see
> > how a "protocol or mechanism" can fulfil that role.  Is s/as/by/ (or
> > similar) intended?
> 
> Indeed. fixed to "by".
> 
> > Section 6.10.7.3
> > 
> >    The choice of addressing sub-scheme and prefix-length in the Vlong
> >    address sub-scheme is subject to ACP registrar policy.  It could be
> >    an ACP domain wide policy, or a per ACP node or per ACP node type
> >    policy.  For example, in BRSKI, the ACP registrar is aware of the
> >    IDevID certificate of the candidate ACP node, which contains a
> >    "serialNnumber" that is typically indicating the node's vendor and
> >    [...]
> >    address scheme for ACP nodes based on the "serialNumber" of the
> >    IDevID certificate, for example by the PID (Product Identifier) part
> >    which identifies the product type, or the complete "serialNumber".
> >    The PID for example could identify nodes that allow for specialized
> >    ASA requiring multiple addresses or non-autonomic VMs for services
> >    and those nodes could receive Vlong sub-address scheme ACP addresses.
> > 
> > [same "serialNumber" comment as in Section 6.1.1, also s/Nn/N/]
> 
> replaced both times with 
> "serialNumber" attribute in the  subjects field distinguished name encoding
> 
> (see above for suggesting better unambiguous terminology if this is not ok.)
> 
> > Section 6.11.1.7
> > 
> >    When using ACP multi-access virtual interfaces, local repair can be
> >    directly by peer breakage, see Section 6.12.5.2.2.
> > 
> > nit: is there a missing word like "triggered" in here (e.g., "can be
> > triggered directly by peer breakage")?
> 
> yes. fixed.
> > 
> > Section 6.11.1.14
> > 
> >    As this requirement raises additional Data-Plane, it does not apply
> >    to nodes where the administrative parameter to become root
> >    (Section 6.11.1.12) can always only be 0b001, e.g.: the node does not
> >    support explicit configuration to be root, or to be ACP registrar or
> >    to have ACP-connect functionality.  If an ACP network is degraded to
> >    the point where there are no nodes that could be configured roots,
> >    ACP registrars or ACP-connect nodes, traffic to unknown destinations
> >    could not be diagnosed, but in the absence of any intelligent nodes
> >    supporting other than 0b001 administrative preference, there is
> >    likely also no diagnostic function possible.
> > 
> > Some nits here.  Maybe:
> > 
> > % As this requirement places additional constraints on the Data-Plane
> > % functionality of the RPL root, it does not apply to "normal" nodes
> > % that are not configured to have special functionality (i.e., the
> > % adminstrative parameter from Section 6.11.1.12 has value 0b001).  If
> > % the ACP network is degraded to the point where there are no nodes that
> > % could be configured as root, registrar, or ACP-connect nodes, it is
> > % possible that the RPL root ( and thus the ACP as a whole) would be
> > % unable to detect traffic to unknown destinations.  However, in the
> > % absence of nodes with administrative preference other than 0b001,
> > % there is also unlikely to be a way to get diagnostic information out
> > % of the ACP, so detection of traffic to unknown destinations would not
> > % be actionable anyway.
> 
> Nice. fixed to use your text. Thanks!
> 
> > Section 6.12.5.1
> > 
> >    8.  Using global scope addresses for subnets between nodes is
> >        unnecessary if those subnets only connect routers, such as ACP
> >        secure channels because they can communicate to remote nodes via
> > 
> > nit: comma after "such as ACP secure channels".
> 
> Ack.
> 
> > Section 6.12.5.2
> > 
> >    Note that all the considerations described here are assuming point-
> >    to-point secure channel associations.  Mapping multi-party secure
> >    channel associations such as [RFC6407] is out of scope (but would be
> >    easy to add).
> > 
> > Let's drop the "but would be easy to add" parenthetical, please.
> 
> Ack.
> 
> > Section 7.2
> > 
> >    This is sufficient when p2p ACP virtual interfaces are established to
> >    every ACP peer.  When it is desired to create multi-access ACP
> >    virtual interfaces (see Section 6.12.5.2.2), it is REQIURED not to
> >    coalesce all the ACP secure channels on the same L3 VLAN interface,
> >    but only all those on the same L2 port.
> > 
> > This requirement that ACP devices know whether multi-access virtual
> > interfaces are expected or not is a bit hidden here, and might benefit
> > from being more prominent in an overall requirements list.
> 
> IMHO this is not hidden: Section 6 does not cover L2 switching but describes
>  ACP for "routers".  Only section 7 describes how to perform ACP routing
> across interfaces that in the Data-Plane are L2 switched segments
> (and only become L3 subnets in the ACP).
> 
> Also: multi-access virtual interfaces are always an optimization, they are
> never required. Even an L2 switch can operate with just p2p ACP
> virtual interfaces (one to each peer). And if an ACP node maps all
> ACPs in the same bridge-domain into a single virtual multi-access subnet,
> ACP will still work fine, but that ACP node will then just operate as
> described in section 6 - as a pure L3 router for the ACP. 
> 
> > Section 8.1.1
> > 
> >    "ACP connect" is an interface level configured workaround for
> >    connection of trusted non-ACP nodes to the ACP.  The ACP node on
> >    which ACP connect is configured is called an "ACP edge node".  With
> >    ACP connect, the ACP is accessible from those non-ACP nodes (such as
> >    NOC systems) on such an interface without those non-ACP nodes having
> >    to support any ACP discovery or ACP channel setup.  This is also
> >    called "native" access to the ACP because to those NOC systems the
> >    interface looks like a normal network interface (without any
> >    encryption/novel-signaling).
> > 
> > It's "native access" (and I see later that there's discussion of how the
> > NMS routes into the ACP and of RPF filtering, and much later about the
> > ability of ACP connect channels to participate in ACP GRASP), but what
> > kind of services are accessible and how?  Do we need to make TLS
> > connections to ACP addresses, or is it at some other layer?  (If TLS,
> > are those services going to let us do anything with no client
> > authentication?)
> 
> ACP does not define what services would run across it. We say that
> end-to-end traffic should use TLS, and that would equally apply over
> ACP connect and i hope apply to all future autonomic services
> to be defined via ASA, but the most likely short term use case of using ACP
> in existing networks and ACP connect for the NOC (rfc8368) would
> likely have all those often non end-to-end encrypted protocols
> (DNS, NTP, syslog, radius / diameter, netconf, SNMP,...). But of course,
> ANI (ACP+BRSKI) makes upgrading those services to end-to-end encryption
> easier because ANI provides the certificates (BRSKI for enrolment, ACP
> for maintenance).
> 
> End-to-end authentication as defined in this spec is symmetric - all
> ACP certificates are equal, aka: no distinction client/server, aka:
> authentication is mutual ACP domain membership check. no change
> when this has an ACP connect segment in the path. 
> 
> Let me know what you think is missing as explanations in the text
> if anything, i couldn't figure out anything to write from your question.

The main thing I was not fully certain about was what level of
encapsulation was to be used.  If most services in the domain are doing
end-to-end TLS with ACP certs, and we want to talk to some of those, is the
TLS-with-ACP-cert done in the connect node or the non-ACP node, that sort
of thing.  (Maybe it's obvious once you actually start building things, but
I was scratching my head.)

> >    ACP Edge nodes SHOULD have a configurable option to filter packets
> >    with RPI headers (xsee Section 6.11.1.13 across an ACP connect
> >    interface.  These headers are outside the scope of the RPL profile in
> >    this specification but may be used in future extensions of this
> >    specification.
> > 
> > Does "filter" just mean "drop anything with an RPI" or something more
> > fine-grained?  (Also, s/xsee/see/.)
> 
> replaced filter with prohibit.
> 
> > Section 8.2.2
> > 
> > I think we want to require (or at least strongly suggest) that the
> > tunnel used to produce a "L2 adjacent" interface provide some sort of
> > cryptographic protection, as otherwise the security properties that we
> > expect from the L2-adjacent nature can be violated by an attacker on the
> > path of the tunnel.
> 
> Not really: this is just an outer tunnel wrapped around existing 
> ACP secure channel connections, so double encryption isn't really
> necessary. For example as explained in the text
> because a firewall may just permit the specific (also unencrypted)
> tunnel encap, or because it helps implementations. Or figures out
> PMTUD. Aka: all benefits for this workaround that would depend on a
> specific tunnel option.
> 
> I added the following paragraph to address the only IMHO relevant
> novel issue:
> 
>         <t>Tunneling using an insecure tunnel encapsulation increases on average
>         the risk of a MITM downgrade attack somewhere along the underlay path
>         that blocks all but the most easily attacked ACP secure channel option.
>         ACP nodes supporting tunneled remote ACP Neighbors SHOULD support
>         configuration on such tunnel interfaces to restrict or explicitly
>         select the available ACP secure channel protocols on such an interface
>         (if the ACP node supports more than one ACP secure channel protocol anyhow).</t>

That's good text to have, thanks.

> > Section 9.1.1
> > 
> >    Another example case is the intended or accidental re-activation of
> >    equipment whose TA certificate has long expired, such as redundant
> >    gear taken from storage after years.  Potentially without following
> >    the correct process set up for such cases.
> > 
> > nit: sentence fragment.
> 
> Hmm... I thought the final sentence in the paragraph is complete, but
> doesn't add too much, so deleted now.
> 
> > Section 9.2.2
> > 
> >       Policies if candidate ACP nodes should receive a domain
> >       certificate or not, for example based on the devices IDevID
> >       certificate as in BRSKI.  The ACP registrar may have a whitelist
> >       or blacklist of devices "serialNumbers" from their IDevID
> >       certificate.
> > 
> > [Same comment about serialNumber as Section 6.1.1]
> 
> ..."serialNumbers" attribute in the subjects field distinguished name encoding..
> 
> > Section 9.2.5
> > 
> >       Which candidate ACP node is permitted or not permitted into an ACP
> >       domain.  This may not be a decision to be taken upfront, so that a
> >       per-"serialNumber" policy can be loaded into every ACP registrar.
> >       Instead, it may better be decided in real-time including
> >       potentially a human decision in a NOC.
> > 
> > (ditto)
> 
> a policy per "serialNumber" attribute in the subjects field distinguished name encoding
> 
> > Section 9.3.5.1
> > 
> >    Automatically setting "ANI enable" on brownfield nodes where the
> >    operator is unaware of BRSKI and MASA operations could also be an
> >    unlikely but then critical security issue.  If an attacker could
> >    impersonate the operator and register as the operator at the MASA or
> >    otherwise get hold of vouchers and can get enough physical access to
> >    the network so pledges would register to an attacking registrar, then
> >    the attacker could gain access to the network through the ACP that
> >    the attacker then has access to.
> > 
> > nit(?): this last bit ("gain access ... then has access to") is easy to
> > read as being a tautology.  Maybe "attacker could gain access to the
> > ACP, and through the ACP gain access to the data plane"?
> 
> Tnanks. Using proposed text.
> 
> > Section 9.3.5.2
> > 
> >    Attempts for BRSKI pledge operations in greenfield state should
> >    terminate automatically when another method of configuring the node
> >    is used.  Methods that indicate some form of physical possession of
> >    the device such as configuration via the serial console port could
> >    lead to immediate termination of BRSKI, while other parallel auto
> >    configuration methods subject to remote attacks might lead to BRSKI
> >    termination only after they were successful.  Details of this may
> >    vary widely over different type of nodes.  [...]
> > 
> > Most of this seems appropriate for, and (IIRC) already in, BRSKI itself
> > and may not need repetition here.
> 
> Actually, these recommendations are not in BRSKI, but the goal of this
> section was to really be independent of BRSKI as much as possible
> but instead define common requirements for an "ACP greenfield" node - that
> has some (automated) mechanism to enroll ACP keying materials (i think
> i mentioned that NetConf ZeroTouch for example can be an alternative to
> BRSKI).
> 
> I revisited the text and its hopefully now a lot better for that goal.

I think it is, yes.

> > Section 9.4
> > 
> >    Note that the non-autonomous ACP-Core VPN would require additional
> >    extensions to propagate GRASP messages when GRASP discovery is
> >    desired across the zones.  For example, one could set up on each Zone
> >    edge router remote ACP tunnel to an appplication level implemented
> >    GRASP hub running in the networks NOC that is generating GRASP
> >    announcements for NOC services into the ACP Zones or propagating them
> >    between ACP Zones.
> > 
> > There's enough nits here that I've lost the intended meaning.  Is it:
> 
> I apologize. german anguage genes.
> > 
> > % For example, one could set up on each Zone edge router a remote ACP
> > % tunnel to a GRASP hub, implemented at the application level, that runs
> > % in the NOC for the network and serves to propagage GRASP announcements
> > % between ACP Zones and/or generate GRASP announcements for NOC services
> 
> Probably need to cut paragraph into even more shorter sentences.
> Its now:
> 
> For example, one could set up on each Zone edge router a remote ACP
> tunnel to a GRASP hub. The GRASP hub could be implemented at the application level
> and could run in the NOC of the network. It would serve to propagage
> GRASP announcements between ACP Zones and/or generate GRASP announcements for NOC
> services.
> 
> > Section 10.1
> > 
> >    Merging two networks with different TA requires the ACP nodes to
> >    trust the union of TA.  As long as the routing-subdomain hashes are
> >    different, the addressing will not overlap, which only happens in the
> >    unlikely event of a 40-bit hash collision in SHA256 (see
> >    Section 6.10).  Note that the complete mechanisms to merge networks
> >    is out of scope of this specification.
> > 
> > Maybe "only happens accidentally"?  40 bits of work is not terribly hard
> > if you're trying to make a collision...
> 
> Changed to 
> 
> As long as the routing-subdomain hashes are different, the addressing will not overlap. Accidentally, overlaps will only happen in the unlikely event

nit: s/Accidentally,/Accidental/ but this is otherwise good.

> [ I hope i do not have to explain the case of a disgruntled network admin
>   in company A that quickly set up company A's ACP to hash collide with
>   company B after learning B would buy out A and create a lot of job
>   redundancies after merging network ops. But the sentence now makes
>    that case out of scope.]

(right)

> > Section 10.2.1
> > 
> > nit: s/ectracting/extracting/
> 
> Thanks.
> 
> > Using RFC 3596 ("DNS Extensions to Support IP Version 6") as the sole
> > reference for "DNS" seems surprising.
> 
> Reviewers just wanted to have references for this list of widely
> deployed and typically unauthenticated protocols, so i tried to get away with
> a single reference for every protocols, and for DNS the most obvious
> one with this one, because all prior ones are not IPv6 but IPv4 only,
> and ACP only does IPv6. RFC3596 itself does refer to all the
> relevant DNS technology anyhow. So technically i see no gap.

I was just making an observation; I will not try to argue with your
reasoning :)

> > Section 15.2
> > 
> > Usually we put RFC 2119 as normative as well as 8174; the two together
> > comprise BCP 14, after all.
> 
> Good catch. Fixed.
> 
> > We seem to say that you MUST offer the TLS elliptic curve ciphers from
> > RFC 4492, which would make it a normative reference.  (It's also been
> > obsoleted by RFC 8422 at this point...)
> 
> Changed reference to normative.
> 
> I think we went through all the necessary arguments, why it is prudent for
> a router centric OPS standard to be somewhat more conservative on what
> to except feasible as the lowest common transport stack denominator short term
> than the latest agile cloud-software and prime client OS choices. Besides, its not too
> difficult to do an updating RFC removing compatibility requirements with
> TLS 1.2, but its a lot more painfull having to wait until the latest TLS 1.2
> only firmware in some strange router OS can get upgraded.
> 
> > Appendix A.7
> > 
> >    Note that RPL scales very well.  It is not necessary to use multiple
> >    routing subdomains to scale ACP domains in a way it would be possible
> >    if other routing protocols where used.  They exist only as options
> >    for the above mentioned reasons.
> > 
> > nit(?) s/it would be possible/that would be required/?
> 
> Very good. Thanks!
> 
> Thank you so much for this comprehensive review.

And thank you for your tireless efforts to improve the document; they are
appreciated.

-Ben


From nobody Thu Oct  1 15:36:31 2020
Return-Path: <noreply@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2211E3A09C6; Thu,  1 Oct 2020 15:36:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org,  anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, jiangsheng@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.17.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <160159178470.16845.16995175102690434365@ietfa.amsl.com>
Date: Thu, 01 Oct 2020 15:36:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/C688lUvnQ8uGWWfqrCZ1czbHYJw>
Subject: [Anima] Benjamin Kaduk's Yes on draft-ietf-anima-autonomic-control-plane-29: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2020 22:36:25 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-anima-autonomic-control-plane-29: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

We're down to largely editorial stuff at this point, and I'm happy with the overall
state of things.

A couple of the new bits in the -29 might benefit from targeted review (noted
inline), e.g., for CDDL, TSV, or INT-specific aspects.

Section 6.1

   TLS MUST offer TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and
   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and MUST NOT offer options
   with less than 256 bit symmetric key strength or hash strength of
   less than SHA384.  When TLS 1.3 is supported, TLS_AES_256_GCM_SHA384

One could potentially say "hash strength of less than 384 bits" instead
of anchoring the reference point at SHA384, but I'm not terribly
concerned about it.

   TLS MUST also include the "Supported Elliptic Curves" extension, it
   MUST support the NIST P-256 (secp256r1(22)) and P-384 (secp384r1(24))
   curves [RFC4492].  In addition, TLS clients SHOULD send an
   ec_point_formats extension with a single element, "uncompressed".

We can say "TLS 1.2 clients" for the ec_point_format extension (nit: no 's').

Section 6.2.1

Thank you for clarifying the "serialNumber" attribute; I think that will
be helpful for a lot of people.

   ACP nodes MUST NOT support certificates with RSA public keys whose
   modulus is less than 2048 bits, or certificates whose ECC public keys
   are in groups whose order is less than 256 bits.  RSA signing
   certificates with 2048-bit public keys MUST be supported, and such

I think I mentioned this previously (and sorry for the repetition if I
did), but just in case I didn't: this 256-bit group order requirement
excludes Ed25519 and friends.  If you're fine with that, that's okay; I
just want to make sure it's an informed choice.

   ACP nodes MUST support RSA certificates that are signed by RSA
   signatures over the SHA-256 digest of the contents, and SHOULD
   additionally support SHA-384 and SHA-512 digests in such signatures.
   The same requirements for certificate signatures apply to ECDSA
   certificates, and additionally, ACP nodes MUST support ECDSA
   signatures on ECDSA certificates.

I think "same requirements for digest usage in certificate signatures"
is more accurate.

   In support of ECDH key establishment, ACP certificates with ECC keys
   MUST indicate to be Elliptic Curve Diffie-Hellman capable (ECDH): If
   the X.509v3 keyUsage extension is present, the keyAgreement bit MUST
   be set.

I think I may have failed to think about and comment on this previously,
but doing direct ECDH with the (static) key in the certificate is pretty
uncommon -- as I understand it you don't need this bit set in order to
use the TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ciphersuite, for
example.  To be clear, I'm not saying it's inherently wrong to make this
requirement, just that I don't think it's needed for the use-cases
presented in this document.  (It may also make it harder to get such
certificates issued in the future, though it's hard to predict what
path CA policies will take in the future.)

Section 6.2.3

It might be nice to say something about in what cases the transport
address used to reach the peer can/cannot be validated against the
acp-address in the peer's ACP certificate.  I think there are some
classes of interactions for which that check can be done and would add
value, even though there are definitely some classes of interaction for
which it is not viable.

Section 6.2.5.3

   When using a private PKI for ACP certificates, the CRL may be need-
   to-know, for example to prohibit insight into the operational
   practices of the domain by tracking the growth of the CRL.  In this
   case, HTTPS may be chosen to provide confidentiality, especially when
   making the CRL available via the Data-Plane.  Authentication and
   authorization SHOULD use ACP certificates and ACP domain membership
   check.  [...]

(I assume that the SHOULD here is still only in the case where the CRL
is need-to-know; no text changes needed if that's correct.)

Section 6.2.5.5

   To prohibit attacks that attempt to force the ACP node to forget its
   prior (expired) certificate and TA, the ACP node should alternate
   between attempting to re-enroll using its old keying material and
   attempting to re-enroll with its IDevID and requesting a voucher.

I think that as written, this doesn't fully "prohibit" such attacks (but
does make them harder and is good advice).  I suppose some nodes might
continue trying with the old key material for some time even after
obtaining a new voucher, but the state-keeping requirements for that are
big enough that we shouldn't require it.  So I'd suggest just a small
change like s/To prohibit/As a countermeasure against/.

   Maintaining existing TA information is especially important when
   enrollment mechanisms are used that unlike BRSKI do not leverage a
   mechanism (such as the voucher in BRSKI) to authenticate the ACP
   registrar and where therefore the injection of certificate failures
   could otherwise make the ACP node easily attackable remotely by
   returning the ACP node to a "duckling" state in which it accepts to
   be enrolled by any network it connects to.  The (expired) ACP
   certificate and ACP TA SHOULD therefore be maintained and used for
   re-enrollment until new keying material is enrolled.

(editorial) the wording here should probably be checked; right now it
seeems to be saying "use X for re-enrollment until [re-enrollment
succeeds]" which makes me wonder how the new keying material would come
into play.

Section 6.4

Figure 7 has some nits, now -- '|' is not a CDDL keyword.
Also, we should probably get a CDDL expert to look at it, since both
method-params and extensions are 1*any, and I'm not 100% sure what the
order of binding is (Appendix A of RFC 8610 suggests that it is a
prioritized choice in CDDL, so things after the first comma would always
be parameters, not extensions).

   Attackers on a subnet may be able to inject malicious DULL GRASP
   messages that are indistinguishable from non-malicious DULL GRASP
   messages to create Denial-of-Service (DoS) attacks that force ACP
   nodes to attempt many unsuccessful ACP secure channel connections.
   When an ACP node sees multiple AN_ACP objectives for the same secure
   channel protocol on different transport addresses, it SHOULD prefer
   connecting via the well-known transport address if the secure channel
   method has one (such as UDP port 500 for IKEv2).

This new text should probably be run by some TSV-area reviewer (e.g.,
AD).

Section 6.8.3.1

   The IKEv2 Diffie-Hellman key exchange group 19 (256-bit random ECP),
   MUST be support.  Reason: ECC provides a similar security level to

nit: "supported".

Section 6.8.3.2

   If IKEv2 initiator and responder support IPsec over GRE, it will be
   preferred over native IPsec because of the way how IKEv2 negotiates
   transport mode as used by this IPsec over GRE profile) versus tunnel
   mode as used by native IPsec (see [RFC7296], section 1.3.1).  The ACP

nit: missing open paren?

Section 9.2.2

   *  Policies if candidate ACP nodes should receive a domain
      certificate or not, for example based on the devices IDevID
      certificate as in BRSKI.  The ACP registrar may have a whitelist
      or blacklist of devices [X.520] "serialNumbers" attribute in the
      subjects field distinguished name encoding from their IDevID
      certificate.

I note we had that long ietf@ thread about terminology, that included
"whitelist" and "blacklist", and trust you to make an informed choice
about terminology usage.

Section 9.3.5.2

   When a greenfield node enables multiple enrollment/botstrap
   protocols/mechanisms in parallel, care must be taken not to terminate
   any protocol/mechanism before another one has progressed to a point
   where greenfield state is defined to end.

(editorial) Do we give a clear definition of when greenfield state is
defined to end, that would apply to arbitrary such mechanisms?  We might
want to reword a little bit.

Section 11

Wow, so much new good stuff here; thanks!

   *  For IDevIDs to securely identify the node to which it IDevID is
      assigned, the node it needs to (1) utilize hardware support such
      as a Trusted Platform Module (TPM) to protect against extraction/
      cloning of the private key of the IDevID and (2) a hardware/
      software infrastructure to prohibit execution of non authenticated
      software to protect against malicious use of the IDevID.

nit: s/node it needs to/node needs to/

   *  A malicious ACP node could declare itself to be an EST server via
      GRASP across the ACP if malicious software could be executed on
      it.  CA should therefore authenticate only known trustworthy EST
      servers, such as nodes with hardware protections against malicious
      software.  Without the ability to talk to the CA, a malicious EST
      server can still attract ACP nodes attempting to renew their
      keying material, but they will fail to perform successful renewal
      of a valid ACP certificate.  The ACP node attempting to use the
      malicious EST server can then continue to use a different EST
      server, and log a failure against a malicious EST server.

We have two copies of basically this text.  The second one (that I
quoted) does not have a note about id-kp-cmcRA, and is the one that
should be removed.

   If public CA are to be used, ACP registrars would need to prove
   ownership of the domain-name of AcpNodeNames to the public CA.
   However, maintaining the ULA based address allocation when using a
   public CA might be considered to be a violation of the private
   allocation expectation of ULA prefixes.  To avoid this issue, further
   changes to registrar address allocation procedures might be needed,
   for example using global IPv6 address prefixes owned by the public CA
   instead of ULA.

I don't expect any problems here, but it might be good to get some
INT-area (e.g., AD) eyes on this text.

Section 12

   0: ACP Zone Addressing Sub-Scheme (ACP RFC 1: ACP Vlong Addressing
   Sub-Scheme (ACP RFC Figure 12) / ACP Manual Addressing Sub-Scheme
   (ACP RFC Section 6.11.4) Section 6.11.5)

Something went awry here (maybe just formatting?), as the '1' is
supposed to be the initial value allocated by this document, not a
reference to RFC 1.

Section 16

RFC 4492 is obsoleted by RFC 8422.

Section A.6

   When the two peers successfully establish the GRASP/TSL session, they
   will negotiate the channel mechanism to use using objectives such as

nit: s/TSL/TLS/

Section A.10.9

Thank you for adding this discussion; it is a good treatment of the
issues and considerations in play.




From nobody Fri Oct  2 01:06:26 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79B23A03FB; Fri,  2 Oct 2020 01:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 L9yHh9DJ4PsE; Fri,  2 Oct 2020 01:06:22 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8409F3A03F1; Fri,  2 Oct 2020 01:06:19 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id AD73C54864E; Fri,  2 Oct 2020 10:06:14 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id A5486440059; Fri,  2 Oct 2020 10:06:14 +0200 (CEST)
Date: Fri, 2 Oct 2020 10:06:14 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
Message-ID: <20201002080614.GA374@faui48f.informatik.uni-erlangen.de>
References: <159727599109.5414.1617295798802435987@ietfa.amsl.com> <20200911125956.GA63981@faui48f.informatik.uni-erlangen.de> <20201001223244.GP89563@kduck.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201001223244.GP89563@kduck.mit.edu>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IZKUzPbLLjTsbpJjxA5l9qEbQMU>
Subject: Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2020 08:06:25 -0000

Thanks, Ben

Let me just comment on possible AI for you, i will do my AI in a few
days when i have more time.

On Thu, Oct 01, 2020 at 03:32:44PM -0700, Benjamin Kaduk wrote:
> I think A.6 is an interesting idea and don't want to drop the idea, but the
> current state of the text in A.6 is better suited for a separate doc than
> inclusion in this one.  I suppose I could try to do a shorter rewrite that
> might be a better fit for this doc if you want; let me know.

A separate doc would have to be an actual spec of the mechanism IMHO,
and alas i do not have the time right now to start it (and after
we have an ACP RFC maybe i can also find other WG participants to
contribute ;-)). So i do not want to loose the thought and think an
 appendix is the best reminder for the problem and solution directions.

Aka: Yes: If you want to send replacement text, please send it,
and i will replace A.6 with it verbatim.

> > End-to-end communication (inside or outside the ACP) will use the
> > ACP address, and it could authenticate its IPv6 address (the ACP
> > address) by using the ACP certificate during end-to-end authentication,
> > but this spec does not mandate that.
> 
> I would like (and will put in my forthcoming COMMENT) to at least mention
> that there are cases where you could do this sort of check, even though it
> is definitely impossible in some cases (such as the secure channel) and
> even if it is not mandated.  I think I can live with not requiring it,
> though.

What do you think would be achieved with such a check ? If we write anything,
we should know (if not write down) the most obvious/relevant attack vector
prohibited:

a) I do not quite care about discovering e.g.: a TCP proxy, because that
to me seems like the most obvious thing we could discover (TLS connection
end to end via TCP proxy). Indeed, in BRSKI we already explicitly benefit
from the BRSKI proxy which is a TCP proxy. So i am worried that unqualified
address comparison would eliminate future positive use of TCP proxies.

b) Where address check really would be beneficial is something where we
are missing a key bilding block, so it would at best be written into
an appendix as a reminder: We need a GRASP authentication block. Example:
ACP node announces (multicast GRASP) a service. We want to know if that
service announcement is actually authentic from the ACP node that
owns the ACP address in the GRASP announcement. If the GRASP message
had an auhentication extension, we would know that the announcement
and its ACP address is from the ACP who claims that address.

c) hmmm... what else... drawing blank...

Let me know what you think...

Cheers
    Toerless


From nobody Fri Oct  2 20:57:52 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0E93A0DD6 for <anima@ietfa.amsl.com>; Fri,  2 Oct 2020 20:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qThwzTxOqAok for <anima@ietfa.amsl.com>; Fri,  2 Oct 2020 20:57:48 -0700 (PDT)
Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 C4B8D3A0C32 for <anima@ietf.org>; Fri,  2 Oct 2020 20:57:48 -0700 (PDT)
Received: by mail-pj1-x1033.google.com with SMTP id p21so2311642pju.0 for <anima@ietf.org>; Fri, 02 Oct 2020 20:57:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Bu8HRxggFC+pePvQIm6XiWtV+xs+RoogEnteeFrpYGs=; b=dRSNkQpbvDEO7Bvob32plcN5s+mS01Shb17wfKeRJw4gQxsCwbKh5G4dwdVgMggEHY Y6IRXqL7gu4V5rVRY9l0jzXFsY8eWXMiFVNlNhxahamGWuFZ9aokz5UX1DCODNujaHQk fbLFNzIaFjmB1N4MEceo5ddLZiuk1Tpse3Crgm0bjOmkQWwDA6mWoIzujO8YD4mkGGly I0ReT6HsqKLPEG9CrL9X7Mb8QROCXmCnOsLdKDrTdJzie0VfJj2PDaEa15hzrzqWhjAX Fege+tkGOVh9xWl1MQYjY/v6LNVBsJUXGf35p4tZJwIVDVGpeCqfz+jdROsIVt1a6lwv cTnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization:cc :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Bu8HRxggFC+pePvQIm6XiWtV+xs+RoogEnteeFrpYGs=; b=J0zwug7cLMlkZleiMFJnfZaWJHzVzdXwm3vBWHbmbGMbUGm0Y9wxWAL872Ej2evVqe Ll2PVTQ/06W3LhY5eiqWtRimbJ6YmghayeiwxCbgkEZ0CT8PjroyYaBImX9WdOHK09vk OR6v/B8m9DoVxKsFrmPlNKw1JC2G4lJxje9eAT6ONpTqRJR+YOUK8d6+lZ7z9oB/FEUH K4/WVx+6isWgr6fGQ9O/KtFfJM/ggAifaBxtMtxYQVfAbjxRFfmugKE7v6kFaF69tXcW tnETooBLo6W+L/zbUHQ3C3a0LVblOTjqk4C3jYr+joWT35JTChmdPig4eYvh6g2EtsxV bRhg==
X-Gm-Message-State: AOAM532i2jmyZC/lyD7eyJyd9rbCON0oJIXClpiT8Y3m3DhNhmie96W0 r+k8I6QzipA0KoBizVEhmtA=
X-Google-Smtp-Source: ABdhPJx25rfGQ8MUditjft4pKsxC4U8hHsbvjklmwpAeOBsVbeXP252KWrWUjixX4421OgerYxrN2A==
X-Received: by 2002:a17:90a:54f:: with SMTP id h15mr6104287pjf.191.1601697468216;  Fri, 02 Oct 2020 20:57:48 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.138.136]) by smtp.gmail.com with ESMTPSA id s11sm3116320pjz.29.2020.10.02.20.57.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Oct 2020 20:57:47 -0700 (PDT)
To: Anima WG <anima@ietf.org>
References: <159573875486.18377.8979475359746431653@ietfa.amsl.com> <9beb2b46-8a08-1d45-1f1b-3bd50283fe20@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Cc: Toerless Eckert <tte@cs.fau.de>
Message-ID: <15a6fcb1-998c-929f-b039-1c27e09e5058@gmail.com>
Date: Sat, 3 Oct 2020 16:57:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <9beb2b46-8a08-1d45-1f1b-3bd50283fe20@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/F3OsGYeAB6LLSXGc_6-qh-iI2no>
Subject: Re: [Anima] Fwd: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Oct 2020 03:57:50 -0000

I was hoping we'd have an adoption call for this document after version 09 was posted, but I got distracted by other matters. Could we do that now? I can't really justify an agenda slot for it, unless the adoption call produces issues that need discussion.

I recommend reading the html version at https://www.ietf.org/id/draft-carpenter-anima-asa-guidelines-09.html

Regards
   Brian Carpenter

On 26-Jul-20 16:53, Brian E Carpenter wrote:
> This is a minor update - a few extra words on authorization of ASAs,
> and editorial fixes.
> 
>    Brian + co-authors
> 
> -------- Forwarded Message --------
> Subject: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
> Date: Sat, 25 Jul 2020 21:45:54 -0700
> From: internet-drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Guidelines for Autonomic Service Agents
>         Authors         : Brian Carpenter
>                           Laurent Ciavaglia
>                           Sheng Jiang
>                           Pierre Peloso
> 	Filename        : draft-carpenter-anima-asa-guidelines-09.txt
> 	Pages           : 26
> 	Date            : 2020-07-25
> 
> Abstract:
>    This document proposes guidelines for the design of Autonomic Service
>    Agents for autonomic networks, as a contribution to describing an
>    autonomic ecosystem.  It is based on the Autonomic Network
>    Infrastructure outlined in the ANIMA reference model, using the
>    Autonomic Control Plane and the Generic Autonomic Signaling Protocol.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-carpenter-anima-asa-guidelines-09
> https://datatracker.ietf.org/doc/html/draft-carpenter-anima-asa-guidelines-09
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-carpenter-anima-asa-guidelines-09
> 
> 
> 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/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Tue Oct  6 11:15:33 2020
Return-Path: <rwilton@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD1E03A14CA; Tue,  6 Oct 2020 11:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level: 
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=WP1gxBsL; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=W7Laocqz
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 nt5cdgRHDKU1; Tue,  6 Oct 2020 11:15:28 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B68D3A14C8; Tue,  6 Oct 2020 11:15:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29424; q=dns/txt; s=iport; t=1602008128; x=1603217728; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=byxJAIHOIzdgOBjUUwO/HDfXy5avwE7THLTejcesk0A=; b=WP1gxBsL34NbSRo1PzHpJm2zHMr91kKNzdOKQasb0FSsD79/EoynbBva M38TmEiRTBPVCr/dXUDXqZWq1B40tkElBCmN5vi8IYN4QbtF3F/jYV41n x/mDn+3JvlWrLDiMK9k6kHWeqJyy9I6u7KHX0fgk7eBtxjQqEp8VbJrVe g=;
IronPort-PHdr: =?us-ascii?q?9a23=3ArTkLahdMwK7VRt1bht0dMm36lGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwaQAdfU7vtFj6zdtKWzEWAD4JPUtncEfdQMUh?= =?us-ascii?q?IekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsutaFjbo3n05jkXSV?= =?us-ascii?q?3zMANvLbHzHYjfx828y+G1/cjVZANFzDqwaL9/NlO4twLU48IXmoBlbK02z0?= =?us-ascii?q?jE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DYCQAAtHxf/4QNJK1gHgEBCxIMQIM?= =?us-ascii?q?hKSgHcFkvLAqEM4NGA410gQKJD45qgUKBEQNVCwEBAQ0BASMKAgQBAYRKAhe?= =?us-ascii?q?BcAIlOBMCAwEBCwEBBQEBAQIBBgRthVwMhXIBAQEBAgESEQQNDAEBNwELBAI?= =?us-ascii?q?BCBEEAQEBAgImAgICHxEVCAgBAQQBDQUIEweCOUyCSwMOIAEDC51iAoE5iGF?= =?us-ascii?q?2fzODAQEBBYUfDQuCEAMGgQ4qgnKDa4ZWG4FBP4ERQ4IYNT6CGkICAQKBHgg?= =?us-ascii?q?ODhyDFTOCLZAJCAaDJocqgn+IW5BAUgqCaIh/jFqFLYMRigOFPo5VkxaIf4F?= =?us-ascii?q?wgmqSPwIEAgQFAg4BAQWBayOBV3AVO4JpEg0xFwINjh+DcYUUhUEBdAI1AgY?= =?us-ascii?q?BCQEBAwl8iweBNAGBEAEB?=
X-IronPort-AV: E=Sophos;i="5.77,343,1596499200"; d="scan'208";a="569195431"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Oct 2020 18:15:23 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 096IF4WP023561 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 6 Oct 2020 18:15:22 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 6 Oct 2020 13:15:10 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 6 Oct 2020 13:15:09 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 6 Oct 2020 13:15:09 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JPNeaCys8lhrpkJjB1UjVlhrqohBH1R+rMw3k6pkZLUH4/HWgf+VJIBfMTYo58ERPPtjvPnEI0DDqo0hRJsPOw0Ln/lx/YwQfzH3K2v3TQ26J16OQITIeEIWktda6vzO/F+gxSPmtQxyUDDrT1aNNOB6/rlOfVJctjTXfyZt7KxnPl09xkb1nJmfTA3CCn3cWcf9rOu3Qn4oIjgGoKf7jb60fXJxwnma/GXSSj1XchowKEd/Mf19iNDtk+genFRRtb+xOCm29+LM/cC6NyiCmZkBkILLy4UesYz1eainJj7Wd8u07I4rtYxBuNe7kYPBo7scu9uqjauh5l7+S2ep5A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=byxJAIHOIzdgOBjUUwO/HDfXy5avwE7THLTejcesk0A=; b=ZHm1fWz5+l95D52mGOzlRDbV3GZEawPZgW7JvPSiJmGvL6R87jdK4gqbm66ZfeFcUZVY5Ak3w4VOUvItLIcV2LNOtyw2K6/cYhiIGCavPVVwx1cMAlXSJQKhiB9syEcE785E7nCwZXAMsVTev5W9dDExGNY+aGOEwFTDvKnOI1U2CzpDcbCsrD5IJhH9QaCU84ZLP9EqcOCf6PrZ9HyQIBenT4zzAAETaZ1ko24EVxNPaf90oqU13TCIw1kEjrfQj0RJaDbbOfhwGUakWmMYnNgfjx6Ozn1EQ16syEwumLnkxXUnCFVqiQ1ihmuttVox3iYCoho8UemIkmbcSsLuKQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=byxJAIHOIzdgOBjUUwO/HDfXy5avwE7THLTejcesk0A=; b=W7LaocqzvtIDAbN24kBC85/v6AbiYpedRthr2Q7g7li3x/HpQv5N+Ybg1jBgEsLVuwQz09dwnWMSs9yG+xJkWY0LT81I58tFmOdf6gf0mt0SqFKipa9pHolUwIPueOeX1nVMjss7KJjbxkBmZ6oi0kYHCYc0rgBGYBem3EdXwaw=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by MN2PR11MB4383.namprd11.prod.outlook.com (2603:10b6:208:17b::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.32; Tue, 6 Oct 2020 18:15:08 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241%4]) with mapi id 15.20.3433.043; Tue, 6 Oct 2020 18:15:08 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-ietf-anima-grasp-api@ietf.org" <draft-ietf-anima-grasp-api@ietf.org>
CC: "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: AD review of draft-ietf-anima-grasp-api-06
Thread-Index: AdaVqYdACp127x0gSqKPFepZQxnBwwBz2nOAABm+chA=
Date: Tue, 6 Oct 2020 18:15:07 +0000
Message-ID: <MN2PR11MB4366C811AAE5295B9A1A0D43B50D0@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <MN2PR11MB4366FCFF358BBABBF64CB27CB5350@MN2PR11MB4366.namprd11.prod.outlook.com> <e547f069-5138-fa04-2c63-ae7d9ead760a@gmail.com>
In-Reply-To: <e547f069-5138-fa04-2c63-ae7d9ead760a@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [82.12.233.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cc5ac9d8-9ff4-4824-6461-08d86a23c1ed
x-ms-traffictypediagnostic: MN2PR11MB4383:
x-microsoft-antispam-prvs: <MN2PR11MB438304EA049981D041066A01B50D0@MN2PR11MB4383.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: npYSdw1dNjjoFakl5zIvx5jln8FzkhZMRXK+s0ruHrKDxRzyFgOafrxdkr4XcDBbd6YRNYQ9G6w3MjsqWOBN/dRi8TP454S1X8JwFG/oUgH/sgWgxLz1+n7lGxARjRurcLb1wuEHXvEXjHYuC0d4C1VdN1IcGwvDaUYj/3N+t67N37gOxq6Nyd0k4Rr9dOvemyEcqzdJSQ/+O4oaw8cM7Mx3Uu/ZEHcJqhx+ys1h6Bpi90OD6JzARqZsWKYbVgItL8EUgLnKHKhubGrwUg7wRCvU/qvCOVu1WvC825GBno9USHaZwzwPquP61xlA/JfCYluAxC5QuEHp8c+O7rxVOnUCnCH0QQqodH41AWTDsOE5+6pyJIlTy1T/szcdmg+GAgPygKULgWLVKUD7J0pEoQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(346002)(136003)(376002)(366004)(396003)(39860400002)(66476007)(8936002)(64756008)(66946007)(53546011)(30864003)(66446008)(66556008)(8676002)(76116006)(52536014)(316002)(83380400001)(110136005)(5660300002)(966005)(83080400001)(86362001)(54906003)(186003)(6506007)(9686003)(478600001)(55016002)(7696005)(26005)(33656002)(2906002)(4326008)(71200400001)(579004); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: W4LjDjmLA5S8oauIb1HWfzrvPUa34y4e+Z6tS3yvaefehmush0OyzLAnJgaN3zwYEI5UxsVyI3nkDtq/abj+w3wc/IBAf6n204/h7vzMXKOZcXL9Ad1NIx8I8lgwP+YVAIwEbXKVG6Ol/8uEDzyTr9zUiHVu7KfikzWfIHjTGNZ8vE20ZB4ORGVl3Ff+5pPhNkXZUYuUl/+K4XzC99L05joDMeyHbBDONdwEU5RmzsGh2w5bOpac0hDuoVhXZSpN0U06ZBAf5j/KAWvtAQvTdfT5+81tF4V/kmpM15snFwP5/uVcvfNz2YL/skMRxYCZ9zLbFOFZd+VAW87TlBG6ASckTCBZN/Ly1zMRydT3HhQtuMIELwFYOQa6+9JarKykk1R16RWexPdIMvncItkRVWLyos7abBJ7V2xWpTT2/U/VI5Rqoa41VzZn48+Qf8oGN8ZWlsoWn+M5fWbiDDjWMtAr5U84MfMKWO9kPLtrE+T3k12hNb0E6TQ1T971/ZD6vwVcYjMNpcmLRSW3MNJ8HsrYwfmjEYox6pl1Pxl/SF7jkJ3g00MpgaYCugmwLhxSACwoVZUJV/vBW98DTxUhOTdYLGfemzCa+wR+HX5rog+wJKFW5Rd8A1yzb8X+mSQKM/FVGOksO3H6x/rs8KRcWQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB4366.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cc5ac9d8-9ff4-4824-6461-08d86a23c1ed
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Oct 2020 18:15:07.8537 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fovt6wsYHZA5tk8nSTnlVE/RmnhfZB25LH/W+SrV9eJS69fk4uQDuyEWZl8cPRE0ndAr9EtKn9GE8S4XmeQItg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4383
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/vKi-vGtdOxuX946IhUEyySfPM60>
Subject: Re: [Anima] AD review of draft-ietf-anima-grasp-api-06
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 18:15:32 -0000

SGkgQnJpYW4sDQoNClRoYW5rcyBmb3IgdGhlIGNvbW1lbnRzLCBwbGVhc2Ugc2VlIHJlcGxpZXMg
aW5saW5lLg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgPGJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbT4NCj4gU2VudDogMzAgU2Vw
dGVtYmVyIDIwMjAgMjM6MjgNCj4gVG86IFJvYiBXaWx0b24gKHJ3aWx0b24pIDxyd2lsdG9uQGNp
c2NvLmNvbT47IGRyYWZ0LWlldGYtYW5pbWEtZ3Jhc3AtDQo+IGFwaUBpZXRmLm9yZw0KPiBDYzog
YW5pbWFAaWV0Zi5vcmc7IFNoZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdlaS5jb20+DQo+IFN1
YmplY3Q6IFJlOiBBRCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1hbmltYS1ncmFzcC1hcGktMDYNCj4g
DQo+IFRoYW5rcyBmb3IgdGhpcyB0aG9yb3VnaCByZXZpZXcsIFJvYi4gU29ycnkgYWJvdXQgdGhl
IHByZXZpb3VzIHBhcnRpYWwNCj4gcmVwbHkuIFNlZSByZXNwb25zZXMgaW4gbGluZS4NCj4gDQo+
IFdlJ2xsIHBhdXNlIGZvciBhbnkgZmVlZGJhY2sgYmVmb3JlIHVwZGF0aW5nIHRoZSBkcmFmdC4g
SW4gcGFydGljdWxhciwgYXJlDQo+IHRoZXJlIGFueSBvcG5pb25zIG9uIHRoZSBleGFtcGxlIGxv
Z2ljIGZsb3dzIGlzc3VlIG5vdGVkIGJlbG93Pw0KPiANCj4gT24gMjktU2VwLTIwIDA0OjE5LCBS
b2IgV2lsdG9uIChyd2lsdG9uKSB3cm90ZToNCj4gPiBIaSwNCj4gPg0KPiA+IEFwb2xvZ2llcyBm
b3IgdGhlIGRlbGF5IGZvciB0aGlzIHJldmlldy4NCj4gPg0KPiA+IFBsZWFzZSBzZWUgY29tbWVu
dHMgYmVsb3cuICBJJ3ZlIGFsc28gYXR0YWNoZWQgdGhlbSBpbiBjYXNlIHRoZXkgZ2V0DQo+IHRy
dW5jYXRlZCAod2hpY2ggaGFzIGhhcHBlbmVkIG9uIG90aGVyIHJldmlld3MpLg0KPiA+DQo+ID4g
VGhhbmsgeW91IGZvciB0aGlzIGRvY3VtZW50LiAgT3ZlcmFsbCwgaXQgaXMgdmVyeSB3ZWxsIHdy
aXR0ZW4sIGVhc3kgdG8NCj4gcmVhZCBhbmQgZWFzeSB0byB1bmRlcnN0YW5kLg0KPiA+DQo+ID4N
Cj4gPiBDb21tZW50czoNCj4gPg0KPiA+ICAgICAxLiAgSW50cm9kdWN0aW9uDQo+ID4NCj4gPiAg
ICAgICAgQXMgdGhlIGZvbGxvd2luZyBmaWd1cmUgc2hvd3MsIGEgR1JBU1AgaW1wbGVtZW50YXRp
b24gY291bGQNCj4gY29udGFpbg0KPiA+ICAgICAgICB0d28gbWFqb3Igc3ViLWxheWVycy4gIFRo
ZSBib3R0b20gaXMgdGhlIEdSQVNQIGJhc2UgcHJvdG9jb2wNCj4gbW9kdWxlLA0KPiA+ICAgICAg
ICB3aGljaCBpcyBvbmx5IHJlc3BvbnNpYmxlIGZvciBzZW5kaW5nIGFuZCByZWNlaXZpbmcgR1JB
U1ANCj4gbWVzc2FnZXMNCj4gPiAgICAgICAgYW5kIG1haW50YWluaW5nIHNoYXJlZCBkYXRhIHN0
cnVjdHVyZXMuICBUaGUgdXBwZXIgbGF5ZXIgY29udGFpbnMNCj4gPg0KPiA+IEkgZm91bmQgdGhl
IHRleHQsIHJlbGF0aXZlIHRvIHRoZSBkaWFncmFtLCB0byBiZSBzb21ld2hhdCBjb25mdXNpbmcs
DQo+IGFsdGhvdWdoIHRoZSBzdWJzZXF1ZW50IHBhcmFncmFwaHMgbWFrZSBpdHMgaW50ZW50IGNs
ZWFyZXIuDQo+ID4NCj4gPiBJIHRoaW5rIHRoYXQgdGhlIHRvcCBzdWItbGF5ZXIgaXMgbWVhbnQg
dG8gYmUgIkdSQVNQIEV4dGVuZGVkIEZ1bmN0aW9uDQo+IE1vZHVsZXMiLCBhbmQgdGhlICJHcmFz
cCBNb2R1bGVzIiBpcyB0aGUgYm90dG9tIHN1Yi1sYXllci4gIEhvd2V2ZXIsIHRoZQ0KPiBkaWFn
cmFtIHNlZW1zIHRvIGhhdmUgYSBzdWItbGF5ZXIgc3BsaXQgaW4gIkdSQVNQIE1vZHVsZXMiLCBh
bmQgZG9lc24ndA0KPiBuZWNlc3NhcmlseSBlcXVhdGUgdG8gIkdSQVNQIGJhc2UgcHJvdG9jb2wg
bW9kdWxlIi4NCj4gDQo+IFBlcmhhcHMgd2UgaGF2ZSBjb25mdXNlZCB0d28gYXNwZWN0czogdGhl
IHZpZXcgdGhhdCB0aGUgYXBwIHdyaXRlciBoYXMgb2YNCj4gdGhlIEFQSSwgYW5kIHRoZSB3YXkg
aXQgaGFzIHRvIGJlIGltcGxlbWVudGVkLiBNb3JlIGJlbG93Li4uDQo+IA0KPiA+DQo+ID4gICAg
IDEuICBJbnRyb2R1Y3Rpb24NCj4gPg0KPiA+ICAgICAgICBJdCBpcyBkZXNpcmFibGUgdGhhdCBB
U0FzIGNhbiBiZSBkZXNpZ25lZCBhcyBwb3J0YWJsZSB1c2VyLXNwYWNlDQo+ID4gICAgICAgIHBy
b2dyYW1zIHVzaW5nIGEgc3lzdGVtLWluZGVwZW5kZW50IEFQSS4gIEluIG1hbnkNCj4gaW1wbGVt
ZW50YXRpb25zLA0KPiA+ICAgICAgICB0aGUgR1JBU1AgbW9kdWxlIHdpbGwgdGhlcmVmb3JlIGJl
IHNwbGl0IGludG8gdHdvIGxheWVycy4gIFRoZQ0KPiB0b3ANCj4gPiAgICAgICAgbGF5ZXIgaXMg
YSBsaWJyYXJ5IHRoYXQgcHJvdmlkZXMgdGhlIEFQSSBhbmQgY29tbXVuaWNhdGVzDQo+IGRpcmVj
dGx5DQo+ID4gICAgICAgIHdpdGggQVNBcy4gIFRoZSBsb3dlciBsYXllciBpcyBhIGRhZW1vbiwg
b3IgYSBzZXQgb2Ygc3ViLQ0KPiBzZXJ2aWNlcywNCj4gPiAgICAgICAgcHJvdmlkaW5nIEdSQVNQ
IGNvcmUgZnVuY3Rpb25zIHRoYXQgYXJlIGluZGVwZW5kZW50IG9mIHNwZWNpZmljDQo+IEFTQXMs
DQo+ID4gICAgICAgIHN1Y2ggYXMgbXVsdGljYXN0IGhhbmRsaW5nIGFuZCByZWxheWluZywgYW5k
IGNvbW1vbiBkYXRhDQo+IHN0cnVjdHVyZXMNCj4gPiAgICAgICAgc3VjaCBhcyB0aGUgZGlzY292
ZXJ5IGNhY2hlLiAgVGhlIEdSQVNQIEFQSSBsaWJyYXJ5IHdvdWxkIG5lZWQgdG8NCj4gPiAgICAg
ICAgY29tbXVuaWNhdGUgd2l0aCB0aGUgR1JBU1AgY29yZSB2aWEgYW4gaW50ZXItcHJvY2Vzcw0K
PiBjb21tdW5pY2F0aW9uDQo+ID4gICAgICAgIChJUEMpIG1lY2hhbmlzbS4gIFRoZSBkZXRhaWxz
IG9mIHRoaXMgYXJlIHN5c3RlbS1kZXBlbmRlbnQuDQo+ID4NCj4gPiBJIGFsc28gZmluZCB0aGlz
IHRleHQgY29uZnVzaW5nIHJlbGF0aXZlIHRvIHRoZSBkaWFncmFtLiAgTW9yZQ0KPiBuYXR1cmFs
bHksIEkgd291bGQgYXNzdW1lIHRoYXQgdGhlIGJveGVzIHJlcHJlc2VudCBkaWZmZXJlbnQgcHJv
Y2Vzc2VzIGFuZA0KPiBoZW5jZSB5b3Ugd291bGQgaGF2ZSBJUEMgYmV0d2VlbiBBU0EgYW5kIHNh
eSB0aGUgIkdSQVNQIEFQSSBMaWJyYXJ5Ii4gIElmDQo+IEkgd2FzIHRvIGRyYXcgdGhpcywgdGhl
biBJIHdvdWxkIHByb2JhYmx5IGhhdmUgcHV0IHRoZSBHUkFTUCBBUEkgbGlicmFyeQ0KPiBjby1s
b2NhdGVkIHdpdGggdGhlIEFTQSBib3hlcy4NCj4gDQo+IFllcy4gSW4gZmFjdCBpbiBteSBkZW1v
IGltcGxlbWVudGF0aW9uLCB3aGVuIEkgYWRkZWQgYW4gSVBDIG1lY2hhbmlzbSwNCj4gdGhhdCBp
cyBlc3NlbnRpYWxseSB3aGF0IEkgZ290OiBzdHViIGZ1bmN0aW9ucyBmb3IgYWxsIHRoZSBBUEkg
Y2FsbHMgaW4NCj4gdGhlIGFwcCBjb250ZXh0LCB0aGVuIElQQyB0byB0aGUgY29yZSwgdGhlbiB0
aGUgInJlYWwiIGZ1bmN0aW9ucyBhbmQgdGhlDQo+IHZhcmlvdXMgZGFlbW9ucy90aHJlYWRzIGlu
IHRoZSBjb3JlIGNvbnRleHQuDQo+IA0KPiBJIGNhbid0IGluc3RhbnRseSBwcm92aWRlIG9sZC9u
ZXcgdGV4dCB0byByZXNwb25kIHRvIHRoaXMgYnV0IHdlIHdpbGwgdHJ5DQo+IHRvIGNsYXJpZnkg
YWxsIHRoaXMuDQpbUlddIA0KDQpPa2F5Lg0KDQoNCj4gDQo+ID4NCj4gPg0KPiA+ICAgICAxLiAg
SW50cm9kdWN0aW9uDQo+ID4NCj4gPiAgICAgICAgTm90ZSB0aGF0IGEgc2ltcGxlIGF1dG9ub21p
YyBub2RlIG1pZ2h0IGNvbnRhaW4gdmVyeSBmZXcgQVNBcyBpbg0KPiA+ICAgICAgICBhZGRpdGlv
biB0byB0aGUgYXV0b25vbWljIGluZnJhc3RydWN0dXJlIGNvbXBvbmVudHMgZGVzY3JpYmVkIGlu
DQo+ID4gICAgICAgIFtJLUQuaWV0Zi1hbmltYS1ib290c3RyYXBwaW5nLWtleWluZnJhXSBhbmQN
Cj4gPiAgICAgICAgW0ktRC5pZXRmLWFuaW1hLWF1dG9ub21pYy1jb250cm9sLXBsYW5lXS4gIFN1
Y2ggYSBub2RlIG1pZ2h0DQo+IGRpcmVjdGx5DQo+ID4gICAgICAgIGludGVncmF0ZSBHUkFTUCBp
biBpdHMgY29kZSBhbmQgdGhlcmVmb3JlIG5vdCByZXF1aXJlIHRoaXMgQVBJIHRvDQo+IGJlDQo+
ID4gICAgICAgIGluc3RhbGxlZC4gIEhvd2V2ZXIsIHRoZSBwcm9ncmFtbWVyIHdvdWxkIHRoZW4g
bmVlZCBhIGRlZXBlcg0KPiA+ICAgICAgICB1bmRlcnN0YW5kaW5nIG9mIHRoZSBHUkFTUCBwcm90
b2NvbCB0aGFuIGlzIG5lZWRlZCB0byB1c2UgdGhlDQo+IEFQSS4NCj4gPg0KPiA+IFBlcmhhcHMg
Y2hhbmdlICJpbnRlZ3JhdGUgR1JBU1AgaW4gaXRzIGNvZGUiIHRvIHNvbWV0aGluZyBsaWtlDQo+
ICJpbnRlZ3JhdGUgdGhlIGZ1bGwgR1JBU1AgaW1wbGVtZW50YXRpb24gaW4gaXRzIGNvZGUiPw0K
PiANCj4gWWVzIChidXQgYWN0dWFsbHkgc29tZSBjYXNlcyBtaWdodCBjaG9vc2UgdG8gaW1wbGVt
ZW50IGEgR1JBU1Agc3Vic2V0KS4NCltSV10gDQoNCk9yIHBvc3NpYmx5IHNvbWV0aGluZyBsaWtl
ICJpbnRlZ3JhdGUgYSBHUkFTUCBwcm90b2NvbCBzdGFjayBpbiBpdHMgY29kZSI/ICBUaGUgYWlt
IG9mIG15IGNvbW1lbnQgd2FzIHRvIHRyeSBhbmQgZGlmZmVyZW50aWF0ZSBiZXR3ZWVuIGp1c3Qg
bGlua2luZyBhZ2FpbnN0IGEgR1JBU1AgQVBJIGxpYnJhcnkgYW5kIGRpcmVjdGx5IGVtYmVkZGlu
ZyBwYXJ0IG9mIHRoZSBHUkFTUCBwcm90b2NvbCBzdGFjay4NCg0KDQoNCj4gDQo+ID4NCj4gPiAg
ICAgMi4yLjEuICBBbHRlcm5hdGl2ZSBBc3luY2hyb25vdXMgTWVjaGFuaXNtcw0KPiA+DQo+ID4g
ICAgICAgIFRodXMsIHNvbWUgQVNBcyBuZWVkIHRvIHN1cHBvcnQgYXN5bmNocm9ub3VzIG9wZXJh
dGlvbnMsIGFuZA0KPiA+ICAgICAgICB0aGVyZWZvcmUgdGhlIEdSQVNQIGNvcmUgbXVzdCBkbyBz
by4gIERlcGVuZGluZyBvbiBib3RoIHRoZQ0KPiBvcGVyYXRpbmcNCj4gPiAgICAgICAgc3lzdGVt
IGFuZCB0aGUgcHJvZ3JhbW1pbmcgbGFuZ3VhZ2UgaW4gdXNlLCB0aGVyZSBhcmUgdGhyZWUgbWFp
bg0KPiA+ICAgICAgICB0ZWNobmlxdWVzIGZvciBzdWNoIHBhcmFsbGVsIG9wZXJhdGlvbnM6IG11
bHRpLXRocmVhZGluZywgYW4NCj4gZXZlbnQNCj4gPiAgICAgICAgbG9vcCBzdHJ1Y3R1cmUgdXNp
bmcgcG9sbGluZywgYW5kIGFuIGV2ZW50IGxvb3Agc3RydWN0dXJlIHVzaW5nDQo+ID4gICAgICAg
IGNhbGxiYWNrIGZ1bmN0aW9ucy4NCj4gPg0KPiA+IFJhdGhlciB0aGFuICJ0aGVyZSBhcmUgdGhy
ZWUgbWFpbiB0ZWNobmlxdWVzIGZvciBzdWNoIHBhcmFsbGVsDQo+IG9wZXJhdGlvbnMiLCBwZXJo
YXBzIGp1c3QgInRocmVlIGNvbW1vbiB0ZWNobmlxdWVzIGFyZSBjb25zaWRlcmVkIGZvcg0KPiBw
YXJhbGxlbCBvcGVyYXRpb25zIi4NCj4gDQo+IE9LDQo+IA0KPiA+IFJlYXNvbmluZywgdGhlcmUg
YXJlIG90aGVyIGFwcHJvYWNoZXMgZm9yIGVmZmVjdGl2ZWx5IGhhbmRsaW5nDQo+IGNvbmN1cnJl
bnQgb3BlcmF0aW9ucywgZS5nLiwgYWN0b3JzLCBmdXR1cmVzLCBjb29wZXJhdGl2ZSB0aHJlYWRz
IGJhY2tlZA0KPiBieSBhIE9TIHRocmVhZCBwb29sIC4uLg0KPiANCj4gW09yIG9mIGNvdXJzZSBk
aWZmZXJlbnQgbmFtZXMgZm9yIHRoZSBzYW1lIHRoaW5nLiBJbWFnaW5lIHRyeWluZyB0bw0KPiBk
ZXNjcmliZSBhbGwgdGhpcyBpbiB0ZXJtcyBvZiBBREEgcmVuZGV6dm91cy5dDQo+IA0KPiA+DQo+
ID4gUG9zc2libHksIGNoYW5nZSAic2ltcGxlIGZ1bmN0aW9uIGNhbGxzIiBpbiB0aGUgbXVsdGkt
dGhyZWFkaW5nDQo+IHBhcmFncmFwaCB0byBiZSAic2ltcGxlIHN5bmNocm9ub3VzIGZ1bmN0aW9u
IGNhbGxzIiB0byBlbXBoYXNpemUgdGhlDQo+IHN5bmNocm9ub3VzIG5hdHVyZS4NCj4gDQo+IE9L
DQo+IA0KPiA+DQo+ID4NCj4gPiAgICAgMi4yLjIuICBNdWx0aXBsZSBOZWdvdGlhdGlvbiBTY2Vu
YXJpbw0KPiA+DQo+ID4gICAgICAgIEluIHRoZSBjYWxsYmFjayBtb2RlbCwgZm9yIHRoZSBzY2Vu
YXJpbyBqdXN0IGRlc2NyaWJlZCwgdGhlIEFTQXMNCj4gIkEiDQo+ID4gICAgICAgIGFuZCAiQiIg
d2lsbCBlYWNoIHByb3ZpZGUgdHdvIGluc3RhbmNlcyBvZg0KPiBuZWdvdGlhdGVfc3RlcF9yZWNl
aXZlZCgpLA0KPiA+ICAgICAgICBvbmUgZm9yIGVhY2ggc2Vzc2lvbi4gIEZvciB0aGlzIHJlYXNv
biwgZWFjaCBBU0EgbXVzdCBiZSBhYmxlIHRvDQo+ID4gICAgICAgIGRpc3Rpbmd1aXNoIHRoZSB0
d28gc2Vzc2lvbnMsIGFuZCB0aGUgcGVlcidzIElQIGFkZHJlc3MgaXMgbm90DQo+ID4gICAgICAg
IHN1ZmZpY2llbnQgZm9yIHRoaXMuICBJdCBpcyBhbHNvIG5vdCBzYWZlIHRvIHJlbHkgb24gdHJh
bnNwb3J0DQo+IHBvcnQNCj4gPiAgICAgICAgbnVtYmVycyBmb3IgdGhpcywgc2luY2UgZnV0dXJl
IHZhcmlhbnRzIG9mIEdSQVNQIG1pZ2h0IHVzZSBzaGFyZWQNCj4gPiAgICAgICAgcG9ydHMgcmF0
aGVyIHRoYW4gYSBzZXBhcmF0ZSBwb3J0IHBlciBzZXNzaW9uLiAgVGhpcyBpcyB3aHkgdGhlDQo+
IEdSQVNQDQo+ID4gICAgICAgIGRlc2lnbiBpbmNsdWRlcyBhIHNlc3Npb24gaWRlbnRpZmllci4g
IFRodXMsIHdoZW4gbmVjZXNzYXJ5LCBhDQo+ID4gICAgICAgICdzZXNzaW9uX25vbmNlJyBwYXJh
bWV0ZXIgaXMgdXNlZCBpbiB0aGUgQVBJIHRvIGRpc3Rpbmd1aXNoDQo+ID4gICAgICAgIHNpbXVs
dGFuZW91cyBHUkFTUCBzZXNzaW9ucyBmcm9tIGVhY2ggb3RoZXIsIHNvIHRoYXQgYW55IG51bWJl
cg0KPiBvZg0KPiA+ICAgICAgICBzZXNzaW9ucyBtYXkgcHJvY2VlZCBhc3luY2hyb25vdXNseSBp
biBwYXJhbGxlbC4NCj4gPg0KPiA+IEl0IHdhc24ndCBvYnZpb3VzIHRvIG1lIHdoeSBib3RoIEFT
QXMgIkEiIGFuZCAiQiIgYm90aCBwcm92aWRlDQo+IGNhbGxiYWNrcywgSSBwcmVzdW1lIHRoYXQg
dGhpcyBpcyBiZWNhdXNlIHRoZXJlIGFyZSBtdWx0aXBsZSBhc3luY2hyb25vdXMNCj4gc3RlcHMg
aW52b2x2ZWQuICBJZiBzbywgd291bGQgaXQgYmUgaGVscGZ1bCB0byBjbGFyaWZ5IHRoaXMgcG9p
bnQ/DQo+IA0KPiBZZXMsIG9uZSBjb3VsZCBidWlsZCB2ZXJ5IGNvbXBsaWNhdGVkIGludGVybG9j
a2luZyBuZWdvdGlhdGlvbnMuIChUaGF0IGlzDQo+IGEgd2hvbGUgY2FuIG9mIHdvcm1zLCBleHBs
b3JlZCBpbiBkcmFmdC1jaWF2YWdsaWEtYW5pbWEtY29vcmRpbmF0aW9uLCBidXQNCj4gZm9yIHBy
ZXNlbnQgcHVycG9zZXMgd2UganVzdCBuZWVkIHRvIGVuc3VyZSB0aGF0IEFTQXMgY2FuIGhhbmRs
ZSBhbnkNCj4gZGVncmVlIG9mIGFzeW5jaHJvbm9zaXR5LCBpZiB0aGF0J3MgYSB3b3JkLikNCj4g
DQo+ID4gQWxzbyBpbiB0aGlzIHBhcmFncmFwaCBzdWdnZXN0ICJIZW5jZSwgIiByYXRoZXIgdGhh
biAiVGhpcyBpcyB3aHQiDQo+IA0KPiBPSw0KPiANCj4gPg0KPiA+DQo+ID4gICAgIDIuMi4zLiAg
T3ZlcmxhcHBpbmcgU2Vzc2lvbnMgYW5kIE9wZXJhdGlvbnMNCj4gPg0KPiA+ICAgICAgICBJbiBj
YWxscyB3aGVyZSBpdCBpcyB1c2VkLCB0aGUgJ3Nlc3Npb25fbm9uY2UnIGlzIGFuIG9wYXF1ZSBy
ZWFkLw0KPiA+ICAgICAgICB3cml0ZSBwYXJhbWV0ZXIuICBPbiB0aGUgZmlyc3QgY2FsbCwgaXQg
aXMgc2V0IHRvIGEgbnVsbCB2YWx1ZSwNCj4gYW5kDQo+ID4gICAgICAgIHRoZSBBUEkgcmV0dXJu
cyBhIG5vbi1udWxsICdzZXNzaW9uX25vbmNlJyB2YWx1ZSBiYXNlZCBvbiB0aGUNCj4gR1JBU1AN
Cj4gPiAgICAgICAgc2Vzc2lvbiBpZGVudGlmaWVyLiAgVGhpcyB2YWx1ZSBtdXN0IGJlIHVzZWQg
aW4gYWxsIHN1YnNlcXVlbnQNCj4gY2FsbHMNCj4gPiAgICAgICAgZm9yIHRoZSBzYW1lIHNlc3Np
b24sIGFuZCB3aWxsIGJlIHByb3ZpZGVkIGFzIGEgcGFyYW1ldGVyIGluIHRoZQ0KPiA+ICAgICAg
ICBjYWxsYmFjayBmdW5jdGlvbnMuICBCeSB0aGlzIG1lY2hhbmlzbSwgbXVsdGlwbGUgb3Zlcmxh
cHBpbmcNCj4gc2Vzc2lvbnMNCj4gPiAgICAgICAgY2FuIGJlIGRpc3Rpbmd1aXNoZWQsIGJvdGgg
aW4gdGhlIEFTQSBhbmQgaW4gdGhlIEdSQVNQIGNvcmUuICBUaGUNCj4gPiAgICAgICAgdmFsdWUg
b2YgdGhlICdzZXNzaW9uX25vbmNlIiBpcyBvcGFxdWUgdG8gdGhlIEFTQS4NCj4gPg0KPiA+IFF1
ZXJ5IHRoZSB1c2Ugb2YgYSBudWxsIHZhbHVlLCBhbmQgd2hldGhlciB0aGF0IGlzIHRvbyByZXN0
cmljdGl2ZS4NCj4gDQo+IEl0cyB2YWx1ZSBvbiB0aGUgZmlyc3QgY2FsbCBpcyBvZiBubyBpbXBv
cnRhbmNlLCBzbyB3ZSBzaG91bGQganVzdCBjYWxsIGl0DQo+IGEgcGxhY2Vob2xkZXIuDQpbUldd
IA0KDQpTb3JyeSwgSSBoYWQgaW50ZW5kZWQgdG8gZXhwYW5kIG15IG9yaWdpbmFsIGNvbW1lbnQu
ICBUbyBtZSB0aGlzIHJlYWRzIHF1aXRlIGxpa2UgYSBDIEFQSSwgd2hlcmUgdGhlIHNlc3Npb25f
bm9uY2UgaXMgYSBJTk9VVCBwYXJhbWV0ZXIsIGJ1dCBvdGhlciBsYW5ndWFnZXMgdGhhdCBzYXkg
YWxsb3cgYSB0dXBsZSB0byBiZSByZXR1cm5lZCB3b3VsZCBwcm9iYWJseSBqdXN0IHJldHVybiBh
IHR1cGxlIGNvbnRhaW5pbmcgd2hhdGV2ZXIgb3RoZXIgcmV0dXJuIHBhcmFtZXRlcnMgYWxvbmcg
d2l0aCBhIHNlc3Npb25fbm9uY2UuDQoNCkhvd2V2ZXIsIEknbSBhbHNvIG5vdCBxdWl0ZSBzdXJl
IHdoZXRoZXIgdGhpcyB0ZXh0IGlzIGVudGlyZWx5IGNvbnNpc3RlbnQgd2l0aCBob3cgdGhlIHNl
c3Npb25fbm9uY2UgaXMgYWN0dWFsbHkgdXNlZCBpbiB0aGUgQVBJcy4gIEUuZy4gcmVxdWVzdF9u
ZWdvdGlhdGUoKSBvcHRpb25zIHJldHVybnMgYSBzZXNzaW9uX25vbmNlLiAgSXQgZG9lc24ndCBh
cHBlYXIgdG8gYmUgYW4gImluIiBwYXJhbWV0ZXIgYXQgYWxsLg0KDQpQZXJoYXBzIHRoZSB0ZXh0
IHNob3VsZCBqdXN0IHNheSBzb21ldGhpbmcgbGlrZSB0aGUgc2Vzc2lvbl9ub25jZSBpcyBwcm92
aWRlZCB3aGVuIHRoZSBzZXNzaW9uIGlzIGVzdGFibGlzaGVkIGFuZCB1c2VkIGluIGFsbCBzdWJz
ZXF1ZW50IGNhbGxzLCBhbmQgZGV0YWlsZWQgc2VtYW50aWNzIHRvIHRoZSBzcGVjaWZpYyBBUElz
Pw0KDQoNCg0KDQoNCj4gDQo+ID4NCj4gPg0KPiA+ICAgICAyLjMuICBBUEkgZGVmaW5pdGlvbg0K
PiA+DQo+ID4gUG9zc2libHkgdGhpcyBBUEkgd291bGQgYmVuZWZpdCBmcm9tIGEgc2hvcnQgc2Vj
dGlvbiAob3IgZXZlbiBwc2V1ZG8NCj4gY29kZSkgZXhwbGFpbmluZyB0aGUgZmxvdyBvciBmbG93
cyBvZiBob3cgdGhlIEFQSXMgYXJlIGV4cGVjdGVkIHRvIHdvcmsNCj4gdG9nZXRoZXIuICBUaGlz
IGNvdWxkIGFsc28gYmUgaW4gYW4gYXBwZW5kaXguICBQZXJoYXBzIHRoZSBHUkFTUA0KPiBzcGVj
aWZpY2F0aW9uIG1ha2VzIHRoaXMgb2J2aW91cywgaW4gd2hpY2ggY2FzZSByZWZlcmVuY2VzIGJh
Y2sgdG8gdGhlDQo+IEdSQVNQIHNwZWMgd291bGQgYmUgc3VmZmljaWVudC4NCj4gDQo+IFdlIGhh
dmUgc29tZSBleGFtcGxlIGxvZ2ljIGZsb3dzIGluIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaWQv
ZHJhZnQtDQo+IGNhcnBlbnRlci1hbmltYS1hc2EtZ3VpZGVsaW5lcy0wOS5odG1sI3NlY3Rpb24t
YXBwZW5kaXguYg0KPiANCj4gV291bGQgYSByZWZlcmVuY2UgdG8gdGhhdCBoZWxwPyBUaGUgYXV0
aG9ycyB3b3VsZCBsaWtlIHRoYXQgZHJhZnQgdG8gYmUNCj4gYWRvcHRlZCBieSB0aGUgV0cuIFdl
IGNvdWxkIG9mIGNvdXJzZSBtb3ZlIHRoZSBleGFtcGxlcyBpbnRvIHRoZSBBUEkNCj4gZHJhZnQs
IGlmIHBlb3BsZSBwcmVmZXIgdGhhdC4NCltSV10gDQoNClllcywgdGhpcyBpcyB3aGF0IEkgd2Fz
IHRoaW5raW5nIG9mLg0KDQpJIGRvbuKAmXQgbWluZCB3aGV0aGVyIGl0IGlzIGluY2x1ZGVkIGlu
IGFuIGFwcGVuZGl4IGluIHRoaXMgZHJhZnQgb3IgYXMgYSByZWZlcmVuY2UuDQoNCg0KDQo+IA0K
PiA+DQo+ID4NCj4gPiAgICAgMi4zLjEuMy4gIE9iamVjdGl2ZQ0KPiA+DQo+ID4gICAgICAgICog
IG5hbWUgKFVURi04IHN0cmluZykgLSB0aGUgb2JqZWN0aXZlJ3MgbmFtZQ0KPiA+DQo+ID4gU2hv
dWxkIHRoZXJlIGJlIGEgbGltaXQgb24gdGhlIGxlbmd0aCBvZiB0aGUgbmFtZT8gIFRoaXMgcXVl
c3Rpb24NCj4gZXF1aXZhbGVudGx5IGFwcGxpZXMgdG8gdGhlIG90aGVyIHN0cmluZ3MvdmFyaWFi
bGUgc2l6ZWQgdHlwZXMuDQo+IA0KPiBJIHRoaW5rIHRoYXQncyBpbXBsZW1lbnRhdGlvbiBkZXBl
bmRlbnQuIEJlY2F1c2UgR1JBU1AgaXMgYSBDQk9SIHByb3RvY29sLA0KPiB0aGVyZSBpcyBubyBw
YXJ0aWN1bGFyIGxpbWl0IG9uIHN0cmluZyBsZW5ndGguIFRoZXJlIGlzIGEgbGltaXQgb24gdGhl
DQo+IHRvdGFsIHNpemUgb2YgYSBHUkFTUCBtZXNzYWdlIChhbHRob3VnaCBJIHN1c3BlY3Qgd2Ug
bWlnaHQgZGVjaWRlIHRvIHJhaXNlDQo+IG9yIHJlbW92ZSB0aGF0IGxpbWl0IG9uZSBkYXkpLg0K
W1JXXSANCg0KVGhhdCBzb3VuZHMgcmVhc29uYWJsZSwgYW5kIEkgZG9uJ3QgZmVlbCB0b28gc3Ry
b25nbHkgb24gdGhpcyBpc3N1ZS4NCg0KSSB0aGluayB0aGF0IG15IGdlbmVyYWwgY29uY2VybiB3
aXRoIGFyYml0cmFyeSBsZW5ndGggc3RyaW5ncyBpbiBBUElzLCB0aGF0IGFyZSBpbXBsZW1lbnRh
dGlvbiBkZXBlbmRlbnQsIGlzIHRoYXQgY2xpZW50cyBtYXkgbm90IGtub3cgd2hhdCAoaWYgYW55
KSBtYXggbGVuZ3RoIGlzIHN1cHBvcnRlZCBieSBhbiBpbXBsZW1lbnRhdGlvbiwgd2hpY2ggcG90
ZW50aWFsbHkgY291bGQgbWFrZSBpbnRlcm9wIGhhcmRlci4gIEluIHRoZSBZQU5HIHdvcmxkLCB0
aGlzIGNhbiBiZSBtaXRpZ2F0ZWQgdmlhIGRldmlhdGlvbnMgdG8gaW5kaWNhdGUgaW1wbGVtZW50
YXRpb24gc3BlY2lmaWMgcmVzdHJpY3Rpb25zLg0KDQpQZXJoYXBzIHdoYXQgSSBhbSB0aGlua2lu
ZyBvZiBpcyBkZWZpbmluZyBhIG1pbmltdW0gc3VwcG9ydGVkIGxlbmd0aC4gIEUuZy4sIHRoZSBs
ZW5ndGggaXMgaW1wbGVtZW50YXRpb24gc3BlY2lmaWMsIGJ1dCBhbGwgaW1wbGVtZW50YXRpb25z
IG11c3Qgc3VwcG9ydCwgc2F5LCBhdCBsZWFzdCA2NCBjaGFyYWN0ZXJzLiAgSGVuY2UsIGEgY2xp
ZW50IHdvdWxkIGtub3cgdGhhdCBpZiB0aGUgbmFtZSB3YXMgYmVsb3cgdGhpcyBsZW5ndGggdGhl
biBpdCB3b3VsZCB3b3JrIHdpdGggYWxsIGltcGxlbWVudGF0aW9ucywgYnV0IGltcGxlbWVudGF0
aW9ucyBtYXkgc3VwcG9ydCBhIG11Y2ggaGlnaGVyIGxpbWl0IGlmIHRoZXkgd2lzaC4NCg0KDQo+
IA0KPiA+ICAgICAgICAqICB2YWx1ZSAtIGEgc3BlY2lmaWMgZGF0YSBzdHJ1Y3R1cmUgZXhwcmVz
c2luZyB0aGUgdmFsdWUgb2YgdGhlDQo+ID4gICAgICAgICAgIG9iamVjdGl2ZS4gIFRoZSBmb3Jt
YXQgaXMgbGFuZ3VhZ2UgZGVwZW5kZW50LCB3aXRoIHRoZQ0KPiBjb25zdHJhaW50DQo+ID4gICAg
ICAgICAgIHRoYXQgaXQgY2FuIGJlIHZhbGlkbHkgcmVwcmVzZW50ZWQgaW4gQ0JPUiAoZGVmYXVs
dCBpbnRlZ2VyID0NCj4gMCkuDQo+ID4NCj4gPiBJIGRpZG4ndCB1bmRlcnN0YW5kIHRoZSAiZGVm
YXVsdCBpbnRlZ2VyID0gMCIgcGFydC4gIElmIHRoaXMgaXMgYSBieXRlDQo+IHN0cmluZyB0aGVu
IEkgd291bGQgdGhvdWdodCB0aGF0IHRoZSBkZWZhdWx0IG1pZ2h0IGJlIGFuIGVtcHR5IGxlbmd0
aA0KPiBieXRlc3RyaW5nLCBvciBwZXJoYXBzIGEgQ0JPUiBOdWxsLg0KPiANCj4gSSdtIG5vdCBl
dmVuIHN1cmUgbm93IHdoeSB3ZSBuZWVkIHRvIHNwZWNpZnkgYSBkZWZhdWx0IGluIGEgZ2VuZXJp
YyBBUEkuDQo+IA0KPiA+ICAgICAgICAgICBBbiBlc3NlbnRpYWwgcmVxdWlyZW1lbnQgZm9yIGFs
bCBsYW5ndWFnZSBtYXBwaW5ncyBhbmQgYWxsDQo+ID4gICAgICAgICAgIGltcGxlbWVudGF0aW9u
cyBpcyB0aGF0LCByZWdhcmRsZXNzIG9mIHdoYXQgb3RoZXIgb3B0aW9ucw0KPiBleGlzdA0KPiA+
ICAgICAgICAgICBmb3IgYSBsYW5ndWFnZS1zcGVjaWZpYyByZXByZXNlbmF0aW9uIG9mIHRoZSB2
YWx1ZSwgdGhlcmUgaXMNCj4gPiAgICAgICAgICAgYWx3YXlzIGFuIG9wdGlvbiB0byB1c2UgYSBD
Qk9SIGJ5dGUgc3RyaW5nIGFzIHRoZSB2YWx1ZS4gIFRoZQ0KPiBBUEkNCj4gPiAgICAgICAgICAg
d2lsbCB0aGVuIHdyYXAgdGhpcyBieXRlIHN0cmluZyBpbiBDQk9SIFRhZyAyNCBmb3INCj4gdHJh
bnNtaXNzaW9uDQo+ID4gICAgICAgICAgIHZpYSBHUkFTUCwgYW5kIHVud3JhcCBpdCBhZnRlciBy
ZWNlcHRpb24uDQo+ID4NCj4gPiBJdCB3YXMgdW5jbGVhciB3aGV0aGVyIHlvdSBqdXN0IG1lYW50
IGFuIG9wYXF1ZSBDQk9SIGJ5dGUgc3RyaW5nIGhlcmUNCj4gKENCT1IgbWFqb3IgdHlwZSAyKSwg
b3IgYSBDQk9SIGJ5dGUgc3RyaW5nIHRoYXQgaXRzZWxmIGNvbnRhaW5zIENCT1INCj4gZW5jb2Rl
ZCBkYXRhIChpLmUuIENCT1IgVGFnIDI0KS4gIElzIHRoZXJlIGFueSBsaW1pdCBvbiB0aGUgbGVu
Z3RoIG9mIHRoZQ0KPiBDQk9SIGJ5dGUgc3RyaW5nIHRoYXQgaXMgYWxsb3dlZD8NCj4gDQo+IEl0
J3Mgbm90IGludGVuZGVkIHRvIGJlIHJlc3RyaWN0ZWQgdG8gbWFqb3IgdHlwZSAyOyBJJ2xsIGhh
dmUgdG8gY2hlY2sgdGhlDQo+IENCT1IgUkZDIHRvIGZpbmQgdGhlIGNvcnJlY3QgcGhyYXNlIHRv
IHVzZS4NCltSV10gDQoNClBlcmhhcHMgc29tZXRoaW5nIGFsb25nIHRoZSBsaW5lcyBvZiAiQW4g
ZW5jb2RlZCBDQk9SIGRhdGEgaXRlbSwgd3JhcHBlZCBpbiBDQk9SIFRhZyAyNCwgYXMgcGVyIHNl
Y3Rpb24gMy40LjUuMSBvZiA3MDQ5YmlzIg0KDQoNCg0KPiANCj4gQXMgYWJvdmUsIHRoZSBvbmx5
IHNpemUgbGltaXQgd2UgaGF2ZSBpcyB0aGUgdG90YWwgR1JBU1AgbWVzc2FnZSBzaXplLg0KPiAN
Cj4gPg0KPiA+DQo+ID4gICAgIDIuMy4yLiAgUmVnaXN0cmF0aW9uDQo+ID4NCj4gPiBTb21lIEFQ
SXMgbGlzdCAiQXN5bmNocm9ub3VzIE1lY2hhbmlzbXM6IiBhbmQgb3RoZXJzIGRvbid0LiAgSXQg
bWlnaHQgYmUNCj4gaGVscGZ1bCB0byBjbGFyaWZ5IHRoYXQgdGhvc2UgQVBJcyB0aGF0IGRvbid0
IGxpc3QgYXN5bmNocm9ub3VzIG1lY2hhbmlzbXMNCj4gYXJlIGltcGxpY2l0bHkgc3luY2hyb25v
dXMgaW4gdGhlaXIgYmVoYXZpb3VyLg0KPiANCj4gT0sNCj4gDQo+ID4NCj4gPg0KPiA+ICAgICAg
ICAgKiAgZGVyZWdpc3Rlcl9hc2EoKQ0KPiA+DQo+ID4gICAgICAgICAgIC0gIE5vdGUgLSB0aGUg
QVNBIG5hbWUgaXMgc3RyaWN0bHkgc3BlYWtpbmcgcmVkdW5kYW50IGluIHRoaXMNCj4gPiAgICAg
ICAgICAgICAgY2FsbCwgYnV0IGlzIHByZXNlbnQgZm9yIGNsYXJpdHkuDQo+ID4NCj4gPiBQcmVz
dW1hYmx5IGl0IGFsc28gbWFrZXMgaXQgc2lnbmlmaWNhbnRseSBoYXJkZXIgZm9yIGEgcm9ndWUg
Y2xpZW50IHRvDQo+IHRyeSBhbmQgZGVyZWdpc3RlciBhbGwgQVNBcyBieSBsb29waW5nIHRocm91
Z2ggYWxsIGFzYV9ub25jZXMuDQo+IA0KPiBUcnVlLCBidXQgdGhlcmUgaXMgc28gbXVjaCBlbnRy
b3B5IGluIHRoZSBub25jZSB0aGF0IHRoaXMgd291bGQgYmUgYQ0KPiBjaGFsbGVuZ2UgYW55d2F5
Lg0KW1JXXSANCg0KT2theS4gIFdoZW4gSSB3cm90ZSB0aGlzLCBJIGFsc28gcmVhbGl6ZWQgdGhh
dCB0aGUgb3RoZXIgQVBJcyBhcmUganVzdCByZWx5aW5nIG9uIHRoZSBub25jZSBhbnl3YXkuDQoN
Cg0KPiANCj4gPg0KPiA+DQo+ID4gICAgIDIuMy40LiAgTmVnb3RpYXRpb24NCj4gPg0KPiA+ICAg
ICAgICAgICAgICAyLiAgVGhlICdzZXNzaW9uX25vbmNlJyBwYXJhbWV0ZXIgaXMgbm90IG51bGwu
ICBJbiB0aGlzDQo+IGNhc2UNCj4gPiAgICAgICAgICAgICAgICAgIG5lZ290aWF0aW9uIG11c3Qg
Y29udGludWUuICBUaGUgcmV0dXJuZWQNCj4gPiAgICAgICAgICAgICAgICAgICdwcm9mZmVyZWRf
b2JqZWN0aXZlJyBjb250YWlucyB0aGUgZmlyc3QgdmFsdWUNCj4gcHJvZmZlcmVkIGJ5DQo+ID4g
ICAgICAgICAgICAgICAgICB0aGUgbmVnb3RpYXRpb24gcGVlci4gIE5vdGUgdGhhdCB0aGlzIGlu
c3RhbmNlIG9mIHRoZQ0KPiA+ICAgICAgICAgICAgICAgICAgb2JqZWN0aXZlIG11c3QgYmUgdXNl
ZCBpbiB0aGUgc3Vic2VxdWVudCBuZWdvdGlhdGlvbg0KPiBjYWxsDQo+ID4gICAgICAgICAgICAg
ICAgICBiZWNhdXNlIGl0IGFsc28gY29udGFpbnMgdGhlIGN1cnJlbnQgbG9vcCBjb3VudC4gIFRo
ZQ0KPiA+ICAgICAgICAgICAgICAgICAgJ3Nlc3Npb25fbm9uY2UnIG11c3QgYmUgcHJlc2VudGVk
IGluIGFsbCBzdWJzZXF1ZW50DQo+ID4gICAgICAgICAgICAgICAgICBuZWdvdGlhdGlvbiBzdGVw
cy4NCj4gPg0KPiA+IFByZXN1bWFibHkgdGhlIGxvb3AgY291bnQgaW4gdGhlIHByb2ZmZXJlZF9v
YmplY3RpdmUgbXVzdCBiZSBvbmUgZ3JlYXRlcg0KPiB0aGFuIHRoZSBsb29wIGNvdW50IGluIHRo
ZSBvYmplY3RpdmUgc3RydWN0dXJlPyAgV291bGQgaXQgYmUgaGVscGZ1bCB0bw0KPiBtZW50aW9u
IHRoaXM/DQo+IA0KPiBSaWdodC4uLiBJJ20gZ29pbmcgdG8gbG9vayBpbiBteSBHUkFTUCBjb2Rl
IGJlZm9yZSBJIHRyeSB0byByZXBocmFzZSB0aGF0Lg0KPiBJIHJlY2FsbCB0aGF0IGl0IHdhcyBh
IGJpdCB0cmlja3kgdG8gZ2V0IGl0IHJpZ2h0Lg0KW1JXXSANCg0KT2theS4NCg0KPiANCj4gPg0K
PiA+IEkgYWxzbyB3YXNuJ3Qgc3VyZSB3aGV0aGVyIGl0IG11c3QgYmUgInRoaXMgaW5zdGFuY2Ug
b2YgdGhlIG9iamVjdGl2ZQ0KPiBtdXN0IGJlIHVzZWQiLCBvciBqdXN0IHRoYXQgdGhlIGxvb3Ag
Y291bnRlciBtdXN0IGJlIGNvcGllZCBhY3Jvc3MuICBFLmcuLA0KPiBmdW5jdGlvbmFsIGxhbmd1
YWdlcyB3b3VsZCBlbmNvdXJhZ2UgdGhlc2Ugc3RydWN0dXJlcyB0byBiZSBpbW11dGFibGUuDQo+
IA0KPiBBbmQgYmVjYXVzZSBvZiBQeXRob24ncyB2YWd1ZW5lc3MgYWJvdXQgd2hldGhlciBpdCdz
IGNhbGwtYnktcmVmZXJlbmNlIG9yDQo+IGNhbGwtYnktdmFsdWUsIHRoZXJlIGFyZSBjYXNlcyB3
aGVyZSBJJ3ZlIGhhZCB0byBleHBsaWNpdGx5IGNsb25lIGEgY29weQ0KPiBvZiBhbiBvYmplY3Rp
dmUgdG8gYmUgc3VyZSB0aGF0IEkgaGF2ZSB0aGUgcmlnaHQgdG8gZGVjcmVtZW50IHRoZSBsb29w
DQo+IGNvdW50ZXIuIFNvIHllcywgaXQncyAidGhpcyBpbnN0YW5jZSBvciBhIGNsb25lIG9mIHRo
aXMgaW5zdGFuY2UiLiBXaWxsDQo+IHJlcGhyYXNlLg0KW1JXXSANCg0KT2theS4NCg0KPiANCj4g
Pg0KPiA+DQo+ID4gICAgICAgICAgLSAgQXN5bmNocm9ub3VzIE1lY2hhbmlzbXM6DQo+ID4NCj4g
PiAgICAgICAgICAgICAgbyAgRXZlbnQgbG9vcCBpbXBsZW1lbnRhdGlvbjogVGhlICdzZXNzaW9u
X25vbmNlJyBwYXJhbWV0ZXINCj4gaXMNCj4gPiAgICAgICAgICAgICAgICAgdXNlZCBpbiByZWFk
L3dyaXRlIG1vZGUuDQo+ID4NCj4gPiBJdCBpcyB1bmNsZWFyIHRvIG1lLCBleGFjdGx5IHdoYXQg
eW91IG1lYW4gYnkgdGhpcywgcGFydGljdWxhcmx5IGJlY2F1c2UNCj4gdGhpcyBpcyBhIHJldHVy
biBwYXJhbWV0ZXIuICBQZXJoYXBzIHRoaXMgY291bGQgYmUgZnVydGhlciBleHBsYWluZWQgaW4N
Cj4gdGhlIHRleHQsIG9yIHJlZmVyIGJhY2sgdGhlIHByZXZpb3VzIHRleHQuDQo+IA0KPiBZZXMu
IEkgdGhpbmsgd2Ugd2VyZSB0cnlpbmcgdG8gZXhwcmVzcyBzb21ldGhpbmcgdGhhdCB3aWxsIGxv
b2sgYSBiaXQNCj4gZGlmZmVyZW50IGluIEMgY29tcGFyZWQgdG8gaGlnaC1sZXZlbCBsYW5ndWFn
ZXMuDQpbUlddIA0KDQpQb3NzaWJseSBldmVuIHJlZmVycmluZyBpdCBhbiBpbi9vdXQgcGFyYW1l
dGVyIHdvdWxkIGJlIGNsZWFyZXIuDQoNCj4gDQo+ID4NCj4gPg0KPiA+ICAgICAyLjMuNC4gIE5l
Z290aWF0aW9uDQo+ID4NCj4gPiAgICAgICAgICogIGxpc3Rlbl9uZWdvdGlhdGUoKQ0KPiA+DQo+
ID4gSSB3YXMgc3VycHJpc2VkIHRoYXQgdGhlIGxpc3Rlbl9uZWdvdGF0ZSBkaWRuJ3QgaW5jbHVk
ZSBhbnkgdGltZW91dCwNCj4gZS5nLiB0byBhbGxvdyBpdCB0byBiZSB1c2VkIGluIHBvbGxpbmcg
ZmFzaGlvbi4gIFNhbWUgY29tbWVudCBhcHBsaWVzIHRvDQo+IGxpc3Rlbl9zeW5jaHJvbml6ZSgp
Lg0KPiANCj4gV2VsbCwgaW4gYSBwb2xsaW5nIHNvbHV0aW9uIHdvbid0IHRoZSBsaXN0ZW4gc3Rh
dGUganVzdCBnbyBpbnRvIHRoZSBldmVudA0KPiBsb29wPyBCdXQgSSdtIGEgYml0IG91dCBvZiBt
eSBkZXB0aCB0aGVyZS4NCltSV10gDQoNCk9rYXksIHBvc3NpYmx5IEkgd2FzIHRocm93biBieSB0
aGUgIlVubGVzcyB0aGVyZSBpcyBhbiB1bmV4cGVjdGVkIGZhaWx1cmUsDQp0aGlzIGNhbGwgb25s
eSByZXR1cm5zIGFmdGVyIGFuIGluY29taW5nIG5lZ290aWF0aW9uIHJlcXVlc3QuIiAgSS5lLiwg
aXQgc2VlbXMgdG8gc3VnZ2VzdCB0aGF0IGl0IGFsd2F5cyBibG9ja3MuICBCdXQgcGVyaGFwcyB0
aGUgZGVzY3JpcHRpb24gbmVlZHMgdG8gYmUgcmVmaW5lZCBkZXBlbmRpbmcgb24gd2hldGhlciBp
dCBpcyBhIHN5bmNocm9ub3VzIG9yIGFzeW5jaHJvbm91cyBBUEkuDQoNCkluIGEgcHVyZSBldmVu
dCBsb29wIHNjZW5hcmlvLCBJIHdvdWxkIGV4cGVjdCBhIHJlZ2lzdHJhdGlvbiBBUEkgdG8gcmVn
aXN0ZXIgYW4gZXZlbnQgKGUuZy4gYW4gb2JqZWN0aXZlKSB0aGF0IEkgYW0gaW50ZXJlc3RlZCBp
biwgYW5kIG9wdGlvbmFsbHkgYSBjYWxsYmFjayBmdW5jdGlvbiB0byBiZSBpbnZva2VkIHdoZW4g
dGhhdCBldmVudCBpcyByZWNlaXZlZC4gIE5vcm1hbGx5LCB0aGUgdGhyZWFkIHdvdWxkIHRoZW4g
aGF2ZSBhIGxvb3Agd2FpdGluZyAoYmxvY2tpbmcpIGZvciBhbiBldmVudCB0byBiZSByZWNlaXZl
ZCB0aGF0IG1pZ2h0IGVpdGhlciBiZSByZXR1cm5lZCBiYWNrIGluIHRoZSBsb29wIChvciBwbGF1
c2libHkgZGlzcGF0Y2hlZCBkaXJlY3RseSkuICBJbiB0aGUgY29kZSB0aGF0IEkgYW0gZmFtaWxp
YXIgd2l0aCB0aGVyZSBhcmUgc2VwYXJhdGUgY2FsbHMgdG8gd2FpdCAoYmxvY2spIGZvciBhIG5l
dyBldmVudCwgYW5kIHRoZW4gYSBzZXBhcmF0ZSBmdW5jdGlvbiBpcyBpbnZva2VkIHRvIGRpc3Bh
dGNoIHRoZSBldmVudCB0byB0aGUgcmVnaXN0ZXJlZCBjYWxsIGJhY2sgaGFuZGxlci4gIEluIHRo
aXMgc2NlbmFyaW8gaXMgaXQgc29tZXRpbWVzIHVzZWZ1bCBmb3IgdGhlIGV2ZW50IGJsb2NrKCkg
Y2FsbCB0byBoYXZlIGEgdGltZW91dCwgYWxsb3dpbmcgdGhlIHRocmVhZCB0byBkbyBvdGhlciBw
ZXJpb2RpYyBob3VzZWtlZXBpbmcgd29yayBhbmQgdGhlbiBtYWtlIGEgbmV3IGV2ZW50X2Jsb2Nr
KCkgY2FsbC4NCg0KSSdtIG5vdCBwYXJ0aWN1bGFyIGZhbWlsaWFyIHdpdGggdGhlIExpbnV4IGVw
b2xsLCBidXQgdGhpcyBnaXZlcyBhbiBleGFtcGxlIG9mIGEgdGltZW91dCB3aGlsc3Qgd2FpdGlu
ZyBmb3IgYW4gZXZlbnQ6IGh0dHBzOi8vbWFuNy5vcmcvbGludXgvbWFuLXBhZ2VzL21hbjIvZXBv
bGxfd2FpdC4yLmh0bWwNCg0KU28sIEkgd2FzIGludGVycHJldGluZyB0aGlzIEFQSSBhcyBlZmZl
Y3RpdmVseSBoYXZpbmcgYSBHUkFTUCBzcGVjaWZpYyBldmVudCBsb29wLCBhbmQgdGhhdCBsaXN0
ZW5fbmVnb3RpYXRlKCkgd2FzIGFjdGluZyBsaWtlIGVwb2xsX3dhaXQoKSBjYWxsLiAgQnV0IEkg
bWlnaHQgYmUgbWlzdW5kZXJzdGFuZGluZyB0aGUgaW50ZW50IGhlcmUuDQoNCg0KDQoNCj4gDQo+
ID4NCj4gPg0KPiA+ICAgICAyLjMuNC4gIE5lZ290aWF0aW9uDQo+ID4NCj4gPiAgICAgICAgICog
IG5lZ290aWF0ZV93YWl0KCkNCj4gPg0KPiA+IEl0IHdhc24ndCBjbGVhciB0byBtZSB3aHkgeW91
IHdvdWxkIHdhbnQgdG8gZG8gdGhpcywgYWx0aG91Z2ggdGhhdCBtYXkNCj4gYmUgYXBwYXJlbnQg
aW4gdGhlIEdSQVNQIGRyYWZ0LiAgUGVyaGFwcyBhIGNyb3NzIHJlZmVyZW5jZSBtaWdodCBiZQ0K
PiBoZWxwZnVsPw0KPiANCj4gWWVzLCB0aGUgaWRlYSBpcyBzaW1wbHkgdGhhdCBvbmUgcGFydHkg
aW4gdGhlIG5lZ290aWF0aW9uIHdhbnRzIHRvIHRlbGwNCj4gdGhlIG90aGVyIHBhcnR5IHRvIGJl
IHBhdGllbnQgZm9yIGEgd2hpbGUuIEl0IGlzIGRlc2NyaWJlZCBpbiB0aGUgR1JBU1ANCj4gc3Bl
YyBzbyBhIHJlZmVyZW5jZSB3aWxsIGhlbHAuDQpbUlddIA0KDQpPa2F5Lg0KDQoNCj4gDQo+ID4N
Cj4gPg0KPiA+ICAgICAyLjMuNC4gIE5lZ290aWF0aW9uDQo+ID4NCj4gPiAgICAgICAgICogIGVu
ZF9uZWdvdGlhdGUoKQ0KPiA+DQo+ID4gUG9zc2libHkgInN1Y2Nlc3NmdWwiIG1pZ2h0IGJlIGEg
YmV0dGVyIHBhcmFtZXRlciBuYW1lIHRoYW4gInJlcGx5Ii4gIEkNCj4gdGhpbmsgdGhhdCB5b3Ug
cmVwbHkgYm90aCBpZiB0aGUgbmVnb3RpYXRpb24gaXMgc3VjY2Vzc2Z1bCBhbmQgYWxzbyBpZiBp
dA0KPiBmYWlsZWQuDQo+IA0KPiBZZXMsIEkgZG9uJ3Qga25vdyB3aGVyZSB0aGF0IGNhbWUgZnJv
bS4gSW4gdGhlIFB5dGhvbiBpbXBsZW1lbnRhdGlvbiBpdCdzDQo+IGNhbGxlZCAncmVzdWx0JyAo
VHJ1ZSBmb3IgYWNjZXB0LCBGYWxzZSBmb3IgZGVjbGluZSkuDQo+IA0KPiA+DQo+ID4NCj4gPiAg
ICAgMi4zLjUuICBTeW5jaHJvbml6YXRpb24gYW5kIEZsb29kaW5nDQo+ID4NCj4gPiAgICAgICAg
KiAgc3luY2hyb25pemUoKQ0KPiA+DQo+ID4gICAgICAgICAgIC0gIElmIHRoZSBvYmplY3RpdmUg
d2FzIGFscmVhZHkgZmxvb2RlZCwgdGhlIGZsb29kZWQgdmFsdWUgaXMNCj4gPiAgICAgICAgICAg
ICAgcmV0dXJuZWQgaW1tZWRpYXRlbHkgaW4gdGhlICdyZXN1bHQnIHBhcmFtZXRlci4gIEluIHRo
aXMNCj4gY2FzZSwNCj4gPiAgICAgICAgICAgICAgdGhlICdzb3VyY2UnIGFuZCAndGltZW91dCcg
YXJlIGlnbm9yZWQuDQo+ID4NCj4gPiBTaG91bGQgc291cmNlIGJlIHF1b3RlZCBoZXJlPyAgSXQg
aXMgdW5jbGVhciB3aGF0IGl0IGlzIHJlZmVycmluZyB0by4NCj4gDQo+IEdvb2QgY2F0Y2guIFRo
YXQgc2hvdWxkIGJlICdwZWVyJy4NCj4gDQo+ID4NCj4gPg0KPiA+ICAgICAgICAgICAtICBPdGhl
cndpc2UsIHN5bmNocm9uaXphdGlvbiB3aXRoIGEgZGlzY292ZXJlZCBBU0EgaXMNCj4gcGVyZm9y
bWVkLg0KPiA+ICAgICAgICAgICAgICBUaGUgJ3BlZXInIHBhcmFtZXRlciBpcyBhbiAnQVNBX2xv
Y2F0b3InIGFzIHJldHVybmVkIGJ5DQo+ID4gICAgICAgICAgICAgIGRpc2NvdmVyKCkuICBJZiAn
cGVlcicgaXMgbnVsbCwgR1JBU1AgZGlzY292ZXJ5IGlzDQo+IHBlcmZvcm1lZA0KPiA+ICAgICAg
ICAgICAgICBmaXJzdC4NCj4gPg0KPiA+IEhvdyBkb2VzIHRoZSBHUkFTUCBkaXNjb3Zlcnkgd29y
ayBpbiB0aGlzIHNjZW5hcmlvPyAgRG9lcyB0aGlzIHJlcXVpcmUNCj4gdXNlIG9mIHRoZSBkaXNj
b3ZlcnkgQVBJcz8gIFRoaXMgbWF5IHJlcXVpcmUgZnVydGhlciBleHBsYW5hdGlvbi4NCj4gDQo+
IE9LLCB3aWxsIGZpeC4gVGhlIGludGVudGlvbiBpcyB0aGF0IGRpc2NvdmVyeSBpcyBsYXVuY2hl
ZCBhdXRvbWF0aWNhbGx5Lg0KW1JXXSANCg0KT2theS4NCg0KDQo+IA0KPiA+DQo+ID4NCj4gPiAg
ICAgMy4gIEltcGxlbWVudGF0aW9uIFN0YXR1cyBbUkZDIEVkaXRvcjogcGxlYXNlIHJlbW92ZV0N
Cj4gPg0KPiA+ICAgICAgICBBIHByb3RvdHlwZSBvcGVuIHNvdXJjZSBQeXRob24gaW1wbGVtZW50
YXRpb24gb2YgR1JBU1AsIGluY2x1ZGluZw0KPiBhbg0KPiA+ICAgICAgICBBUEkgc2ltaWxhciB0
byB0aGlzIGRvY3VtZW50LCBoYXMgYmVlbiB1c2VkIHRvIHZlcmlmeSB0aGUNCj4gY29uY2VwdHMN
Cj4gPiAgICAgICAgZm9yIHRoZSB0aHJlYWRlZCBtb2RlbC4gIEl0IG1heSBiZSBmb3VuZCBhdA0K
PiA+ICAgICAgICBodHRwczovL2dpdGh1Yi5jb20vYmVjYXJwZW50ZXIvZ3Jhc3B5IHdpdGggYXNz
b2NpYXRlZA0KPiBkb2N1bWVudGF0aW9uDQo+ID4gICAgICAgIGFuZCBkZW1vbnN0cmF0aW9uIEFT
QXMuDQo+ID4NCj4gPiBUaGlzIHNlY3Rpb24gd2lsbCBiZSByZW1vdmVkIGFueXdheSwgYnV0IEkg
dGhvdWdodCB0aGF0IHRoZSBHSUwgKGdsb2JhbA0KPiBpbnRlcnByZXRlciBsb2NrKSBlZmZlY3Rp
dmVseSBwcmV2ZW50ZWQgUHl0aG9uIHRocmVhZHMgZnJvbSBydW5uaW5nDQo+IGNvbmN1cnJlbnRs
eS4NCj4gDQo+IEl0J3Mgbm90IHRoYXQgc2ltcGxlLCBiZWNhdXNlIHlvdSBjYW4gZ2V0IHRydWUg
Y29uY3VycmVuY3kgZHVyaW5nIEkvTyBhbmQNCj4gY2xvY2sgd2FpdHMuIEluIGFueSBjYXNlLCB0
aGUgUHl0aG9uIHF1ZXVlIGFuZCBsb2NrIG1lY2hhbmlzbSBpcyB2YWxpZA0KPiByZWdhcmRsZXNz
IG9mIHRoaXMuDQo+IGh0dHBzOi8vd2lraS5weXRob24ub3JnL21vaW4vR2xvYmFsSW50ZXJwcmV0
ZXJMb2NrIGlzIGluZm9ybWF0aXZlLg0KW1JXXSANCg0KQWgsIG9rYXkuICBNeSBrbm93bGVkZ2Ug
b2YgUHl0aG9uIGlzIGZhaXJseSBzdXBlcmZpY2lhbC4NCg0KPiANCj4gPg0KPiA+DQo+ID4NCj4g
PiBOaXRzOg0KPiA+DQo+ID4gSSd2ZSBub3RlZCB0aGF0IHlvdSBoYXZlIGNob3NlbiBub3QgdG8g
dXNlIFJGQzIxMTkgbGFuZ3VhZ2UuICBObyBpc3N1ZXMNCj4gd2l0aCB0aGlzLCBidXQgdGhpcyBt
YXkgY29tZSB1cCBpbiBJRVNHIHJldmlldyAuLi4NCj4gDQo+IFdlbGwsIGl0J3MgSW5mb3JtYXRp
b25hbC4NCltSV10gDQpBaCwgeWVzLg0KDQo+IA0KPiA+DQo+ID4NCj4gPiBVc2Ugb2YgdGhlIHRl
cm0gIm5vbmNlIi4gIE5vdGUgaW4gVUsgRW5nbGlzaCB0aGlzIHdvcmQgc29tZXRpbWVzIHRha2Vz
DQo+IGFuIGFsdGVybmF0aXZlIG1lYW5pbmcsIGRlcGVuZGluZyBvbiB3aG8geW91IGFzayBhbmQg
d2hpY2ggZGljdGlvbmFyeSB5b3UNCj4gbG9vayBhdDogaHR0cHM6Ly9kaWN0aW9uYXJ5LmNhbWJy
aWRnZS5vcmcvZGljdGlvbmFyeS9lbmdsaXNoL25vbmNlDQo+ID4NCj4gPiBZb3UgbWF5IHdpc2gg
dG8gY29uc2lkZXIgYW4gYWx0ZXJuYXRpdmUgdGVybSwgYnV0IHBsZWFzZSBub3RlIHRoYXQgdGhp
cw0KPiBpcyB1cCB0byB0aGUgYXV0aG9ycy4gIEknbSBub3Qgb2JqZWN0aW5nIHRvIHRoaXMgdGVy
bSwganVzdCBtYWtpbmcgeW91DQo+IGF3YXJlLCBpZiB5b3Ugd2VyZW4ndCBhbHJlYWR5Lg0KPiAN
Cj4gSSdtIG5vdCBhd2FyZSBvZiBhIHZpYWJsZSBhbHRlcm5hdGl2ZS4NCltSV10gDQoNClRoYXQn
cyBmaW5lLg0KDQoNCj4gDQo+ID4gICAgIEFic3RyYWN0Og0KPiA+IE1heWJlIGxhbmd1YWdlcyA9
PiBwcm9ncmFtbWluZyBsYW5ndWFnZXMuDQo+IA0KPiBPSw0KPiANCj4gPg0KPiA+DQo+ID4NCj4g
PiAgICAgMS4gIEludHJvZHVjdGlvbg0KPiA+ICAgICAgICAgQXMgdGhlIGZvbGxvd2luZyBmaWd1
cmUgc2hvd3MsDQo+ID4NCj4gPiBHaXZlbiB0aGF0IHRoZSBmaWd1cmUgaXMgYSBmZXcgcGFyYWdy
YXBocyBhd2F5IChhbmQgb24gdGhlIG5leHQgcGFnZSBpbg0KPiB0aGUgdHh0IHZlcnNpb24pLCBw
ZXJoYXBzIGdpdmUgdGhlIGZpZ3VyZSBhIG5hbWUgYW5kIHJlZmVyZW5jZSBpdCBieSBuYW1lLg0K
PiANCj4gWWVzLg0KPiA+DQo+ID4NCj4gPg0KPiA+ICAgICAyLjMuMS4zLiAgT2JqZWN0aXZlLg0K
PiA+IEZvciBtZSwgSSB3b3VsZCBvdXRkZW50IHRoZSAifSBvYmplY3RpdmUiIGluIHRoZSBDIHN0
cnVjdCBleGFtcGxlLg0KPiANCj4gWWVzLg0KPiANCj4gPg0KPiA+IHJlcHJlc2VuYXRpb24gLT4g
cmVwcmVzZW50YXRpb24NCj4gDQo+IFllcy4NCj4gDQo+IFRoYW5rcyBtdWNoLA0KPiANCj4gICAg
IEJyaWFuDQpbUlddIA0KDQpUaGFua3MsDQpSb2INCg0KDQo+ID4NCj4gPiBUaGFua3MsDQo+ID4g
Um9iDQo+ID4NCg==


From nobody Tue Oct  6 13:31:09 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E380C3A0F55 for <anima@ietfa.amsl.com>; Tue,  6 Oct 2020 13:31:07 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5BggQnioSWHp for <anima@ietfa.amsl.com>; Tue,  6 Oct 2020 13:31:02 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 310753A0EB8 for <anima@ietf.org>; Tue,  6 Oct 2020 13:31:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 81E89389C6 for <anima@ietf.org>; Tue,  6 Oct 2020 16:36:20 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gLExIqkWJLwU for <anima@ietf.org>; Tue,  6 Oct 2020 16:36:19 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 655AD389C5 for <anima@ietf.org>; Tue,  6 Oct 2020 16:36:19 -0400 (EDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 12F4970D for <anima@ietf.org>; Tue,  6 Oct 2020 16:30:59 -0400 (EDT)
To: anima@ietf.org
References: <19427.1600704984@localhost>
From: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <668b988a-8fc9-5bdb-e703-1dc8d14521f6@sandelman.ca>
Date: Tue, 6 Oct 2020 16:30:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <19427.1600704984@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/vZ0qXZIxoojYFIX_9vLnaOHjG58>
Subject: [Anima] getting BRSKI and ACP done
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 20:31:08 -0000

Warren sent an email to the RFC-editor informing them that the LC on the 
name change was success, but it wasn't CC to the list.
    https://www.rfc-editor.org/cluster_info.php?cid=C325 shows version 
-44 in queue.

My understanding is that the ACP document has been revised according to 
the Erik Kline's DISCUSS, but awaits his confirmation.


From nobody Tue Oct  6 13:43:36 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC3503A1084 for <anima@ietfa.amsl.com>; Tue,  6 Oct 2020 13:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level: 
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 On5uj4-2nUkM for <anima@ietfa.amsl.com>; Tue,  6 Oct 2020 13:43:34 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2153F3A106D for <anima@ietf.org>; Tue,  6 Oct 2020 13:43:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2184C389C6; Tue,  6 Oct 2020 16:48:53 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pLl8gCZYGvev; Tue,  6 Oct 2020 16:48:52 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id ED1AD389C5; Tue,  6 Oct 2020 16:48:51 -0400 (EDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 942C870D; Tue,  6 Oct 2020 16:43:31 -0400 (EDT)
To: anima@ietf.org, kaduk@mit.edu, Toerless Eckert <tte@cs.fau.de>
References: <160159178470.16845.16995175102690434365@ietfa.amsl.com>
From: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <dcc69101-73be-cf9d-2e6f-8356ca38cb56@sandelman.ca>
Date: Tue, 6 Oct 2020 16:43:31 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <160159178470.16845.16995175102690434365@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/JITK3GEtp6a2FxpV8GX4_UurDUM>
Subject: Re: [Anima] Benjamin Kaduk's Yes on draft-ietf-anima-autonomic-control-plane-29: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 20:43:36 -0000

On 2020-10-01 6:36 p.m., Benjamin Kaduk via Datatracker wrote:
> A couple of the new bits in the -29 might benefit from targeted review (noted
> inline), e.g., for CDDL, TSV, or INT-specific aspects.

Carsten has already done that for CDDL.
I'm unclear what TSV and INT specific things you have in mind.


>     ACP nodes MUST NOT support certificates with RSA public keys whose
>     modulus is less than 2048 bits, or certificates whose ECC public keys
>     are in groups whose order is less than 256 bits.  RSA signing
>     certificates with 2048-bit public keys MUST be supported, and such
> 
> I think I mentioned this previously (and sorry for the repetition if I
> did), but just in case I didn't: this 256-bit group order requirement
> excludes Ed25519 and friends.  If you're fine with that, that's okay; I
> just want to make sure it's an informed choice.

Right, Ed25519 is considered to be a curve of 128-bits of equivalent 
strength.  My understanding is that secp256*, while having 256-bit 
curves, is also 128-bits of strength.
And RSA keys of 2048 bits is also of that relative strength.

I think that this is what Toerless is trying to say, but he didn't get 
the wording right.  Can you advise what the correct way to ask for this 
is?  Can we just point elsewhere?

> I think I may have failed to think about and comment on this previously,
> but doing direct ECDH with the (static) key in the certificate is pretty
> uncommon -- as I understand it you don't need this bit set in order to
> use the TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ciphersuite, for
> example.  To be clear, I'm not saying it's inherently wrong to make this
> requirement, just that I don't think it's needed for the use-cases
> presented in this document.  (It may also make it harder to get such
> certificates issued in the future, though it's hard to predict what
> path CA policies will take in the future.)

Agreed, and it's why I prefer to say less.


From nobody Tue Oct  6 13:46:44 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3943A10D0; Tue,  6 Oct 2020 13:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PojkvaNj6Mhb; Tue,  6 Oct 2020 13:46:40 -0700 (PDT)
Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (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 9EFF63A10BF; Tue,  6 Oct 2020 13:46:40 -0700 (PDT)
Received: by mail-pg1-x544.google.com with SMTP id r10so1611704pgb.10; Tue, 06 Oct 2020 13:46:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=AHXqa0bLbNHfTUXO/ZSGE+makbN9OxiIbAEQoTo44rg=; b=I2fTjfmSiHltzZZJMvoXBm5niniBtuOC4k9dfB0IHwOL8hTQAtlyvz8pStxbMaEPb1 xpC6/ISxobJ+twi+dg9frjVZRwBHG58E4zPvJIJzHcOjjE1UHcg04LUiXqhixPHknLD0 WhJdtxH6KZhaQZxQCp509b8D/n6uSQfnszznqGD91mwYGsyqqZJZnSagk5mQuZvHNC2D yGgfIkb5hi07K7Hi6K3QcUecMRZ35/uXGMgCytoZc7Ct6B0900dJ5PToCcDmKaG4cYhW djg2yBs6TjflBwMrUppaKJO64cI7CUDPoiZs3QDiiLUimAqGWFA3USSfcQCghquRASvl RqHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=AHXqa0bLbNHfTUXO/ZSGE+makbN9OxiIbAEQoTo44rg=; b=ikzpMk9x95uS0TbkaUakVuv9K9TkqeV6Q01YkEYeBf+NclYz0XUebMDob1mljnINmz vbN5sMFnbMVue0PkTbaPoMHCDwcpb0z6D2k3M/18ehAcvDXzRDQQRcGt678EMKGRzNP3 58AhU97lL51HQ6PkrZ5CiieFdXbgS4Q62/TamacNjgClZLpCo8KkveCkHMsXAQRoyWRC zsbYKh7K7KJxjpLBP8zjfiL6FhxSwRF3pKJcn2RXxKZaWvkmP6Zae3FCIz2+D59QxJVR H2S/Q4Jca7OdigNtRTcZsaG5If9hUMcVSR8SwpNr9gAr5BKHnwbgfrS8gTV6eafn0UvE Aklw==
X-Gm-Message-State: AOAM533TXqUDaphb+ce2c10m/maQkhUCpX2DrYWkFbScfPUn5RKxdgYx yUIXXznEjw4YTFID+967Nts=
X-Google-Smtp-Source: ABdhPJz0IrZHF9mSQU9agBvbpT5AxMQ/2vhKIbbkV4cY+ueyO/IDaYgcoxHdp3vs8rZrPwRKbSaB1g==
X-Received: by 2002:a63:da13:: with SMTP id c19mr44313pgh.68.1602017199982; Tue, 06 Oct 2020 13:46:39 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.138.136]) by smtp.gmail.com with ESMTPSA id v22sm51940pff.159.2020.10.06.13.46.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Oct 2020 13:46:39 -0700 (PDT)
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, "draft-ietf-anima-grasp-api@ietf.org" <draft-ietf-anima-grasp-api@ietf.org>
Cc: "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
References: <MN2PR11MB4366FCFF358BBABBF64CB27CB5350@MN2PR11MB4366.namprd11.prod.outlook.com> <e547f069-5138-fa04-2c63-ae7d9ead760a@gmail.com> <MN2PR11MB4366C811AAE5295B9A1A0D43B50D0@MN2PR11MB4366.namprd11.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <8b53f456-694c-aab0-24e8-6f34ac262f21@gmail.com>
Date: Wed, 7 Oct 2020 09:46:34 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <MN2PR11MB4366C811AAE5295B9A1A0D43B50D0@MN2PR11MB4366.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/CY7BmmO02xI294y7RixSORsnRso>
Subject: Re: [Anima] AD review of draft-ietf-anima-grasp-api-06
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 20:46:43 -0000

Thanks Rob. I think things are clear, so we'll work on an update over the=
 next few days.

Regards
   Brian

On 07-Oct-20 07:15, Rob Wilton (rwilton) wrote:
> Hi Brian,
>=20
> Thanks for the comments, please see replies inline.
>=20
>=20
>> -----Original Message-----
>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> Sent: 30 September 2020 23:28
>> To: Rob Wilton (rwilton) <rwilton@cisco.com>; draft-ietf-anima-grasp-
>> api@ietf.org
>> Cc: anima@ietf.org; Sheng Jiang <jiangsheng@huawei.com>
>> Subject: Re: AD review of draft-ietf-anima-grasp-api-06
>>
>> Thanks for this thorough review, Rob. Sorry about the previous partial=

>> reply. See responses in line.
>>
>> We'll pause for any feedback before updating the draft. In particular,=
 are
>> there any opnions on the example logic flows issue noted below?
>>
>> On 29-Sep-20 04:19, Rob Wilton (rwilton) wrote:
>>> Hi,
>>>
>>> Apologies for the delay for this review.
>>>
>>> Please see comments below.  I've also attached them in case they get
>> truncated (which has happened on other reviews).
>>>
>>> Thank you for this document.  Overall, it is very well written, easy =
to
>> read and easy to understand.
>>>
>>>
>>> Comments:
>>>
>>>     1.  Introduction
>>>
>>>        As the following figure shows, a GRASP implementation could
>> contain
>>>        two major sub-layers.  The bottom is the GRASP base protocol
>> module,
>>>        which is only responsible for sending and receiving GRASP
>> messages
>>>        and maintaining shared data structures.  The upper layer conta=
ins
>>>
>>> I found the text, relative to the diagram, to be somewhat confusing,
>> although the subsequent paragraphs make its intent clearer.
>>>
>>> I think that the top sub-layer is meant to be "GRASP Extended Functio=
n
>> Modules", and the "Grasp Modules" is the bottom sub-layer.  However, t=
he
>> diagram seems to have a sub-layer split in "GRASP Modules", and doesn'=
t
>> necessarily equate to "GRASP base protocol module".
>>
>> Perhaps we have confused two aspects: the view that the app writer has=
 of
>> the API, and the way it has to be implemented. More below...
>>
>>>
>>>     1.  Introduction
>>>
>>>        It is desirable that ASAs can be designed as portable user-spa=
ce
>>>        programs using a system-independent API.  In many
>> implementations,
>>>        the GRASP module will therefore be split into two layers.  The=

>> top
>>>        layer is a library that provides the API and communicates
>> directly
>>>        with ASAs.  The lower layer is a daemon, or a set of sub-
>> services,
>>>        providing GRASP core functions that are independent of specifi=
c
>> ASAs,
>>>        such as multicast handling and relaying, and common data
>> structures
>>>        such as the discovery cache.  The GRASP API library would need=
 to
>>>        communicate with the GRASP core via an inter-process
>> communication
>>>        (IPC) mechanism.  The details of this are system-dependent.
>>>
>>> I also find this text confusing relative to the diagram.  More
>> naturally, I would assume that the boxes represent different processes=
 and
>> hence you would have IPC between ASA and say the "GRASP API Library". =
 If
>> I was to draw this, then I would probably have put the GRASP API libra=
ry
>> co-located with the ASA boxes.
>>
>> Yes. In fact in my demo implementation, when I added an IPC mechanism,=

>> that is essentially what I got: stub functions for all the API calls i=
n
>> the app context, then IPC to the core, then the "real" functions and t=
he
>> various daemons/threads in the core context.
>>
>> I can't instantly provide old/new text to respond to this but we will =
try
>> to clarify all this.
> [RW]=20
>=20
> Okay.
>=20
>=20
>>
>>>
>>>
>>>     1.  Introduction
>>>
>>>        Note that a simple autonomic node might contain very few ASAs =
in
>>>        addition to the autonomic infrastructure components described =
in
>>>        [I-D.ietf-anima-bootstrapping-keyinfra] and
>>>        [I-D.ietf-anima-autonomic-control-plane].  Such a node might
>> directly
>>>        integrate GRASP in its code and therefore not require this API=
 to
>> be
>>>        installed.  However, the programmer would then need a deeper
>>>        understanding of the GRASP protocol than is needed to use the
>> API.
>>>
>>> Perhaps change "integrate GRASP in its code" to something like
>> "integrate the full GRASP implementation in its code"?
>>
>> Yes (but actually some cases might choose to implement a GRASP subset)=
=2E
> [RW]=20
>=20
> Or possibly something like "integrate a GRASP protocol stack in its cod=
e"?  The aim of my comment was to try and differentiate between just link=
ing against a GRASP API library and directly embedding part of the GRASP =
protocol stack.
>=20
>=20
>=20
>>
>>>
>>>     2.2.1.  Alternative Asynchronous Mechanisms
>>>
>>>        Thus, some ASAs need to support asynchronous operations, and
>>>        therefore the GRASP core must do so.  Depending on both the
>> operating
>>>        system and the programming language in use, there are three ma=
in
>>>        techniques for such parallel operations: multi-threading, an
>> event
>>>        loop structure using polling, and an event loop structure usin=
g
>>>        callback functions.
>>>
>>> Rather than "there are three main techniques for such parallel
>> operations", perhaps just "three common techniques are considered for
>> parallel operations".
>>
>> OK
>>
>>> Reasoning, there are other approaches for effectively handling
>> concurrent operations, e.g., actors, futures, cooperative threads back=
ed
>> by a OS thread pool ...
>>
>> [Or of course different names for the same thing. Imagine trying to
>> describe all this in terms of ADA rendezvous.]
>>
>>>
>>> Possibly, change "simple function calls" in the multi-threading
>> paragraph to be "simple synchronous function calls" to emphasize the
>> synchronous nature.
>>
>> OK
>>
>>>
>>>
>>>     2.2.2.  Multiple Negotiation Scenario
>>>
>>>        In the callback model, for the scenario just described, the AS=
As
>> "A"
>>>        and "B" will each provide two instances of
>> negotiate_step_received(),
>>>        one for each session.  For this reason, each ASA must be able =
to
>>>        distinguish the two sessions, and the peer's IP address is not=

>>>        sufficient for this.  It is also not safe to rely on transport=

>> port
>>>        numbers for this, since future variants of GRASP might use sha=
red
>>>        ports rather than a separate port per session.  This is why th=
e
>> GRASP
>>>        design includes a session identifier.  Thus, when necessary, a=

>>>        'session_nonce' parameter is used in the API to distinguish
>>>        simultaneous GRASP sessions from each other, so that any numbe=
r
>> of
>>>        sessions may proceed asynchronously in parallel.
>>>
>>> It wasn't obvious to me why both ASAs "A" and "B" both provide
>> callbacks, I presume that this is because there are multiple asynchron=
ous
>> steps involved.  If so, would it be helpful to clarify this point?
>>
>> Yes, one could build very complicated interlocking negotiations. (That=
 is
>> a whole can of worms, explored in draft-ciavaglia-anima-coordination, =
but
>> for present purposes we just need to ensure that ASAs can handle any
>> degree of asynchronosity, if that's a word.)
>>
>>> Also in this paragraph suggest "Hence, " rather than "This is wht"
>>
>> OK
>>
>>>
>>>
>>>     2.2.3.  Overlapping Sessions and Operations
>>>
>>>        In calls where it is used, the 'session_nonce' is an opaque re=
ad/
>>>        write parameter.  On the first call, it is set to a null value=
,
>> and
>>>        the API returns a non-null 'session_nonce' value based on the
>> GRASP
>>>        session identifier.  This value must be used in all subsequent=

>> calls
>>>        for the same session, and will be provided as a parameter in t=
he
>>>        callback functions.  By this mechanism, multiple overlapping
>> sessions
>>>        can be distinguished, both in the ASA and in the GRASP core.  =
The
>>>        value of the 'session_nonce" is opaque to the ASA.
>>>
>>> Query the use of a null value, and whether that is too restrictive.
>>
>> Its value on the first call is of no importance, so we should just cal=
l it
>> a placeholder.
> [RW]=20
>=20
> Sorry, I had intended to expand my original comment.  To me this reads =
quite like a C API, where the session_nonce is a INOUT parameter, but oth=
er languages that say allow a tuple to be returned would probably just re=
turn a tuple containing whatever other return parameters along with a ses=
sion_nonce.
>=20
> However, I'm also not quite sure whether this text is entirely consiste=
nt with how the session_nonce is actually used in the APIs.  E.g. request=
_negotiate() options returns a session_nonce.  It doesn't appear to be an=
 "in" parameter at all.
>=20
> Perhaps the text should just say something like the session_nonce is pr=
ovided when the session is established and used in all subsequent calls, =
and detailed semantics to the specific APIs?
>=20
>=20
>=20
>=20
>=20
>>
>>>
>>>
>>>     2.3.  API definition
>>>
>>> Possibly this API would benefit from a short section (or even pseudo
>> code) explaining the flow or flows of how the APIs are expected to wor=
k
>> together.  This could also be in an appendix.  Perhaps the GRASP
>> specification makes this obvious, in which case references back to the=

>> GRASP spec would be sufficient.
>>
>> We have some example logic flows in https://tools.ietf.org/id/draft-
>> carpenter-anima-asa-guidelines-09.html#section-appendix.b
>>
>> Would a reference to that help? The authors would like that draft to b=
e
>> adopted by the WG. We could of course move the examples into the API
>> draft, if people prefer that.
> [RW]=20
>=20
> Yes, this is what I was thinking of.
>=20
> I don=E2=80=99t mind whether it is included in an appendix in this draf=
t or as a reference.
>=20
>=20
>=20
>>
>>>
>>>
>>>     2.3.1.3.  Objective
>>>
>>>        *  name (UTF-8 string) - the objective's name
>>>
>>> Should there be a limit on the length of the name?  This question
>> equivalently applies to the other strings/variable sized types.
>>
>> I think that's implementation dependent. Because GRASP is a CBOR proto=
col,
>> there is no particular limit on string length. There is a limit on the=

>> total size of a GRASP message (although I suspect we might decide to r=
aise
>> or remove that limit one day).
> [RW]=20
>=20
> That sounds reasonable, and I don't feel too strongly on this issue.
>=20
> I think that my general concern with arbitrary length strings in APIs, =
that are implementation dependent, is that clients may not know what (if =
any) max length is supported by an implementation, which potentially coul=
d make interop harder.  In the YANG world, this can be mitigated via devi=
ations to indicate implementation specific restrictions.
>=20
> Perhaps what I am thinking of is defining a minimum supported length.  =
E.g., the length is implementation specific, but all implementations must=
 support, say, at least 64 characters.  Hence, a client would know that i=
f the name was below this length then it would work with all implementati=
ons, but implementations may support a much higher limit if they wish.
>=20
>=20
>>
>>>        *  value - a specific data structure expressing the value of t=
he
>>>           objective.  The format is language dependent, with the
>> constraint
>>>           that it can be validly represented in CBOR (default integer=
 =3D
>> 0).
>>>
>>> I didn't understand the "default integer =3D 0" part.  If this is a b=
yte
>> string then I would thought that the default might be an empty length
>> bytestring, or perhaps a CBOR Null.
>>
>> I'm not even sure now why we need to specify a default in a generic AP=
I.
>>
>>>           An essential requirement for all language mappings and all
>>>           implementations is that, regardless of what other options
>> exist
>>>           for a language-specific represenation of the value, there i=
s
>>>           always an option to use a CBOR byte string as the value.  T=
he
>> API
>>>           will then wrap this byte string in CBOR Tag 24 for
>> transmission
>>>           via GRASP, and unwrap it after reception.
>>>
>>> It was unclear whether you just meant an opaque CBOR byte string here=

>> (CBOR major type 2), or a CBOR byte string that itself contains CBOR
>> encoded data (i.e. CBOR Tag 24).  Is there any limit on the length of =
the
>> CBOR byte string that is allowed?
>>
>> It's not intended to be restricted to major type 2; I'll have to check=
 the
>> CBOR RFC to find the correct phrase to use.
> [RW]=20
>=20
> Perhaps something along the lines of "An encoded CBOR data item, wrappe=
d in CBOR Tag 24, as per section 3.4.5.1 of 7049bis"
>=20
>=20
>=20
>>
>> As above, the only size limit we have is the total GRASP message size.=

>>
>>>
>>>
>>>     2.3.2.  Registration
>>>
>>> Some APIs list "Asynchronous Mechanisms:" and others don't.  It might=
 be
>> helpful to clarify that those APIs that don't list asynchronous mechan=
isms
>> are implicitly synchronous in their behaviour.
>>
>> OK
>>
>>>
>>>
>>>         *  deregister_asa()
>>>
>>>           -  Note - the ASA name is strictly speaking redundant in th=
is
>>>              call, but is present for clarity.
>>>
>>> Presumably it also makes it significantly harder for a rogue client t=
o
>> try and deregister all ASAs by looping through all asa_nonces.
>>
>> True, but there is so much entropy in the nonce that this would be a
>> challenge anyway.
> [RW]=20
>=20
> Okay.  When I wrote this, I also realized that the other APIs are just =
relying on the nonce anyway.
>=20
>=20
>>
>>>
>>>
>>>     2.3.4.  Negotiation
>>>
>>>              2.  The 'session_nonce' parameter is not null.  In this
>> case
>>>                  negotiation must continue.  The returned
>>>                  'proffered_objective' contains the first value
>> proffered by
>>>                  the negotiation peer.  Note that this instance of th=
e
>>>                  objective must be used in the subsequent negotiation=

>> call
>>>                  because it also contains the current loop count.  Th=
e
>>>                  'session_nonce' must be presented in all subsequent
>>>                  negotiation steps.
>>>
>>> Presumably the loop count in the proffered_objective must be one grea=
ter
>> than the loop count in the objective structure?  Would it be helpful t=
o
>> mention this?
>>
>> Right... I'm going to look in my GRASP code before I try to rephrase t=
hat.
>> I recall that it was a bit tricky to get it right.
> [RW]=20
>=20
> Okay.
>=20
>>
>>>
>>> I also wasn't sure whether it must be "this instance of the objective=

>> must be used", or just that the loop counter must be copied across.  E=
=2Eg.,
>> functional languages would encourage these structures to be immutable.=

>>
>> And because of Python's vagueness about whether it's call-by-reference=
 or
>> call-by-value, there are cases where I've had to explicitly clone a co=
py
>> of an objective to be sure that I have the right to decrement the loop=

>> counter. So yes, it's "this instance or a clone of this instance". Wil=
l
>> rephrase.
> [RW]=20
>=20
> Okay.
>=20
>>
>>>
>>>
>>>          -  Asynchronous Mechanisms:
>>>
>>>              o  Event loop implementation: The 'session_nonce' parame=
ter
>> is
>>>                 used in read/write mode.
>>>
>>> It is unclear to me, exactly what you mean by this, particularly beca=
use
>> this is a return parameter.  Perhaps this could be further explained i=
n
>> the text, or refer back the previous text.
>>
>> Yes. I think we were trying to express something that will look a bit
>> different in C compared to high-level languages.
> [RW]=20
>=20
> Possibly even referring it an in/out parameter would be clearer.
>=20
>>
>>>
>>>
>>>     2.3.4.  Negotiation
>>>
>>>         *  listen_negotiate()
>>>
>>> I was surprised that the listen_negotate didn't include any timeout,
>> e.g. to allow it to be used in polling fashion.  Same comment applies =
to
>> listen_synchronize().
>>
>> Well, in a polling solution won't the listen state just go into the ev=
ent
>> loop? But I'm a bit out of my depth there.
> [RW]=20
>=20
> Okay, possibly I was thrown by the "Unless there is an unexpected failu=
re,
> this call only returns after an incoming negotiation request."  I.e., i=
t seems to suggest that it always blocks.  But perhaps the description ne=
eds to be refined depending on whether it is a synchronous or asynchronou=
s API.
>=20
> In a pure event loop scenario, I would expect a registration API to reg=
ister an event (e.g. an objective) that I am interested in, and optionall=
y a callback function to be invoked when that event is received.  Normall=
y, the thread would then have a loop waiting (blocking) for an event to b=
e received that might either be returned back in the loop (or plausibly d=
ispatched directly).  In the code that I am familiar with there are separ=
ate calls to wait (block) for a new event, and then a separate function i=
s invoked to dispatch the event to the registered call back handler.  In =
this scenario is it sometimes useful for the event block() call to have a=
 timeout, allowing the thread to do other periodic housekeeping work and =
then make a new event_block() call.
>=20
> I'm not particular familiar with the Linux epoll, but this gives an exa=
mple of a timeout whilst waiting for an event: https://man7.org/linux/man=
-pages/man2/epoll_wait.2.html
>=20
> So, I was interpreting this API as effectively having a GRASP specific =
event loop, and that listen_negotiate() was acting like epoll_wait() call=
=2E  But I might be misunderstanding the intent here.
>=20
>=20
>=20
>=20
>>
>>>
>>>
>>>     2.3.4.  Negotiation
>>>
>>>         *  negotiate_wait()
>>>
>>> It wasn't clear to me why you would want to do this, although that ma=
y
>> be apparent in the GRASP draft.  Perhaps a cross reference might be
>> helpful?
>>
>> Yes, the idea is simply that one party in the negotiation wants to tel=
l
>> the other party to be patient for a while. It is described in the GRAS=
P
>> spec so a reference will help.
> [RW]=20
>=20
> Okay.
>=20
>=20
>>
>>>
>>>
>>>     2.3.4.  Negotiation
>>>
>>>         *  end_negotiate()
>>>
>>> Possibly "successful" might be a better parameter name than "reply". =
 I
>> think that you reply both if the negotiation is successful and also if=
 it
>> failed.
>>
>> Yes, I don't know where that came from. In the Python implementation i=
t's
>> called 'result' (True for accept, False for decline).
>>
>>>
>>>
>>>     2.3.5.  Synchronization and Flooding
>>>
>>>        *  synchronize()
>>>
>>>           -  If the objective was already flooded, the flooded value =
is
>>>              returned immediately in the 'result' parameter.  In this=

>> case,
>>>              the 'source' and 'timeout' are ignored.
>>>
>>> Should source be quoted here?  It is unclear what it is referring to.=

>>
>> Good catch. That should be 'peer'.
>>
>>>
>>>
>>>           -  Otherwise, synchronization with a discovered ASA is
>> performed.
>>>              The 'peer' parameter is an 'ASA_locator' as returned by
>>>              discover().  If 'peer' is null, GRASP discovery is
>> performed
>>>              first.
>>>
>>> How does the GRASP discovery work in this scenario?  Does this requir=
e
>> use of the discovery APIs?  This may require further explanation.
>>
>> OK, will fix. The intention is that discovery is launched automaticall=
y.
> [RW]=20
>=20
> Okay.
>=20
>=20
>>
>>>
>>>
>>>     3.  Implementation Status [RFC Editor: please remove]
>>>
>>>        A prototype open source Python implementation of GRASP, includ=
ing
>> an
>>>        API similar to this document, has been used to verify the
>> concepts
>>>        for the threaded model.  It may be found at
>>>        https://github.com/becarpenter/graspy with associated
>> documentation
>>>        and demonstration ASAs.
>>>
>>> This section will be removed anyway, but I thought that the GIL (glob=
al
>> interpreter lock) effectively prevented Python threads from running
>> concurrently.
>>
>> It's not that simple, because you can get true concurrency during I/O =
and
>> clock waits. In any case, the Python queue and lock mechanism is valid=

>> regardless of this.
>> https://wiki.python.org/moin/GlobalInterpreterLock is informative.
> [RW]=20
>=20
> Ah, okay.  My knowledge of Python is fairly superficial.
>=20
>>
>>>
>>>
>>>
>>> Nits:
>>>
>>> I've noted that you have chosen not to use RFC2119 language.  No issu=
es
>> with this, but this may come up in IESG review ...
>>
>> Well, it's Informational.
> [RW]=20
> Ah, yes.
>=20
>>
>>>
>>>
>>> Use of the term "nonce".  Note in UK English this word sometimes take=
s
>> an alternative meaning, depending on who you ask and which dictionary =
you
>> look at: https://dictionary.cambridge.org/dictionary/english/nonce
>>>
>>> You may wish to consider an alternative term, but please note that th=
is
>> is up to the authors.  I'm not objecting to this term, just making you=

>> aware, if you weren't already.
>>
>> I'm not aware of a viable alternative.
> [RW]=20
>=20
> That's fine.
>=20
>=20
>>
>>>     Abstract:
>>> Maybe languages =3D> programming languages.
>>
>> OK
>>
>>>
>>>
>>>
>>>     1.  Introduction
>>>         As the following figure shows,
>>>
>>> Given that the figure is a few paragraphs away (and on the next page =
in
>> the txt version), perhaps give the figure a name and reference it by n=
ame.
>>
>> Yes.
>>>
>>>
>>>
>>>     2.3.1.3.  Objective.
>>> For me, I would outdent the "} objective" in the C struct example.
>>
>> Yes.
>>
>>>
>>> represenation -> representation
>>
>> Yes.
>>
>> Thanks much,
>>
>>     Brian
> [RW]=20
>=20
> Thanks,
> Rob
>=20
>=20
>>>
>>> Thanks,
>>> Rob
>>>


From nobody Tue Oct  6 14:15:27 2020
Return-Path: <kaduk@mit.edu>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 997913A14F0 for <anima@ietfa.amsl.com>; Tue,  6 Oct 2020 14:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 JS9uji8NFg4T for <anima@ietfa.amsl.com>; Tue,  6 Oct 2020 14:15:24 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 238573A14E2 for <anima@ietf.org>; Tue,  6 Oct 2020 14:15:23 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 096LFCKp014899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 6 Oct 2020 17:15:14 -0400
Date: Tue, 6 Oct 2020 14:15:12 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org, Toerless Eckert <tte@cs.fau.de>
Message-ID: <20201006211512.GM89563@kduck.mit.edu>
References: <160159178470.16845.16995175102690434365@ietfa.amsl.com> <dcc69101-73be-cf9d-2e6f-8356ca38cb56@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <dcc69101-73be-cf9d-2e6f-8356ca38cb56@sandelman.ca>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/e6UDKxD-doloHUuikJlLWUm8nFs>
Subject: Re: [Anima] Benjamin Kaduk's Yes on draft-ietf-anima-autonomic-control-plane-29: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2020 21:15:26 -0000

On Tue, Oct 06, 2020 at 04:43:31PM -0400, Michael Richardson wrote:
> On 2020-10-01 6:36 p.m., Benjamin Kaduk via Datatracker wrote:
> > A couple of the new bits in the -29 might benefit from targeted review (noted
> > inline), e.g., for CDDL, TSV, or INT-specific aspects.
> 
> Carsten has already done that for CDDL.

(If you have a link handy, I'd love to have it.  I couldn't quite convince
myself that RFC 8610 actually said that CDDL has the "first successful
match" nature of a PEG, with respect to the method-params and extensions.
Maybe I was just reading too quickly.)

> I'm unclear what TSV and INT specific things you have in mind.

Sorry; this was:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
   Attackers on a subnet may be able to inject malicious DULL GRASP
   messages that are indistinguishable from non-malicious DULL GRASP
   messages to create Denial-of-Service (DoS) attacks that force ACP
   nodes to attempt many unsuccessful ACP secure channel connections.
   When an ACP node sees multiple AN_ACP objectives for the same secure
   channel protocol on different transport addresses, it SHOULD prefer
   connecting via the well-known transport address if the secure channel
   method has one (such as UDP port 500 for IKEv2).

This new text should probably be run by some TSV-area reviewer (e.g.,
AD).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
(Specifically, the use of the well-known port as a signal.)

and

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
   If public CA are to be used, ACP registrars would need to prove
   ownership of the domain-name of AcpNodeNames to the public CA.
   However, maintaining the ULA based address allocation when using a
   public CA might be considered to be a violation of the private
   allocation expectation of ULA prefixes.  To avoid this issue, further
   changes to registrar address allocation procedures might be needed,
   for example using global IPv6 address prefixes owned by the public CA
   instead of ULA.

I don't expect any problems here, but it might be good to get some
INT-area (e.g., AD) eyes on this text.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
(The ULA usage here is IIUC a bit different than previous revs of the
draft.)


> 
> >     ACP nodes MUST NOT support certificates with RSA public keys whose
> >     modulus is less than 2048 bits, or certificates whose ECC public keys
> >     are in groups whose order is less than 256 bits.  RSA signing
> >     certificates with 2048-bit public keys MUST be supported, and such
> > 
> > I think I mentioned this previously (and sorry for the repetition if I
> > did), but just in case I didn't: this 256-bit group order requirement
> > excludes Ed25519 and friends.  If you're fine with that, that's okay; I
> > just want to make sure it's an informed choice.
> 
> Right, Ed25519 is considered to be a curve of 128-bits of equivalent 
> strength.  My understanding is that secp256*, while having 256-bit 
> curves, is also 128-bits of strength.
> And RSA keys of 2048 bits is also of that relative strength.
> 
> I think that this is what Toerless is trying to say, but he didn't get 
> the wording right.  Can you advise what the correct way to ask for this 

This one is a bit awkward, since we need to allow 2048-bit RSA based on our
understanding of the TPM ecosystem, but 2048-bit RSA is currently thought
to have roughly 112 bits of strength (you need 3072-bit RSA to get 128-bit
strength).  RFC 8032 hedges a little bit to say that "Ed25519 is intended
to operate at around the 128-bit security level" (i.e., just below).  The
smallest possible change here would be s/256/254/, I think, but it could be
restructured a bit to be genericized if we want, perhaps:

% The ACP aims to provide authentication at around the 128-bit security
% level or stronger.  Accordingly, ACP nodes MUST NOT support certificates
% whose ECC public keys are in groups providing weaker security than this
% 128-bit level.  In order to accomodate limitations of TPM hardware
% modules, this requirement is slightly weakened for RSA certificates; ACP
% nodes MUST NOT support certificates with RSA public keys whose modulus is
% less than 2048 bits (which corresponds to roughly a 112-bit security
% level).  RSA signing certificates with [...]

A parenthetical note that "(this explicitly permits Ed25519 keys)" is
possible, but probably optional.

> is?  Can we just point elsewhere?

I am not thinking of anything offhand that we can just refer to,
unfortunately.

> > I think I may have failed to think about and comment on this previously,
> > but doing direct ECDH with the (static) key in the certificate is pretty
> > uncommon -- as I understand it you don't need this bit set in order to
> > use the TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ciphersuite, for
> > example.  To be clear, I'm not saying it's inherently wrong to make this
> > requirement, just that I don't think it's needed for the use-cases
> > presented in this document.  (It may also make it harder to get such
> > certificates issued in the future, though it's hard to predict what
> > path CA policies will take in the future.)
> 
> Agreed, and it's why I prefer to say less.

That's my preference, too, but (as Brian has recently reminded us [0]) I'm not
in charge.

-Ben

[0] https://www.ietf.org/id/draft-carpenter-nomcom2020-letter-00.html


From nobody Wed Oct  7 03:03:50 2020
Return-Path: <esko.dijk@iotconsultancy.nl>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07DC93A047D; Wed,  7 Oct 2020 03:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iotconsultancy.nl
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 m2FDehNQF_vk; Wed,  7 Oct 2020 03:03:47 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70103.outbound.protection.outlook.com [40.107.7.103]) (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 CE77E3A07C4; Wed,  7 Oct 2020 03:03:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ghfm2xGWmuC2Wu3xiNOUIGr5LQatA4Kedkz/WKSpmQON4/UHD9jmRsUW6zBSNLrkJVW2wAr/oj4GVygb46pLUbifcdgkf+82hEiYY8hJ+y+RcMxDcLQfQHHzvNvbgqUiD/Vfzd2XxWf0Hw8b7mzks38Xj/5O4xdnsC99MBbuS63b0PZ3A1/8RvXaN8W+AHuftupZBpmaa9nuXSTln7UVpvJuz6bkl7hZBhZoP6pqZQ3yawN3oVLQrYMqIwoFoYsalY11721nXnAmg2WrM5tpCTFTgu0dOuEn0ooqQcjOpFCSq3A6PxgdFXui+ya4fSECQWyy/pyVvOlxBKF5lYy19w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HxgUV0Kl8Wm8LbpP4ubSLiaqPvRIk3CN3htK/y3OYZY=; b=C7feRzVvVyH7jApA9UcK7/tkfkG0o+UE3WZsaSdU22HKrqonUU3iLwsiRgQvYpzbpeAy65xhbVD2sKsZJC0V5w97OYWbiKZLXt1gKmE2GCPlcimyC06vdbXYhMlEISSq1y4KByMZmL1xh08HddZQ0nq3mMABTEyQr/Akx5M2Ngdw87NBAWRTLJCyBn/uLe8wnSdCqO5URX5Oe/a2QgzteHl/de3t3f1aYfOnyAzwdRohDiZ/mtQDcTySFUoRAhKBrGeTqacKS71NyV//E/jJIL9pMylR4MpPVdCZLC4n/bpII9oF3ZNXThcHNKKR6XPkPVSepYwZCQ1HfH2Q+9VXCA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=iotconsultancy.nl; dmarc=pass action=none header.from=iotconsultancy.nl; dkim=pass header.d=iotconsultancy.nl; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iotconsultancy.nl; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HxgUV0Kl8Wm8LbpP4ubSLiaqPvRIk3CN3htK/y3OYZY=; b=nSo2oei5+wYfzKshL0dlF+qa10Gbk7UHzlCJDOoDV0/Xhmsx0dfQNbbKTaTHI9GG40pzAt9zW98++BfUBlFdix67KAlThKV00F/JxpO6kRolXjqmDupJXeqsZxZjIPaNrFrSpMkSUh9bh0lexP0MqdKQzLIaSEuvKmlyJJljfYw=
Received: from AM8P190MB0979.EURP190.PROD.OUTLOOK.COM (2603:10a6:20b:1d3::8) by AM8P190MB0963.EURP190.PROD.OUTLOOK.COM (2603:10a6:20b:1c6::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.39; Wed, 7 Oct 2020 10:03:41 +0000
Received: from AM8P190MB0979.EURP190.PROD.OUTLOOK.COM ([fe80::b0bf:bd8a:de8f:55fa]) by AM8P190MB0979.EURP190.PROD.OUTLOOK.COM ([fe80::b0bf:bd8a:de8f:55fa%5]) with mapi id 15.20.3455.022; Wed, 7 Oct 2020 10:03:41 +0000
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
To: "anima@ietf.org" <anima@ietf.org>
CC: "draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org" <draft-ietf-anima-bootstrapping-keyinfra.all@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: BRSKI: clarification needed on how MASA may check consistency of proximity-registrar-cert
Thread-Index: Adacjc5732V1vixFQJ+DhRS1iBGdlw==
Date: Wed, 7 Oct 2020 10:03:41 +0000
Message-ID: <AM8P190MB0979B4F5CE106A12E91863A4FD0A0@AM8P190MB0979.EURP190.PROD.OUTLOOK.COM>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none; ietf.org; dmarc=none action=none header.from=iotconsultancy.nl; 
x-originating-ip: [85.147.167.236]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 894fd519-f965-4941-7d6d-08d86aa84510
x-ms-traffictypediagnostic: AM8P190MB0963:
x-microsoft-antispam-prvs: <AM8P190MB0963AFD67616C6BFD64303F3FD0A0@AM8P190MB0963.EURP190.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: SrY+Y1DYUSSy+bf7CXtM9nakqpkrJ89GWe6NbwZnXk0L/oEmDS9o5oikztIdwFwteB9lgU/isXlL/sd7yvc3vaxWsf3SdY7LpP6oWiC9WufAqJlYq7OZj4tF7EZEcOcZkfLcwLry76M2VhPVZ8EIzhejjIN+Sfqhb3c7XotqVCV+P4h9Tx33BeTNGedzVoyqDgelmm3YWcQz3Xldo6wEi/gk3bJ/q0I70Sqy1VDAAm/7l6FCLCj/EI0zohd6qBllbGYEGDlKaD7F3BrXvhu3UkJ0uKRuCWwz5qUb0ku+K+TL2M0FkAiM7VSEApqUXPf1gsXUlW1Zc2Y8tJiytFwqzQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM8P190MB0979.EURP190.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(39830400003)(376002)(346002)(136003)(366004)(396003)(478600001)(71200400001)(54906003)(6506007)(26005)(2906002)(33656002)(52536014)(6916009)(186003)(316002)(83380400001)(44832011)(9686003)(86362001)(7696005)(5660300002)(66946007)(4326008)(8676002)(8936002)(55016002)(66476007)(66556008)(66446008)(64756008)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: scVd1vHttYSY021h7YhCEEnX8GzGGU6KOT3g31I/5Ey6Uf9vI2RZSc/9XOXoCVNahB5hKPQsSYDFM2zpeBlEO1vJhr5GAzjf5Ee5BE9YBwTlmV6ZgQzUZORhmOdNsZqKJ+Ou5sig7dMtEh/oHA7CqsBefKSEpISoxvjKz4JhaItEAm6NXDGUTqgUcDQ7JfIuEX19l6XYIiSBAe1tuUpDnU0q3yeLyvtPKOzMa5kaslcVfRs8joHduF6EnQTWKlpQDkh88FpzNAklhXImLUbVilYNC15nPVM8ungTOlEYfkk4uCyy8hkv9xvxBMvTOmH3i/DAIu4YBSGd1dKqNjSXRtwhuKGGFDBE2XARnYqBYg5cLnERz98GAD+xemvGGPCCJVi/fqBkuZ06K7IuwI+5dPurWUwDM7LTqEuLdEWnLQLa2qsU0cWWnHgwTQ+1mYn5oGS8IC9YM93yz1xskQ6P/aOUG0AlO2GrTqW/eCYTIKvzx+SWmXkmVIaImmtEfe3Od3WsJxVikuNn1h38rrasgZTy1fti0Zs4xw2Tmph274idz6fqZsEgN3CcymF/ibBTiwqJxz7PLQtM+5+1OSm5FFW3kceYVvZbXzcoozF1tSXD72kMzSd3Hp+E/fZsKFNIQ6QKsNGFH4QRH3t00ueiDA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM8P190MB0979B4F5CE106A12E91863A4FD0A0AM8P190MB0979EURP_"
MIME-Version: 1.0
X-OriginatorOrg: iotconsultancy.nl
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM8P190MB0979.EURP190.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 894fd519-f965-4941-7d6d-08d86aa84510
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2020 10:03:41.7837 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 58bbf628-15d2-46bc-820b-863b6774d44b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: kfRtqNRAk899PvZtKUYqEhE4blVuSBVP4DNLq6fiObDGXe3wDxbqJ6Zen68u7FK43b4LuvdxtG7GUVj1VCdRTz92EyA26eG8dtNcOQbWJSQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8P190MB0963
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/NxI10dI3urjsWbdH1nCKchVVMPM>
Subject: [Anima] BRSKI: clarification needed on how MASA may check consistency of proximity-registrar-cert
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Oct 2020 10:03:49 -0000

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

SGVsbG8gYWxsLA0KDQpUaGUgZm9sbG93aW5nIHF1ZXN0aW9uIGNhbWUgdXAgZHVyaW5nIGltcGxl
bWVudGF0aW9uIG9mIEJSU0tJOiB3aGVuIHRoZSBNQVNBIHZlcmlmaWVzIHRoZSBwcmlvci1zaWdu
ZWQtdm91Y2hlci1yZXF1ZXN0IGFuZCBpdHMgaW5jbHVkZWQg4oCYcHJveGltaXR5LXJlZ2lzdHJh
ci1jZXJ04oCZIHBlciBTZWN0aW9uIDUuNS41LCAgZG9lcyB0aGUg4oCYcHJveGltaXR5LXJlZ2lz
dHJhci1jZXJ04oCZIG5lY2Vzc2FyaWx5IG5lZWQgdG8gYmUgaW5jbHVkZWQgaW4gdGhlIFJlZ2lz
dHJhcuKAmXMgQ01TIHNpZ25hdHVyZSBjZXJ0IGNoYWluPw0KDQpCZWNhdXNlIGZvciBjYXNlcyB3
aGVyZSBhIFJlZ2lzdHJhciB1c2VzIGRpZmZlcmVudCBpZGVudGl0aWVzIChrZXlwYWlycykgZm9y
IFRMUy1zZXJ2ZXIgYW5kIGZvciBWb3VjaGVyLVJlcXVlc3Qgc2lnbmluZywgIHRoZSBDTVMgc2ln
bmF0dXJlIGNlcnQgY2hhaW4gd2lsbCB0eXBpY2FsbHkgbm90IGluY2x1ZGUgdGhlIFRMUy1zZXJ2
ZXIgY2VydCBhbmQgaGVuY2UgdGhlIOKAmHByb3hpbWl0eS1yZWdpc3RyYXItY2VydOKAmSB3aWxs
IG5vdCBhcHBlYXIgZGlyZWN0bHkgaW4gdGhlIENNUyBzaWduYXR1cmUgY2VydCBjaGFpbi4NCklu
c3RlYWQgdGhlIE1BU0EgY2FuIHZlcmlmeSB0aGF0IHRoZSDigJhwcm94aW1pdHktcmVnaXN0cmFy
LWNlcnTigJkgaXMgZGlyZWN0bHkgKnNpZ25lZCogYnkgb25lIG9mIHRoZSBDQShzKSBwcmVzZW50
IGluIHRoZSBDTVMgc2lnbmF0dXJlIGNlcnQgY2hhaW47IHRodXMgaXQgY2FuIGJlIHRydXN0ZWQu
DQoNCkV4YW1wbGU6DQoNCkRvbWFpbiBDQSAocm9vdCkNCiAgICAgICB8DQogICAgIFN1Ym9yZGlu
YXRlIENBDQogICAgICAgfCAgICAgICAgICBcDQpSZWdpc3RyYXIgUkEgICAgICBSZWdpc3RyYXIg
UkENCmNlcnQgMSAgICAgICAgICAgIGNlcnQgMg0KKFRMUyBzZXJ2ZXIpICAgICAgKHNpZ25pbmcp
DQoNClRoZSBSQSBjZXJ0IDEgaXMgdXNlZCBmb3IgdGhlIFRMUyBzZXJ2ZXIuIFRoZSBSQSBjZXJ0
IDIgaXMgdXNlZCBmb3Igc2lnbmluZyB0aGUgVm91Y2hlci1SZXF1ZXN0IHRvIE1BU0EuDQpUaGUg
UkEgY2VydCAxIGlzIHNlZW4gYnkgdGhlIFBsZWRnZSBhbmQgcHJlc2VudCBpbiB0aGUg4oCYcHJv
eGltaXR5LXJlZ2lzdHJhci1jZXJ04oCZIGZpZWxkLg0KTUFTQSBzZWVzIHRoZSBmb2xsb3dpbmcg
Y2hhaW4gaW4gdGhlIENNUyBzaWduYXR1cmU6DQoNCkRvbWFpbiBDQSAocm9vdCkNCiAgICAgICB8
DQpTdWJvcmRpbmF0ZSBDQQ0KICAgICAgIHwNClJlZ2lzdHJhciBSQSBjZXJ0IDINCg0KTXkgaW50
ZXJwcmV0YXRpb24gb2YgY3VycmVudCBCUlNLSSBTZWN0aW9uIDUuNS41IGlzIHRoYXQgdGhlIHZl
cmlmaWNhdGlvbiAvIGNvbnNpc3RlbmN5LWNoZWNrIGF0IE1BU0Egd2lsbCBub3cgZmFpbC4gSG93
ZXZlciwgYW5vdGhlciBvcGluaW9uIGluIG15IHRlYW0gaXMgdGhhdCBpdCBjYW4gc3VjY2VlZCBi
ZWNhdXNlIE1BU0EgY2FuIHZlcmlmeSB0aGF0IFJBIGNlcnQgMSBpcyBzaWduZWQgYnkg4oCYU3Vi
b3JkaW5hdGUgQ0HigJkgYW5kIGhlbmNlIGNhbiBiZSB0cnVzdGVkLg0KT24gdGhlIG90aGVyIGhh
bmQsIFJBIGNlcnQgMSBhbmQgUkEgY2VydCAyIGFyZSBkaWZmZXJlbnQgZW50aXRpZXMgbG9naWNh
bGx5IHNvIHRoZW4gdGhlIOKAnHByb3hpbWl0eeKAnSBhc3NlcnRpb24gb2YgQlJTS0kgd291bGQg
YmUgd2Vha2VuZWQuDQpBbnkgb3BpbmlvbnMgb24gdGhpcz8NCg0KRm9yIGludGVyb3BlcmFiaWxp
dHksIGl0IG5lZWRzIHRvIGJlIGNsZWFyIGZvciB0aGUgUmVnaXN0cmFyIGhvdyB0aGUgTUFTQSB3
aWxsIHBlcmZvcm0sIGlmIHRoaXMgdmVyaWZpY2F0aW9uIGlzIGVuYWJsZWQsIHRoZSB2ZXJpZmlj
YXRpb24gb2YgU2VjdGlvbiA1LjUuNS4gIFRoaXMgaW1wYWN0cyB3aXRoIHdoYXQgaWRlbnRpdHkg
aXQgY2FuIHNpZ24gVm91Y2hlci1SZXF1ZXN0cy4NCg0KQmVzdCByZWdhcmRzDQpFc2tvIERpamsN
Cg0KSW9UY29uc3VsdGFuY3kubmwgIHwgIEVtYWlsL1RlYW1zOiBlc2tvLmRpamtAaW90Y29uc3Vs
dGFuY3kubmw8bWFpbHRvOmVza28uZGlqa0Bpb3Rjb25zdWx0YW5jeS5ubD4NCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0
eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToi
Q2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtz
aXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2
LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0i
MTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86
c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEi
IC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBs
YW5nPSJFTi1VUyIgbGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhlbGxvIGFsbCw8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+VGhlIGZvbGxvd2luZyBxdWVzdGlvbiBjYW1lIHVwIGR1cmluZyBpbXBs
ZW1lbnRhdGlvbiBvZiBCUlNLSTogd2hlbiB0aGUgTUFTQSB2ZXJpZmllcyB0aGUgcHJpb3Itc2ln
bmVkLXZvdWNoZXItcmVxdWVzdCBhbmQgaXRzIGluY2x1ZGVkIOKAmHByb3hpbWl0eS1yZWdpc3Ry
YXItY2VydOKAmSBwZXIgU2VjdGlvbiA1LjUuNSwgJm5ic3A7ZG9lcyB0aGUg4oCYcHJveGltaXR5
LXJlZ2lzdHJhci1jZXJ04oCZIG5lY2Vzc2FyaWx5IG5lZWQNCiB0byBiZSBpbmNsdWRlZCBpbiB0
aGUgUmVnaXN0cmFy4oCZcyBDTVMgc2lnbmF0dXJlIGNlcnQgY2hhaW4/PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkJlY2F1c2UgZm9yIGNhc2VzIHdoZXJlIGEgUmVnaXN0cmFyIHVzZXMgZGlmZmVy
ZW50IGlkZW50aXRpZXMgKGtleXBhaXJzKSBmb3IgVExTLXNlcnZlciBhbmQgZm9yIFZvdWNoZXIt
UmVxdWVzdCBzaWduaW5nLCZuYnNwOyB0aGUgQ01TIHNpZ25hdHVyZSBjZXJ0IGNoYWluIHdpbGwg
dHlwaWNhbGx5IG5vdCBpbmNsdWRlIHRoZSBUTFMtc2VydmVyIGNlcnQgYW5kIGhlbmNlIHRoZSDi
gJhwcm94aW1pdHktcmVnaXN0cmFyLWNlcnTigJkNCiB3aWxsIG5vdCBhcHBlYXIgZGlyZWN0bHkg
aW4gdGhlIENNUyBzaWduYXR1cmUgY2VydCBjaGFpbi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkluc3RlYWQgdGhlIE1BU0EgY2FuIHZlcmlmeSB0aGF0IHRoZSDigJhwcm94
aW1pdHktcmVnaXN0cmFyLWNlcnTigJkgaXMgZGlyZWN0bHkgKjxiPnNpZ25lZDwvYj4qIGJ5IG9u
ZSBvZiB0aGUgQ0EocykgcHJlc2VudCBpbiB0aGUgQ01TIHNpZ25hdHVyZSBjZXJ0IGNoYWluOyB0
aHVzIGl0IGNhbiBiZSB0cnVzdGVkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5FeGFtcGxlOjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29sYXMi
PkRvbWFpbiBDQSAocm9vdCk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29sYXMiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyAmbmJzcDsmbmJzcDt8PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNvbnNvbGFzIj4mbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgU3Vib3JkaW5hdGUgQ0E8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29sYXMiPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDt8Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwO1w8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29sYXMiPlJlZ2lz
dHJhciBSQSAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtSZWdpc3RyYXIgUkE8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6Q29uc29sYXMiPmNlcnQgMSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDtjZXJ0IDI8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29s
YXMiPihUTFMgc2VydmVyKSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAoc2lnbmluZykm
bmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5UaGUgUkEgY2VydCAxIGlzIHVzZWQgZm9yIHRoZSBUTFMgc2VydmVyLiBUaGUgUkEgY2Vy
dCAyIGlzIHVzZWQgZm9yIHNpZ25pbmcgdGhlIFZvdWNoZXItUmVxdWVzdCB0byBNQVNBLjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIFJBIGNlcnQgMSBpcyBzZWVuIGJ5
IHRoZSBQbGVkZ2UgYW5kIHByZXNlbnQgaW4gdGhlIOKAmHByb3hpbWl0eS1yZWdpc3RyYXItY2Vy
dOKAmSBmaWVsZC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TUFTQSBz
ZWVzIHRoZSBmb2xsb3dpbmcgY2hhaW4gaW4gdGhlIENNUyBzaWduYXR1cmU6PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDb25zb2xhcyI+RG9tYWluIENB
IChyb290KTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTpDb25zb2xhcyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZu
YnNwOyZuYnNwO3w8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29sYXMiPlN1Ym9yZGluYXRlIENBPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OkNvbnNvbGFzIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7fCZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29s
YXMiPlJlZ2lzdHJhciBSQSBjZXJ0IDI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q29uc29sYXMiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk15IGludGVycHJldGF0aW9u
IG9mIGN1cnJlbnQgQlJTS0kgU2VjdGlvbiA1LjUuNSBpcyB0aGF0IHRoZSB2ZXJpZmljYXRpb24g
LyBjb25zaXN0ZW5jeS1jaGVjayBhdCBNQVNBIHdpbGwgbm93IGZhaWwuIEhvd2V2ZXIsIGFub3Ro
ZXIgb3BpbmlvbiBpbiBteSB0ZWFtIGlzIHRoYXQgaXQgY2FuIHN1Y2NlZWQgYmVjYXVzZSBNQVNB
IGNhbiB2ZXJpZnkgdGhhdCBSQSBjZXJ0IDEgaXMgc2lnbmVkIGJ5IOKAmFN1Ym9yZGluYXRlDQog
Q0HigJkgYW5kIGhlbmNlIGNhbiBiZSB0cnVzdGVkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+T24gdGhlIG90aGVyIGhhbmQsIFJBIGNlcnQgMSBhbmQgUkEgY2VydCAyIGFy
ZSBkaWZmZXJlbnQgZW50aXRpZXMgbG9naWNhbGx5IHNvIHRoZW4gdGhlIOKAnHByb3hpbWl0eeKA
nSBhc3NlcnRpb24gb2YgQlJTS0kgd291bGQgYmUgd2Vha2VuZWQuPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5Bbnkgb3BpbmlvbnMgb24gdGhpcz88bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Rm9yIGludGVyb3BlcmFiaWxpdHksIGl0IG5lZWRzIHRvIGJlIGNsZWFyIGZvciB0
aGUgUmVnaXN0cmFyIGhvdyB0aGUgTUFTQSB3aWxsIHBlcmZvcm0sIGlmIHRoaXMgdmVyaWZpY2F0
aW9uIGlzIGVuYWJsZWQsIHRoZSB2ZXJpZmljYXRpb24gb2YgU2VjdGlvbiA1LjUuNS4mbmJzcDsg
VGhpcyBpbXBhY3RzIHdpdGggd2hhdCBpZGVudGl0eSBpdCBjYW4gc2lnbiBWb3VjaGVyLVJlcXVl
c3RzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0IHJlZ2FyZHM8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkVza28gRGlqazxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPklvVGNvbnN1bHRhbmN5
Lm5sPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0IiPiZu
YnNwOyB8Jm5ic3A7IEVtYWlsL1RlYW1zOg0KPGEgaHJlZj0ibWFpbHRvOmVza28uZGlqa0Bpb3Rj
b25zdWx0YW5jeS5ubCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMwNTYzQzEiPmVza28uZGlqa0Bpb3Rj
b25zdWx0YW5jeS5ubDwvc3Bhbj48L2E+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9ImVuLU5MIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM8P190MB0979B4F5CE106A12E91863A4FD0A0AM8P190MB0979EURP_--


From nobody Wed Oct  7 17:07:48 2020
Return-Path: <noreply@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 110D53A0858; Wed,  7 Oct 2020 17:07:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org,  anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, jiangsheng@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <160211566645.2456.18172889573633510280@ietfa.amsl.com>
Date: Wed, 07 Oct 2020 17:07:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/xNhbeYVVC1qAoezB07PCzK-a7I8>
Subject: [Anima] Erik Kline's Yes on draft-ietf-anima-autonomic-control-plane-29: (with COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 00:07:47 -0000

Erik Kline has entered the following ballot position for
draft-ietf-anima-autonomic-control-plane-29: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing things!




From nobody Wed Oct  7 17:08:06 2020
Return-Path: <ek.ietf@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6BC3A09D8; Wed,  7 Oct 2020 17:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCnld3rHCmSd; Wed,  7 Oct 2020 17:07:48 -0700 (PDT)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 B9A3F3A0855; Wed,  7 Oct 2020 17:07:43 -0700 (PDT)
Received: by mail-ot1-x335.google.com with SMTP id s66so3999379otb.2; Wed, 07 Oct 2020 17:07:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rWxQC501DczwJidtm6xsHfnrWWyXnorPdeynFF52hsI=; b=qujqroHVIJ2QsV3G2eteDOtUFeucneZJooZkGv1vVx1sLSVWuabVTZ3rbxRrt1wIZ+ hpAY2WaL44e3wwfXdSXI9aZlJMQLLdsNbWCJEQLabQ87TOV8Y4JmZz1vKoRVWT3q37YF 3UsXDispTL0Jhw2d7p0UX47IChns8k3/Tir5BgXRtjJk7ykeED7xEoSx1QUxqg8fl0Y9 qzNY8eauQbWC2vE8Athsfw7yAWBcLjoribdgXRjfwWW4Hin31K+Hco898ew4LqBXkoa7 UmdTL+uJU+p4LnIrhhigIrh7EfSeHeKfK50+C7h0KG8yfR67MXB6OZSddD+Ra8Nqbv2e nQqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rWxQC501DczwJidtm6xsHfnrWWyXnorPdeynFF52hsI=; b=YNHA8QaK7qD93b7yyCJpAZOXk8QOtfarucA3DXEC6lg/oafyMrVLAGxaXhLkZl//RF IoT0ApVjmD0DIlmHs83S9x7ycxgAyRjaKutBZtvdwiFt1/CT0LZSjW4qG9THHYOino9h Wo7Q+xRlQEBAO4KzshuMMbzuc336mTKjlYXXPs5FU1YCPMF3u6AowI/rTLkIefsyMhhI 4a1UStzZuCbmuH6yEjgZ4zOQM+5HVTmivWe1iU8GbKbzhS0WfPFd3FkF31vMmdU9rUDY aOhFo01YQYF8l8JsQQVJbfpOaZR6j5/NLpFj67J2fMfGP48zkefXEeI/LeJyXrrWp/4x gYug==
X-Gm-Message-State: AOAM530yc0GeSbyk1vFm6XUHuwMGQ5n2QG+IRvT4/OBFXWGrPqawqghx NqKe+vEOL9fA5CJ7cwICl2JJHcsoY2KB/YtDHYg=
X-Google-Smtp-Source: ABdhPJySI0cQfEv4sdxqfwEXqZTmpSbbHfAgC71TiyE3qmt+SlfmzenCUyxteNbeByqsOd+UimnIfwIfq7TE/INupg8=
X-Received: by 2002:a9d:32e:: with SMTP id 43mr2917929otv.144.1602115663055; Wed, 07 Oct 2020 17:07:43 -0700 (PDT)
MIME-Version: 1.0
References: <159730676576.12387.18205135091671983859@ietfa.amsl.com> <20200911130023.GA64542@faui48f.informatik.uni-erlangen.de> <CAMGpriVX12nhjwPzATRCkntmH5DQNjtQ3M2d490ya2_yJ75CLA@mail.gmail.com> <20200930135504.GA34365@faui48f.informatik.uni-erlangen.de> <A866FDD1-3FF8-430E-BB01-9F05F20C062D@cisco.com> <20201001110651.GB34365@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20201001110651.GB34365@faui48f.informatik.uni-erlangen.de>
From: Erik Kline <ek.ietf@gmail.com>
Date: Wed, 7 Oct 2020 17:07:32 -0700
Message-ID: <CAMGpriXZhfY10r4MtWNa9ZavD_Ymv7w15ZYqqKWHu-o6gJcqug@mail.gmail.com>
To: Toerless Eckert <tte@cs.fau.de>
Cc: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>,  "draft-ietf-anima-autonomic-control-plane@ietf.org" <draft-ietf-anima-autonomic-control-plane@ietf.org>,  The IESG <iesg@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary="000000000000fc512b05b11d9e07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/7HPIN0_ga9D14XDm5CdzHnjgAfY>
Subject: Re: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 00:07:56 -0000

--000000000000fc512b05b11d9e07
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I've read the text in -29, and I do think it's much better.  Thank you.
The "counterpart" sentence is followed immediately by "There are important
differences", and maybe that's good enough.  (Still concerned about this
one sentence being taken out of context, but I'll just have to remain
vigilant and point out the missing context if/when I see such things).
Thank you.

Cleared my discuss.  Thanks for your patience and effort!


On Thu, Oct 1, 2020 at 4:06 AM Toerless Eckert <tte@cs.fau.de> wrote:

> On Wed, Sep 30, 2020 at 02:14:25PM +0000, Eric Vyncke (evyncke) wrote:
> > About ULA, why not simply keeping:
> >
> > "    ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an IPv6
> >        address in the block fc00::/7, defined in [RFC4193]."
> >
> > And nothing else of the existing paragraph. IMHO, there is no need to
> justify the choice
>
> Eric: If we can not agree on a simple sentence comparing what we have in
> IPv6
> with what we had in IPv4, we should stop writing RFCs or using IPv6.
>
> Eliot: Thanks for the "analog" suggestion, but i think "analog" is
> semantically
> close to "counterpoint", aka: suggesting a closer functional equivalence
> with
>  rfc1918 than there actual is, so IMHO it would not resolve Eriks concern=
.
>
> Cheers
>     Toerless
> >
> > -=C3=A9ric
> >
> > ???-----Original Message-----
> > From: Anima <anima-bounces@ietf.org> on behalf of Toerless Eckert <
> tte@cs.fau.de>
> > Date: Wednesday, 30 September 2020 at 15:55
> > To: Erik Kline <ek.ietf@gmail.com>
> > Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "
> draft-ietf-anima-autonomic-control-plane@ietf.org" <
> draft-ietf-anima-autonomic-control-plane@ietf.org>, The IESG <
> iesg@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <
> jiangsheng@huawei.com>
> > Subject: Re: [Anima] Erik Kline's Discuss on
> draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
> >
> >     Inline
> >
> >     On Sun, Sep 27, 2020 at 02:52:17PM -0700, Erik Kline wrote:
> >     > Toerless,
> >     >
> >     > Thanks for taking the time to go through all this.  Generally
> LGTM, but I
> >     > would like to iterate on the ULA text (nothing major).
> >     >
> >     >
> >     > > > [ section 2 ]
> >     > > >
> >     > > > * "It is the approximate IPv6 counterpart of the IPv4 private
> address
> >     > > >   ([RFC1918])."
> >     > > >
> >     > > >   I understand the intent but I don't think this statement is
> complete. I
> >     > > >   think we shouldn't let this sentence out into the wild as i=
s
> since it
> >     > > could
> >     > > >   be read without any context nor even any pretense of
> interest in
> >     > > nuance.
> >     > > >
> >     > > >   May I suggest:
> >     > > >
> >     > > >   "It is often thought of as the approximate IPv6 counterpart
> of the IPv4
> >     > > >   private address space ([RFC1918]), though it is in fact
> meaningfully
> >     > > >   different in important and subtle ways [and upon which this
> document
> >     > > relies]."
> >     > >
> >     > > Thanks for not trying to talk me out of the comparison, which i
> >     > > successfully
> >     > > used to explain ULA to many customers. Your proposal is a bit
> too verbose
> >     > > for
> >     > > the terminoloy section, so it's now:
> >     > >
> >     > > It is often thought of as the approximate IPv6 counterpart of
> the IPv4
> >     > > private address (<xref target=3D"RFC1918" format=3D"default"/>)=
.
> There are
> >     > > important differences though that are beneficial for and
> exploited by the
> >     > > ACP, such as the ULA Global ID prefix, which are the first
> 48-bits of a ULA
> >     > > address. In this document it is abbreviated as "ULA prefix".
> >     > >
> >     >
> >     > It's a statement of fact that this is how people unfamiliar with
> this space
> >     > view this space.  It's apparently also a statement of fact that
> people are
> >     > still actively being told this.  ;-)
> >     >
> >     > But I still think it's not quite right.  For one, the real
> counterpart to
> >     > 1918 in IPv6 is the deprecated site-local prefix.
> >     >
> >     > Also, to say it's "often
> >     > thought of" in an IETF document implies more IETF folks think of
> this way,
> >     > when in reality I'm not sure that's the case.
> >
> >     *cough* *cough*
> >
> >     |> [ section 2 ]
> >     |>
> >     |> * "It is the approximate IPv6 counterpart of the IPv4 private
> address
> >     |>   ([RFC1918])."
> >     |> ...
> >     |> May I suggest:
> >     |>   "It is often thought of as the approximate IPv6 counterpart of
> the IPv4
> >     |>   private address space ([RFC1918]), though it is in fact
> meaningfully
> >     |>   different in important and subtle ways ...
> >
> >     Aka: It is now your text that you would like to see revisited !
> >
> >     > If you really want to leave this notion in (removing the sentence
> >     > altogether is good by me), perhaps we can wordsmith it a bit
> more.  If I
> >     > may propose:
> >
> >     How about:
> >
> >         ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an
> IPv6
> >            address in the block fc00::/7, defined in [RFC4193].  ULA is
> the
> >            IPv6 successor of the IPv4 private address space ([RFC1918])=
.
> >            ULA have important differences over IPv4 private addresses
> that
> >            are beneficial for and exploited by the ACP, such as the
> Locally
> >            Assigned Global ID prefix, which are the first 48-bits of a
> ULA
> >            address [RFC4193 section 3.2.1].  In this document this
> prefix is
> >            abbreviated as "ULA prefix".
> >
> >     Successor is hopefully more correct word. Sure, site local prefixes
> >     where a successor too, but i hope i do not have to write
> >
> >     "ULA is the (only surviving) IPv6 successor..."
> >
> >     > OLD:
> >     >
> >     >    ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an
> IPv6
> >     >       address in the block fc00::/7, defined in [RFC4193].  It is
> often
> >     >       thought of as the approximate IPv6 counterpart of the IPv4
> private
> >     >       address ([RFC1918]).  There are important differences thoug=
h
> that
> >     >       are beneficial for and exploited by the ACP, such as the UL=
A
> >     >       Global ID prefix, which are the first 48-bits of a ULA
> address.
> >     >       In this document it is abbreviated as "ULA prefix".
> >     >
> >     > NEW:
> >     >
> >     >    ULA: (Global ID prefix)  A "Unique Local Address" (ULA) is an
> IPv6
> >     >       address in the block fc00::/7, defined in [RFC4193].
> Sometimes
> >     >       thought of as the approximate IPv6 counterpart of the IPv4
> private
> >     >       address ([RFC1918]), there are important differences that a=
re
> >     >       beneficial for and exploited by the ACP.  In this document,
> the
> >     >       "ULA prefix" refers to Locally Assigned Global ID prefixes,
> which
> >     >       are the first 48-bits of the ULA address [RFC4193 section
> 3.2.1].
> >
> >     Beside the counterpart wordsmithing,
> >     i do not like the removal of pointing out that the ULA prefix is th=
e
> >     new benefit of ULA that we exploit with ACP. That was at the core o=
f
> the
> >     explanation.
> >
> >     > (I didn't think it was worth trying to get into the fc00::/8 vs
> fd00::/8
> >     > distinction in this glossary text.)
> >
> >     I agree, but i do not see neither the glossary or the rest of the
> text
> >     doing that. The spec part just specifies use of fd00:/8 without
> >     discussion and the glossary just uses the ::/7 as thats what rfc419=
3
> say..
> >     Am i missing something ?
> >
> >     > > [ section 8.1.3 ]
> >     > > >
> >     > > > * Why is an RIO for ::/0 with a lifetime of 0 required?
> Doesn't it
> >     > > suffice
> >     > > >   it set the default router lifetime to 0?  Separately, are
> all nodes
> >     > > required
> >     > > >   to be Type C?
> >     > >
> >     > > Check the new text, i hope it explains everything.
> >     > >
> >     > > Yes, type A and B do not support per-prefix auto selection of
> router,
> >     > > The lifetime of 0 is used so only Type C hosts will invalidate
> the
> >     > > default route for the ACP edge node, but not Type A/B hosts.
> Maybe there
> >     > > is another parameter combination that achieves this goal, but
> this was
> >     > > the easiest for me to assess/describe.
> >     > >
> >     >
> >     > This looks better, thank you.
> >     >
> >     > To be honest, I don't know what the point of Type A/B hosts is
> anymore (and
> >     > if it were possible to declare these anima deployments greenfield
> I would
> >     > recommend saying the default router lifetime MUST be zero in the
> RA header
> >     > to force clients to use a stack that works -- but that's just me)=
.
> >
> >     I would guess that A and B have been seen in the wild before 4191 w=
as
> >     released and so the RFC was written to be inclusive. No idea.
> >
> >     I have no idea how prevalent these types are, and the current
> described
> >     method may be a tiny bit more convoluted but seems to be more
> compatible.
> >
> >     Given my deployment experience of enterprises withholding from
> adopting
> >     new network technology when it wasn't compatible with their oldest
> >     NMS equipment, i am a bit burned in promoting "hard cut" solutions,
> and
> >     this ben an OPS area draft instead of e.g.: RTG is a good excuse fo=
r
> that
> >     approach ;-))
> >
> >     Cheers
> >         Toerless
> >
> >     _______________________________________________
> >     Anima mailing list
> >     Anima@ietf.org
> >     https://www.ietf.org/mailman/listinfo/anima
> >
>
> --
> ---
> tte@cs.fau.de
>

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

<div dir=3D"ltr">I&#39;ve read the text in -29, and I do think it&#39;s muc=
h better.=C2=A0 Thank you.=C2=A0 The &quot;counterpart&quot; sentence is fo=
llowed immediately by &quot;There are important differences&quot;, and mayb=
e that&#39;s good enough.=C2=A0 (Still concerned about this one sentence be=
ing taken out of context, but I&#39;ll just have to remain vigilant and poi=
nt out the missing context if/when I see such things).=C2=A0 Thank you.<div=
><br></div><div>Cleared my discuss.=C2=A0 Thanks for your patience and effo=
rt!</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Thu, Oct 1, 2020 at 4:06 AM Toerless Eckert &lt;=
<a href=3D"mailto:tte@cs.fau.de">tte@cs.fau.de</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Sep 30, 2020 at 02:14=
:25PM +0000, Eric Vyncke (evyncke) wrote:<br>
&gt; About ULA, why not simply keeping:<br>
&gt; <br>
&gt; &quot;=C2=A0 =C2=A0 ULA: (Global ID prefix)=C2=A0 A &quot;Unique Local=
 Address&quot; (ULA) is an IPv6<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 address in the block fc00::/7, defined in [=
RFC4193].&quot;<br>
&gt; <br>
&gt; And nothing else of the existing paragraph. IMHO, there is no need to =
justify the choice<br>
<br>
Eric: If we can not agree on a simple sentence comparing what we have in IP=
v6<br>
with what we had in IPv4, we should stop writing RFCs or using IPv6.<br>
<br>
Eliot: Thanks for the &quot;analog&quot; suggestion, but i think &quot;anal=
og&quot; is semantically<br>
close to &quot;counterpoint&quot;, aka: suggesting a closer functional equi=
valence with<br>
=C2=A0rfc1918 than there actual is, so IMHO it would not resolve Eriks conc=
ern.<br>
<br>
Cheers<br>
=C2=A0 =C2=A0 Toerless<br>
&gt; <br>
&gt; -=C3=A9ric<br>
&gt; <br>
&gt; ???-----Original Message-----<br>
&gt; From: Anima &lt;<a href=3D"mailto:anima-bounces@ietf.org" target=3D"_b=
lank">anima-bounces@ietf.org</a>&gt; on behalf of Toerless Eckert &lt;<a hr=
ef=3D"mailto:tte@cs.fau.de" target=3D"_blank">tte@cs.fau.de</a>&gt;<br>
&gt; Date: Wednesday, 30 September 2020 at 15:55<br>
&gt; To: Erik Kline &lt;<a href=3D"mailto:ek.ietf@gmail.com" target=3D"_bla=
nk">ek.ietf@gmail.com</a>&gt;<br>
&gt; Cc: &quot;<a href=3D"mailto:anima-chairs@ietf.org" target=3D"_blank">a=
nima-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:anima-chairs@ietf.org"=
 target=3D"_blank">anima-chairs@ietf.org</a>&gt;, &quot;<a href=3D"mailto:d=
raft-ietf-anima-autonomic-control-plane@ietf.org" target=3D"_blank">draft-i=
etf-anima-autonomic-control-plane@ietf.org</a>&quot; &lt;<a href=3D"mailto:=
draft-ietf-anima-autonomic-control-plane@ietf.org" target=3D"_blank">draft-=
ietf-anima-autonomic-control-plane@ietf.org</a>&gt;, The IESG &lt;<a href=
=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a>&gt;, &quot;<a=
 href=3D"mailto:anima@ietf.org" target=3D"_blank">anima@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:anima@ietf.org" target=3D"_blank">anima@ietf.org</a>&=
gt;, Sheng Jiang &lt;<a href=3D"mailto:jiangsheng@huawei.com" target=3D"_bl=
ank">jiangsheng@huawei.com</a>&gt;<br>
&gt; Subject: Re: [Anima] Erik Kline&#39;s Discuss on draft-ietf-anima-auto=
nomic-control-plane-28: (with DISCUSS and COMMENT)<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Inline<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0On Sun, Sep 27, 2020 at 02:52:17PM -0700, Erik Klin=
e wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Toerless,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Thanks for taking the time to go through all t=
his.=C2=A0 Generally LGTM, but I<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; would like to iterate on the ULA text (nothing=
 major).<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt; [ section 2 ]<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt; * &quot;It is the approximate IPv6 c=
ounterpart of the IPv4 private address<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0([RFC1918]).&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0I understand the intent =
but I don&#39;t think this statement is complete. I<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0think we shouldn&#39;t l=
et this sentence out into the wild as is since it<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; could<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0be read without any cont=
ext nor even any pretense of interest in<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; nuance.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0May I suggest:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0&quot;It is often though=
t of as the approximate IPv6 counterpart of the IPv4<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0private address space ([=
RFC1918]), though it is in fact meaningfully<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0different in important a=
nd subtle ways [and upon which this document<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; relies].&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; Thanks for not trying to talk me out of t=
he comparison, which i<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; successfully<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; used to explain ULA to many customers. Yo=
ur proposal is a bit too verbose<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; for<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; the terminoloy section, so it&#39;s now:<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; It is often thought of as the approximate=
 IPv6 counterpart of the IPv4<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; private address (&lt;xref target=3D&quot;=
RFC1918&quot; format=3D&quot;default&quot;/&gt;). There are<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; important differences though that are ben=
eficial for and exploited by the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; ACP, such as the ULA Global ID prefix, wh=
ich are the first 48-bits of a ULA<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; address. In this document it is abbreviat=
ed as &quot;ULA prefix&quot;.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; It&#39;s a statement of fact that this is how =
people unfamiliar with this space<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; view this space.=C2=A0 It&#39;s apparently als=
o a statement of fact that people are<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; still actively being told this.=C2=A0 ;-)<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; But I still think it&#39;s not quite right.=C2=
=A0 For one, the real counterpart to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; 1918 in IPv6 is the deprecated site-local pref=
ix.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; Also, to say it&#39;s &quot;often<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; thought of&quot; in an IETF document implies m=
ore IETF folks think of this way,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; when in reality I&#39;m not sure that&#39;s th=
e case.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0*cough* *cough*<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt; [ section 2 ]<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt; * &quot;It is the approximate IPv6 counterpar=
t of the IPv4 private address<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt;=C2=A0 =C2=A0([RFC1918]).&quot;<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt; ...<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt; May I suggest:<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt;=C2=A0 =C2=A0&quot;It is often thought of as t=
he approximate IPv6 counterpart of the IPv4<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt;=C2=A0 =C2=A0private address space ([RFC1918])=
, though it is in fact meaningfully<br>
&gt;=C2=A0 =C2=A0 =C2=A0|&gt;=C2=A0 =C2=A0different in important and subtle=
 ways ...<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Aka: It is now your text that you would like to see=
 revisited !<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; If you really want to leave this notion in (re=
moving the sentence<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; altogether is good by me), perhaps we can word=
smith it a bit more.=C2=A0 If I<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; may propose:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0How about:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ULA: (Global ID prefix)=C2=A0 A &quot=
;Unique Local Address&quot; (ULA) is an IPv6<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 address in the block fc00::/7=
, defined in [RFC4193].=C2=A0 ULA is the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IPv6 successor of the IPv4 pr=
ivate address space ([RFC1918]). <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ULA have important difference=
s over IPv4 private addresses that<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 are beneficial for and exploi=
ted by the ACP, such as the Locally<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Assigned Global ID prefix, wh=
ich are the first 48-bits of a ULA<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 address [RFC4193 section 3.2.=
1].=C2=A0 In this document this prefix is<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 abbreviated as &quot;ULA pref=
ix&quot;.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Successor is hopefully more correct word. Sure, sit=
e local prefixes<br>
&gt;=C2=A0 =C2=A0 =C2=A0where a successor too, but i hope i do not have to =
write <br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&quot;ULA is the (only surviving) IPv6 successor...=
&quot;<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; OLD:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 ULA: (Global ID prefix)=C2=A0 A &=
quot;Unique Local Address&quot; (ULA) is an IPv6<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0address in the block=
 fc00::/7, defined in [RFC4193].=C2=A0 It is often<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0thought of as the ap=
proximate IPv6 counterpart of the IPv4 private<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0address ([RFC1918]).=
=C2=A0 There are important differences though that<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0are beneficial for a=
nd exploited by the ACP, such as the ULA<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Global ID prefix, wh=
ich are the first 48-bits of a ULA address.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0In this document it =
is abbreviated as &quot;ULA prefix&quot;.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; NEW:<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 ULA: (Global ID prefix)=C2=A0 A &=
quot;Unique Local Address&quot; (ULA) is an IPv6<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0address in the block=
 fc00::/7, defined in [RFC4193].=C2=A0 Sometimes<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0thought of as the ap=
proximate IPv6 counterpart of the IPv4 private<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0address ([RFC1918]),=
 there are important differences that are<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0beneficial for and e=
xploited by the ACP.=C2=A0 In this document, the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ULA prefix&quo=
t; refers to Locally Assigned Global ID prefixes, which<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0are the first 48-bit=
s of the ULA address [RFC4193 section 3.2.1].<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Beside the counterpart wordsmithing, <br>
&gt;=C2=A0 =C2=A0 =C2=A0i do not like the removal of pointing out that the =
ULA prefix is the<br>
&gt;=C2=A0 =C2=A0 =C2=A0new benefit of ULA that we exploit with ACP. That w=
as at the core of the<br>
&gt;=C2=A0 =C2=A0 =C2=A0explanation.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; (I didn&#39;t think it was worth trying to get=
 into the fc00::/8 vs fd00::/8<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; distinction in this glossary text.)<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I agree, but i do not see neither the glossary or t=
he rest of the text<br>
&gt;=C2=A0 =C2=A0 =C2=A0doing that. The spec part just specifies use of fd0=
0:/8 without<br>
&gt;=C2=A0 =C2=A0 =C2=A0discussion and the glossary just uses the ::/7 as t=
hats what rfc4193 say..<br>
&gt;=C2=A0 =C2=A0 =C2=A0Am i missing something ?<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; [ section 8.1.3 ]<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt; * Why is an RIO for ::/0 with a life=
time of 0 required?=C2=A0 Doesn&#39;t it<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; suffice<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0it set the default route=
r lifetime to 0?=C2=A0 Separately, are all nodes<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; required<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; &gt;=C2=A0 =C2=A0to be Type C?<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; Check the new text, i hope it explains ev=
erything.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; Yes, type A and B do not support per-pref=
ix auto selection of router,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; The lifetime of 0 is used so only Type C =
hosts will invalidate the<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; default route for the ACP edge node, but =
not Type A/B hosts. Maybe there<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; is another parameter combination that ach=
ieves this goal, but this was<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt; the easiest for me to assess/describe.<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; &gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; This looks better, thank you.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; To be honest, I don&#39;t know what the point =
of Type A/B hosts is anymore (and<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; if it were possible to declare these anima dep=
loyments greenfield I would<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; recommend saying the default router lifetime M=
UST be zero in the RA header<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; to force clients to use a stack that works -- =
but that&#39;s just me).<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I would guess that A and B have been seen in the wi=
ld before 4191 was<br>
&gt;=C2=A0 =C2=A0 =C2=A0released and so the RFC was written to be inclusive=
. No idea.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0I have no idea how prevalent these types are, and t=
he current described<br>
&gt;=C2=A0 =C2=A0 =C2=A0method may be a tiny bit more convoluted but seems =
to be more compatible.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Given my deployment experience of enterprises withh=
olding from adopting<br>
&gt;=C2=A0 =C2=A0 =C2=A0new network technology when it wasn&#39;t compatibl=
e with their oldest<br>
&gt;=C2=A0 =C2=A0 =C2=A0NMS equipment, i am a bit burned in promoting &quot=
;hard cut&quot; solutions, and<br>
&gt;=C2=A0 =C2=A0 =C2=A0this ben an OPS area draft instead of e.g.: RTG is =
a good excuse for that<br>
&gt;=C2=A0 =C2=A0 =C2=A0approach ;-))<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0Cheers<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Toerless<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0_______________________________________________<br>
&gt;=C2=A0 =C2=A0 =C2=A0Anima mailing list<br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:Anima@ietf.org" target=3D"_blank"=
>Anima@ietf.org</a><br>
&gt;=C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.org/mailman/listinfo/an=
ima" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/anima</a><br>
&gt; <br>
<br>
-- <br>
---<br>
<a href=3D"mailto:tte@cs.fau.de" target=3D"_blank">tte@cs.fau.de</a><br>
</blockquote></div>

--000000000000fc512b05b11d9e07--


From nobody Wed Oct  7 18:22:07 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B4FE3A09C4 for <anima@ietfa.amsl.com>; Wed,  7 Oct 2020 18:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level: 
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 lf5V0tzFmFLG for <anima@ietfa.amsl.com>; Wed,  7 Oct 2020 18:22:03 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 108C43A09AD for <anima@ietf.org>; Wed,  7 Oct 2020 18:22:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 20651389D0 for <anima@ietf.org>; Wed,  7 Oct 2020 21:27:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id I7oVgJWtEsXR for <anima@ietf.org>; Wed,  7 Oct 2020 21:27:24 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 631B1389CC for <anima@ietf.org>; Wed,  7 Oct 2020 21:27:24 -0400 (EDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 83D54C3B for <anima@ietf.org>; Wed,  7 Oct 2020 21:21:59 -0400 (EDT)
To: anima@ietf.org
References: <AM0PR10MB195656D42D37797072F4106CE7320@AM0PR10MB1956.EURPRD10.PROD.OUTLOOK.COM> <24741.1601393763@localhost>
From: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <d74a9d26-b28f-6074-26fa-24451c41da9c@sandelman.ca>
Date: Wed, 7 Oct 2020 21:21:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <24741.1601393763@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/N9SsEKOgLiENWxwtWJTmIkdOjjc>
Subject: Re: [Anima] BRSKI extensions design team - meeting
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 01:22:05 -0000

On 2020-09-29 11:36 a.m., Michael Richardson wrote:
> On *THIS* Thursday, I happen to have a conflict until 8am.
> But, next week, no problem at 7:30am.
> (Come to my webinar on Software Updates... iotsecurityfoundation.org/consumer-iot ...)

Hi, there was a meeting last week from 8:10am to just after 9am.
We met using https://meet.sandelman.ca/BRSKIDesignTeam
and it was fine for the group, but Cisco VPN users need to turn it off.

I did not capture much in the way of minutes.
Attendees were:
         1) Toerless. TE.
         3) Peter.               Constrained Voucher.  stateless proxy.
         4) Esko.                Constrained voucher + bootstrap process.
                                 Working with Thomas.
         5) Aurelio.             6tisch-zero-touch document.  ZHAW.
         7) Hendrik.             Siemens, AG. Steffen+Thomas. BRSKI,
                                  BRSKI-AE. Certificate management.
                                  Industrial use cases.
         6) Thomas.              Siemens. BRSKI implementation. Thread.
         7) Steffen Fries.       Siemens. BRSKI-AE. offline scenarios.
         8) Eliot.               Cisco. Fairhair. no single method.
         9) Max Pritikin.        Cisco. other things.

With the words there having to do with who was working on what.
I have a note that constrained-voucher would get a better set of 
examples.  I though that there was a PR from Peter to review, but now 
I've lost it!

constrained-voucher has 17 open issues, and 1 pull request:
   https://github.com/anima-wg/constrained-voucher/issues

I will take some this week, and make sure that the recording function works.

There will be another meeting tomorrow at 11:30UTC.
I updated the calendar invite to include the URL above.

I am working on a pull request for brski-ae now.


From nobody Wed Oct  7 19:44:26 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA15B3A0DFB for <anima@ietfa.amsl.com>; Wed,  7 Oct 2020 19:44:24 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 9c76L050wUMA for <anima@ietfa.amsl.com>; Wed,  7 Oct 2020 19:44:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34C533A09F4 for <anima@ietf.org>; Wed,  7 Oct 2020 19:44:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8E948389D0 for <anima@ietf.org>; Wed,  7 Oct 2020 22:49:46 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mJrpqKprctKq for <anima@ietf.org>; Wed,  7 Oct 2020 22:49:46 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2AD36389C6 for <anima@ietf.org>; Wed,  7 Oct 2020 22:49:46 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1D60B11A for <anima@ietf.org>; Wed,  7 Oct 2020 22:44:21 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: anima@ietf.org
In-Reply-To: <d74a9d26-b28f-6074-26fa-24451c41da9c@sandelman.ca>
References: <AM0PR10MB195656D42D37797072F4106CE7320@AM0PR10MB1956.EURPRD10.PROD.OUTLOOK.COM> <24741.1601393763@localhost> <d74a9d26-b28f-6074-26fa-24451c41da9c@sandelman.ca>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 07 Oct 2020 22:44:21 -0400
Message-ID: <10830.1602125061@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Gej0kD0kivOVAxCQ6bvCCDAy9os>
Subject: Re: [Anima] BRSKI extensions design team - meeting
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 02:44:25 -0000

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


Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > I am working on a pull request for brski-ae now.

Only, it's not in github that I can find.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl9+fQQACgkQgItw+93Q
3WXvcQf9FsXa+eVbTp5nu2eM8ap5lv/VzRGidOiGmELaf4nkZd+X4En1IslGkOJP
eYdISxUWGxS8tv2+x6rNXXKm0t+YQqHqMw3cUdg3mycAXkL9Ch9AFLcaFjLBtVvD
2Pa9YuQ/UNYBBp2mJxyO1Lfe1aHjN7cGUruLL8RsHf4jM8n2VFUGEoMJxsN1Wf83
ZGQSjMMaOi2+iKOar6HaHgLTXOVvXI8H1jB0faeooVZFSRaQcsWspJdQ/QkxvcyL
Fn4tpmETzlCQ13wUzgWM89e8fR9ZZq7rHmIl5iNH9mSZmS7U8gpjMQde7G8kj/yd
45MO+CpG6nagGdYpXfxq3M5eEPIqqA==
=Mhlc
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Oct  7 19:55:21 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A117F3A0E52 for <anima@ietfa.amsl.com>; Wed,  7 Oct 2020 19:55:19 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Xguu8MV4RaEy for <anima@ietfa.amsl.com>; Wed,  7 Oct 2020 19:55:17 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 323CA3A0E47 for <anima@ietf.org>; Wed,  7 Oct 2020 19:55:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4CA02389D0 for <anima@ietf.org>; Wed,  7 Oct 2020 23:00:41 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Rfj4AQa2gL1M for <anima@ietf.org>; Wed,  7 Oct 2020 23:00:40 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 85303389C6 for <anima@ietf.org>; Wed,  7 Oct 2020 23:00:40 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6C4F211A for <anima@ietf.org>; Wed,  7 Oct 2020 22:55:15 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <160212522084.3578.16492497792284322279@ietfa.amsl.com>
References: <160212522084.3578.16492497792284322279@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 07 Oct 2020 22:55:15 -0400
Message-ID: <13393.1602125715@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8bmxr0FYclPsuK9ieeSPRc1NDzk>
Subject: Re: [Anima] New Version Notification for draft-richardson-enrollment-roadmap-03.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 02:55:20 -0000

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


At last week's BRSKI extension meeting, I was asked to revise the
enrollment-roadmap document.  It is here.

I had previously abandonned it in favour of content in the IoTDIR wiki, but
many found that difficult to actually find.
I wish our IETF wiki spoke markdown.

There are numerous inaccuracies in the document!
I've tried to update the state of things as I know them.

I would appreciate comments and updates as you know them.
Pull requests to github.com/anima-wg/enrollment-roadmap.git

This is not intended to be adopted or published, but to remain a live docum=
ent.

    > Name:		draft-richardson-enrollment-roadmap
    > Revision:	03
    > Title:		Device Enrollment in IETF protocols -- A Roadmap
    > Document date:	2020-10-07
    > Group:		Individual Submission
    > Pages:		15
    > URL:            https://www.ietf.org/id/draft-richardson-enrollment-r=
oadmap-03.txt
    > Status:         https://datatracker.ietf.org/doc/draft-richardson-enr=
ollment-roadmap/
    > Htmlized:       https://datatracker.ietf.org/doc/html/draft-richardso=
n-enrollment-roadmap
    > Htmlized:       https://tools.ietf.org/html/draft-richardson-enrollme=
nt-roadmap-03
    > Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-richardson-=
enrollment-roadmap-03

    > Abstract:
    > This document provides an overview of enrollment or imprinting
    > mechanisms in current IETF protocols.

    > This document is being worked on in the ANIMA-WG, and on github at:
    > https://github.com/anima-wg/enrollment-roadmap




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

    > The IETF Secretariat




=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl9+f5MACgkQgItw+93Q
3WX6VAf6A4OCJ1v6tde/NtX7d3n+axGiBwFOdwGM5HUu/BSJBLP5S2B7EY3Vl71I
d7hOw2Wkgjz3wgaX2O1M2SfHrspAyil21Q8BSqTYAlGeiTNwaKBYhcDei4nEKSY9
buMBLlNJHCcCEab1ITESKHLVaKOgMk7bHkfskvyO7gL/bjemXrr2IUf8NTXMjYDk
7V3vEzgJ5La91aavMWAN7PPMuHN1Ov91jbCN9xGyKABAFI6nBowOO9RlTfElA0tH
By8NLLCNUtjLlCqcVMn6W5JSsGruwOzWX4fih91pnsvSQy/HoJTCP2VW0IPicseR
mqVpeoCsH3XUBRhmY5liEXC7+3nIAA==
=cDxG
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct  8 06:29:27 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872ED3A0B6E; Thu,  8 Oct 2020 06:29:25 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 yn8aCXjmGC3C; Thu,  8 Oct 2020 06:29:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F0223A0B01; Thu,  8 Oct 2020 06:29:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4CC61389B7; Thu,  8 Oct 2020 09:34:47 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mAoJVxYhpBrX; Thu,  8 Oct 2020 09:34:45 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B755338997; Thu,  8 Oct 2020 09:34:45 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 008464DB; Thu,  8 Oct 2020 09:29:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>, "anima-chairs\@ietf.org" <anima-chairs@ietf.org>
In-Reply-To: <20201001125721.GC34365@faui48f.informatik.uni-erlangen.de>
References: <20201001125721.GC34365@faui48f.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 08 Oct 2020 09:29:18 -0400
Message-ID: <2765.1602163758@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/5hZaaIWLPfCbXEwsuFK15UE6lCQ>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 109, online
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2020 13:29:26 -0000

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


Toerless Eckert <tte@cs.fau.de> wrote:
    > Name of time slot:
    > Name of draft(s) (if any, NOT REQUIRED, but usually desired ;-):
    > Amount of time requested:
    > Presenter name(s):

Hi.

Name of time slot: BRSKI-44 LC-prime summary of activity around rename
Name of draft(s): draft-ietf-anima-bootstrap-keyinfra
Amount of time requested: 6 minutes
Presenter name(s): Michael Richardson


Name of time slot: BRSKI-cloud use case/applicability
Name of draft(s): draft-friel-anima-brski-cloud-03
Amount of time requested: 6 minutes
Presenter name(s): Michael Richardson, Owen Friel


Name of time slot: Constrained-Voucher --- overview of changes from design =
team
Name of draft(s): draft-ietf-anima-constrained-voucher
Amount of time requested: 10 minutes
Presenter name(s): Michael Richardson, Peter van der Stok




=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl9/FC4ACgkQgItw+93Q
3WXdTAf+Mx0A3MwwcYDgZdh4ksxGwpGEWsAK9Ng6OqLjE6CxRXx4Xr5n4aieZMgn
iTY62483uFIiolWLfNTTeD4G5Qk8+K+SHvTRriWxuK2y6tEmCirScKU2hVNpPE2/
xiyAqnsMPPz0mLoipOXzO1Pi6SlfF0vpoekpR8czNqcK8JGJlxefD/2pD+SZVEo8
jaEaf9jdKzzT6VlSnz+oEWmtT5FzFkjLLW59TzzPEpw00cEPSrQjaaeJkJl09efH
u8gvL2kVWDoDct6Tv3wKlpaaRsofoDffzuEP+QXRMDFPSCyew8uSe8BiCBwtFgYF
RE5Si9OvbfNS/la9PqmvzT6o0/wFUw==
=nRUo
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Oct  9 06:11:07 2020
Return-Path: <steffen.fries@siemens.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19B53A003F for <anima@ietfa.amsl.com>; Fri,  9 Oct 2020 06:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 AXOtKgUsSOhT for <anima@ietfa.amsl.com>; Fri,  9 Oct 2020 06:11:05 -0700 (PDT)
Received: from gw-eagle2.siemens.com (gw-eagle2.siemens.com [194.138.20.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE4923A0039 for <anima@ietf.org>; Fri,  9 Oct 2020 06:11:04 -0700 (PDT)
Received: from mail2.dc4ca.siemens.de (mail2.dc4ca.siemens.de [139.25.224.94]) by gw-eagle2.siemens.com (Postfix) with ESMTPS id CFD8446800B; Fri,  9 Oct 2020 15:11:02 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (sop-solman.siemens.com [139.25.226.107]) by mail2.dc4ca.siemens.de (Postfix) with ESMTPS id 8820115E821B6; Fri,  9 Oct 2020 15:11:02 +0200 (CEST)
Received: from DEMCHDC89XA.ad011.siemens.net (139.25.226.103) by DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Fri, 9 Oct 2020 15:11:01 +0200
Received: from DEMCHDC89XA.ad011.siemens.net ([139.25.226.103]) by DEMCHDC89XA.ad011.siemens.net ([139.25.226.103]) with mapi id 15.01.2044.004;  Fri, 9 Oct 2020 15:11:01 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] BRSKI extensions design team - meeting
Thread-Index: AQHWnRF3yoU6UAA0a0i1w7DGmCYh1amM3i+AgAJivPA=
Content-Class: 
Date: Fri, 9 Oct 2020 13:11:01 +0000
Message-ID: <a1bf9b311ff64006a7c3919b6e1ab2f2@siemens.com>
References: <AM0PR10MB195656D42D37797072F4106CE7320@AM0PR10MB1956.EURPRD10.PROD.OUTLOOK.COM> <24741.1601393763@localhost> <d74a9d26-b28f-6074-26fa-24451c41da9c@sandelman.ca> <10830.1602125061@localhost>
In-Reply-To: <10830.1602125061@localhost>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2020-10-09T13:11:00Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=d60cb970-beb2-4a8d-98ac-722f20615a5a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
x-originating-ip: [139.25.107.175]
x-tm-snts-smtp: C38CEF58F6765597A4040FBD09123FC59BDF4FC971645944AD980D637E263A862000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/6U5jbGOfwNHx1aqOIwcLgcwTZcg>
Subject: Re: [Anima] BRSKI extensions design team - meeting
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2020 13:11:06 -0000

SGkgTWljaGFlbCwNCg0KSXQgaXMgb24gZ2l0aHViIG5vdy4gVGhhbmtzIHRvIFRob2FtcywgSSB3
YXMgYWJsZSB0byB1cGxvYWQgdGhlIGN1cnJlbnQgdmVyc2lvbiBhbmQgdGhlIHdvcmtpbmcgZG9j
dW1lbnQNCg0KQmVzdCByZWdhcmRzDQpTdGVmZmVuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gRnJvbTogQW5pbWEgPGFuaW1hLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBP
ZiBNaWNoYWVsIFJpY2hhcmRzb24NCj4gU2VudDogRG9ubmVyc3RhZywgOC4gT2t0b2JlciAyMDIw
IDA0OjQ0DQo+IFRvOiBhbmltYUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW0FuaW1hXSBCUlNL
SSBleHRlbnNpb25zIGRlc2lnbiB0ZWFtIC0gbWVldGluZw0KPiANCj4gDQo+IE1pY2hhZWwgUmlj
aGFyZHNvbiA8bWNyK2lldGZAc2FuZGVsbWFuLmNhPiB3cm90ZToNCj4gICAgID4gSSBhbSB3b3Jr
aW5nIG9uIGEgcHVsbCByZXF1ZXN0IGZvciBicnNraS1hZSBub3cuDQo+IA0KPiBPbmx5LCBpdCdz
IG5vdCBpbiBnaXRodWIgdGhhdCBJIGNhbiBmaW5kLg0KPiANCj4gLS0NCj4gTWljaGFlbCBSaWNo
YXJkc29uIDxtY3IrSUVURkBzYW5kZWxtYW4uY2E+ICAgLiBvIE8gKCBJUHY2IEnDuFQgY29uc3Vs
dGluZyApDQo+ICAgICAgICAgICAgU2FuZGVsbWFuIFNvZnR3YXJlIFdvcmtzIEluYywgT3R0YXdh
IGFuZCBXb3JsZHdpZGUNCj4gDQo+IA0KPiANCg0K


From nobody Fri Oct  9 10:33:06 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22EB3A0DA4 for <anima@ietfa.amsl.com>; Fri,  9 Oct 2020 10:32:58 -0700 (PDT)
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=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 500TsD6MFwZx for <anima@ietfa.amsl.com>; Fri,  9 Oct 2020 10:32:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5A73A0D57 for <anima@ietf.org>; Fri,  9 Oct 2020 10:32:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 4F8D2389A8 for <anima@ietf.org>; Fri,  9 Oct 2020 13:38:25 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9xh59_HZs1Iv for <anima@ietf.org>; Fri,  9 Oct 2020 13:38:24 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id DAA7938998 for <anima@ietf.org>; Fri,  9 Oct 2020 13:38:24 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B42AD18B for <anima@ietf.org>; Fri,  9 Oct 2020 13:32:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 09 Oct 2020 13:32:53 -0400
Message-ID: <15324.1602264773@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/N-1b6P4vuTU8rma1XrpP5yL1M3w>
Subject: [Anima] NIST and BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2020 17:33:05 -0000

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


A google alert found this:

https://www.nist.gov/publications/formal-verification-bootstrapping-remote-=
secure-key-infrastructures-brski-protocol

By some authors known to this WG.

Author(s)
Monika Singh, Mudumbai Ranganathan
Abstract

The last decade has seen significant growth in the number of IoT
devices. These devices can connect to each other and networks. The process
through which a new IoT device connects to the network and subsequently
enables its services is called bootstrapping. A single entity connecting
large numbers of new IoT devices to networks makes manual bootstrapping
infeasible. It requires an automated system to enable a new device to be
located and securely onboard the network. The Bootstrapping Remote Secure K=
ey
Infrastructure (BRSKI) protocol is one of the well-known protocols that
provides a way for secure device onboarding. In this work, we present the
first formal security analysis of the BRSKI protocol using a verification
tool called AVISPA (Automated Validation of Internet Security Protocols and
Applications). AVISPA provides a formal security validation of any network
protocol by building and analyzing the formal security models of that
protocols operations.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+AnsUACgkQgItw+93Q
3WWctwf+NO+Pc4wzRV8zNXVqPpRQvT+andAzwl7Q+x+JwZaXKZj0aoNhYKZXhK5E
MQQsUARlWUA5eKmgfcdhnlPNHChnPVbluAZdNzKVXNOFY5eM2zRug20W0/gYf12i
OcFyc8H2qzooQH8oyt3hWab/F8dEaTV8TtuKmGGUp9RfzNtvUJ8WqXuR5RdlupbT
mk5WiBDjOgqAKrlbjpR5w2NB0R47lGlkDiadw3UTG7J7VsvEv/MMkCC2qpJjkpYs
StDp0bxzlIKJiYKbMuJtGxQDt8qevyau3Iy393CHbsLXCFBdmQRhz3izbWrD1YGL
bvGqj2WvTCTK/ZpjpM1IOCrWKvGArA==
=mGsa
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Oct 13 15:12:13 2020
Return-Path: <session-request@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 759883A11B2; Tue, 13 Oct 2020 15:12:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: anima-chairs@ietf.org, lflynn@amsl.com, anima@ietf.org, rwilton@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160262713100.7428.18281945575336971254@ietfa.amsl.com>
Date: Tue, 13 Oct 2020 15:12:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/U5LONBsYbdhDU9WgV4A56a5uN8w>
Subject: [Anima] anima - New Meeting Session Request for IETF 109
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2020 22:12:11 -0000

A new meeting session request has just been submitted by Liz Flynn, on behalf of the anima working group.


---------------------------------------------------------
Working Group Name: Autonomic Networking Integrated Model and Approach
Area Name: Operations and Management Area
Session Requester: Liz Flynn


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 60
Conflicts to Avoid: 
 Chair Conflict: bier pim mboned 6man 6lo 6tisch ace
 Technology Overlap: emu netconf homenet roll
 Key Participant Conflict: nmrg panrg dinrg opsarea intarea saag cfrg detnet





People who must be present:
  Toerless T. Eckert
  Sheng Jiang
  Robert Wilton

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Tue Oct 13 19:59:44 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 94B753A0D9A; Tue, 13 Oct 2020 19:59:42 -0700 (PDT)
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>
Cc: anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <160264438254.12888.5559910355899486306@ietfa.amsl.com>
Date: Tue, 13 Oct 2020 19:59:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/xtBZMagJ18YGify4LildLfUCJSo>
Subject: [Anima] I-D Action: draft-ietf-anima-grasp-api-07.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 02:59:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.

        Title           : Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)
        Authors         : Brian Carpenter
                          Bing Liu
                          Wendong Wang
                          Xiangyang Gong
	Filename        : draft-ietf-anima-grasp-api-07.txt
	Pages           : 32
	Date            : 2020-10-13

Abstract:
   This document is a conceptual outline of an application programming
   interface (API) for the Generic Autonomic Signaling Protocol (GRASP).
   Such an API is needed for Autonomic Service Agents (ASA) calling the
   GRASP protocol module to exchange autonomic network messages with
   other ASAs.  Since GRASP is designed to support asynchronous
   operations, the API will need to be adapted to the support for
   asynchronicity in various programming languages and operating
   systems.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-anima-grasp-api-07.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-grasp-api-07


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 Tue Oct 13 20:05:33 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8113A1156 for <anima@ietfa.amsl.com>; Tue, 13 Oct 2020 20:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L16och3qEa-6 for <anima@ietfa.amsl.com>; Tue, 13 Oct 2020 20:05:29 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 C8F893A02BD for <anima@ietf.org>; Tue, 13 Oct 2020 20:05:29 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id ds1so693317pjb.5 for <anima@ietf.org>; Tue, 13 Oct 2020 20:05:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=bezGGtS7rQmo12EIDqZQzeXv/pEPh8M6K6mBoNwMP+w=; b=S9+2iZXUx/yUtj+VgCaqj7gDeoj+EX9BHi0RAWOyvyjA4zfH4yAaGJxM3IiROOSQ3q jI5QsNaizYupgxZCL1LlUxku9iowT8zVoaCFxcjNb58v+H9FCpUlPYUGvrx15SnkWqfZ ACj2pRlulyVX+JwIDh7L3pqVspd931vRZO2TUEmPD0PT4rhvrw3kvBZKeULbQPjPKGqS KXQQXJo2SPTJFTJe8zWp6l53/oxgIRoRGjSsYE8ksmnFmPHofVpnu0TPFlchZxm/nVI4 SwaCkCgn250vJ2GL05qxJz9JW92c4Hua5o0djS3jbquzkFj/LDY+oHw4Wr5oq8KXo8KU 7jtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bezGGtS7rQmo12EIDqZQzeXv/pEPh8M6K6mBoNwMP+w=; b=QNzqPaLtH81GExLU8B9qMWYwpbfyORFf9sPWNINiaKWp+AhZcsnRWPxQ4KeOLpb9P3 a+JaB0nQoCFBO0X7N9ibUYqJtz/xtmXn5pDW93/EbgOyzn+rdMmlPXMd4U/I/mtRGnyL RalTB7NUp/nemwctqeAvhzlGUaGmwgAbkrgiSKCyX426+y+tNfsGwfiSQp+uVNg7/+Yu SQlS3zcp/rAZ5mPtUv02LgZTWttv2qxYaVyjQPxQa4sTIS8aCegPAGVe3Wx5cBShFA9E Yy5uoJBHuYX6Q/VGDJ6sbWy6jBS1oNEVXxZ6WaPgG2cVFrtSP3h4Dqczkmiva4xd+AMN wi2w==
X-Gm-Message-State: AOAM531l9HvnH75YoplzUReTrYxEL3frzolbDJ6bh0NVkQvhv+8a3jFj iorr9BlX5rdRM81dhuuHskjDpI2v/0uluQ==
X-Google-Smtp-Source: ABdhPJwhhW09/kPYq4o0T4ItqTOhOIWyopNAag7jftRqj8RMtqq4/QrZuvF3151QHe3nE+FTdYfMQg==
X-Received: by 2002:a17:90a:f0c6:: with SMTP id fa6mr1404257pjb.12.1602644728796;  Tue, 13 Oct 2020 20:05:28 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.159]) by smtp.gmail.com with ESMTPSA id b6sm733996pjq.42.2020.10.13.20.05.27 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Oct 2020 20:05:28 -0700 (PDT)
To: anima@ietf.org
References: <160264438254.12888.5559910355899486306@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bc208115-5f6b-1dba-e690-256bcc62d12f@gmail.com>
Date: Wed, 14 Oct 2020 16:05:25 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160264438254.12888.5559910355899486306@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/2XtBxrZGHOwgr37DwiIK6_faUHg>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-grasp-api-07.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 03:05:32 -0000

Hi,

This version has been updated following the excellent AD review.

* Improved diagram and its description
* Added pointer to example logic flows
* Added note on variable length parameters
* Clarified that API decrements loop count automatically
* Other corrections and clarifications from AD review

Regards
   Brian + co-authors

On 14-Oct-20 15:59, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.
> 
>         Title           : Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)
>         Authors         : Brian Carpenter
>                           Bing Liu
>                           Wendong Wang
>                           Xiangyang Gong
> 	Filename        : draft-ietf-anima-grasp-api-07.txt
> 	Pages           : 32
> 	Date            : 2020-10-13
> 
> Abstract:
>    This document is a conceptual outline of an application programming
>    interface (API) for the Generic Autonomic Signaling Protocol (GRASP).
>    Such an API is needed for Autonomic Service Agents (ASA) calling the
>    GRASP protocol module to exchange autonomic network messages with
>    other ASAs.  Since GRASP is designed to support asynchronous
>    operations, the API will need to be adapted to the support for
>    asynchronicity in various programming languages and operating
>    systems.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-anima-grasp-api-07.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-grasp-api-07
> 
> 
> 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/
> 
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> 


From nobody Wed Oct 14 06:24:08 2020
Return-Path: <rwilton@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C23E3A0AB7 for <anima@ietfa.amsl.com>; Wed, 14 Oct 2020 06:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level: 
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=DWN6be5W; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=bZccfEtw
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 KTQWon8mNb7w for <anima@ietfa.amsl.com>; Wed, 14 Oct 2020 06:24:05 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A23B33A0A88 for <anima@ietf.org>; Wed, 14 Oct 2020 06:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2988; q=dns/txt; s=iport; t=1602681845; x=1603891445; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=G/zV66bxHUw7e3EKrH/xlWsXT5FjS+PfYbewUHbVPyc=; b=DWN6be5WKp0/Y59arepvrHMhBgHVmU/K7jMApeHur28JCxgv2x0d1K9r NCDulWyP437FWgiV4a6L+oX4/AoOlYIqlqiywmjmoddAX7RLHT/dgveqH WRGBmHn9YLAj4K4ycv/VS2fGQNy9km934qfHQB4qul75tXQme1jlLlnhN I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AFQaVPh9TpmsAW/9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+7ZRCN6vBkjVuPVoLeuLpIiOvT5qbnX2FIoZOMq2sLf5EEUR?= =?us-ascii?q?gZwd4XkAotDI/gawX7IffmYjZ8EJFEU1lorH6+OElRXs35Yg6arni79zVHHB?= =?us-ascii?q?L5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BEEQDm+oZf/4QNJK1gHQEBPAEFBQE?= =?us-ascii?q?CAQkBFYFRgVBRB3BZLywKh3kDjVGYe4JTA1ULAQEBDQEBGAsKAgQBAYRKAoI?= =?us-ascii?q?CAiU4EwIDAQELAQEFAQEBAgEGBG2FXAyFcgEBAQQBARAoBgEBLAwLBAIBCBE?= =?us-ascii?q?EAQEBHhAnCx0IAgQBEggagwWCSwMuAQMLniQCgTmIYXSBNIMBAQEFgTcCDkG?= =?us-ascii?q?DExiCEAmBOAGCcYpEG4FBP4FUgk0+glwBAQEBAQEVgUiDSIItkDSnPAqCaok?= =?us-ascii?q?EkgyDFYEqiF6UJpMpinGVOAIEAgQFAg4BAQWBayM2gSFwFRohgmkJRxcCDZI?= =?us-ascii?q?QhRSFQnQCNgIGCgEBAwl8jDsBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.77,374,1596499200"; d="scan'208";a="562301632"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 Oct 2020 13:24:04 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 09EDO2E8015017 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 14 Oct 2020 13:24:03 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 14 Oct 2020 08:24:02 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 14 Oct 2020 08:24:01 -0500
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 14 Oct 2020 08:24:01 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=d6gcqFv8XgbbgFoTCyBZgVx696P6TErCfHgErquuEKaf2jZelyMezBW4LKdh4gAFX7/T5A4q3Y98Ax2Chv1wZ6Ss0ECAE9xYz6vmZSZdU6iCSgi4yi/ztJ8k0vPT7itGXyJSvjImQOfJH6t0BCSKJKX9ZLgPCNF3ogcVz8BW0Gb0O0Aqf0RTgry3yxSMsA0+SYsqEDOU96qtLXijIdYzCE6NSEBgYkAHF+QvAxJA4WXXVeEok8Hi0CAt+Ak57lvn0S03bMk3/rKVrISkLVw5QKjUusmyOYWuumi1ToLu6b13VeWeoUVPuUD2Xf2O0WD+plXtAJ7ttVoVJ9jvjcRFjg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9DNtQu7nlMJtexLAW2Ant+gYO1dqwMp0SFX4Qb2nJb8=; b=XOXQvaoORiiPXU8s+8JccaDVz2C2WNCpQjwgvRgFRMVHshxzmuTVlY5k0F6F16d/rn7yxRbHcW590zEB+yNeqN3Q4Wf8N2v3JjxuE4lxveclffH7zl10txuzPOm+cxcItDWdU+qXXGdJ3DbLTmHSgBo94XHre97XB0+QN27PADRFLlpB1WThKjf11K5AEZJZh1tOOXpzF+NyE2FffMdga0j4F0NVHb2r+LIBJk/+i+FD9FEultwNqzGlH/R3+HCLjWwFaHV5oNWumhrvbVe7L0o89TdH8N8ITIxD4vV5OZm0ov+ge83Ozq0mSqp+wwZaRD9f51gRsBhWPIfQU/6RGQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9DNtQu7nlMJtexLAW2Ant+gYO1dqwMp0SFX4Qb2nJb8=; b=bZccfEtwMe0elTI0OCYBoorvjR+Ke5GYaMx6WQnltEnNueVgvPbQ8EYJqHqDrGFOrfQIFjT3wsy4EoY8ZvDni3FCfpapFwGkYK3MCop1XXFI7wYGKHwEfkATV3icGehslAHn1pPjVh4s5qs264UoU/JcOLhyc4TUunfc+5woTsg=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by MN2PR11MB4551.namprd11.prod.outlook.com (2603:10b6:208:269::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.23; Wed, 14 Oct 2020 13:24:00 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241%4]) with mapi id 15.20.3455.030; Wed, 14 Oct 2020 13:24:00 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] I-D Action: draft-ietf-anima-grasp-api-07.txt
Thread-Index: AQHWodYjHMvSqKEZfEGDKRMMapJ4DqmWagyAgACsfpA=
Date: Wed, 14 Oct 2020 13:24:00 +0000
Message-ID: <MN2PR11MB436641A415B734E9C1C1DB25B5050@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <160264438254.12888.5559910355899486306@ietfa.amsl.com> <bc208115-5f6b-1dba-e690-256bcc62d12f@gmail.com>
In-Reply-To: <bc208115-5f6b-1dba-e690-256bcc62d12f@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [82.12.233.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f02fec84-c6f7-42c0-5ac2-08d87044696e
x-ms-traffictypediagnostic: MN2PR11MB4551:
x-microsoft-antispam-prvs: <MN2PR11MB4551710FAA96B95919D00BA8B5050@MN2PR11MB4551.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: I1lXGi1J3xwpEGYo5zZTEa1rT4Ev+bYC/WR2QY+lIn63iwjs7d06vQ9NqYBfegEQU9HT7zK0aTW8hvB6GtMHUq9bYcZEeqfEZIboRihqMjpLiiH87kuVhXcMRC3+mHcLNtg0ZAxqE/uC/MBmUXfY7jMT7Tgb/76KkM8OV9XrnwfA2vwN94sEvX+LA4iM1W3EITXQGBSausPOXiowBu5m3mZQy+2nEPNbZwWhnW9syn9CutHBdlUD6UsUc2ZZtY9ZyL/MoZCHSKb2fG6izLl7xQ7NqhiWtu0aGXfFtrWA+8lDlu7cS8Q4DdKY2ifhQr7nunHB8feAsexwptmgKLnHU5atoD8Fsv0X9d3KlsXqfaTP4GM0hjstTsWADLk63Sa8cH3bosErL5ZDL/+4voNbqw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(39860400002)(136003)(346002)(376002)(396003)(366004)(33656002)(64756008)(478600001)(66446008)(6506007)(52536014)(8676002)(8936002)(7696005)(5660300002)(4001150100001)(71200400001)(2906002)(53546011)(110136005)(316002)(55016002)(9686003)(66574015)(186003)(66556008)(83080400001)(66946007)(966005)(86362001)(76116006)(83380400001)(26005)(66476007); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: p9jvDKgdzO3hauawPxiPlwaEodZ70SboyfkdFEH3/Sc4jds0WaoR5Ct+Pf8Qx9RjH1HgF0Gl71F8VnPmeBviwwmlJwkyU8oKJuW7oIWvKprxG3aw2PlR/eRAgWQ9oabFf5UgJUkGUDTjWK2Ce7KcEMTgu7uOEY6hhNP0EWmCMV7wVU5LZXvkZMUrB0fkovKUF9A7yIYvrwF5Vost7bKhRmCXX/q8scLd9XuSK6aOwRVZsqmRM4stnXjOfNNtMhS4t27fn8DdGXjazwGtw4e3ANjnhmIm6cn1g898x9q+Ame7ghh1juUuFuyuRuEnENqHg7DGOfTqQGQkQ4F7KGx0tXFyCoqrrni4z/vG9fb7UqhsCGbUPvExtHxqt1h52ngSqIm8hqyXCT/TJjTJHPEDdwmLVCRp2rL4kA/e8dvGYdhvjtJ1C5aNEuV8alzJ/rKNvgiFOrfAtqhsQ30xwtSbethvyv1OUvca8e540NLX/3BCxhfG9tv4re5zPzh92pwG/CrW02f7ZR7m/OX8JH4p1UqW9xMrmNFY6edD6/EyTYpUSe+71eL/KY67AH+HbvdvSAuRD9sU0JHOZVbhjtltjGgq4zjfWEC349R0n6zUJQaYpRGnwG592Vft7KcRzgNLCcu/r8v0MzbUZxTOySNciw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB4366.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f02fec84-c6f7-42c0-5ac2-08d87044696e
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2020 13:24:00.1252 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: oZT55jhghozNrAy2gO6LQEEz79O5/J1MdSE3l8t1crS9JFwPMtxeA1ui37Qn19rGOggvchn1NmtSTNAnWEM24w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4551
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/s_qpWhEYFh-f71aEl1S8-O4w4yE>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-grasp-api-07.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 13:24:08 -0000

Thanks for the work on this document and being responsive to my comments.  =
Apologies again for the delay in my AD review.

I've kicked off the IETF LC.

Regards,
Rob


> -----Original Message-----
> From: Anima <anima-bounces@ietf.org> On Behalf Of Brian E Carpenter
> Sent: 14 October 2020 04:05
> To: anima@ietf.org
> Subject: Re: [Anima] I-D Action: draft-ietf-anima-grasp-api-07.txt
>=20
> Hi,
>=20
> This version has been updated following the excellent AD review.
>=20
> * Improved diagram and its description
> * Added pointer to example logic flows
> * Added note on variable length parameters
> * Clarified that API decrements loop count automatically
> * Other corrections and clarifications from AD review
>=20
> Regards
>    Brian + co-authors
>=20
> On 14-Oct-20 15:59, internet-drafts@ietf.org wrote:
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > This draft is a work item of the Autonomic Networking Integrated Model
> and Approach WG of the IETF.
> >
> >         Title           : Generic Autonomic Signaling Protocol
> Application Program Interface (GRASP API)
> >         Authors         : Brian Carpenter
> >                           Bing Liu
> >                           Wendong Wang
> >                           Xiangyang Gong
> > 	Filename        : draft-ietf-anima-grasp-api-07.txt
> > 	Pages           : 32
> > 	Date            : 2020-10-13
> >
> > Abstract:
> >    This document is a conceptual outline of an application programming
> >    interface (API) for the Generic Autonomic Signaling Protocol (GRASP)=
.
> >    Such an API is needed for Autonomic Service Agents (ASA) calling the
> >    GRASP protocol module to exchange autonomic network messages with
> >    other ASAs.  Since GRASP is designed to support asynchronous
> >    operations, the API will need to be adapted to the support for
> >    asynchronicity in various programming languages and operating
> >    systems.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-ietf-anima-grasp-api-07.html
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-anima-grasp-api-07
> >
> >
> > 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/
> >
> >
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima
> >
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Wed Oct 14 06:24:14 2020
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB623A0AA0; Wed, 14 Oct 2020 06:24:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: rwilton@cisco.com, jiangsheng@huawei.com, Sheng Jiang <jiangsheng@huawei.com>, draft-ietf-anima-grasp-api@ietf.org, anima@ietf.org, anima-chairs@ietf.org
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160268184860.3332.4510035010071284061@ietfa.amsl.com>
Date: Wed, 14 Oct 2020 06:24:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/AejfDlCEnbUMXJns0QXjptDcW9k>
Subject: [Anima] Last Call: <draft-ietf-anima-grasp-api-07.txt> (Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)) to Informational RFC
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 13:24:09 -0000

The IESG has received a request from the Autonomic Networking Integrated
Model and Approach WG (anima) to consider the following document: - 'Generic
Autonomic Signaling Protocol Application Program Interface
   (GRASP API)'
  <draft-ietf-anima-grasp-api-07.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-10-28. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document is a conceptual outline of an application programming
   interface (API) for the Generic Autonomic Signaling Protocol (GRASP).
   Such an API is needed for Autonomic Service Agents (ASA) calling the
   GRASP protocol module to exchange autonomic network messages with
   other ASAs.  Since GRASP is designed to support asynchronous
   operations, the API will need to be adapted to the support for
   asynchronicity in various programming languages and operating
   systems.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/



No IPR declarations have been submitted directly on this I-D.






From nobody Wed Oct 14 12:34:48 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 976413A0FEB for <anima@ietfa.amsl.com>; Wed, 14 Oct 2020 12:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXX7cLYFNaFg for <anima@ietfa.amsl.com>; Wed, 14 Oct 2020 12:34:45 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 E67893A0FA6 for <anima@ietf.org>; Wed, 14 Oct 2020 12:34:44 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id b23so285017pgb.3 for <anima@ietf.org>; Wed, 14 Oct 2020 12:34:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=evKBMteErXcZHGQYDONli/yUiVota9+suae/zRJrw2E=; b=X3topAUAfRDNYZdL51ONuOIZaDg3H0Icsk091ejdLJlPEh9UkzUlSIzkbJF8acURbJ FwKBD/gAwtuWRR7+rGa7o7oJlK2hflCwJBOIhLWztXKhQFu/Y14TaxBuQqRPolQZU22C af6WRATMGx+KLoP3zF8VGKYTXd5o5R8F0ywqC4NLDOhxFLtpEGfdUhRrgWUKIuYhtoy1 TDjc9K/NLRpuXe3uwTd2aoUPm5xJ1x6hnkub3EUniJePOMH1f6/eGlhSHMJjgLCgJVRG 7aJMq8/fA81qFtciU49yvR6L5KHP2CQU7QETtPa/MFrBV0PK5rmSOgYp/NLS2fyCeWsY TmrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=evKBMteErXcZHGQYDONli/yUiVota9+suae/zRJrw2E=; b=DmAPptSgdwrI64WB7u5izOxwwSV02Ml/cPAI+smASQC9iANqb38Porki58ZKHOKWFC 6xNYOnlIXRhzHoEZI1twAAaqCTVcEocig95f3s2o7rp8NU9wvWSxWDDUATmmkijfvo0U j1h0hTelhxJB2JNkpboSEy6YqZXve8PWf+qFCDMsO8NcGsCfTzDTEJwGy8uHv+vuGkkW NqodaloQI9/rrS7sDM5EfE740zmmOO4Y1QYjiEAl+lpXUnwo6NIGxUIdBDy0M1VLCp8j XSHUOgJwFPgKL8sUvXLcyIua6h01LtPnqTLsYv2xGwO7TMclbZBaByAH4a1QSifw8ddQ cY2w==
X-Gm-Message-State: AOAM533kOZPRQZdFvXvizLhy8BFLqOgS8Ta09+RQJVAlAoP/OCqmUjqk cGt0+PziIQ7py65cbzqPRmQ2oTllQTcGkA==
X-Google-Smtp-Source: ABdhPJxO0U8rzdgpeDiV5Qkt+F+m39O71+ypo2thy1o1GEMAFChl2C4h89sfagdxYkmev7gVXL16qQ==
X-Received: by 2002:a63:f20:: with SMTP id e32mr437162pgl.61.1602704084377; Wed, 14 Oct 2020 12:34:44 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.159]) by smtp.gmail.com with ESMTPSA id f204sm409383pfa.189.2020.10.14.12.34.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Oct 2020 12:34:43 -0700 (PDT)
To: Anima WG <anima@ietf.org>
Cc: Toerless Eckert <tte@cs.fau.de>
References: <159573875486.18377.8979475359746431653@ietfa.amsl.com> <9beb2b46-8a08-1d45-1f1b-3bd50283fe20@gmail.com> <15a6fcb1-998c-929f-b039-1c27e09e5058@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <75d275d1-87d2-587b-6e67-765e5d91e582@gmail.com>
Date: Thu, 15 Oct 2020 08:34:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <15a6fcb1-998c-929f-b039-1c27e09e5058@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/go9laL00l7N-S-lXUCMZmL9oKsY>
Subject: Re: [Anima] Fwd: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 19:34:47 -0000

Again - when will the chairs issue the adoption call for this draft? I really don't see a need to discuss it in the WG meeting again. If it was my choice I'd take it to WG Last Call ASAP so that it can catch up with the other documents.

If there is no support for this draft please tell us. At the AD's request, we added a reference to it in draft-ietf-anima-grasp-api-07. If draft-carpenter-anima-asa-guidelines is not going to advance, I would prefer to move the relevant material into the API draft as an appendix.

Decision please!

Regards
   Brian Carpenter

On 03-Oct-20 16:57, Brian E Carpenter wrote:
> I was hoping we'd have an adoption call for this document after version 09 was posted, but I got distracted by other matters. Could we do that now? I can't really justify an agenda slot for it, unless the adoption call produces issues that need discussion.
> 
> I recommend reading the html version at https://www.ietf.org/id/draft-carpenter-anima-asa-guidelines-09.html
> 
> Regards
>    Brian Carpenter
> 
> On 26-Jul-20 16:53, Brian E Carpenter wrote:
>> This is a minor update - a few extra words on authorization of ASAs,
>> and editorial fixes.
>>
>>    Brian + co-authors
>>
>> -------- Forwarded Message --------
>> Subject: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
>> Date: Sat, 25 Jul 2020 21:45:54 -0700
>> From: internet-drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>>
>>         Title           : Guidelines for Autonomic Service Agents
>>         Authors         : Brian Carpenter
>>                           Laurent Ciavaglia
>>                           Sheng Jiang
>>                           Pierre Peloso
>> 	Filename        : draft-carpenter-anima-asa-guidelines-09.txt
>> 	Pages           : 26
>> 	Date            : 2020-07-25
>>
>> Abstract:
>>    This document proposes guidelines for the design of Autonomic Service
>>    Agents for autonomic networks, as a contribution to describing an
>>    autonomic ecosystem.  It is based on the Autonomic Network
>>    Infrastructure outlined in the ANIMA reference model, using the
>>    Autonomic Control Plane and the Generic Autonomic Signaling Protocol.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-carpenter-anima-asa-guidelines-09
>> https://datatracker.ietf.org/doc/html/draft-carpenter-anima-asa-guidelines-09
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-carpenter-anima-asa-guidelines-09
>>
>>
>> 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/
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>


From nobody Wed Oct 14 18:14:23 2020
Return-Path: <jiangsheng@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8073A11A3 for <anima@ietfa.amsl.com>; Wed, 14 Oct 2020 18:14:21 -0700 (PDT)
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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 e41TZD3vwbfI for <anima@ietfa.amsl.com>; Wed, 14 Oct 2020 18:14:19 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 8CB4F3A11A2 for <anima@ietf.org>; Wed, 14 Oct 2020 18:14:19 -0700 (PDT)
Received: from lhreml722-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 9D74D1EA7D91881622A6; Thu, 15 Oct 2020 02:14:16 +0100 (IST)
Received: from nkgeml704-chm.china.huawei.com (10.98.57.158) by lhreml722-chm.china.huawei.com (10.201.108.73) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 15 Oct 2020 02:14:16 +0100
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by nkgeml704-chm.china.huawei.com (10.98.57.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 15 Oct 2020 09:14:13 +0800
Received: from nkgeml708-chm.china.huawei.com ([10.98.57.160]) by nkgeml708-chm.china.huawei.com ([10.98.57.160]) with mapi id 15.01.1913.007; Thu, 15 Oct 2020 09:14:13 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Anima WG <anima@ietf.org>
CC: Toerless Eckert <tte@cs.fau.de>
Thread-Topic: [Anima] Fwd: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
Thread-Index: AQHWmTl8oL1kbMON4Eqo66w1iDjXyamXCY+AgADixzA=
Date: Thu, 15 Oct 2020 01:14:13 +0000
Message-ID: <5a5abe817982403f912c9bfbdb44012b@huawei.com>
References: <159573875486.18377.8979475359746431653@ietfa.amsl.com> <9beb2b46-8a08-1d45-1f1b-3bd50283fe20@gmail.com> <15a6fcb1-998c-929f-b039-1c27e09e5058@gmail.com> <75d275d1-87d2-587b-6e67-765e5d91e582@gmail.com>
In-Reply-To: <75d275d1-87d2-587b-6e67-765e5d91e582@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.235.253]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/r72K0Fc631YBL-WBmtDKYRv5uQw>
Subject: Re: [Anima] Fwd: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 01:14:21 -0000

Hi, Brian,

Yes, the adoption call is in our plan for, which covers four documents.  Th=
e chairs had an agreement on this after last meeting. Also the voucher-dele=
gation adoption should follow afterward.

It has to be Toerless to take action on this document. I did send a remind =
email to him almost three weeks ago and have not received his reply. He may=
 be in holiday or taken by ACP heavy workload. Hopefully, he will launch th=
e adoption call soon when he see this email. Thanks for your contribution a=
nd patient.

Best regards,

Sheng

> -----Original Message-----
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Brian E
> Carpenter
> Sent: Thursday, October 15, 2020 3:35 AM
> To: Anima WG <anima@ietf.org>
> Cc: Toerless Eckert <tte@cs.fau.de>
> Subject: Re: [Anima] Fwd: I-D Action: draft-carpenter-anima-asa-guideline=
s-
> 09.txt
>=20
> Again - when will the chairs issue the adoption call for this draft? I re=
ally don't
> see a need to discuss it in the WG meeting again. If it was my choice I'd=
 take it
> to WG Last Call ASAP so that it can catch up with the other documents.
>=20
> If there is no support for this draft please tell us. At the AD's request=
, we
> added a reference to it in draft-ietf-anima-grasp-api-07. If draft-carpen=
ter-
> anima-asa-guidelines is not going to advance, I would prefer to move the
> relevant material into the API draft as an appendix.
>=20
> Decision please!
>=20
> Regards
>    Brian Carpenter
>=20
> On 03-Oct-20 16:57, Brian E Carpenter wrote:
> > I was hoping we'd have an adoption call for this document after version=
 09
> was posted, but I got distracted by other matters. Could we do that now? =
I
> can't really justify an agenda slot for it, unless the adoption call prod=
uces
> issues that need discussion.
> >
> > I recommend reading the html version at
> > https://www.ietf.org/id/draft-carpenter-anima-asa-guidelines-09.html
> >
> > Regards
> >    Brian Carpenter
> >
> > On 26-Jul-20 16:53, Brian E Carpenter wrote:
> >> This is a minor update - a few extra words on authorization of ASAs,
> >> and editorial fixes.
> >>
> >>    Brian + co-authors
> >>
> >> -------- Forwarded Message --------
> >> Subject: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
> >> Date: Sat, 25 Jul 2020 21:45:54 -0700
> >> From: internet-drafts@ietf.org
> >> Reply-To: internet-drafts@ietf.org
> >> To: i-d-announce@ietf.org
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>
> >>
> >>         Title           : Guidelines for Autonomic Service Agents
> >>         Authors         : Brian Carpenter
> >>                           Laurent Ciavaglia
> >>                           Sheng Jiang
> >>                           Pierre Peloso
> >> 	Filename        : draft-carpenter-anima-asa-guidelines-09.txt
> >> 	Pages           : 26
> >> 	Date            : 2020-07-25
> >>
> >> Abstract:
> >>    This document proposes guidelines for the design of Autonomic Servi=
ce
> >>    Agents for autonomic networks, as a contribution to describing an
> >>    autonomic ecosystem.  It is based on the Autonomic Network
> >>    Infrastructure outlined in the ANIMA reference model, using the
> >>    Autonomic Control Plane and the Generic Autonomic Signaling Protoco=
l.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines
> >> /
> >>
> >> There are also htmlized versions available at:
> >> https://tools.ietf.org/html/draft-carpenter-anima-asa-guidelines-09
> >> https://datatracker.ietf.org/doc/html/draft-carpenter-anima-asa-guide
> >> lines-09
> >>
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=3Ddraft-carpenter-anima-asa-guidelin=
e
> >> s-09
> >>
> >>
> >> 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/
> >>
> >>
> >> _______________________________________________
> >> I-D-Announce mailing list
> >> I-D-Announce@ietf.org
> >> https://www.ietf.org/mailman/listinfo/i-d-announce
> >> Internet-Draft directories: http://www.ietf.org/shadow.html or
> >> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Thu Oct 15 03:36:56 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D15EA3A113E; Thu, 15 Oct 2020 03:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 nUIF_SA0e9QP; Thu, 15 Oct 2020 03:36:52 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE6E73A11D1; Thu, 15 Oct 2020 03:36:52 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 638C6548621; Thu, 15 Oct 2020 12:36:47 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 5CE31440059; Thu, 15 Oct 2020 12:36:47 +0200 (CEST)
Date: Thu, 15 Oct 2020 12:36:47 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Anima WG <anima@ietf.org>
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
Message-ID: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/oy0UxAlkirObsRR8U7KKBErMIUs>
Subject: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 10:36:55 -0000

Dear ANIMA WG

This message starts a two-week adoption call, ending on October 29th, 2020.

draft-carpenter-anima-asa-guidelines-09 has been progressed by the authors with help of the WG for a long while and the WG showed good interest. It was last presented at IETF108 and had no opposition. The draft is now clearly in scope of ANIMA charter 2 that was adopted around IETF106. The authors asked for adoption of the document at IETF108.

We therefore are asking the ANIMA working group for adoption of the following work:

Title:    Guidelines for Autonomic Service Agents
Name:     draft-carpenter-anima-asa-guidelines-09
Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/

This document is intended to become an informational ANIMA WG document.

Please express your support or rejection.
If you think this document should _not_ be adopted, please also explicitly indicate the reasons.

Regards,

Toerless


From nobody Thu Oct 15 04:50:19 2020
Return-Path: <william.atwood@concordia.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303C03A13CB for <anima@ietfa.amsl.com>; Thu, 15 Oct 2020 04:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.213, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=concordia.ca header.b=Ki8ienDR; dkim=pass (1024-bit key) header.d=liveconcordia.onmicrosoft.com header.b=ExVtsMO7
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 Ocd74ISsWTy6 for <anima@ietfa.amsl.com>; Thu, 15 Oct 2020 04:50:16 -0700 (PDT)
Received: from ums-loy-gw1.concordia.ca (ums-loy-gw1.concordia.ca [132.205.157.20]) (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 1C15C3A13C5 for <anima@ietf.org>; Thu, 15 Oct 2020 04:50:15 -0700 (PDT)
Received: from algol.concordia.ca (ums-sgw-mbs1.concordia.ca [132.205.123.130]) by ums-loy-gw1.concordia.ca  with ESMTP id 09FBoEh8011411-09FBoEhA011411 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <anima@ietf.org>; Thu, 15 Oct 2020 07:50:15 -0400
Received: from UMS-LOY-MBS1.concordia.ca (132.205.123.140) by ums-sgw-mbs1.concordia.ca (132.205.123.130) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 15 Oct 2020 07:50:14 -0400
Received: from CAN01-QB1-obe.outbound.protection.outlook.com (104.47.60.52) by UMS-LOY-MBS1.concordia.ca (132.205.123.140) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 15 Oct 2020 07:50:13 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=BE/W45xl19KHKP9LHtJvQbvICI7PUc3PGurWfniNjyrqHy87EBfQytCh2i85Bx5mUkZMSAb0GleBAJOog+cRtvY2aV8EGpBkvKa47va/1hT6bJo0dPMZgV4Js5p4+2dTsR2btbIr3jKn6xXr/nZd3xE+clbkDAZ//F2WI3Q3R6A0enmd4Fw5d1smZMRs2Sr1UUa9qGL7bQZxVaYQhj5a9BGLV1zR1r4XtNYWUC+iRESHb6HiNDIcGXLw0+ft+7+IEUZyIY05lrqSuqTP2n5zsbaYWY4vlN1gLpsuCZebF/b7HuO5V+s8UCnom+rrDvQ14oh1cIRNLYVStBX9xPioIg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vHIIDPIr3Bvp4dqQ9QJ1bW+NPdNEi5O2c8l8yFtxZYo=; b=U+uoTGYz9OAzr/GNHLUOGeTCy3gQn0MhlXJ/r2P/WTe14FodMbMtLHdHPzGZvQC9Rkvk9dZ6MSNaj8SMjjtOSOHGdy4nf1KnK3IoDAUznRGKrN71kTeEZS3ctBQFgJoGu4ookCN/iub9lGukxAXk3EJPSjcaKzbvL06sLF6GA8TYqtExWR/gLnp67MNqfUQe9j6xE1fRWA94LCPNEi7zCkgrsIXVLxGqhQSUbXoouHxgSARiVI14WshB8DwhZwlxf60XtnQbwtFFTvv1V5ovyMTWGAX+H7cGNc++/XRWaVQtT+fQHyVCHS+Oer3oxjWX8ApgE5umwkkAbFpf89NR3A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=concordia.ca; dmarc=pass action=none header.from=concordia.ca; dkim=pass header.d=concordia.ca; arc=none
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=concordia.ca; s=dkim-concordia_ca; c=relaxed/relaxed;  h=subject:to:references:from:message-id:date:content-type:mime-version; bh=vHIIDPIr3Bvp4dqQ9QJ1bW+NPdNEi5O2c8l8yFtxZYo=; b=Ki8ienDRC8Wl3mWcvm4Vl5Ev91wIigRQ4XoUwLSzoqQR77NFtceuK2+vre7kORXfeE55j4rDN2+f Y95ow0XBu0ICGgJEXePgyRmdDVVqS5pML2DIV6Lqrvg8uft8N83ehFZUTr/s9sIRBufJE1CUXF87 A26FSKBcumB7U2r3M+8MLVFKRiWlXuHlx7G/vJIxeQs2aYbeANBpwer6VJkFGetTVZYBuha+EQCM Vxcgh6WnozGEihCP45QHv/L2cwlCOGm5QL6awHL8JbAgCXMFd5JBbRpmo3QJG1cc4/aX9j04k6RO 3kNrgPjez0GBbkBAILYr4Fn/+h3aIPZt4jDl/A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=liveconcordia.onmicrosoft.com; s=selector2-liveconcordia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vHIIDPIr3Bvp4dqQ9QJ1bW+NPdNEi5O2c8l8yFtxZYo=; b=ExVtsMO7WhAyiv3M2xuh1yvXVTEY1Hj3W3SBNJk26iM5zRXZgyhVZm/pUxeXbb7xhy1K6fg0oKL/fvqi/ihsWz7qdVW9J1IgAWtYP29oXw1ylZoPKpaGGvDauD2zGTH3PCJyFxqcE2IKIL1hx3kGbOsztiGOb2qJhB9ajpGoUQk=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=concordia.ca;
Received: from YTBPR01MB3597.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:22::22) by YTBPR01MB2813.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:25::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Thu, 15 Oct 2020 11:50:13 +0000
Received: from YTBPR01MB3597.CANPRD01.PROD.OUTLOOK.COM ([fe80::95de:123e:3b31:953]) by YTBPR01MB3597.CANPRD01.PROD.OUTLOOK.COM ([fe80::95de:123e:3b31:953%6]) with mapi id 15.20.3477.024; Thu, 15 Oct 2020 11:50:12 +0000
To: <anima@ietf.org>
References: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
From: William Atwood <william.atwood@concordia.ca>
Message-ID: <81c00fd5-1a2e-01c6-338c-9afd2eb248a6@concordia.ca>
Date: Thu, 15 Oct 2020 07:50:36 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
In-Reply-To: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [2607:f2c0:93bc:1100:9979:1ee0:30e1:2641]
X-ClientProxiedBy: YT1PR01CA0074.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:2d::13) To YTBPR01MB3597.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:22::22)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [IPv6:2607:f2c0:93bc:1100:9979:1ee0:30e1:2641] (2607:f2c0:93bc:1100:9979:1ee0:30e1:2641) by YT1PR01CA0074.CANPRD01.PROD.OUTLOOK.COM (2603:10b6:b01:2d::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20 via Frontend Transport; Thu, 15 Oct 2020 11:50:12 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 86109632-32eb-4aec-fedc-08d8710079a0
X-MS-TrafficTypeDiagnostic: YTBPR01MB2813:
X-Microsoft-Antispam-PRVS: <YTBPR01MB28137D7D9A20694BFEEBF278F5020@YTBPR01MB2813.CANPRD01.PROD.OUTLOOK.COM>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: UeoK4FaBct3DQvPqBEMyZtN4Co7clVpud2Yz4op/7r8/cnI1inUi5eSjj8fmH4ug93Lk+f79E5FRr7ZZTLPeMj0kGX6FSXkn/82XLSms0XbNikrhmXgCqARCuuJv9Ljv6YxeOQAT8eP0qLlFyMH8gWtnVkV791rVXTXO4Yj1ScUVAsoftgBatv2UlCC/tfGpI5IX4mug1sJb9SzOdMBiCg9j8H+T8M/5ObJr7d/SWB7/fjBwDjBY7d6BoOEPv2dP6SW0JD2mPkF4jKm+cRXk7bBQqhMDB5Dm9144zUG+jxwtDMrxP3517A/lkknAMCXgSsSZD5LLuBOcPoMCAf5TG7eDXBHkvGiHFV9HbVtbPkSplhk2J+TgblHSt6C/SDN97XyGPLe2rd7Uy+5cWxlp9NFvhBuKA+waOf912jfHKqiY8xdrNudMt73I7bqfyTy7ROeWPzEubssW15HiiPEYsw==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:YTBPR01MB3597.CANPRD01.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFS:(396003)(366004)(136003)(39860400002)(376002)(346002)(31696002)(786003)(6666004)(53546011)(6486002)(8676002)(66476007)(186003)(16526019)(66556008)(6916009)(31686004)(66946007)(2906002)(2616005)(8936002)(83080400001)(5660300002)(83380400001)(966005)(316002)(86362001)(44832011)(4001150100001)(478600001)(52116002)(36756003)(43740500002); DIR:OUT; SFP:1101; 
X-MS-Exchange-AntiSpam-MessageData: iUlJhLubykkbvABj2jwtFRyyQDUXFtRlbQW7fasUrcasEU2nrWfRf8jmH1q+ijTs8ekmDfNi6M2ePuWwU87StsZikESGRGa3jn2uFjZwPKlUDfvgvgVrvL7FuuHXZyA3/KRxXxXUx7Cq7cQN1D3BfR+Pfr+a9rr/wqpQ0X0LxoVu8bOCWSH5JcL/EQMbPfp/COAbxzX6JQmKXqPw+P094KdlQuCgob8ZCbms8ZTwHdjAaGsoZaHWPADRubixboQkzaFoEYcVd05QRZWS+Uhhnw1L197ExJ5HMV/OptPG7IcrLSbz22rQRahJ0vvv1I50ecQtOZ1+VicMQBngQwfQiLrid46dzoe/o27EL7Vx1esgnl4TGL/Uv/pz/HvtR3C7SwBBkZ6CiB/q6tvv+sphiIim+h0r75eAleaR7gvGn2V8sNYsy4PkIwEfkPStshDrGIYx+0hz/oMZc6lvpl+Kas7Hll4drOv9OTURke1sO7YnlL2bTKr1Lz3fyJBrtroOZPwFSZqfqJyEVOyu7UTuyj6g0VgLseqvEFTmpH5ShTCLFvTXVbx0dSDa3TZOPP44dJxU/R4RMmFSza1jERKmGkhBXtDSYG2eLoPHh4M+6yVfc1Jw1zayc1i67czJYLN8EllslNKjM9n+cwRcZK4lPwgQbrNQ1cMLELnWM7KlxVLG7o7VRP/7jJEy6MHwRiGmkv2JGgxnFZBMkYI38U94HQ==
X-MS-Exchange-CrossTenant-Network-Message-Id: 86109632-32eb-4aec-fedc-08d8710079a0
X-MS-Exchange-CrossTenant-AuthSource: YTBPR01MB3597.CANPRD01.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 15 Oct 2020 11:50:12.9147 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5569f185-d22f-4e13-9850-ce5b1abcd2e8
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: LJ1x/QS4+DU1/NsCL4IQ+lEn1J6Y5hVr616KDB+fHE7MMye3jQnlJDrJn9oBNfNSy4+J6KgikJ8UT0SRL9T5X29N6hZjTOXGj7FN4vDXnn0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTBPR01MB2813
X-OriginatorOrg: concordia.ca
X-PMWin-Version: 4.0.2, Antivirus-Engine: 3.79.0, Antivirus-Data: 5.78
X-PureMessage: [Scanned]
X-FE-Policy-ID: 5:6:0:SYSTEM
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8hEwQ3wVpunqyq555ksAWAL9XJA>
Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 11:50:18 -0000

I support adoption of this document.

  Bill


On 2020-10-15 6:36 a.m., Toerless Eckert wrote:
> Attention This email originates from outside the concordia.ca domain. // Ce courriel provient de l'exterieur du domaine de concordia.ca
> Dear ANIMA WG
> 
> This message starts a two-week adoption call, ending on October 29th, 2020.
> 
> draft-carpenter-anima-asa-guidelines-09 has been progressed by the authors with help of the WG for a long while and the WG showed good interest. It was last presented at IETF108 and had no opposition. The draft is now clearly in scope of ANIMA charter 2 that was adopted around IETF106. The authors asked for adoption of the document at IETF108.
> 
> We therefore are asking the ANIMA working group for adoption of the following work:
> 
> Title:    Guidelines for Autonomic Service Agents
> Name:     draft-carpenter-anima-asa-guidelines-09
> Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
> URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/
> 
> This document is intended to become an informational ANIMA WG document.
> 
> Please express your support or rejection.
> If you think this document should _not_ be adopted, please also explicitly indicate the reasons.
> 
> Regards,
> 
> Toerless
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> 

-- 
Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:william.atwood@concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8


From nobody Thu Oct 15 15:04:18 2020
Return-Path: <kaduk@mit.edu>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4824F3A0905; Thu, 15 Oct 2020 15:04:16 -0700 (PDT)
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=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 uY5FxywZwAAR; Thu, 15 Oct 2020 15:04:14 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 E68133A08EB; Thu, 15 Oct 2020 15:04:13 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 09FM3oDA007564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Oct 2020 18:03:55 -0400
Date: Thu, 15 Oct 2020 15:03:49 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Toerless Eckert <tte@cs.fau.de>
Cc: The IESG <iesg@ietf.org>, draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
Message-ID: <20201015220349.GH50845@kduck.mit.edu>
References: <159727599109.5414.1617295798802435987@ietfa.amsl.com> <20200911125956.GA63981@faui48f.informatik.uni-erlangen.de> <20201001223244.GP89563@kduck.mit.edu> <20201002080614.GA374@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201002080614.GA374@faui48f.informatik.uni-erlangen.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ijSf_c4dXGKidkAxfi_IhoXdb48>
Subject: Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 22:04:16 -0000

Hi Toerless,

On Fri, Oct 02, 2020 at 10:06:14AM +0200, Toerless Eckert wrote:
> Thanks, Ben
> 
> Let me just comment on possible AI for you, i will do my AI in a few
> days when i have more time.

I guess I took more than a few days for mine :(

> On Thu, Oct 01, 2020 at 03:32:44PM -0700, Benjamin Kaduk wrote:
> > I think A.6 is an interesting idea and don't want to drop the idea, but the
> > current state of the text in A.6 is better suited for a separate doc than
> > inclusion in this one.  I suppose I could try to do a shorter rewrite that
> > might be a better fit for this doc if you want; let me know.
> 
> A separate doc would have to be an actual spec of the mechanism IMHO,
> and alas i do not have the time right now to start it (and after
> we have an ACP RFC maybe i can also find other WG participants to
> contribute ;-)). So i do not want to loose the thought and think an
>  appendix is the best reminder for the problem and solution directions.
> 
> Aka: Yes: If you want to send replacement text, please send it,
> and i will replace A.6 with it verbatim.

Here's a first crack.  I'll set a reminder to read over it again in a
few weeks to see if it still looks okay (and presumably we can get some
other eyes on it in the intervening period, too).

The discovery procedure in this specification for low-level ACP channel
support by layer-2 peers involves DULL GRASP and attempting (usually in
parallel) to establish all supported channel types, learning the peer ACP
address and correspondingly the assignment of Decider and Follower roles,
and tearing down all channels other than the one preferred by the Decider.
This procedure, in general, becomes resource intensive as the number of
possible secure channels grows; even worse, under some threat models, the
security of the discovery result is only as strong as the weakest supported
secure channel protocol.  Furthermore, the unilateral determination of
"best" channel type by the Decider does not result in the optimal outcome
in all possible scenarios.

This situation is tolerable at present, with only two secure channels (DTLS
and IPsec) defined, but long-term agility in the vein of [BCP201] will
require the introduction of an alternate discovery/negotiation procedure.
While IKEv2 is the IETF standard protocol for negotiating security
associations, it currently does not have a defined mechanism flexible
enough to negotiate the parameters needed for, e.g., an ACP DTLS channel,
let alone for allowing ACP peers to indicate their preference metrics for
channel selection.  Such a mechanism or mechanisms could be defined, but if
ACP agility requires introducing a new channel type, for example MacSec,
IKEv2 would again need to be extended in order to negotiate an ACP MacSec
association.  Making ACP channel agility dependent on updates to IKEv2 is
likely to result in obstacles due to differeng timescales of evolution,
since IKEv2 implementations help form the core of Internet-scale security
infrastructure and must accordingly be robust and thoroughly tested.

Accordingly, a dedicated ACP channel negotiation mechanism is appropriate
as a way to provide long-term algorithm and secure-channel protocol
agility.  Such a mechanism is not currently defined, but one possible
design is as follows.  A new DULL GRASP objective is defined to indicate
the GRASP-over-TLS channel, which is by definition preferred to other
channel types (including DTLS and IPsec).  When both peers advertise
support for GRASP-over-TLS, GRASP-over-TLS must run to completion before
other channel types are attempted.  The GRASP-over-TLS channel performs the
necessary negotiation by establishing a TLS connection between the peers
and using that connection to secure a dedicated GRASP instance for
negotiating supported channel types and preference metrics.  This provides
a rich language for determining what secure channel protocol to use for the
ACP link while taking into account the capabilities and preferences of the
ACP peers, all protected by the security of the TLS channel.

> > > End-to-end communication (inside or outside the ACP) will use the
> > > ACP address, and it could authenticate its IPv6 address (the ACP
> > > address) by using the ACP certificate during end-to-end authentication,
> > > but this spec does not mandate that.
> > 
> > I would like (and will put in my forthcoming COMMENT) to at least mention
> > that there are cases where you could do this sort of check, even though it
> > is definitely impossible in some cases (such as the secure channel) and
> > even if it is not mandated.  I think I can live with not requiring it,
> > though.
> 
> What do you think would be achieved with such a check ? If we write anything,
> we should know (if not write down) the most obvious/relevant attack vector
> prohibited:
> 
> a) I do not quite care about discovering e.g.: a TCP proxy, because that
> to me seems like the most obvious thing we could discover (TLS connection
> end to end via TCP proxy). Indeed, in BRSKI we already explicitly benefit
> from the BRSKI proxy which is a TCP proxy. So i am worried that unqualified
> address comparison would eliminate future positive use of TCP proxies.
> 
> b) Where address check really would be beneficial is something where we
> are missing a key bilding block, so it would at best be written into
> an appendix as a reminder: We need a GRASP authentication block. Example:
> ACP node announces (multicast GRASP) a service. We want to know if that
> service announcement is actually authentic from the ACP node that
> owns the ACP address in the GRASP announcement. If the GRASP message
> had an auhentication extension, we would know that the announcement
> and its ACP address is from the ACP who claims that address.

I think I'm mostly coming at this from the "it's intuitively the Right
Thing to do" based on my accumulated experience.  But let's consider GRASP
-- signing the announcements (e.g., with CMS) could be a use case as you
describe, but I would also like to ask about unicast GRASP.  IIRC it runs
over TLS, but with the current procedures for certificate validation a TCP
proxy could be on the path as you note in (a).  Is the TCP proxy still a
feature for you for this case?

Perhaps we are looking for a statement akin to:

% The presence of the ACP node address prefix in the ACP certificate in
% principle allows for end-to-end authentication of certain interactions.
% However, because the ACP is assumed to consist entirely of trusted nodes,
% the baseline requirements for establishing a secure channel within the
% ACP do not require validation of the peer address against the ACP
% certificate.  In some cases ([example of stuff that uses link-local
% addresses]), such end-to-end validation is not technically possible, and
% for cases where it is technically possible ([example of end-to-end]) the
% baseline requirement is still left flexible so as to allow for the
% introduction of (e.g.) TCP proxies in the ACP topology.  This does not
% preclude individual ACP mechanisms or objectives from making use of
% end-to-end authentication with ACP certificates; such mechanisms might
% for example include signed GRASP announcements.

-Ben


From nobody Fri Oct 16 02:41:41 2020
Return-Path: <jiangsheng@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C50E3A0E4F for <anima@ietfa.amsl.com>; Fri, 16 Oct 2020 02:41:39 -0700 (PDT)
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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Xk3fesAsO1Yd for <anima@ietfa.amsl.com>; Fri, 16 Oct 2020 02:41:37 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C87E63A0E4D for <anima@ietf.org>; Fri, 16 Oct 2020 02:41:37 -0700 (PDT)
Received: from lhreml732-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 0C9CE54B6FC9AB57A8D4; Fri, 16 Oct 2020 10:41:36 +0100 (IST)
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by lhreml732-chm.china.huawei.com (10.201.108.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 16 Oct 2020 10:41:35 +0100
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by nkgeml705-chm.china.huawei.com (10.98.57.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 16 Oct 2020 17:41:32 +0800
Received: from nkgeml708-chm.china.huawei.com ([10.98.57.160]) by nkgeml708-chm.china.huawei.com ([10.98.57.160]) with mapi id 15.01.1913.007; Fri, 16 Oct 2020 17:41:32 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: William Atwood <william.atwood@concordia.ca>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
Thread-Index: AQHWot9DKjBuU1bvhEGEJGQc8mV0n6mYBu8AgAHz12A=
Date: Fri, 16 Oct 2020 09:41:32 +0000
Message-ID: <a9d3230b0bf54b4bade1a779e4703832@huawei.com>
References: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de> <81c00fd5-1a2e-01c6-338c-9afd2eb248a6@concordia.ca>
In-Reply-To: <81c00fd5-1a2e-01c6-338c-9afd2eb248a6@concordia.ca>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.235.253]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/F3vaOrbiDgZymmZpbkh1clDypWc>
Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2020 09:41:39 -0000

I support the adoption as co-author. This document is very helpful for the =
purpose to reuse ANIMA fundamental components in many autonomic scenarios.

Sheng

> -----Original Message-----
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of William Atwood
> Sent: Thursday, October 15, 2020 7:51 PM
> To: anima@ietf.org
> Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelin=
es-
> 09, ends October 29th 2020
>=20
> I support adoption of this document.
>=20
>   Bill
>=20
>=20
> On 2020-10-15 6:36 a.m., Toerless Eckert wrote:
> > Attention This email originates from outside the concordia.ca domain.
> > // Ce courriel provient de l'exterieur du domaine de concordia.ca Dear
> > ANIMA WG
> >
> > This message starts a two-week adoption call, ending on October 29th, 2=
020.
> >
> > draft-carpenter-anima-asa-guidelines-09 has been progressed by the
> authors with help of the WG for a long while and the WG showed good
> interest. It was last presented at IETF108 and had no opposition. The dra=
ft is
> now clearly in scope of ANIMA charter 2 that was adopted around IETF106.
> The authors asked for adoption of the document at IETF108.
> >
> > We therefore are asking the ANIMA working group for adoption of the
> following work:
> >
> > Title:    Guidelines for Autonomic Service Agents
> > Name:     draft-carpenter-anima-asa-guidelines-09
> > Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
> > URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-
> guidelines/
> >
> > This document is intended to become an informational ANIMA WG
> document.
> >
> > Please express your support or rejection.
> > If you think this document should _not_ be adopted, please also explici=
tly
> indicate the reasons.
> >
> > Regards,
> >
> > Toerless
> >
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima
> >
>=20
> --
> Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
> Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
> Department of Computer Science
>    and Software Engineering
> Concordia University EV 3.185     email:william.atwood@concordia.ca
> 1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
> Montreal, Quebec Canada H3G 1M8
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Mon Oct 19 01:12:49 2020
Return-Path: <Xun.Xiao@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B563A1501; Mon, 19 Oct 2020 01:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 EAAiVTUVYNZU; Mon, 19 Oct 2020 01:12:47 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 E6A473A14FF; Mon, 19 Oct 2020 01:12:46 -0700 (PDT)
Received: from lhreml743-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 0C0561FABEB2BD5AE288; Mon, 19 Oct 2020 09:12:45 +0100 (IST)
Received: from fraeml735-chm.china.huawei.com (10.206.15.216) by lhreml743-chm.china.huawei.com (10.201.108.193) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 19 Oct 2020 09:12:44 +0100
Received: from fraeml737-chm.china.huawei.com (10.206.15.218) by fraeml735-chm.china.huawei.com (10.206.15.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 19 Oct 2020 10:12:44 +0200
Received: from fraeml737-chm.china.huawei.com ([10.206.15.218]) by fraeml737-chm.china.huawei.com ([10.206.15.218]) with mapi id 15.01.1913.007;  Mon, 19 Oct 2020 10:12:44 +0200
From: Xun Xiao <Xun.Xiao@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>, Anima WG <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
Thread-Topic: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
Thread-Index: AQHWouDjQJGDDfNwlUyRf8tS4ZIVyKmelqZQ
Date: Mon, 19 Oct 2020 08:12:44 +0000
Message-ID: <9f67774e9f534bb5abc42528d43f3b51@huawei.com>
References: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.48.223.198]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jk5PNcoym8R12PVSPemAmhzigd8>
Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2020 08:12:48 -0000

Dear ANIMA WG,

I support the adoption as it defines the standard way to expose the functio=
nalities of GRASP. This also provides a regulated way to expose more functi=
onalities of GRASP extension.

Best,

Xun Xiao

-----Original Message-----
From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Toerless Eckert
Sent: Thursday, October 15, 2020 12:37 PM
To: Anima WG <anima@ietf.org>
Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>
Subject: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09,=
 ends October 29th 2020

Dear ANIMA WG

This message starts a two-week adoption call, ending on October 29th, 2020.

draft-carpenter-anima-asa-guidelines-09 has been progressed by the authors =
with help of the WG for a long while and the WG showed good interest. It wa=
s last presented at IETF108 and had no opposition. The draft is now clearly=
 in scope of ANIMA charter 2 that was adopted around IETF106. The authors a=
sked for adoption of the document at IETF108.

We therefore are asking the ANIMA working group for adoption of the followi=
ng work:

Title:    Guidelines for Autonomic Service Agents
Name:     draft-carpenter-anima-asa-guidelines-09
Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidel=
ines/

This document is intended to become an informational ANIMA WG document.

Please express your support or rejection.
If you think this document should _not_ be adopted, please also explicitly =
indicate the reasons.

Regards,

Toerless

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


From nobody Tue Oct 20 02:03:13 2020
Return-Path: <laurent.ciavaglia@nokia.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 945C33A0AA1; Tue, 20 Oct 2020 02:03:11 -0700 (PDT)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aloV-ix7TckT; Tue, 20 Oct 2020 02:03:08 -0700 (PDT)
Received: from FRA01-PR2-obe.outbound.protection.outlook.com (mail-eopbgr120101.outbound.protection.outlook.com [40.107.12.101]) (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 955BB3A0AA3; Tue, 20 Oct 2020 02:03:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=X1zasqmCS41+zbtVZJBPOM7idxEQI5cBNViNLqFZuKFgg5ZOU2h/LAeFjSLJwD1yZK8aBjwtGmHW0Ys3XvREbiQlttsG+rE6aGaIYgVSCbgHYTDnGm+3UKrw8WCze/eZdrLzpMn5Di48ujR7GbU62cBXGGrk6Xnpyf5GR3nwf0tDmprflezlPV5qNj/nhGjrmcDDg4luBhp8+COZG9lAKJFso6kzDzsYbiuAUjOUmMvKTJz4pRZ4qpN4/ZvbqtvuxC/O2RUWr+v2r8JBhP+mrV09VmyCyJkte0F0Hy0Az3oSvhX6iJ5Hk5JQHE5Ai6cTZmjup+6uzz7pSWUlSLnjlQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HR6RjW0Mo99BZW/eYpMtIyDMOdFxJhBbR7EQF5NuSuA=; b=SClZ9bK6kT9wFUfJbxn814EQ9pMFWyFGkWd+0nGTCKuMN4gRfCcIS68R9qNwtDve91KWpXFjhN0KO3dGi73FX+ruiZu88SXu7qVXIwZUiliNTj0VTDKRZtGfSlnw/loo8teV9RsSrB9oZHPBXrgaKVCznVqmdqXFL+Q+dGdYhDSZ1epNKKb3JxZOR3/7vPdnUr6l0fS+4lPRAFkNmKbrGBPZH0BpR5m7g7ff9RizmwYe59ZmDWlnrSrXc6ytq5WLIKONukzw2uooUHAVftzxVHAAMrcIMHjhM1JmhecR6HSh18JUhqScHf2W1UEX239D8uOLLRZgPd2p8tJHrw3Frw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HR6RjW0Mo99BZW/eYpMtIyDMOdFxJhBbR7EQF5NuSuA=; b=smyEmVGsuz78sxrUbm87QMquKVOqTCup4pjohqRUZYFmBJeedact9AxZwCE24wyHolmUG6Pw/1pfWg0i9xUS9UpREgapHihiD3DzDSi67xWR4ZQLROKYXGyhKJi4FAGjs6EeauOE8d398FUePurUoIGkNkLHHydxTkQ5/9Y6bBE=
Received: from PR3PR07MB6826.eurprd07.prod.outlook.com (2603:10a6:102:7f::20) by PR1PR07MB4860.eurprd07.prod.outlook.com (2603:10a6:102:6::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.9; Tue, 20 Oct 2020 09:03:02 +0000
Received: from PR3PR07MB6826.eurprd07.prod.outlook.com ([fe80::35a8:7108:9413:951e]) by PR3PR07MB6826.eurprd07.prod.outlook.com ([fe80::35a8:7108:9413:951e%4]) with mapi id 15.20.3499.016; Tue, 20 Oct 2020 09:03:02 +0000
From: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia.com>
To: Toerless Eckert <tte@cs.fau.de>, Anima WG <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
Thread-Topic: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
Thread-Index: AQHWot8hrinTgtOV8kaQLYFnFs58bamgOZBA
Date: Tue, 20 Oct 2020 09:03:02 +0000
Message-ID: <PR3PR07MB6826D4E3CEE5855071E398AAF31F0@PR3PR07MB6826.eurprd07.prod.outlook.com>
References: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cs.fau.de; dkim=none (message not signed) header.d=none;cs.fau.de; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [176.130.37.253]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 4d0eb432-db35-4cd0-140f-08d874d6f372
x-ms-traffictypediagnostic: PR1PR07MB4860:
x-microsoft-antispam-prvs: <PR1PR07MB486050AA7D9C05F8901F5E36F31F0@PR1PR07MB4860.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jqF6VqfBALM4Pu98DvhqqSw9yRFyNliQLN7RoubtC+P2LBp/0vhJka25YyNvQ89l3wRMnFxkFjNBlTuhOYACM04VodShdrEqXesNYwlAw1M0OpsZxhNLwybgN7e1SwjoOhWxH+t4OVE4iQB1RsaIdJnpmvLrxDk5V2ZM1kUOuYyTEymFNG/+aomgTEtJWEsx4ivAyXDEazwU7UX+2BSxJraN36z3WTjJEZNDlfbBMzEcjcWRvb/joJjEEnzsEE0wPnA+aasvJiSBs1ht2KIL60qkzRbyhf1ZCvu+/3kbCoqN1MMQMDoZT7EqxTL5qmLHsprgp/khze3NViyvwPgQ/flGBC3pCIb1tOkar15Jkd1+UhBzpLICyCRHjbtCpLuRErE2nIRixlMk0y4l8ScVyg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:PR3PR07MB6826.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(136003)(396003)(346002)(376002)(39860400002)(66946007)(66476007)(8936002)(2906002)(76116006)(66556008)(316002)(66446008)(54906003)(64756008)(9686003)(52536014)(71200400001)(966005)(4326008)(478600001)(110136005)(83380400001)(86362001)(5660300002)(33656002)(55016002)(53546011)(6506007)(8676002)(26005)(186003)(7696005); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: bLA6cgHvUwdGhBV2lahb7LUVAvCWt6sV4qt0x9klGpVlDN5Jto+XjCF6VPPbySEe5W5X7j9NyaElgq6RHv6iggbCbK1JinrGgwhWP6Kpd3cngvod9CDn7NgoNbWStyVXQGZlQYGk5XPSg7qzW1MSSTc8PjQExqsRcZPo9TpQ+tFBUYya34aMxY49vaDVWFZDwHP6KVALrEpa2LfyNyAx7RRGVaeJmAPjORWtFyaZE7QSG9GW9VL4ERNtd0AJEphFxhagmdz3cUPx8Jf/S6D56px6VHYwsCSna9QMy81Oo6WGHfqR6HRKb5qxm0bIVZ2L565SNNEyDnbaAR8tlqG8xvRxgjuuPh/iWf5e2IP2Es/tH9g6kVGUj92zdZYs2HJ8XIkwZiU8Z2JM3ao/xOHN7Nr4G1czFAIy1INCWFBHfQj/D/l81hpZ+rn+aaWsrunz1uJUjv4GRwVTui0RMgNaGnR51CTpko4vdIM4lZj5BiP3Y98Un2dE9a5MAZ+r7HQFqtViCmxwCAabK+K38y1SB5HL6VMiHRgjkPFe4KShv/yprWi+TtHzAyutYHyj6KghD+l3YPpccNCTJgf8rE3dzZSSUkK5q5QyurSDBsPpgEGdDxJEG2dv+4+ysvsJHu7pviaiY7r1Djrl/KCBtHxqEg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PR3PR07MB6826.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4d0eb432-db35-4cd0-140f-08d874d6f372
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Oct 2020 09:03:02.7893 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Il4LysjhGm+kCdDa+Ud9XxEblcj9mCGaquBvJ8wa0AFpDP0oROsfKaD3Ox4gpREtTePKjxsyTC4CYt2Pf73TxeWbJj00TXfuIP0kMcBTasY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR1PR07MB4860
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/SIdNUyferjfkXKsiPIc6Zcsvwws>
Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 09:03:12 -0000

Hello,

I'm a co-author of this draft.
I support its adoption as WG document.

Best regards,=20
Laurent

> -----Original Message-----
> From: Anima <anima-bounces@ietf.org> On Behalf Of Toerless Eckert
> Sent: Thursday, October 15, 2020 12:37
> To: Anima WG <anima@ietf.org>
> Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>
> Subject: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-
> 09, ends October 29th 2020
>=20
> Dear ANIMA WG
>=20
> This message starts a two-week adoption call, ending on October 29th,
> 2020.
>=20
> draft-carpenter-anima-asa-guidelines-09 has been progressed by the author=
s
> with help of the WG for a long while and the WG showed good interest. It
> was last presented at IETF108 and had no opposition. The draft is now
> clearly in scope of ANIMA charter 2 that was adopted around IETF106. The
> authors asked for adoption of the document at IETF108.
>=20
> We therefore are asking the ANIMA working group for adoption of the
> following work:
>=20
> Title:    Guidelines for Autonomic Service Agents
> Name:     draft-carpenter-anima-asa-guidelines-09
> Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
> URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-
> guidelines/
>=20
> This document is intended to become an informational ANIMA WG document.
>=20
> Please express your support or rejection.
> If you think this document should _not_ be adopted, please also explicitl=
y
> indicate the reasons.
>=20
> Regards,
>=20
> Toerless
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Thu Oct 22 10:34:39 2020
Return-Path: <rwilton@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EC13A09D6; Thu, 22 Oct 2020 10:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=emhEOJmJ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ykbArP7F
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 hDD-1qwK_I8f; Thu, 22 Oct 2020 10:34:28 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FC243A09D3; Thu, 22 Oct 2020 10:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1758; q=dns/txt; s=iport; t=1603388068; x=1604597668; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hBBGCdnTLQ0WYGHaAMLLE5rU4MIM9QJGhctMTL6rR/I=; b=emhEOJmJBFL5EP4UgKl/yzggwjeriXe+Lcf+UlSznF6LuvsiVoACDYp8 qfW82eO/IqWU6zmKGQOhtmXeWufJTxigi/FZbEQq7GBN7qD07277LgE3w IK3OirO/o+cM+9VAA/IED4+NXRobAdHM0SI8SW0KCbgfhALrtm3/pL+Dw w=;
IronPort-PHdr: =?us-ascii?q?9a23=3AkjluChM2MPgM0mBwKEIl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEvKw33l7EQYud7OhL2KLasKHlDGoH55vJ8HUPa4dFWB?= =?us-ascii?q?JNj8IK1xchD8iIBQyeTrbqYiU2Ed4EWApj+He2YklYBMi4YEfd8TW+6DcIEU?= =?us-ascii?q?D5Mgx4bu3+Bo/ViZGx0Oa/s53eaglFnnyze7R3eR63tg7W8MIRhNhv?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DREQBgwZFf/4YNJK1gHQEBPAEFBQE?= =?us-ascii?q?CAQkBFYFRgVBRB3BZLywKhDKDSQONTph6gUKBEQNVCwEBAQ0BARgLCgIEAQG?= =?us-ascii?q?EBkQCF4FyAiU4EwIDAQELAQEFAQEBAgEGBG2FYQyFcgEBAQEDAQEQEREMAQE?= =?us-ascii?q?sCwELBAIBCBEEAQEDAggeAgICJQsVBgEBBQMCBAENBQgagwWCSwMuAQMLpzw?= =?us-ascii?q?CgTmIaHaBMoMEAQEFhQEYghADBoEOKgGCcYNwhlcbgUE/gVSCTT6CXAEBA4E?= =?us-ascii?q?nARIBI4MVM4Isk1WkNAqCaokEkheDF4oNlDqGAY07inaVQQIEAgQFAg4BAQW?= =?us-ascii?q?BayNncHAVO4I1ATNQFwINjiaDaoUUhUJ0OAIGCgEBAwl8jDsBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.77,404,1596499200"; d="scan'208";a="605335438"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Oct 2020 17:34:27 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 09MHYRDR015655 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 22 Oct 2020 17:34:27 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 22 Oct 2020 12:34:26 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 22 Oct 2020 12:34:26 -0500
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 22 Oct 2020 13:34:26 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SSUR7J46sHgDrFkYDrrrg9CJKi3MOrLFRNQcxq3DwsCtnHolpIzPW7BULZ6rfMPpXL74PBkgqAYr7IhHV9yrg1CYlodvhMjj/+CP04zLllxmzLVNbIs7G4RWMu3wwMwCajfnXjRyir3EMW/ZbY90XSqf8SRvLBDZJDvzHmxHwSJm7wmTQTYj+dRDN7VDGv8udyX4vMqoZZRMbNatDuNnTS/fi4kOSr2Pg61zm3K5BQOvXrbpOt0FzMO0YhIqVhf5PxSssuE/NIZdqk+u7kGNUaip0eyp6RBKTV4mjhIE/YrWi3lS1jGYrelBnvI1SmuOd+a6v5Myjz7mzIorqdQwPA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hBBGCdnTLQ0WYGHaAMLLE5rU4MIM9QJGhctMTL6rR/I=; b=dgh5WhObfd4HOOJ3Ii7za/b0jseNz5TXggQLlgPgmLETt59OGa6//2S0YV1LADJZjRmYfz0iNLbQuJ7TWIpsrghjbMpmxeTy+02xNXPbTQEFGxssshM3kXhwGlJzfSu08U5JKw2ELE4P5EFlrarJ0jc61Hx8JvnjbL2dSCpuU57ti1lJvDSRK6aE4SAraVbOQtJLUsX7jVXRNB/blQZyK9eJ2gzt+YOmG1EMJaoOM2/158+Y/Ty9RFzc6Xtewl8Bnpvfkja9NFqSgD2SMieQ34spDbsCmEmNEjEism8W8pXW8LsMUdqpYpkSiSXnUK7AsseqW+/r6kSEe7rLBpyWYg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hBBGCdnTLQ0WYGHaAMLLE5rU4MIM9QJGhctMTL6rR/I=; b=ykbArP7FD9rZtiiyWXG7HdNT+Mo4bkXUoZAdvPMrqbtw6CVrOhP/G+bD0FXVXVV71HhtiAhvJ1XhKnQNQBKHkgBqXXbmIn2sbRBiNXur1/XeaBvkTz567wolivo9nGZIlpFd5OUiALCaohglWVAbo5oRYGJ2xX+DgVIksUaWzPY=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by BL0PR11MB2929.namprd11.prod.outlook.com (2603:10b6:208:75::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.29; Thu, 22 Oct 2020 17:34:25 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::d84a:115:9ce0:8241%4]) with mapi id 15.20.3477.028; Thu, 22 Oct 2020 17:34:25 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>, "anima@ietf.org" <anima@ietf.org>, "mud@ietf.org" <mud@ietf.org>
CC: "ops-ads@ietf.org" <ops-ads@ietf.org>
Thread-Topic: New Non-WG Mailing List: IOTOPS -- IOT Operations
Thread-Index: AQHWqJeHI1OerKNAtU6HrFqgN1Mf8amj4CuQ
Date: Thu, 22 Oct 2020 17:34:24 +0000
Message-ID: <MN2PR11MB436675A4C6A955FD2E75CDF3B51D0@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <160338716989.22551.17761888498316049460@ietfa.amsl.com>
In-Reply-To: <160338716989.22551.17761888498316049460@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [82.12.233.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 394c3a18-8427-47f3-3440-08d876b0b846
x-ms-traffictypediagnostic: BL0PR11MB2929:
x-microsoft-antispam-prvs: <BL0PR11MB2929944392508BB7BCAA2614B51D0@BL0PR11MB2929.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: huZh8C/LjDddLOf23XVENp2daPNcnHbO0kra9S2+aeX2fStLGvItTMhKjJHN1IfT937PJsa9Oe+4uAHnJU03rwUYDNRcbkFbt7uOal+i0y6UTg1FiMzZjM2d+ETdHP0kYUVLjcmTaHgTqbjMg7UBDN8jAS2UW0t2yoAsxN394/J9E1oRpIyc8TK6RGzfpUtJSoZcMFFcmf7FokeB8mgJKXESjsUP4wokCbq/UlVuTtaATk2KeCOCR/CucDKOOk6HAk2rYLudHXesVMBygcHzz01K4fOwRyIds9sf+QDSbw6WubQDwkCpJbK4ru9PXXo514AFPNfVFzh+iL7r0fdmbfjvt0EDSLphJOWHKI0+Md6CuYFCY0cdSgdDUbwBNLE2DQHjPiF/2+NGz2O04okC5pQhwEkYkYohQn4OaL6VZVef9UCZt9nd12nuO5LckDAO3Aa1CEE8UbViEDCGQtEz8e6GmFuSQL2uNXwP2pZyjOw=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFS:(396003)(136003)(39860400002)(346002)(366004)(376002)(316002)(2906002)(478600001)(8676002)(9686003)(66574015)(55016002)(186003)(83380400001)(86362001)(8936002)(7696005)(33656002)(52536014)(4326008)(5660300002)(450100002)(6506007)(53546011)(76116006)(66476007)(110136005)(66446008)(66556008)(64756008)(66946007)(966005)(71200400001)(26005)(223123001)(130980200001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: QAKT6ZgHvfJxVN8+gjLQZhN6d6/io99dCM6ZA85M/EPiS41Nmwvz+bTpr2PDTeily83jp0RF2y4NfkTKgiGyYlV7QUHVEYDt6asJfxN1rDPHyMQMSUFwZ4vmpErYoCdzmFrzTTZqpuFvfrSgr+WK9SyZcOn59bsWt9U+Tay/kdzB1OP+hIwQk0c+wSyX5jOanKgOib72xFyxRK/7u2CfDPjR2yV4AN+IpJzwWhBvxZipqO0/HEHE19I/KPfs7dO/q88NPeKwsa8wGRCgtyKlEyjNlFRN5TvrhQts8ZOLeAGh59064MIXsERPqKBDtVzB5ixfYLAUJ3avvqSwGqYkmySO4KJHzwGvr7NY5ZA34rhyXAdBWpqbtPpkhYacJFX2ygvOt1CJ1+2dtCAuTNbtFid/DGuY0prsQWZV1CEKAauDAvVcPaQoZbEZoQELVGKpXVQr+cjKjug/tbnd5OQrnOFSF3aPfdiXBXjDId/cfzqqnnE24/r8QMe+2k3T6Mf0O6ZXk/EUpTWIdVFdN2G9iubSIFexyiaJo3xwerwDjbByo1KVy1GWhwzKaOAXwAmHK7ZgduAxdVNESqU8euqsNq6OTC+MJf9QMAdLQrC3huByfROt+pKg+V3nwZPzsqQRvaZ3lKXX8i4Jw3xdccN2OA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB4366.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 394c3a18-8427-47f3-3440-08d876b0b846
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2020 17:34:24.9136 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9AXIGcpan+TLCykJ95fn/V1qel/n0nb7pCLvwDdDe84rmLgBtxpPub4YWQ2iO2YTLlCuic1h2olD+TiRxBPeww==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB2929
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/b4ftllIJa014awMLqD9XILuN248>
Subject: [Anima] FW: New Non-WG Mailing List: IOTOPS -- IOT Operations
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 17:34:30 -0000

V2FycmVuIGFuZCBJIGhhdmUgY3JlYXRlZCBhIG5ldyBtYWlsaW5nIGxpc3QgdG8gZGlzY3VzcyBh
bmQgcmVmaW5lIGNoYXJ0ZXIgdGV4dCBmb3IgYSBwb3RlbnRpYWwgSU9UT1BTIFdHLg0KDQpXZSB3
b3VsZCB2YWx1ZSB5b3VyIGZlZWRiYWNrIChvbiB0aGUgbmV3IG1haWxpbmcgbGlzdCkgb24gcmVm
aW5pbmcgdGhpcyBwcm9wb3NlZCBjaGFydGVyIHRleHQuDQoNClJlZ2FyZHMsDQpSb2INCg0KDQo+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IElFVEYgU2VjcmV0YXJpYXQgPGll
dGYtc2VjcmV0YXJpYXRAaWV0Zi5vcmc+DQo+IFNlbnQ6IDIyIE9jdG9iZXIgMjAyMCAxODoxOQ0K
PiBUbzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdCA8aWV0Zi1hbm5vdW5jZUBpZXRmLm9yZz4NCj4g
Q2M6IGlvdG9wc0BpZXRmLm9yZzsgd2FycmVuQGt1bWFyaS5uZXQ7IFJvYiBXaWx0b24gKHJ3aWx0
b24pDQo+IDxyd2lsdG9uQGNpc2NvLmNvbT4NCj4gU3ViamVjdDogTmV3IE5vbi1XRyBNYWlsaW5n
IExpc3Q6IElPVE9QUyAtLSBJT1QgT3BlcmF0aW9ucw0KPiANCj4gQSBuZXcgSUVURiBub24td29y
a2luZyBncm91cCBlbWFpbCBsaXN0IGhhcyBiZWVuIGNyZWF0ZWQuDQo+IA0KPiBMaXN0IGFkZHJl
c3M6IGlvdG9wc0BpZXRmLm9yZw0KPiBBcmNoaXZlOiBodHRwczovL21haWxhcmNoaXZlLmlldGYu
b3JnL2FyY2gvYnJvd3NlL2lvdG9wcy8NCj4gVG8gc3Vic2NyaWJlOiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lvdG9wcw0KPiANCj4gUHVycG9zZToNCj4gDQo+IFRoaXMg
bGlzdCBpcyBmb3IgdGhlIGRpc2N1c3Npb24gb2YgdGhlIHByb3Bvc2VkIElPVE9QUyBXRy4NCj4g
DQo+IFRoaXMgV0cgd2lsbCBiZSBmb3IgdGhlIGRpc2N1c3Npb24gb2Ygb3BlcmF0aW9uYWwgaXNz
dWVzDQo+IHJlbGF0ZWQgdG8gSW50ZXJuZXQgb2YgVGhpbmdzIChJb1QpIGRldmljZXMgYW5kIHRo
ZSBwdWJsaWNhdGlvbiBhbmQNCj4gc3RhbmRhcmRpemF0aW9uIG9mIGRvY3VtZW50cyB0aGF0IHJl
bGF0ZSB0byBtYW5hZ2VtZW50IG9mIElvVCBkZXZpY2VzLA0KPiBpbiBwYXJ0aWN1bGFyIHJlbGF0
ZWQgdG8gZGV2aWNlIG9uYm9hcmRpbmcgYW5kIGxpZmVjeWNsZSBtYW5hZ2VtZW50Lg0KPiANCj4g
TGluayB0byBwcm9wb3NlZCBXRzogaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy93Zy9pb3Rv
cHMvYWJvdXQvDQo+IA0KPiBGb3IgYWRkaXRpb25hbCBpbmZvcm1hdGlvbiwgcGxlYXNlIGNvbnRh
Y3QgdGhlIGxpc3QgYWRtaW5pc3RyYXRvcnMuDQo=


From nobody Fri Oct 23 14:20:50 2020
Return-Path: <agenda@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B06893A151C; Fri, 23 Oct 2020 14:16:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <anima-chairs@ietf.org>, <lflynn@amsl.com>
Cc: anima@ietf.org, rwilton@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160348779569.5087.13476473408435195105@ietfa.amsl.com>
Date: Fri, 23 Oct 2020 14:16:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0KJL2UoDjuPmmF4bErihYZhJA4k>
Subject: [Anima] anima - Requested session has been scheduled for IETF 109
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 21:16:38 -0000

Dear Liz Flynn,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    anima Session 1 (1:00 requested)
    Friday, 20 November 2020, Session II 1430-1530
    Room Name: Room 3 size: 503
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/109/sessions/anima.ics

Request Information:


---------------------------------------------------------
Working Group Name: Autonomic Networking Integrated Model and Approach
Area Name: Operations and Management Area
Session Requester: Liz Flynn


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 60
Conflicts to Avoid: 
 Chair Conflict: bier pim mboned 6man 6lo 6tisch ace
 Technology Overlap: emu netconf homenet roll
 Key Participant Conflict: nmrg panrg dinrg opsarea intarea saag cfrg detnet





People who must be present:
  Toerless T. Eckert
  Sheng Jiang
  Robert Wilton

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Sun Oct 25 11:40:01 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322B23A1123 for <anima@ietfa.amsl.com>; Sun, 25 Oct 2020 11:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYfS3LMHQ_51 for <anima@ietfa.amsl.com>; Sun, 25 Oct 2020 11:39:57 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 6750E3A1121 for <anima@ietf.org>; Sun, 25 Oct 2020 11:39:57 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id o9so3597559plx.10 for <anima@ietf.org>; Sun, 25 Oct 2020 11:39:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=xESpR+klJs46d6JXM5+tll0jDBrZl7pdTeL2ZyWRSEw=; b=N4sh7yofbcyD2Gv8A9d2KRjXmiOSG1CsMlMEzG6I0EOLgEMzJ2ACepGOLQXMZD+cTf 3srMjkPlvMYHsmPz2tV/k4xf0eXfI8cptw0E+FNWbBfLfiYOQimutZ7BnemFY3C1hcCe fB+B9QMaBT3+/Npaa5JN+op7+4WzUDyiTyAW5jxKbEdLCWcT2diISxYOJu+XifaLNK2g dbwj0eZkS5yRtMeSSMG5MP2RUAZjn0gtheFaofWMR/7Xo+Ka9R+d3NeI1y6fMZeGRdrd 9l8jXCedOTU14q7wXlqVdSv7MoRdXZ9zHCcghnK8aHBMD6p8Zc+rw3XRSTph9dn1D2Ss Jmug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xESpR+klJs46d6JXM5+tll0jDBrZl7pdTeL2ZyWRSEw=; b=LCKr9ZKz2w129Y7eiaOI3B5RO/dwlFPxT1qSQQRTtiInRtQCTObj6skYioFH4jNRea EFovicJORee8YlefOUjpLh2jBXzP2RdzGrq516oBNQnk2DdQLs40z4LWaz672OyJIPra UIMaPnazYOwYoWDKeisk0IeCRdn9lT+F+s72lToP1Csp6B+9CJK0JUJQ4xyUDt0xQr03 WCkR8yCrOME7L6LWpkuiwGha//XV8dCnJg127qUhdXVxzVvIXEpGXT2LBlUySBJHazny 9QNui1O+6qix17XcxgcZwG+fRbau5j95mkmm9ve0giLHiB8GWpMV68lB3gqcg6jcesu4 hqQw==
X-Gm-Message-State: AOAM5304hsEsGYq6RUJerocpat/lbX281zVtXcefd/ivEaRiCPmj81lJ QWF9ZetSd8bPUp0nUF3Ytm0=
X-Google-Smtp-Source: ABdhPJzyS2Md/CpdIGoAdiEDR/llr//Z54w01yM9650ID7S8Owj0Ps5ZscZCUsnbbaMpiH8Pv3ZI0A==
X-Received: by 2002:a17:90b:1085:: with SMTP id gj5mr13515285pjb.30.1603651196999;  Sun, 25 Oct 2020 11:39:56 -0700 (PDT)
Received: from [10.2.2.3] ([103.23.18.158]) by smtp.gmail.com with ESMTPSA id u8sm8889155pfk.79.2020.10.25.11.39.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Oct 2020 11:39:55 -0700 (PDT)
References: <5f954608.1c69fb81.6337f.9df2SMTPIN_ADDED_MISSING@mx.google.com>
To: Anima WG <anima@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Forwarded-Message-Id: <5f954608.1c69fb81.6337f.9df2SMTPIN_ADDED_MISSING@mx.google.com>
Message-ID: <c8dde31e-f509-99b6-9e25-970d792df182@gmail.com>
Date: Mon, 26 Oct 2020 07:39:51 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <5f954608.1c69fb81.6337f.9df2SMTPIN_ADDED_MISSING@mx.google.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/oYRyvS8KrGxMgL-rpLtp-yyhm4k>
Subject: [Anima] A reminder of why we need ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 18:39:59 -0000

Hi ANIMA,

I think the document below is a timely reminder of why we *need* truly autonomic networks that are not subject to human misconfiguration errors. Start reading at "Root Cause and Event Summary".

   Brian

-------- Forwarded Message --------
Subject: how to misconfigurer ospf and take out your cellullar net
Date: Sun, 25 Oct 2020 09:31:46 +0000
From: jon.crowcroft@cl.cam.ac.uk

https://docs.fcc.gov/public/attachments/DOC-367699A1.docx


jon 



From nobody Tue Oct 27 06:47:13 2020
Return-Path: <Artur.Hecker@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB2353A0C36; Tue, 27 Oct 2020 06:47:11 -0700 (PDT)
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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 yQYYMf-jrgCt; Tue, 27 Oct 2020 06:47:09 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 7F7213A0AC7; Tue, 27 Oct 2020 06:47:09 -0700 (PDT)
Received: from lhreml714-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id C3699DF2C5E56B7B2D96; Tue, 27 Oct 2020 13:47:07 +0000 (GMT)
Received: from fraeml740-chm.china.huawei.com (10.206.15.221) by lhreml714-chm.china.huawei.com (10.201.108.65) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 27 Oct 2020 13:47:07 +0000
Received: from fraeml735-chm.china.huawei.com (10.206.15.216) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 27 Oct 2020 14:47:07 +0100
Received: from fraeml735-chm.china.huawei.com ([10.206.15.216]) by fraeml735-chm.china.huawei.com ([10.206.15.216]) with mapi id 15.01.1913.007;  Tue, 27 Oct 2020 14:47:07 +0100
From: Artur Hecker <Artur.Hecker@huawei.com>
To: Anima WG <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
Thread-Index: AQHWouDjOTp6W7NDGEOJkp1bSw2VlamriTqQ
Date: Tue, 27 Oct 2020 13:47:06 +0000
Message-ID: <9d59ca784eff480abef690edd22ae9a9@huawei.com>
References: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.98.57]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ofaX1KPCPlQg8hBKu30JZwuyA4I>
Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 13:47:12 -0000

Hi


I support the adoption of this work. We already discussed the advantages of=
 this type of document several times.


Best regards
Artur

> -----Original Message-----
> From: Anima <anima-bounces@ietf.org> On Behalf Of Toerless Eckert
> Sent: Thursday, October 15, 2020 12:37 PM
> To: Anima WG <anima@ietf.org>
> Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>
> Subject: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-0=
9,
> ends October 29th 2020
>=20
> Dear ANIMA WG
>=20
> This message starts a two-week adoption call, ending on October 29th, 202=
0.
>=20
> draft-carpenter-anima-asa-guidelines-09 has been progressed by the
> authors with help of the WG for a long while and the WG showed good
> interest. It was last presented at IETF108 and had no opposition. The dra=
ft is
> now clearly in scope of ANIMA charter 2 that was adopted around IETF106.
> The authors asked for adoption of the document at IETF108.
>=20
> We therefore are asking the ANIMA working group for adoption of the
> following work:
>=20
> Title:    Guidelines for Autonomic Service Agents
> Name:     draft-carpenter-anima-asa-guidelines-09
> Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
> URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-
> guidelines/
>=20
> This document is intended to become an informational ANIMA WG
> document.
>=20
> Please express your support or rejection.
> If you think this document should _not_ be adopted, please also explicitl=
y
> indicate the reasons.
>=20
> Regards,
>=20
> Toerless
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Tue Oct 27 06:49:14 2020
Return-Path: <Artur.Hecker@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3663A0AD5 for <anima@ietfa.amsl.com>; Tue, 27 Oct 2020 06:49:12 -0700 (PDT)
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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 pI2217TwDG1k for <anima@ietfa.amsl.com>; Tue, 27 Oct 2020 06:49:10 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 AA8DE3A0AD7 for <anima@ietf.org>; Tue, 27 Oct 2020 06:49:10 -0700 (PDT)
Received: from lhreml730-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 62DAB775E516E8860076 for <anima@ietf.org>; Tue, 27 Oct 2020 13:49:09 +0000 (GMT)
Received: from fraeml735-chm.china.huawei.com (10.206.15.216) by lhreml730-chm.china.huawei.com (10.201.108.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 27 Oct 2020 13:49:09 +0000
Received: from fraeml735-chm.china.huawei.com (10.206.15.216) by fraeml735-chm.china.huawei.com (10.206.15.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 27 Oct 2020 14:49:08 +0100
Received: from fraeml735-chm.china.huawei.com ([10.206.15.216]) by fraeml735-chm.china.huawei.com ([10.206.15.216]) with mapi id 15.01.1913.007;  Tue, 27 Oct 2020 14:49:08 +0100
From: Artur Hecker <Artur.Hecker@huawei.com>
To: Anima WG <anima@ietf.org>
Thread-Topic: [Anima] A reminder of why we need ANIMA
Thread-Index: AQHWqv5UWJP6R1/KFEmmp5ysZkmVEKmrdsoA
Date: Tue, 27 Oct 2020 13:49:08 +0000
Message-ID: <0bc8be5831844875bf500d7002b69447@huawei.com>
References: <5f954608.1c69fb81.6337f.9df2SMTPIN_ADDED_MISSING@mx.google.com> <c8dde31e-f509-99b6-9e25-970d792df182@gmail.com>
In-Reply-To: <c8dde31e-f509-99b6-9e25-970d792df182@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.98.57]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IhxgDiy9xarZvqsVWuSx0TRVFsc>
Subject: Re: [Anima] A reminder of why we need ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 13:49:13 -0000

QnJpYW4sIGFsbA0KDQoNCkdyZWF0IHJlZmVyZW5jZSwgdGhhbmtzIGZvciBzaGFyaW5nIQ0KDQpR
dW90ZTogImVuZ2luZWVycyBhbG1vc3QgaW1tZWRpYXRlbHkgcmVjb2duaXplZCB0aGF0IHRoZXkg
aGFkIG1pc2RpYWdub3NlZCB0aGUgcHJvYmxlbS4gIEhvd2V2ZXIsIHRoZXkgd2VyZSB1bmFibGUg
dG8gcmVzb2x2ZSB0aGUgaXNzdWUgYnkgcmVzdG9yaW5nIHRoZSBsaW5rLCBiZWNhdXNlIHRoZSBu
ZXR3b3JrIG1hbmFnZW1lbnQgdG9vbHMgcmVxdWlyZWQgdG8gZG8gc28gcmVtb3RlbHkgcmVsaWVk
IG9uIHRoZSBzYW1lIHBhdGhzIHRoZXkgaGFkIGp1c3QgZGlzYWJsZWTigJ0uDQoNClRoaXMgaXMg
d2h5IHdlIG5lZWQgYW4gYWRhcHRpdmUsIHZpcnR1YWxseSBpbi1iYW5kIGNvbnRyb2wgcGxhbmUu
IFByb2dyYW1tYWJsZSwgc29mdHdhcmUtZHJpdmVuIG5ldHdvcmtzIHdpbGwgc3Ryb25nbHkgYW1w
bGlmeSB0aGlzIGVmZmVjdC4gVG8gbWUsIG91dC1vZi1iYW5kIGNvbnRyb2wgcGxhbmUgaXMgYSBt
aXNjb25jZXB0aW9uIG9mIHZpcnR1YWxpemF0aW9uIPCfmIkgKGhhdmUgMiBuZXR3b3JrcywgdXNl
IDEpLCBhbmQgaXQgbXVzdCBzdGlsbCBiZSBhZGFwdGl2ZSAmIG9tbmlwcmVzZW50Lg0KDQpBbHNv
IG5pY2U6IHJlY29tbWVuZGF0aW9ucyBvZiB0aGUgQnVyZWF1IHRvIHRoZSBvcGVyYXRvcnMuIA0K
DQoNCkFydHVyDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbmlt
YSA8YW5pbWEtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIEJyaWFuIEUgQ2FycGVudGVy
DQo+IFNlbnQ6IFN1bmRheSwgT2N0b2JlciAyNSwgMjAyMCA3OjQwIFBNDQo+IFRvOiBBbmltYSBX
RyA8YW5pbWFAaWV0Zi5vcmc+DQo+IFN1YmplY3Q6IFtBbmltYV0gQSByZW1pbmRlciBvZiB3aHkg
d2UgbmVlZCBBTklNQQ0KPiANCj4gSGkgQU5JTUEsDQo+IA0KPiBJIHRoaW5rIHRoZSBkb2N1bWVu
dCBiZWxvdyBpcyBhIHRpbWVseSByZW1pbmRlciBvZiB3aHkgd2UgKm5lZWQqIHRydWx5DQo+IGF1
dG9ub21pYyBuZXR3b3JrcyB0aGF0IGFyZSBub3Qgc3ViamVjdCB0byBodW1hbiBtaXNjb25maWd1
cmF0aW9uIGVycm9ycy4NCj4gU3RhcnQgcmVhZGluZyBhdCAiUm9vdCBDYXVzZSBhbmQgRXZlbnQg
U3VtbWFyeSIuDQo+IA0KPiAgICBCcmlhbg0KPiANCj4gLS0tLS0tLS0gRm9yd2FyZGVkIE1lc3Nh
Z2UgLS0tLS0tLS0NCj4gU3ViamVjdDogaG93IHRvIG1pc2NvbmZpZ3VyZXIgb3NwZiBhbmQgdGFr
ZSBvdXQgeW91ciBjZWxsdWxsYXIgbmV0DQo+IERhdGU6IFN1biwgMjUgT2N0IDIwMjAgMDk6MzE6
NDYgKzAwMDANCj4gRnJvbTogam9uLmNyb3djcm9mdEBjbC5jYW0uYWMudWsNCj4gDQo+IGh0dHBz
Oi8vZG9jcy5mY2MuZ292L3B1YmxpYy9hdHRhY2htZW50cy9ET0MtMzY3Njk5QTEuZG9jeA0KPiAN
Cj4gDQo+IGpvbg0KPiANCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+IEFuaW1hIG1haWxpbmcgbGlzdA0KPiBBbmltYUBpZXRmLm9yZw0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hDQo=


From nobody Tue Oct 27 10:25:51 2020
Return-Path: <noreply@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB593A1264; Tue, 27 Oct 2020 10:25:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joseph Salowey via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: last-call@ietf.org, anima@ietf.org, draft-ietf-anima-grasp-api.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160381954432.30121.9559007698502161410@ietfa.amsl.com>
Reply-To: Joseph Salowey <joe@salowey.net>
Date: Tue, 27 Oct 2020 10:25:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/WrRLNDBuZjwSwVJUAswGxE26KRY>
Subject: [Anima] Secdir last call review of draft-ietf-anima-grasp-api-07
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 17:25:44 -0000

Reviewer: Joseph Salowey
Review result: Has Issues

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

The summary of the review is Has issues.  The document does needs a bit more
discussion of the security implications.

1. Authorization

In the security considerations section the document says that authorization is
left for future work.  I would expect that the section should at least describe
what the implications of no authorizations are. What risks are not being
mitigated?   What modes of operations should not be used?   In general leaving
security items out suggests that the work is not ready for wide deployment. 
Perhaps this is OK because the work is informational, but the document should
probably say this.

2. Authentication

Section 2.3.1.4 discusses the ASA_locator.  How is is the entity accessed by
the locator authenticated?  How does the caller of the API know they are
talking to the right entity?  I don't see any discussion of this in this
document and there is very little in draft-ietf-anima-grasp-15 on this.    Is
there a section in one of these documents I should be looking for?

3. ASA_Nonce

The ASA nonce is described as a security mechanism.  It is only 4 bytes long. 
This seems short, making the ASA_Nonce vulnerable to collisions.  Why is this
not a problem?

How long is the ASA nonce supposed to be valid?  How often does registration
happen?

4. Session Nonce

Are there security implications of revealing the session nonce to the caller as
suggested in section 2.3.1.7?  Could it allow for the ASA to bypass
authorization if it knows this value?   Perhaps forming the nonce from the
underlying session ID is not the best guidance?  Also it seems the underlying
protocol session ID is only 4 bytes and collisions are likely and may be a
problem for the protocol.

5. Error Codes

In general, the list of API codes in the appendix is not described in the API. 
It seems they should be.  Some of the error codes seem related to
authorization, which is out of scope?

It seems that some of the error code could lead to disclosure of information,
for example:

notYourASA       7 "ASA registered but not by you"  might reveal a valid nonce
from an invalid nonce

6. Denial of service

are there protections in the underlying protocol for denial of service with
respect to Flood(), Synchronize() or any other method?




From nobody Tue Oct 27 17:20:33 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4C63A0994 for <anima@ietfa.amsl.com>; Tue, 27 Oct 2020 17:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 zNsywTTHXv1e for <anima@ietfa.amsl.com>; Tue, 27 Oct 2020 17:20:28 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83D583A09C9 for <anima@ietf.org>; Tue, 27 Oct 2020 17:20:28 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DC23F54843F; Wed, 28 Oct 2020 01:20:22 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D3229440059; Wed, 28 Oct 2020 01:20:22 +0100 (CET)
Date: Wed, 28 Oct 2020 01:20:22 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Artur Hecker <Artur.Hecker@huawei.com>
Cc: Anima WG <anima@ietf.org>
Message-ID: <20201028002022.GA18251@faui48f.informatik.uni-erlangen.de>
References: <5f954608.1c69fb81.6337f.9df2SMTPIN_ADDED_MISSING@mx.google.com> <c8dde31e-f509-99b6-9e25-970d792df182@gmail.com> <0bc8be5831844875bf500d7002b69447@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0bc8be5831844875bf500d7002b69447@huawei.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/goTM-yOu0IlOGPYARwn50NJn69k>
Subject: Re: [Anima] A reminder of why we need ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 00:20:32 -0000

Gee, christmas already in October ?

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/905f21becaa50760419c3ba28d8df4bb82e7a911/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt&url2=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/64d5f691f350984383eb573de01afdddaefe33ed/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt

Thanks Brian, Artur. That was the missing piece of marketing collateral for the RFC.

Cheers
    Toerless

On Tue, Oct 27, 2020 at 01:49:08PM +0000, Artur Hecker wrote:
> Brian, all
> 
> 
> Great reference, thanks for sharing!
> 
> Quote: "engineers almost immediately recognized that they had misdiagnosed the problem.  However, they were unable to resolve the issue by restoring the link, because the network management tools required to do so remotely relied on the same paths they had just disabled???.
> 
> This is why we need an adaptive, virtually in-band control plane. Programmable, software-driven networks will strongly amplify this effect. To me, out-of-band control plane is a misconception of virtualization ???? (have 2 networks, use 1), and it must still be adaptive & omnipresent.
> 
> Also nice: recommendations of the Bureau to the operators. 
> 
> 
> Artur
> 
> 
> > -----Original Message-----
> > From: Anima <anima-bounces@ietf.org> On Behalf Of Brian E Carpenter
> > Sent: Sunday, October 25, 2020 7:40 PM
> > To: Anima WG <anima@ietf.org>
> > Subject: [Anima] A reminder of why we need ANIMA
> > 
> > Hi ANIMA,
> > 
> > I think the document below is a timely reminder of why we *need* truly
> > autonomic networks that are not subject to human misconfiguration errors.
> > Start reading at "Root Cause and Event Summary".
> > 
> >    Brian
> > 
> > -------- Forwarded Message --------
> > Subject: how to misconfigurer ospf and take out your cellullar net
> > Date: Sun, 25 Oct 2020 09:31:46 +0000
> > From: jon.crowcroft@cl.cam.ac.uk
> > 
> > https://docs.fcc.gov/public/attachments/DOC-367699A1.docx
> > 
> > 
> > jon
> > 
> > 
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima

-- 
---
tte@cs.fau.de


From nobody Tue Oct 27 18:59:12 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7735D3A09EA; Tue, 27 Oct 2020 18:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level: 
X-Spam-Status: No, score=-2.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egVs9s2_OCG1; Tue, 27 Oct 2020 18:59:01 -0700 (PDT)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 918173A09EB; Tue, 27 Oct 2020 18:58:58 -0700 (PDT)
Received: by mail-pj1-x1035.google.com with SMTP id az3so1750153pjb.4; Tue, 27 Oct 2020 18:58:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=TKQPg2jna8LEXY2S9D008aZgL7XQIZFhJpLkfmjYj74=; b=ogfoBXgt9hbC37ORJJA1IXgzQTdNhEiplbcNC3xPPn1SuOU9dd/esqF5kKn5wb2uC6 K6aoYu2cl7cabVaGAfmUo+d841sIAAOkrRZCPAjfO8g9R2a4BBlGoOLJ+ElbkrzUf2wv vBvN6dDXU603ZftmvYsaJa/nVZYFnBbIhc+6xpgDRr5EtcTgHE+BUMzQZO5JODwaMqVI zAnCM0TGbnhQ66ofW79+FZa8WbSQlF3v6CfNs/YHxvBdzlO9bN2i4/cPi1WvJxr75hcw ZKbvaUVD4077vue+icQIlFvLvLDrwe16ROq08hDIGZhG8PK/PR9+FGHOmEnrK+SpiTgb Wo9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=TKQPg2jna8LEXY2S9D008aZgL7XQIZFhJpLkfmjYj74=; b=Or089ieiLm9rgDr34bl7MCnrmpYHN5L9jfkhnUD+2xP5tUlWxdmec3RcmhZ1Nz0k+X OLoiHoGfrsIIoKAfbjC2kBXOvvS+2sifVHL1SfHawPsh+QowPhQLex+vWbe4EqxUGsws TXxggzO3tg8jASDwyr7bYKbkmAfJotZ1BdA0CX9h8zXVoxPw4M7SdKXivVyJNAPlFML8 /VfycWZvJc08B/ZPXevmX6mxiLoJNLkX0tFGnY5wFsyz3uxn3S4ULKhEmNOKec+SkNIe zTXAqQ+JRpmh0CLiX0sHwcm5mIN1AALjnzWjsTZD7kHGEYIWkGbRF6MeOc9TqnNPHQcX ePjg==
X-Gm-Message-State: AOAM531nr42xb0xew1XPVBbjvrejNfSy/9VLLdhpH1VQu95xsA/yKZiH dk57yiTPm1GnUYgKJa5tshBo44LI7Vc=
X-Google-Smtp-Source: ABdhPJzlG3bVOmEP7oa7FQtX5fzNZokDx+rGzUoVK5CBAAisH8A1wm8LyKsP26Hob0Bqdvt76JTxag==
X-Received: by 2002:a17:902:9347:b029:d3:7c08:86c6 with SMTP id g7-20020a1709029347b02900d37c0886c6mr5056474plp.84.1603850337222;  Tue, 27 Oct 2020 18:58:57 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id mn15sm2548429pjb.21.2020.10.27.18.58.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Oct 2020 18:58:55 -0700 (PDT)
To: Joseph Salowey <joe@salowey.net>, secdir@ietf.org
Cc: last-call@ietf.org, anima@ietf.org, draft-ietf-anima-grasp-api.all@ietf.org
References: <160381954432.30121.9559007698502161410@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b132bb6d-4a5b-5388-6f0d-0f94c71bc51b@gmail.com>
Date: Wed, 28 Oct 2020 14:58:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <160381954432.30121.9559007698502161410@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/YS8vk43BeYGiFps9OaGExnYx4xc>
Subject: Re: [Anima] Secdir last call review of draft-ietf-anima-grasp-api-07
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 01:59:04 -0000

Hi Joseph,

Thanks for the review. Comments in line...

On 28-Oct-20 06:25, Joseph Salowey via Datatracker wrote:
> Reviewer: Joseph Salowey
> Review result: Has Issues
> 
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
> 
> The summary of the review is Has issues.  The document does needs a bit more
> discussion of the security implications.
> 
> 1. Authorization
> 
> In the security considerations section the document says that authorization is
> left for future work.  I would expect that the section should at least describe
> what the implications of no authorizations are. 

This isn't really an issue for the API itself, but for the underlying protocol
and for the ANIMA ecosystem. It's an issue that the WG explicitly deferred
(and it's now a chartered work item). Let me quote here what the GRASP spec
says in its security considerations:

>>    - Authorization and Roles
>> 
>>       The GRASP protocol is agnostic about the roles and capabilities of
>>       individual ASAs and about which objectives a particular ASA is
>>       authorized to support.  An implementation might support
>>       precautions such as allowing only one ASA in a given node to
>>       modify a given objective, but this may not be appropriate in all
>>       cases.  For example, it might be operationally useful to allow an
>>       old and a new version of the same ASA to run simultaneously during
>>       an overlap period.  These questions are out of scope for the
>>       present specification.

and what draft-carpenter-anima-asa-guidelines says:

>> Authorization of ASAs is a subject for future study. At present, ASAs are trusted by virtue of being installed on a node that has successfully joined the ACP. In the general case, a node may have mutltiple roles and a role may use multiple ASAs, each using multiple GRASP objectives. Additional mechanisms for the authorization of nodes and ASAs to manipulate specific GRASP objectives could be designed.

That draft is on the verge of WG adoption. The point is that the current
trust model is that we trust any node that has successfully joined the ACP,
and therefore we trust any ASA in such a node. We should state that clearly
in the text.

IMHO it would be out of scope for the API to say more but we should add a
reference to the GRASP Security Considerations.

> What risks are not being
> mitigated?   What modes of operations should not be used? 

Those are good questions for the WG to look at.

> In general leaving
> security items out suggests that the work is not ready for wide deployment. 
> Perhaps this is OK because the work is informational, but the document should
> probably say this.


Personally I don't think we have left a hole here, because there's a well-defined
trust boundary, but we should indeed state that as well as citing the GRASP spec's
security considerations.

> 
> 2. Authentication
> 
> Section 2.3.1.4 discusses the ASA_locator.  How is is the entity accessed by
> the locator authenticated?  How does the caller of the API know they are
> talking to the right entity?  I don't see any discussion of this in this
> document and there is very little in draft-ietf-anima-grasp-15 on this.    Is
> there a section in one of these documents I should be looking for?

No, you're not missing anything. The trust boundary is the ACP, and that takes
us back to the previous point. If we do decide that we need a fine-grained
trust model inside the ACP, we'll presumably need to extend GRASP itself
to add some form of authentication option beyond what GRASP over TLS can
provide. 

> 
> 3. ASA_Nonce
> 
> The ASA nonce is described as a security mechanism.  It is only 4 bytes long. 
> This seems short, making the ASA_Nonce vulnerable to collisions.  Why is this
> not a problem?

This isn't used on the wire, just locally within the GRASP instance,
so collisions can be excluded.

> How long is the ASA nonce supposed to be valid?  How often does registration
> happen?

At the moment, there is no sensible answer to those questions. When we develop
the authorization model, we'd definitely have to answer those questions and maybe
the nonce would have to be replaced by a crypto object.

> 
> 4. Session Nonce
> 
> Are there security implications of revealing the session nonce to the caller as
> suggested in section 2.3.1.7?  Could it allow for the ASA to bypass
> authorization if it knows this value?   Perhaps forming the nonce from the
> underlying session ID is not the best guidance?  Also it seems the underlying
> protocol session ID is only 4 bytes and collisions are likely and may be a
> problem for the protocol.

No, the collision risk is avoided because the session nonce includes the
ACP IPv6 address of the session originator. We should explain that
more clearly.

> 
> 5. Error Codes
> 
> In general, the list of API codes in the appendix is not described in the API. 
> It seems they should be.  Some of the error codes seem related to
> authorization, which is out of scope?

Our hope was the the WG could move faster on that topic, but the
incredible delays on BRSKI and the ACP made that impossible.
Our idea is certainly that register_asa() and register_objective()
should include authorization in the longer term.

> It seems that some of the error code could lead to disclosure of information,
> for example:
> 
> notYourASA       7 "ASA registered but not by you"  might reveal a valid nonce
> from an invalid nonce

Hmm... I don't think so. Let me glance at the code...

The only place where I found that error code useful was in deregister_asa()
and that doesn't return anything else. It could be used in an exhaustive
search attack to deregister an ASA, but in the current trust model that
doesn't seem like a significant risk. 

> 
> 6. Denial of service
> 
> are there protections in the underlying protocol for denial of service with
> respect to Flood(), Synchronize() or any other method?

There are recommendations about rate throttling for relaying GRASP Flood and
Discover multicasts, which should confine any multicast abuse to a single
link-layer segment. That's one good reason for using link-layer multicast only.
We also have recommendations for exponential backoff in the GRASP spec, but
of course a malicious sender could ignore those. In any case we can put a
specific pointer to that subsection of the GRASP Security Considerations.

DoS against the Negotiate or Synchronize parts of GRASP seems to be like
any other client/server protocol. I'm not sure what we can say in the
API spec about that. In my implementation (which is not intended to be
production quality) I've simply put finite queues for all the request
handlers, with silent discard if the queue overflows.

We'll collate updates to all reviews after the LC expires.

Thanks again
    Brian


 


From nobody Wed Oct 28 08:02:47 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC333A0A5F for <anima@ietfa.amsl.com>; Wed, 28 Oct 2020 08:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.867
X-Spam-Level: 
X-Spam-Status: No, score=-0.867 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LOTS_OF_MONEY=0.001, MILLION_USD=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 VJ6qmrjj_kLB for <anima@ietfa.amsl.com>; Wed, 28 Oct 2020 08:02:44 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78EEF3A0BFD for <anima@ietf.org>; Wed, 28 Oct 2020 08:02:18 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id E3C99548054; Wed, 28 Oct 2020 16:02:12 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id DB846440059; Wed, 28 Oct 2020 16:02:12 +0100 (CET)
Date: Wed, 28 Oct 2020 16:02:12 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Artur Hecker <Artur.Hecker@huawei.com>
Cc: Anima WG <anima@ietf.org>
Message-ID: <20201028150212.GA20823@faui48f.informatik.uni-erlangen.de>
References: <5f954608.1c69fb81.6337f.9df2SMTPIN_ADDED_MISSING@mx.google.com> <c8dde31e-f509-99b6-9e25-970d792df182@gmail.com> <0bc8be5831844875bf500d7002b69447@huawei.com> <20201028002022.GA18251@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201028002022.GA18251@faui48f.informatik.uni-erlangen.de>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/QD6dMeRpwL7fxtTDajv8JvBpowg>
Subject: Re: [Anima] A reminder of why we need ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 15:02:46 -0000

Some followup ponderings:

I was not even aware that the FCC publishes these fine reports. Very nice
as a tax payer (and user of 911 services) to see this level of transparency
for live & death impacting service oversight. I wonder if/how this is
handled in other countries.

These things happen regularily and hefty fines have to be paid. From quickly
googling, the last one i can find from 2015 was 17.5 million USD. This
is because the 911 service is affected. If it was not for FCC, these things
would not be publically known, because no operator likes to see things like
this published.

Having these events be reported on IP networks is i would think also a rather
new occurrance. I have not tracked and analyzed history, but 20 years ago,
i would not have expected the 911 service to run over an IP network. And back
then the TDMA/ATM networks always had some out-of-band network access,
even if it was modems over leased lines because there was not even in-band
management capabilities on a lot of (non-IP) equipment.

So, while pointing to a single incident may be anecdotal, i think it might
actually help sell the ACP, because these recurring fines add up to real
money, so improvement of network operations to provide even more than
five 9 of reliability should certainly be in everybody's interest for live
& death services, including the operators who could avoid fines then.

Cheers
    Toerless


On Wed, Oct 28, 2020 at 01:20:22AM +0100, Toerless Eckert wrote:
> Gee, christmas already in October ?
> 
> http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/905f21becaa50760419c3ba28d8df4bb82e7a911/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt&url2=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/64d5f691f350984383eb573de01afdddaefe33ed/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt
> 
> Thanks Brian, Artur. That was the missing piece of marketing collateral for the RFC.
> 
> Cheers
>     Toerless
> 
> On Tue, Oct 27, 2020 at 01:49:08PM +0000, Artur Hecker wrote:
> > Brian, all
> > 
> > 
> > Great reference, thanks for sharing!
> > 
> > Quote: "engineers almost immediately recognized that they had misdiagnosed the problem.  However, they were unable to resolve the issue by restoring the link, because the network management tools required to do so remotely relied on the same paths they had just disabled???.
> > 
> > This is why we need an adaptive, virtually in-band control plane. Programmable, software-driven networks will strongly amplify this effect. To me, out-of-band control plane is a misconception of virtualization ???? (have 2 networks, use 1), and it must still be adaptive & omnipresent.
> > 
> > Also nice: recommendations of the Bureau to the operators. 
> > 
> > 
> > Artur
> > 
> > 
> > > -----Original Message-----
> > > From: Anima <anima-bounces@ietf.org> On Behalf Of Brian E Carpenter
> > > Sent: Sunday, October 25, 2020 7:40 PM
> > > To: Anima WG <anima@ietf.org>
> > > Subject: [Anima] A reminder of why we need ANIMA
> > > 
> > > Hi ANIMA,
> > > 
> > > I think the document below is a timely reminder of why we *need* truly
> > > autonomic networks that are not subject to human misconfiguration errors.
> > > Start reading at "Root Cause and Event Summary".
> > > 
> > >    Brian
> > > 
> > > -------- Forwarded Message --------
> > > Subject: how to misconfigurer ospf and take out your cellullar net
> > > Date: Sun, 25 Oct 2020 09:31:46 +0000
> > > From: jon.crowcroft@cl.cam.ac.uk
> > > 
> > > https://docs.fcc.gov/public/attachments/DOC-367699A1.docx
> > > 
> > > 
> > > jon
> > > 
> > > 
> > > _______________________________________________
> > > Anima mailing list
> > > Anima@ietf.org
> > > https://www.ietf.org/mailman/listinfo/anima
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima
> 
> -- 
> ---
> tte@cs.fau.de
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima

-- 
---
tte@cs.fau.de


From nobody Wed Oct 28 20:35:37 2020
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81CBA3A0985; Wed, 28 Oct 2020 20:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level: 
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8sehSeZc-U4; Wed, 28 Oct 2020 20:35:35 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 08FBF3A097F; Wed, 28 Oct 2020 20:35:34 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id 15so1201378pgd.12; Wed, 28 Oct 2020 20:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=AyRA7ltn6K3O7RJUjJcTbb+qRg91JemkuMRJXYormws=; b=C3IVnvRt50B4y8nt1hV0X2inkne/TBZdl43u1lwL/PrX3LYRFhjP1O/qoRgX0OPvjG O/pGT85voraSuHjG/a3VFBgiJdv2RwBmrM8t3c9JT1HomdtsZ8AVCCuj5H4eBXZKRT60 zXpl9FlkLIBHt4LYDJQ+acwN3SCyZfVP3zt5vwZ6JPGguAZAvxLPNS5kBuV6g842BmN+ jVixipl+PDm0y1bAH2RAjUgqPhqnopB1kBX7B4DbflZ8i6GoKyLPJ+OBZvAstHHFpzKx 2s1gI3zjSTJyNoNnllSiT+3q3sLj7buP+9lNQnrLJIo9B5uYDg05/eiV89LWulkc6dBp fwPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=AyRA7ltn6K3O7RJUjJcTbb+qRg91JemkuMRJXYormws=; b=A9cFcZxWTID4b2uliK6PRc3PzbZg7nDYbj6ieVsSSdmS6u0qlft1IkBvXNgx/PesTc EqaJu1PsKAJV91wlz7mX1sxHYk9r/QgS7HQKANDWQTHuRECG2mtNUI8EFk6k17ioSAGA E5M0XhYCRnDPxewa/YmHuNSkZ892HN8GWvbIn5gwGlWIdHAox6DKgdhCOnEb2d+R/LvP /83FWwozelxSUw2JMXFj1HUhTAsnmNmFgY/spGX/PfngpCJYD2yMq1KqB6X3jSeCJQmI pP/WJojegWekBYDFgjnY5sufRhmo6nl8au3q54Q212TudhBHvr76BWxMSCpKNshj1k/m 8sUg==
X-Gm-Message-State: AOAM531fvIKZ2uG/zlo0o3LUMnnSm+xBEVNQ37IXBK3oQCNUxrRBd/fk 26BPqlo1HUwVN1ZWHq9wwgQ=
X-Google-Smtp-Source: ABdhPJwSXpAUOWyCQhwA7EhUiys9n+8dViv7FJ/VfxMua/uByjt2+7PXKoQs+5alj1wgcWPiKqTUig==
X-Received: by 2002:a05:6a00:8c5:b029:142:2501:39e6 with SMTP id s5-20020a056a0008c5b0290142250139e6mr2221358pfu.53.1603942534324;  Wed, 28 Oct 2020 20:35:34 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id i2sm851908pjk.12.2020.10.28.20.35.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Oct 2020 20:35:33 -0700 (PDT)
To: Toerless Eckert <tte@cs.fau.de>, Anima WG <anima@ietf.org>
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20e8ff7e-94b7-2fc9-1e03-5279c57c66cb@gmail.com>
Date: Thu, 29 Oct 2020 16:35:29 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20201015103647.GA32715@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/BUmxRG3_s-eFCc8_wodM3MoiyM8>
Subject: Re: [Anima] Adoption call for draft-carpenter-anima-asa-guidelines-09, ends October 29th 2020
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 03:35:37 -0000

I feel strange saying "yes" to the adoption of a draft I helped to write, but since our AD suggested referring to this document from the GRASP API draft, I really think we need to adopt it and move it forward as soon as possible.

Regards
   Brian Carpenter

On 15-Oct-20 23:36, Toerless Eckert wrote:
> Dear ANIMA WG
> 
> This message starts a two-week adoption call, ending on October 29th, 2020.
> 
> draft-carpenter-anima-asa-guidelines-09 has been progressed by the authors with help of the WG for a long while and the WG showed good interest. It was last presented at IETF108 and had no opposition. The draft is now clearly in scope of ANIMA charter 2 that was adopted around IETF106. The authors asked for adoption of the document at IETF108.
> 
> We therefore are asking the ANIMA working group for adoption of the following work:
> 
> Title:    Guidelines for Autonomic Service Agents
> Name:     draft-carpenter-anima-asa-guidelines-09
> Authors:  B. E. Carpenter, L. Ciavaglia, S. Jiang, P. Peloso
> URL:      https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/
> 
> This document is intended to become an informational ANIMA WG document.
> 
> Please express your support or rejection.
> If you think this document should _not_ be adopted, please also explicitly indicate the reasons.
> 
> Regards,
> 
> Toerless
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> .
> 


From nobody Fri Oct 30 11:40:13 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 082A13A110E; Fri, 30 Oct 2020 11:40:08 -0700 (PDT)
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>
Cc: anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <160408320798.2760.9590324636002996650@ietfa.amsl.com>
Date: Fri, 30 Oct 2020 11:40:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/t7jQ2sV-j4sdbN0ItZtRXOsnRKg>
Subject: [Anima] I-D Action: draft-ietf-anima-autonomic-control-plane-30.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 18:40:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.

        Title           : An Autonomic Control Plane (ACP)
        Authors         : Toerless Eckert
                          Michael H. Behringer
                          Steinthor Bjarnason
	Filename        : draft-ietf-anima-autonomic-control-plane-30.txt
	Pages           : 180
	Date            : 2020-10-30

Abstract:
   Autonomic functions need a control plane to communicate, which
   depends on some addressing and routing.  This Autonomic Control Plane
   should ideally be self-managing, and as independent as possible of
   configuration.  This document defines such a plane and calls it the
   "Autonomic Control Plane", with the primary use as a control plane
   for autonomic functions.  It also serves as a "virtual out-of-band
   channel" for Operations, Administration and Management (OAM)
   communications over a network that provides automatically configured
   hop-by-hop authenticated and encrypted communications via
   automatically configured IPv6 even when the network is not
   configured, or misconfigured.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-anima-autonomic-control-plane-30.html

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-autonomic-control-plane-30


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 Oct 30 12:01:53 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C28F3A1483; Fri, 30 Oct 2020 12:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 pnTJ19QrhSEK; Fri, 30 Oct 2020 12:01:42 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EBBA3A132D; Fri, 30 Oct 2020 12:01:12 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 9C91A54843F; Fri, 30 Oct 2020 20:01:07 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 94D32440059; Fri, 30 Oct 2020 20:01:07 +0100 (CET)
Date: Fri, 30 Oct 2020 20:01:07 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "anima@ietf.org" <anima@ietf.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Message-ID: <20201030190107.GA57054@faui48f.informatik.uni-erlangen.de>
References: <20201001125721.GC34365@faui48f.informatik.uni-erlangen.de> <2765.1602163758@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2765.1602163758@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/tYp_KLsputiy1K7JuUWRkVOpQHo>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 109, online
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 19:01:51 -0000

Thanks, Michael

I'll add the hopefully last update for ACP from myself. max 10 minutes.

So, we still have free time, please bring your interests to the agenda!

Cheers
    Toerless

On Thu, Oct 08, 2020 at 09:29:18AM -0400, Michael Richardson wrote:
> 
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > Name of time slot:
>     > Name of draft(s) (if any, NOT REQUIRED, but usually desired ;-):
>     > Amount of time requested:
>     > Presenter name(s):
> 
> Hi.
> 
> Name of time slot: BRSKI-44 LC-prime summary of activity around rename
> Name of draft(s): draft-ietf-anima-bootstrap-keyinfra
> Amount of time requested: 6 minutes
> Presenter name(s): Michael Richardson
> 
> 
> Name of time slot: BRSKI-cloud use case/applicability
> Name of draft(s): draft-friel-anima-brski-cloud-03
> Amount of time requested: 6 minutes
> Presenter name(s): Michael Richardson, Owen Friel
> 
> 
> Name of time slot: Constrained-Voucher --- overview of changes from design team
> Name of draft(s): draft-ietf-anima-constrained-voucher
> Amount of time requested: 10 minutes
> Presenter name(s): Michael Richardson, Peter van der Stok
> 
> 
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 



-- 
---
tte@cs.fau.de

